Pillar 04 · Accountability
C4 Flagged-Answer Triage and Log
Your users will find wrong answers first. Make it easy for them to say so.
Form Document and workbook
What it's for
Monitoring catches some problems. Users catch more, because they know when an answer doesn't fit what they know. A wrong answer with no route to an owner gets worked around, then repeated. This process turns each flag into a data issue with a root cause, fixed at source, so the next person gets the right answer.
Use it with the flagged-answer log (C4 workbook), which routes each flag and tracks the framework's measures.
What you get
- The process Six stages, from the flag to closing it and telling the user.
- Finding the root cause Eight questions, in this order
- Flag log Each flag: the question, the answer, what was wrong, its priority and root cause, the fix at source and whether the user was told.
- Summary Median time from flag to fix, and the share of flags traced to a root cause.
Worked out for you Routed to, Days to acknowledge, Days to fix, Fixed within target?
How it connects
Each flag names its S1 use case, and its root cause routes it to the owner who fixes it: the source owner (S2), the term owner (M1, M3) or the dataset owner (A1, A2).
A flavour of the worked example
| Question asked | What is the portfolio WAULT for the IC paper? |
|---|---|
| Answer given | 7.6 years |
| What was wrong | Overstated by 1.4 years: an expired lease was still marked active |
| Root cause | Data quality |
| Routed to worked out | Dataset owner (A1, A2) |
| Days to fix worked out | 30 |
A few fields from one record of the toolkit's worked example, with long text shortened.
Next step
Guided build coming next.
Request access
Ask for access to the guided builds, including this kit's when it is ready.