What It Shows
Constrovet shows delay days, affected work, cost impact, and missing proof separately. It links schedule slippage to cost only when records support the link.
Why It Matters
Delay often appears in schedules while cost appears in other files. Executives need to know what the evidence can and cannot prove.
What Executives Get
- Baseline and revised schedule comparison.
- Delay links to procurement, resources, work packages, and cost records.
- Evidenced days separated from unproven cost impact.
- Citations and confidence for each finding.
- Recovery actions tied to documented impact.
What Documents Help
- Baseline schedule, updated schedule, look-ahead plan, and progress reports.
- Delay notices, meeting minutes, site instructions, and correspondence.
- Procurement logs, purchase order dates, delivery dates, and vendor notes.
- Idle resource records, penalty clauses, invoices, and cost summaries.
Example Output
| Delay signal | Evidence used | Output |
|---|---|---|
| Procurement delay | PO date, delivery record, progress report | Delay window, affected activity, action owner |
| Idle resource impact | Daily report and resource log | Days evidenced, cost if supported, missing-evidence note |
| Milestone slippage | Baseline and revised schedule | Slipped milestone, cited schedule evidence, recovery priority |
From Evidence to Action
Delay becomes useful when it is tied to evidence, cost impact where available, and next actions. Constrovet keeps that chain visible.
Why 7/30/90 Helps
The 7-day horizon supports evidence review. The 30-day horizon supports correction, and the 90-day horizon supports controls.
Action Use
Delay findings can become 7-day evidence checks, 30-day procurement recovery, and 90-day schedule controls. Actions stay tied to records.
A delay claim without dated, cited evidence is harder to defend in a contractor dispute or an extension-of-time review — the record has to exist before the question is asked, not after.