Ask a field PM what they spent this week and they'll give you a number. Ask the manager and they'll give you a different number — usually higher, because they're including expenses the PM forgot about, or lower, because they haven't received all the receipts yet. Ask both of them to reconcile and you've just created an hour of work on a Friday afternoon that nobody wanted.
The information gap between field and office isn't a people problem. It's an architecture problem. When data entry happens on paper, in texts, or in the PM's camera roll, reconciliation is inevitable. When data flows directly from the field into a shared system the moment it's captured, reconciliation becomes unnecessary.
Two Interfaces, One Data Layer
BLT's architecture is built around a single truth: the PM and the manager should be looking at the same data, always, with no synchronization step required.
When the PM logs an expense on their phone at 2pm, it's visible on the manager's dashboard at 2pm. When the manager approves a purchase request from their desk at 3pm, the PM gets a notification at 3pm. When the manager closes the week and records the wire payment on Friday afternoon, the PM sees the settlement confirmation in the app.
The Mobile Manager Reality
Managers aren't always at their desks. The approval queue, AI alerts, and expense review all work fully on a phone. A purchase request that comes in while the manager is driving can be reviewed and approved from a phone in under a minute. This matters for the PM who's standing in the plumbing supply house waiting for an answer before they fill up a cart.
Communication That Stays in Context
When the manager has a question about a specific expense, they don't text the PM. They flag the expense in BLT and add a comment. The PM gets a notification that links directly to the flagged expense with the comment visible. They respond in the same thread. The conversation lives permanently attached to the financial record — visible in the weekly review, in reports, in the audit log.
No lost texts. No "can you send me that receipt again." No "what was this for?" six weeks later when the auditor asks. The context travels with the data.
What the Weekly Review Looks Like When This Works
In the ideal workflow, the manager's weekly review session is 20–30 minutes: open the review screen, see all submitted expenses grouped by project and phase, review each one (most are approved in one click because the PM tagged them correctly), close the week, record the wire. Done.
This works because the PM has been logging expenses in real time all week, tagging them to projects and phases as they go. The manager isn't doing data entry during the review — they're making decisions on data that was entered when the expense happened, by the person who was there.