Pilot planning

Runs in your browser No storage

Pilot Readiness Review

Create a Pilot Decision Record before you start, so your pilot has clear evidence, honest boundaries and a defensible decision at the end.

Create the record

Privacy and scope

Use anonymised planning details only.

This tool uses structured choices only - there are no free-text fields, nothing is sent anywhere, and nothing is saved. Use anonymised, non-confidential planning details only.

It is planning support, not a substitute for legal, compliance, clinical, financial, HR, procurement, security or formal governance review.

Guided review

Build the decision record in four steps.

Choose structured answers only. Generate a record when you are ready; if you change an answer later, update the record deliberately.

1 Best-fit pilot situation

Pick the closest fit. The record is based mainly on what the pilot must prove and the conditions you select.

First pilot Use this when the team is testing the idea in practice for the first time. Follow-up pilot Use this when an earlier pilot gave a signal and the next run needs to test what is still uncertain. Failed or confidence-rebuild pilot Use this when a previous attempt struggled and the next pilot needs clearer evidence boundaries before confidence is rebuilt. Commercial-model pilot Use this when the pilot needs to test whether pricing, payment or the economics can work. Scale-readiness pilot Use this when something worked in a controlled setting and the next question is whether it can survive broader rollout. Operational-feasibility pilot Use this when the pilot needs to show whether the surrounding people, process and support model can run at all. Mixed or not sure Use this when more than one situation fits. The record will still be driven by the proof areas and conditions you choose.

2 What the pilot needs to prove

A proof area is the claim people may want to make after the pilot. Pick one main claim so the tool can judge whether the pilot design is valid for that claim.

Pick one Main claim. Choose Also informs only for areas the pilot should help with, but does not need to prove fully. Anything left unselected is outside this pilot's evidence claim.

Product/technical readiness

The thing works reliably enough to use.

Main claim Also informs

Usability/adoption

Intended users will actually use it without heavy hand-holding.

Main claim Also informs

Demand/desirability

People genuinely want it, not just because they were asked.

Main claim Also informs

Willingness to pay/commercial viability

People will pay, at a price that works.

Main claim Also informs

Operational feasibility

The surrounding process, people and support can run it at all.

Main claim Also informs

Operational scalability

It can run at real volume, not just in a hothouse.

Main claim Also informs

Downstream value/outcome

It produces the result that matters, not just activity.

Main claim Also informs

Stakeholder confidence

It builds enough belief to unlock the next decision or funding.

Main claim Also informs

Pilot Readiness Review

Use anonymised planning details only.

Build the decision record in four steps.

Product/technical readiness

Usability/adoption

Demand/desirability

Willingness to pay/commercial viability

Operational feasibility

Operational scalability

Downstream value/outcome

Stakeholder confidence

Pilot Decision Record

What this pilot must prove

What this pilot will not prove

Conditions to set before starting

Start with these conditions

Other limits to note

Stakeholder summary