The sandbox exposes daysFigured directly and derives days-on-site from it plus a delta, so re-figuring a job holds the 'two days early' meaning. The headline names it in words: finished on time, finished 2 days early, ran 1 day over.
Also called: finished early · ran over · what if we save a day · days figured stepper
- 1setFigured writes the new figure and moves days-on-site by the same delta.
- 2setDelta moves days-on-site relative to the figure.
- 3The pooled model opens level — days on site equal to days figured — so the surplus only appears once the builder moves it.
- 4Named result fields (pool, surplus, poolLeft, daysFigured, daysDelta) drive the headline rather than string-matching labels.
The surplus in a day-rate model comes from the gap between the days a job was figured for and the days it actually took, and the sandbox could only change one of those two numbers — so the mechanism it existed to explain was the one thing it could not show. Both are now set independently: figure a job for seven days, run it in five or in nine, and watch what each does to the pool and to every man's share. It opens on-plan rather than three days early, because a builder's first look used to be a large surplus with no explanation of where it came from. Pricing the pool from the crew a builder actually built, rather than one man of every tier, was the other fix — a day saved should return exactly one crew-day, and it did not.
- No way to model the plan-versus-outcome gap the pay model exists for.
- A sandbox pricing the pool from the ladder rather than the actual crew, disagreeing with production.
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 →