Picture a Monday morning operations meeting. Eight project managers, one shared screen, forty minutes. Each PM gives a two-minute update. Green, green, green, then someone says, "We're a little tight on the east wing."
Nobody pushes on it. The meeting moves on.
That sentence is the whole problem. "A little tight" is what a PM says when an issue has already been real for a week or two. They are hoping to fix it before anyone asks. By the time it reaches the room, the cheap options are gone.
The meeting reports. It does not detect.
A status meeting shares what people already know. It does that well. It cannot surface what nobody has noticed yet. The only inputs are what each PM chooses to say and remembers to say.
Think about what shows up before a project goes sideways. Open RFIs sitting past their due date. A subcontractor's billing running ahead of the work in place. Change orders pending longer than usual. A milestone that slid a few days, got a new date in the schedule, and never got flagged.
All of that already lives in your systems. None of it is a secret. Reading it across every project every morning is nobody's job. So it gets read one project at a time, when someone has a spare hour. That usually means after the problem already has a name.
Three numbers worth checking before the meeting
If you run more than a handful of jobs, put a short list together before the meeting, not during it.
Start with RFI age. Count how many are open past ten days on each project. One or two is normal. A growing pile means someone in the field is waiting on an answer, and waiting costs schedule.
Next, compare billed percent to complete percent. If a sub has billed forty percent and the work in place looks closer to twenty-five, you want to know now. Not when the pay application lands.
Last, look at which dates changed since last week. A schedule that shifts three days twice in a month is telling you something. That stays true even when every update says "on track."
What a two-week slip costs at different moments
Here is a hypothetical, not a client story. Say a $20M commercial job picks up a two-week slip in framing.
If the team catches it when the RFI backlog starts growing, the options are still open. They can resequence, add a crew for a stretch, or move an inspection. If they catch it when the milestone is missed, the options narrow to overtime and a hard conversation with the owner.
The slip is the same size either way. The price of fixing it is not.
A small change to try
Pull those three numbers for every active project before Monday's meeting and put them on one page. Do not redesign the meeting. Start the conversation with the project that looks worst on paper instead of the one whose PM talks first.
You can do this with a spreadsheet and ten minutes. I am building SiteSignal to do that reading automatically, so the page is waiting on Monday morning.
Related reading
If you want a number attached to delay, read the real cost of a 14-day schedule slip. To size exposure across active jobs, try the portfolio risk calculator. For how SiteSignal surfaces those signals automatically, see the product tour of construction risk intelligence.