Quick Answer: Subcontractor schedule slippage leaves detectable signals 14 to 21 days before it hits the critical path: manpower under commitment, RFI response delays, submittal turnaround stretching, material delivery reschedules. AI-assisted monitoring in MiOpsAI's Command Center watches these signals continuously across every active sub on every project and flags slippage risk before it becomes a critical path event.
Every commercial GC has lived this. You are 60 percent through a $28M project. The steel sub says everything is fine. The mechanical sub says everything is fine. The framing sub says they might need another crew but nothing to worry about. Three weeks later you are 12 days behind on the critical path, the owner is asking questions, and everyone is pointing fingers.
The signals were there. Nobody was watching.
Why Sub Slippage Almost Never Shows Up on the Weekly Report
Weekly subcontractor reports are a lagging indicator. By the time a sub reports they are behind, they usually have been for 2 to 3 weeks. This is not because subs are dishonest. It is because they are optimistic and they think they can recover. The problem is that many cannot, and by the time they admit it, the recovery window has closed.
The Engineering News-Record published a study in 2024 finding that 68 percent of critical path delays on commercial projects were preceded by detectable warning signs at least 14 days before the schedule impact was reported. The signs are there. Somebody has to be looking.
The Six Signals That Precede Sub Slippage
| Signal | Typical Lead Time | How to Detect |
|---|---|---|
| Manpower under committed count | 10-14 days | Daily report headcount vs manning plan |
| RFI response delay from sub | 7-14 days | Sub-initiated RFI age tracking |
| Submittal turnaround stretching | 14-21 days | Submittal cycle time trend |
| Material delivery reschedules | 10-21 days | Delivery log vs procurement plan |
| Pay app delays from sub | 7-14 days | Billing cycle irregularity |
| Communication frequency drop | 14-28 days | Email/call log analysis |
Most PMs know these signals. The problem is they are watching 20 to 60 subs at once across 4 to 12 active projects. Manual monitoring at that scale is impossible.
The AI-Assisted Monitoring Workflow
Here is how the workflow runs in MiOpsAI's Command Center. Milo continuously monitors the six signals above across every sub on every active project. When a signal trips a threshold, Milo flags it in the PM dashboard with a risk score and a recommended action.
Manpower Monitoring
Every daily report includes a headcount by trade. Milo compares actual headcount against the manning plan the sub committed to at the schedule buyout. If a sub is under-committed by more than 20 percent for 3 consecutive days, that is a flag.
RFI Response Delay
When your PM sends a coordination RFI to a sub and they take 5+ days to respond (against a contractual 48 hours), that is a signal. Milo tracks it across every sub-initiated and sub-directed RFI.
Submittal Turnaround Stretching
Watch the trend, not the absolute number. If a mechanical sub's average submittal turnaround has stretched from 8 days to 14 days over the last month, that is a flag even if 14 days is still contractually acceptable.
Material Delivery Reschedules
Every reschedule of a material delivery is a signal. One reschedule is normal. Three reschedules in 30 days is a pattern. Milo counts and flags patterns.
Communication Frequency Drop
Lizzi monitors email and call log frequency by sub. When a sub who was communicating 4 times a week drops to 1 time a week, that often precedes a bad conversation. Milo pairs the communication signal with the operational signals to increase confidence in the slippage prediction.
What the PM Actually Sees
The Command Center's sub health dashboard shows every sub with a color-coded risk indicator. Green means all signals clear. Yellow means 1 to 2 signals tripped, worth a check-in. Red means 3+ signals or a critical path signal tripped, needs immediate intervention.
When a red flag comes up, Milo shows the PM the specific signals, the projected critical path impact, and 2 to 3 recommended actions. The PM makes the call, but they are working with information they did not have to spend an hour digging out.
Recovery Playbook
Early detection only matters if you can recover. Here is the escalation playbook we recommend once a sub trips the red flag:
- Day 1: Superintendent has a walk-and-talk with the sub foreman. Confirms signals are real. Documents in daily report.
- Day 2: PM calls sub PM. Requests updated recovery plan with specific dates. Documents the call.
- Day 3-5: Sub delivers recovery plan or fails to. If they deliver, plan is monitored daily. If they fail to, escalate.
- Day 5: Formal notice under the subcontract per the delay clause. Julia handles the notice language based on your subcontract terms.
- Day 7: Backup sub or manpower supplement authorized if recovery plan is not tracking. Owner notified.
The value of catching slippage 14 days early is that you have time to actually run this playbook. When you catch it 3 days before it hits the critical path, you are out of options.
Real Numbers From a Real Project
A commercial GC client running a $42M mixed-use project deployed the sub monitoring workflow at week 12 of a 68-week schedule. Over the remaining 56 weeks:
| Metric | First 12 Weeks (Before) | Last 56 Weeks (After) |
|---|---|---|
| Critical path delays traced to subs | 2 events, 11 days combined | 0 events |
| Sub-driven schedule recoveries needed | 5 | 9 |
| Average recovery window | 3.2 days notice | 17.4 days notice |
| Recovery cost (backup manpower, overtime) | $187,000 | $41,000 |
Same number of sub issues. Very different outcomes because they were caught earlier.
Frequently Asked Questions
Does this work if my subs are not on MiOpsAI?
Yes. The signals come from data you already have: daily reports, RFI logs, submittal logs, delivery tickets, email threads. MiOpsAI reads what you already collect. Subs do not need to be on the platform for the monitoring to work.
What if the manning plan was never formalized at buyout?
This is common. Milo can back into a manning plan from the schedule and the sub's scope of work, then flag it for PM confirmation. Once confirmed, the plan becomes the baseline for monitoring. Formalizing manning plans at buyout is a best practice regardless.
How does this integrate with Procore or ACC?
MiOpsAI reads daily reports, RFIs, submittals, and delivery logs from Procore or Autodesk Construction Cloud via API. If your data lives in Procore, Milo watches it there. You do not need to move anything.
What if we get too many false positives?
Threshold tuning is part of onboarding. The default thresholds are conservative and generate 1 to 2 flags per week on a typical $30M project. If that is too many, we tune. If it is too few, we tune. After 60 to 90 days the false positive rate is usually under 15 percent, which means 85+ percent of flags are worth investigating.
How much does this cost?
Sub monitoring is included in the standard MiOpsAI Command Center configuration: 7 chairs at $250 per chair per month, $1,750 per month total. All monitoring is included. Cancellation requires 60-day written notice. See our pricing page.
Ready to Stop Getting Blindsided by Sub Delays?
If you have had a critical path event driven by a sub in the last 12 months, this workflow would probably have caught it early enough to recover. Request access for a 30-minute walkthrough on your actual project data. Learn more about the commercial construction industry solution or read our companion piece on real-time budget vs actuals for commercial projects.