Budget & transactions
Budgets the spreadsheet cannot corrupt.
Build the budget once, lock it down, and watch transactions reconcile against it as the project runs. Less forensic month-end work to figure out where the framing money went.
What it covers
Schema-enforced line items
The trade, division, cost code, and vendor fields are all validated against project-level lists. Vendor names like "ESJ Plumbing" and "ESJ Plumb" cannot end up on different rows of the same project.
Transactions reconcile against budget
Each transaction posts against a specific budget line, and variance is visible in real time rather than at month-end.
Change orders without tears
A change order updates the relevant budget lines and snapshots the prior version, leaving a full audit trail on the project.
Built-in calculators
Markup, contingency, soft costs, and retainage held are all derived from the budget rather than maintained on a parallel sheet.
How it fits the workflow
- Step 1
Import or build the budget from a template
- Step 2
Lock the baseline before construction begins
- Step 3
Code transactions to budget lines as bills come in
- Step 4
Watch variance live and flag anything outside tolerance
- Step 5
Generate draw packages from current numbers
Related
Draw management
AIA-style draw schedules, lender-ready PDF packages, and e-signed waivers all run through a single workflow.
Lien waivers
Conditional, unconditional, partial, and final waivers are generated from vendor data and tracked through e-signature.
Field operations
Daily logs, inspections, punch list, weather, and photos all run on the phones and tablets your team carries on site.