Capability
Schedule Review & Assurance
Test a submitted or live programme for logic, density, calendars, constraints, and control readiness before it is treated as approved.
C02 — The problem
The technical problem
Approval is often a date on a letter, not a technical test. Open ends, negative float hidden by constraints, missing scope, and update procedures that cannot be followed are left in the file.
Schedule Review & Assurance is an independent technical read of a programme someone else built. The buyer needs to know whether that file is safe to baseline against, not whether a new programme should be written from scratch (that is Baseline Schedule Development).
C03 — Engagement
When this capability is needed
-
01
Baseline submission
An owner, PMC, or contractor needs a structured review before acceptance.
-
02
Periodic assurance
A live programme has drifted and needs a health check.
-
03
Dispute or claim window
The contemporaneous programmes must be characterised before analysis starts.
-
04
Lender / governance review
A third party needs a technical opinion on schedule quality.
C04 — Scope / method
How the work is approached
Review of logic, calendars, constraints, density, open ends, coding, completeness against known scope, and whether the file can be updated. The assignment may recommend rebuild; it does not automatically rebuild.
-
01
Confirm the review basis
Contract programme requirements and the file actually submitted.
-
02
Test technical health
Logic, open ends, lags, constraints, calendars, and float behaviour.
-
03
Test control readiness
Can progress and change be coded without breaking the model?
-
04
Compare to known scope
Missing areas, interfaces, and contractual milestones.
-
05
Issue findings
Accept, return with defects, or reject — with evidence, not adjectives.
C05 — Outputs
Typical deliverables
| Output | What it contains |
|---|---|
| Schedule review report | Method, tests, and recommendation. |
| Findings register | Defects ranked by effect on control and completion. |
| Technical checklist | The tests applied, so the next submission can be compared. |
| Assurance note | What the file can and cannot currently support. |
C06 — Decision value
What this work is used to decide
Accept, return, or reject the programme as a control baseline. The review does not certify that the works will finish on the dates shown.
C08 — Project environments
Relevant project environments
C09 — Who we support
Who commonly needs this capability
C10 — Boundaries
Important distinctions
Schedule review is not design certification, constructability sign-off, or delay analysis. It characterises the file in front of you.
C11 — Next step
Discuss your project
If this is the technical problem you are facing, talk to Value Construction about the work, the records required, and what you would receive. Outcomes are not guaranteed.