Budget hours, not just labor dollars

Labor dollars only tell you half of it. A crew can come in under on cost and still be burning hours, because the rate was cheaper than you bid. Or the reverse: on hours, over on dollars, because the overtime landed. You want both numbers, and you want them kept apart.

Now you have both. The Job Budget has a Labor Hrs column that reads timecard hours against budgeted hours for each cost code, with a total in the footer and a Labor Hours card up top. The Budget page across all your jobs carries the same column, so you can spot the job that's eating hours before the cost report catches up.

Where the budgeted hours come from:

• Your estimate. Every labor line has a small hrs field under its unit cost. Lines priced with the production calculator fill it in on their own (quantity with waste ÷ daily production × hours per shift). The derived number shows greyed out, and you only type over it if you want something different. Price a line with the CBA rate picker and its hours fill in too (the line is priced per hour, so its hours are its quantity), and they follow the quantity if you change it later. A labor line priced off a typed unit cost has no hours until you enter them. We don't back them out of the dollars.
• Budget adjustments. On a labor (L) bucket, ± Adjust and Transfer now take hours as well as dollars, or hours alone. Move 40 hours from rough-in to trim without touching the money.

Actual hours are the ones already on your timecards: submitted and approved, by cost code. T&M hours show underneath, not against the budget. They're extra work you bill for, and the estimate never planned them. Hours on timecards with no cost code count in the job total but can't land on a budget line, so the page tells you how many there are and points you to the timecards. The CSV export carries baseline, current, actual, variance and T&M hours next to the dollars.

Executed change orders still add cost only. Hours on COs come later. Until then, an hours adjustment covers it.