@Clark Mason For us it started breaking once we had more than a handful of active jobs and multiple contractors on different timelines. The first things to slip were draw tracking and who owned each punch-list item. We've since pivoted to AI tools, and there are some amazing ones now for tracking all of this. They keep things organized on a lot of fronts at once: scope, budget, draws, and photos in one place. How many jobs are you running at once?
I'm on my first rehab, so I can't speak to running several jobs at once. What I've noticed already is that the spreadsheet isn't the hard part. The hard part is keeping the receipts and change orders tied to the right line, so the bid and the actual cost can be compared. I'd love to hear where it broke down for the folks who've done this a while.
For comparing contractor performance, I’d separate contractor delays from owner decisions and material delays. “Finished ten days late” doesn’t tell you much if the owner changed the scope twice. A short reason field beside each schedule change would make the cross-project comparison fairer. Otherwise a more sophisticated dashboard can just make a misleading comparison look more convincing.
Thanks — the idea of recording a reason beside each schedule change is a useful detail. In practice, is that reason usually recorded when the change happens, or reconstructed later? And do you use a fixed set of reason categories, or does each person describe it in their own words?
A spreadsheet stops working when the jobs stop being the same job. My rehabs work on paper because the scope is repeatable: same floor plans in the same Memphis ZIPs, same line items, same prices for roof, HVAC, flooring, kitchen, bath. When every house is a conversion — 2/1 to 3/1, 3/1 to 4/2, carport to master bed and bath — the tracking that matters is not bid versus actual on a custom job, it is whether the crew finished the standard scope on schedule across all the houses running at once. At 236 doors the miss I watch is not a $200 overrun on one line. It is a job sitting idle for a week while the sheet still looks green. Standardize the scope first. Then any simple system works, because there is less to track.
Thanks — "a job sitting idle for a week while the sheet still looks green" is a concrete failure mode I haven't seen described this way.
When that happens, how does it usually come to light in your operation — does your tracking system flag it, or does someone notice it through site visits, contractor updates, or some other process?