What this crew is owed for this job

A payout breakdown for the job, computed from the hours the crew actually logged — pool, day rates, fuel, surplus, then the split.

What it is

A panel inside the project modal showing the crew, the number of days the job was figured for and where that number came from, the hours logged, and a per-person table (tier, hours, days credited, day rates, surplus share, owed) with a total. It shows the pool arithmetic above the table: pool, day rates earned, fuel & equipment, and surplus shared or overrun.

Also called: crew pay · day rate payout · what do I owe the crew · pool split

See it, piece by piece
01

What the crew is owed for this job, with the arithmetic on the screen

The pool, the day rates earned, fuel and equipment, and the surplus shared — then a line per man with his tier, hours, days credited, day rates, surplus share and what he is owed. What a crew was owed used to be worked out in a spreadsheet or in somebody's head and then argued about on payday with four men standing there. A screen that prints one number per person is asking to be argued with; this one shows how it got there.

Crew payout
Crew payout
Crew A · figured for 12 days · 361h logged over 11 days
Refresh
Pool
$21,840
Day rates earned
$15,833
Fuel & equipment
$3,300
Surplus shared
$2,708
WhoTierHoursDaysDay ratesSurplusOwed
Levi YutzyTier 19611$5,500.00$720.00$6,220.00
Dwayne MillerTier 29210.5$4,200.00$690.00$4,890.00
Curt HershbergerTier 38810$3,500.00$660.00$4,160.00
Andre OcampoTier 4859.75$2,632.50$637.50$3,270.00
Total to the crew$18,540.00

Hours come from what the crew logged on their field links. Day rates are earned per day worked; the surplus is split by share of hours, so being there is what moves it.

Pool, day rates, fuel and surplus above a per-man table and the total to the crew. The real screen, drawn from the product’s own design system. Sample data — no customer information appears here.
02

The hours are the ones the crew logged, not the ones anyone remembers

Days worked come off the field links the crew already uses on site, so the payout is built from a record both sides could see while the job was running. Day rates are earned per day worked and the surplus is split by share of hours, so being there is what moves a man's number — which is the part a crew will accept and the part a napkin never proves.

03

When a job runs past the days it was figured for, it says so

Go past that day count and the panel states it: the crew still earns its day rates, and the overrun comes out of your margin because there is no surplus left to share. That is the sentence that tells you a job stopped making money, and it arrives while you still have the next three jobs to price differently.

04

It will not fill a gap with a plausible-looking number

A man with no pay tier set is named, with a pointer to the crew card where you fix it. A job that was never figured for a day count comes back as that reason rather than as a total. People are paid off this screen, so anything it cannot source it leaves visibly missing.

05

The job screen and the man's own record can never disagree

The arithmetic runs in one place, so what the project says a man is owed and what his own record says are the same number. On a crew that is not on the day-rate pool the panel hides itself completely rather than showing an empty table that means nothing to them.

How it works
  1. 1Fetches the authenticated payout for the project; the arithmetic lives in a shared library so the person dossier and the project screen can never pay different numbers
  2. 2Self-hides entirely when the crew isn't on the day-rate pool model
  3. 3Crew members with no pay tier are named explicitly, with a pointer to set it on the crew card
  4. 4Overrun is stated plainly: 'They have gone past the N days this job was figured for, so there is no surplus to share. The crew still earns its day rates — the overrun comes out of your margin.'
  5. 5A missing tier or unfigured day count comes back as a stated reason rather than a number
Why we built it

What a crew was owed for a job got worked out in a spreadsheet or in someone's head, and then argued about on payday with the crew standing there. A payout screen that prints one number per person is asking to be argued with; this one shows how it got there — the stages, the rates, the extras — so the argument is settled before it starts. People are paid from this screen, so it will not fill a gap with a plausible-looking guess: anything it cannot source, it leaves visibly missing.

The problem
  • Payout arithmetic done by hand from logged hours
  • Disputes about how a pool was split
  • No visibility on whether a job overran its figured days
Sound familiar?
What you get
The split is shown with its working, not just a total
Refuses to guess rather than paying a made-up number
Sits where the question actually gets asked — on the 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 →