An admin-only rollup on Team › Field Performance. Headline figures for labour paid, cost per crew-day, difference against the day rates and hours logged; a bar chart of hours by person coloured by crew; and a crew table anchored on the pay ladder.
Also called: what is my labour costing · who works the most hours · team labour analytics · cost per day
Crews compared against the ladder they are actually paid on
Each crew's day rate is its own members' tiers plus its equipment allowance, projected across the days it worked, set beside what those jobs actually paid out, with the difference named. Above the day rate means the crew came in inside the days its jobs were figured for and kept the surplus. Below means the pool did not stretch to every day they were out.
Cost per crew-day, because that is the unit you buy
Total labour divided by crew-days, not by calendar days and not by man-hours. Two crews out on the same Tuesday is two days of crew cost. Money over calendar days reads low every time more than one crew is working, and money over man-hours reads like an hourly wage that nobody on this pay model is actually paid.
One bar per person for hours, with the money one hover away
Bars are hours and the colour is the crew, so who is carrying the work and which crew they belong to arrive in the same glance. The tooltip holds the money: share of crew hours, earned, actual per day against their tier's rate, average day length. A chart of dollars per person on a screen in a room starts a conversation you did not want to have.
It reconciles with every job's payout screen
Each job is costed once, through the same function the project payout panel runs, and every person's share is read out of that single result. So the total on this page, the figure on the man's own record and the number on the job all agree — which is not automatic, and is the reason the arithmetic lives in one place.
A framer's history survives him getting an account
Hours are folded through every id a person has ever been known under before they are totalled. The day a crew member gains a login his identity changes underneath, and without this his year restarts at zero and his old field link stops working. Both keep working.
Jobs it could not price are counted and said out loud
Where a job has no crew, no tiers or a crew paid another way, it is excluded and the count of unpriced jobs is shown. A labour total that silently covers two thirds of the work is more dangerous than no total, because you will act on it.
- 1Every job is costed ONCE through computeProjectPayout and member lines are distributed out of that single result.
- 2Hours are folded through the roster's alias map so ids written before someone gained a login still count.
- 3Earnings are added per JOB, not per entry, so forty time rows on one job earn that job once.
- 4Crew rows are priced from the crew as established — every active member's tier plus equipment — and projected across the days they actually worked.
- 5Unpriced jobs are counted and stated so a cost total is never read as covering every job.
A builder could see what one job paid a crew but not what he had paid anybody over a quarter, because the numbers existed one job at a time and nobody was going to add up forty of them. Hours and labour cost roll up across every person, every crew and the whole company, with each job costed once and its shares distributed, so every individual's share of every job adds up to exactly what that job paid. The crew performance view measures delivery against plan and says nothing about hours or money; this is the other half of the same question.
- Labour cost visible only per job, never in aggregate.
- Per-person shares that do not sum to what the job paid.
- Hours lost from totals when a person's id changed.
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 →