ProjectPayoutPanel runs the real payout against the hours the crew actually clocked on their field links, showing its working before the per-person table. It self-hides on any job whose crew is not on the pooled model.
Also called: crew payout screen · what do I pay them · job payout · settle up with the crew
The settle-up happens in front of the arithmetic
Pool, day rates earned, fuel and equipment, surplus shared — then a line for every man: tier, hours, days, day rates, surplus, owed, and a Total to the crew at the foot. A payout screen that prints one number per person is asking to be argued with. One that shows how it reached that number settles the argument before it starts.
The hours are the ones they clocked, not the ones somebody re-keyed
Every entry the crew logged on their field links for this job is collapsed to one row per person per day and priced. Nothing is typed into this screen. The Friday spreadsheet, the phone call to the crew leader and the transcription mistake in the middle of it all disappear at the same time.
It refuses to answer rather than invent a total
No crew assigned, no tiers set up yet, a crew paid by the hour, nobody on the crew: each comes back as a stated reason instead of a number. And with no hours logged there is no surplus at all — an untouched pool is money you have set aside, never money somebody is owed. This is what people get paid from, so a plausible-looking invented figure is the worst thing it could produce.
A man off sick does not shrink what the others share
The pool is priced from the crew as established — every active member's tier plus the equipment allowance — not from whoever happened to turn up. Attendance moves what each person earns and shares; it does not quietly re-price the job underneath them mid-build.
One calculation behind every screen that mentions this job's pay
The project panel, the person's own record in Team, and the company-wide labour rollup all run the same function. Two implementations of “what did this job pay” is two answers, and the one on the employee's own record is the one they would argue with you about.
Rounding never invents or loses a cent
Shares are computed to four decimal places, and the drift between the distributed total and the actual surplus is handed to whoever worked the most hours, so the per-person lines always sum exactly to the surplus. A payout sheet whose parts do not add up to the total is a payout sheet nobody trusts twice.
- 1GET /api/projects/payout?projectId=... behind requireRole(admin, PM, crew_lead).
- 2computeProjectPayout resolves the crew, its model, the tier ladder, the roster and every time entry for the job.
- 3Hours are accepted under either the crew row id or the user id, because the portal may have written either.
- 4The pool is priced from the crew AS ESTABLISHED, so a man off sick does not shrink what the others share.
- 5Header shows Pool / Day rates earned / Fuel & equipment / Surplus shared; the table shows Who, Tier, Hours, Days, Day rates, Surplus and Owed with a 'Total to the crew' foot.
- 6Non-applicable cases come back with a stated reason rather than a number.
Handing a crew one number per man is asking to be argued with, and the argument happens in a yard with nothing there to settle it. The payout screen shows how it got there — the pool, each man's tier and base pay, hours worked, the surplus and every share — so the arithmetic is visible before anyone questions it. When something it needs is missing, such as an untiered man or a job with no figured days, it refuses and names what is missing, because a plausible invented total on the screen people are paid from is the worst thing it could produce. The same arithmetic drives each person's own record, so a job's payout and an employee's record can never quote different money.
- Manual payout arithmetic per job.
- Payout disputes with no visible working.
- Two screens quoting different money for the same job.
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 →