The chain · Initiative → Milestone
Delivery data that never reaches the funder is just paperwork.
Project tools cannot roll up to a mandate they have never heard of. TruMandate holds every initiative against the objective that funded it, so slip is a subtraction, visible the day it happens.
The list continues past the crop. The red row raised itself; nobody filed an exception report.
Where it breaks
The monthly pack is stale and negotiated. Committees fund on it anyway.
The ritual
Someone requests status. Someone retypes it into a template. Each number is rounded toward the answer its author would rather give, because the writer is also the one who will be asked about it.
The subtraction
Every milestone carries a baseline date and an actual date, so slip is arithmetic, not judgement. The steering pack stops being assembled because it was never disassembled.
The name
Every stage gate decision is recorded against a person and a date, and it stays on the record after that person moves on. A wrong number leads back to someone who can be asked.
AI in the platform
A risk neither owner had raised.
Two records no person had a reason to compare: a date that moved on one initiative, and a start condition on another that points at it. Different departments, no shared meeting. The model put it in front of someone with a week still on the clock.
Cross-department dependency at risk
Initiative 07 and Initiative 21, different departments. Evidence: gate 3 slipped on one, and the other's start condition references it. Suggested action: raise a dependency flag before the steering meeting.
Decision logged · m.alfarsi · 08:15
Held back from this page
What happens when a gate is rejected.
How far the change propagates through dates, dependencies and owners before anyone sits down to re-plan.