The whole life of a job lives in one platform (estimate, commitment, actual, and WIP) so every dollar on the cost ledger traces back to a real document instead of an assumption. Filter by department and location, click any number through to the bills and POs behind it, and keep projections in a forecast that never touches your actuals.
The fastest way to lose trust in a job-cost report is to blend estimates and prorations into the actuals. SitewideOps won't. The Costs ledger is source-document only: actuals come from posted bills and burdened labor, committed cost from purchase orders and subcontracts, inventory from posted issues net of returns. If a dollar is on the ledger, there's a document behind it, and you can open it.
The grid lays out budget, committed, and actual side by side by cost code: starting budget through approved change orders, committed cost net of what's already been billed, and actual to date. The total always ties out, because every cell is arithmetic on real records, not a ratio someone tuned to look right.
Enough detail to manage the job, structured so the totals never drift.
See committed cost from POs and subcontracts alongside actual cost from posted bills and labor, with unbilled committed broken out so nothing hides.
Click any cost code to open the source documents behind the number: the exact bills, POs, subcontracts, issues, and labor that make up that cell.
Filter the ledger by department and location. Anything that can't be attributed to what you filtered on is shown to you, not quietly folded into the wrong code.
Field time hits job cost at burdened labor rates (the same hours that produce certified payroll) so labor cost is real, not a plug.
A separate Forecast view shows cost-to-complete, EAC, and variance. It’s clearly labeled as a projection and kept out of the actuals grid.
Approved change orders roll into the CO and Updated Budget columns, so budget-to-actual reflects the revised contract, not the original bid.
When your controller, your PM, and your bonding company all read the same job-cost report, it has to mean one thing. A ledger that quietly folds in percent-complete or prorated overhead can't be audited: you can't click a number and see why it's that number, so every review turns into a debate about whose figure is right.
Projections still matter for steering the job. They just belong in their own place. The Forecast view is clearly labeled: cost-to-complete is open commitments plus remaining uncommitted budget, EAC is actual plus cost-to-complete, and variance is budget minus EAC. It's the estimate you want when you're managing to the finish, and it never leaks into the actuals that feed WIP.
The same ledger feeds your WIP. Because actuals are source-document-only, cost-to-cost WIP percent-complete is defensible to the penny: the WIP schedule and the job-cost report can't disagree.
See a source-document cost ledger that reconciles, and the forecast that keeps projections in their place.