The chain · Objective → KPI
A mandate is not a plan until someone owns a number.
Every office can draw the objective tree. TruMandate makes the KPI the join: a baseline, a target, a named owner and a live actual, wired to the objective above it and the initiatives below it.
One KPI record as the platform stores it. The status dot is computed from movement, never typed in.
Where it breaks
The tree was never the hard part.
The break
Objectives are written by the people who set direction. KPIs are defined months later by the people who report. Nobody's job is to reconcile the two, so they drift apart quietly.
The join
In TruMandate the KPI is the join, not a downstream artefact. Rescope an initiative and the consequence shows at the KPI it feeds, because the link is part of the record.
The refusal
The platform will not accept a KPI without a baseline. A measure with no starting point is an opinion, and an opinion does not survive a minister asking what changed.
AI in the platform
Two KPIs, one benefit, counted twice.
The model compares measure definitions and initiative links, not names, so it catches duplication that a tidy naming convention hides. It states what it found, how sure it is, and what it would do. A person chooses, and the choice is stored with their name.
Two KPIs counting the same benefit
Objective 2.1 and Objective 4.3. Evidence: identical source measure and an overlapping initiative set. Suggested action: merge, or mark one as a contributing measure.
Decision logged · h.alsuwaidi · 11:07
Held back from this page
The cascade editor. Watch it built live, in about ten minutes.
A national framework document in at the top, weighted objectives out at the bottom.