Use whenA use case has been selected for pilot — drafted, then signed, before anyone touches a tool.
OutputA signed pilot charter with baseline, stop conditions, and review date.
A
Pilot & people
Pilot name
Executive sponsor
Workflow owner
Participating users
1
Baseline, outcome & tool
Baseline — documented before the pilot starts No charter, no pilot. Without a starting point, no pilot can demonstrate improvement.Meridian: 26 staff-days/quarter; 4 revision cycles per report; 2 late submissions in 4 quarters.
Intended outcome A named improvement against the baseline numbers.
Approved tool From the approved-tool registry.
2
Evaluation & oversight
RESPECT evaluation summary
Decision
Human-review plan
Evidence, concerns, and required controls — each concern paired with a control and owner.
Who reviews what, before it reaches whom — and who certifies the final output.
3
Measures, stop conditions & review
Success measures Each measured against the charter baseline.
STOP CONDITIONS Name numbers and events, not sentiments. Deciding in advance what result would end the pilot separates experimentation from commitment-by-drift.
Review date On the council calendar.
⛔ Gate 3 — Portfolio. The executive sponsor approves the pilot portfolio and budget. Each pilot charter is signed by its sponsor and workflow owner. Unsigned pilots do not launch.
4
Signatures
Executive sponsor — signature
Date
Workflow owner — signature
Date
You should now have