State the post-pilot decision before selecting sample size.
A.M.P.E.R.E. TOOLKIT · ANNEX F
Pilot Planning and Design
Defines representative scope, objectives, governance, budget, risks and measures.
A decision instrument, not a paperwork exercise.
Design a pilot that answers specific operating and investment questions under representative conditions.
Start with uncertainty.
Use the annex to make the decision and its missing evidence visible before discussing a preferred product or schedule.
- 01What decisions must the pilot enable?
- 02Does the sample represent service types, geography, communications and operating complexity?
- 03Which systems and workflows must work end to end?
- 04What thresholds, baselines and authorities control acceptance?
Required inputs
- Approved objectives and readiness findings
- Baseline and communications evidence
- Architecture, integrations and security requirements
- Budget, responsibilities, risks and proposed success measures
Controlled outputs
- Controlled pilot charter and scope
- Representative-area and sample rationale
- Test, data and acceptance plan
- Governance, schedule, budget and risk controls
Four disciplined moves.
Select representative strata and end-to-end use cases.
Define baseline, tests, thresholds and evidence ownership.
Approve governance, risk, change and corrective-action controls.
What this page does not do.
Pilot quantity alone does not establish representativeness, duration, statistical confidence or rollout suitability. This educational page explains the instrument but does not reproduce its complete working tables. Use the controlled Protocol PDF and the responsible professional or authority for actual project work.
Open the complete working instrument in Protocol 3.2.
The downloadable publication preserves the full annex, version context and framework limitations.