Programme OversightRecords not loaded — Delivery tracking (second instance)
Connection lost. Figures on this page do not include the latest data from Delivery tracking (second instance) (DT-C). Use Retry on this source in Administration → Data sources.
Overdue milestones
Milestones incomplete at the cutoff whose plan baseline due date is before the cutoff. Critical milestones are flagged separately.
Scope: Network Modernisation · Internal tooling refresh · Show the whole programme · Show all programmes
As of 20 Oct 2026 (cutoff)
Definition and formula
Definition v1
- Formula
- Overdue = count of milestones with due date before cutoff and no completion before cutoff
- Target
- 0
- Thresholds
- · Red: an overdue critical milestone
- · Amber: any other overdue milestone
Comparison and source
Previous month and the systems behind the number.
- Previous month (Sept 2026)
- 0 → 0
- Data source
- Delivery tracking (main)Loaded at09:58Data as of20 Oct 2026
Provenance and audit
Where this number came from, and which published versions produced it.
Quality: Partial — Partial total — 1 record(s) excluded.
- Reporting cutoff
- 20 Oct 2026
- Last calculated
- 20 Oct 2026, 10:00
- Definition version
- Definition v1
- Threshold version
- Not applicable
- Plan baseline version
- Not applicable
- Configuration version
- Version 1
- Contributing records
- 0
- Records excluded
- 1
Exclusion reasons: Held for review — no plan baseline due date in effect
- Delivery tracking (main) · batch DT-MAIN:initial (version 1) · Loaded at 2 minutes ago · Data as of 20 Oct 2026
Full provenance for each record is on its record page.
Contributing records
These records reproduce the total. Days overdue.
No contributing records
Nothing counted in this month.
Exclusions
Records held for review, not linked to a project, not in USD, or without an approved budget.
| Excluded | Reason | Amount |
|---|---|---|
| Tooling licence renewal | Held for review — no plan baseline due date in effect | — |