The office-side labour cockpit inside the project modal: per-stage labour assignment (crew or sub), hour/unit entries and expenses logged against stages, an approval flow for submitted entries, and a rollup showing revenue, estimated material and labour, actual labour, expenses and materials, and margin.
Also called: log hours · labour cost · job P&L · approve timesheets · expenses on a job
You find out a job is losing money while you can still do something
The panel sets revenue against estimated material and labour, actual labour, expenses and materials, and shows margin and margin percent as the hours come in. Finding out that a build lost money after it handed over is the most expensive report in the business, and it is the one most builders are left with.
Hours are logged once, in the field, and approved in the office
Time and expenses go in against the stage they belong to and arrive as submitted entries the office approves or rejects. Field and office read and write the same rows, so nothing gets keyed a second time off a paper timesheet and the two screens cannot hold different numbers.
You can tell which stage ate the budget
Each stage is assigned to a labour source — your crew or a sub — and hours and expenses attach to that stage. So the answer to “where did it go on this one” is a stage name, not a total at the bottom of a page. The next time you quote the same building, that is what you are quoting from.
A sub's hours and your own crew's hours sit in the same rows
Both are labour against a stage on a job, and both are entered through the same data layer the field portals write to. Keeping subs in one system and your own men in another is how the true cost of a build ends up in nobody's hands.
Nothing counts against the job until you approve it
Entries run submitted, then approved or rejected, shown on a status ramp. Hours become cost when you say they do, so the margin figure is not moved by a mis-tap on a phone at the end of a long day.
- 1Reads and writes the shared labour data layer — the exact same rows the field and sub portals write
- 2Entry status runs submitted → approved / rejected, rendered on a status ramp
- 3The P&L block compares estimated against actual and computes margin and margin percent
Hours and costs from the field arrived as texts, photos of a paper timesheet, and a phone call on Friday, which put a job's real labour cost about a month behind the job itself — margin was found out after it was spent. Labour and costs sit on the job as they are recorded. The field portals and the office read the same records, so a crew lead and a manager can never be looking at two different totals for the same week.
- Labour costs unknown until after the job
- Double entry between the field and the office
- No stage-level cost attribution
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →