Charity service pilots: 4 stage-gates for clearer decisions and lower delivery risk

Ever had a strong idea for a new charity service, only to watch the pilot stumble, or worse, get quietly rubber-stamped as “the new normal” before anyone really checked whether it worked on the frontline? Most of us have been there.

That’s where stage-gates come in. At their simplest, stage-gates are just clear decision points. Moments where you stop, look at the evidence, and make an intentional call: carry on, scale up, slow down, or stop well. They exist to turn optimism into learning and learning into better decisions.

Stage-gates sit inside the wider service lifecycle. From identifying a need, to designing and delivering a service, and eventually deciding whether to adapt or retire it. Done well, they connect big-picture strategy with day-to-day reality, instead of letting pilots drift on momentum alone.

Below are four key stage-gates for charity service pilots, with practical prompts to help you make clearer decisions under delivery pressure.

Four key stage-gates for charity service pilots

Gate 1: Go

Use when: You have an idea and want to test it without overbuilding.

Ask: Are we clear on the one problem we’re solving, and who it’s for?

Look for:

• A 1–2 sentence purpose.

• 1–2 success signals (plus one safety/quality check).

• A time-boxed pilot window and a named owner.

• Lived experience input on what “harm” or “failure” would look like.

Decision: Go only if you can explain the test in plain language and deliver it within current capacity and safeguards.

Gate 2: Grow

Use when: The pilot “works” locally and pressure builds to roll it out.

Ask: If we scale this, what will it add and what might it accidentally break?

Look for:

• Evidence it works across different contexts.

• A clear view of hidden work created.

• Equity check: who benefited, who didn’t show up, who dropped out.

• A realistic resourcing plan.

Decision: Grow only if scaling is operationally survivable and you can name the new risks and how you’ll manage them.

Gate 3: Pause

Use when: Results are mixed, context has shifted, or the team is improvising.

Ask: Are we learning, or are we drifting?

Look for:

• A time-bound learning sprint with 1–3 focused questions

• One named lead and one place where learning is captured

• A clear next gate date booked now

• A safeguard check if anything feels off

Decision: Pause when you believe the idea is still worth testing but you need sharper evidence before committing.

Gate 4: Stop

Use when: The pilot isn’t delivering, isn’t equitable, isn’t safe, or isn’t affordable.

Ask: If we continue, what harm or cost are we accepting and is it justified?

Look for:

• A plain-language stopping rationale

• A transition plan for people affected

• A risk tidy-up

• A short 'what we learned' note to prevent repeating the same experiment

  
  

Decision: Stop when the evidence says it’s not the right answer and close it in a way that protects trust.

Make the four stage gates work: quick checklist

• Name the owner: Who convenes the gate and records the decision?

  
  

• Define success early: Agree decision-driving metrics and how to collect them.

  
  

• Time-box each gate: Set the review date and commit to it.

  
  

• Include lived experience: Build in real voices at each checkpoint.

  
  

• Write it down: Record the decision and rationale.

Next steps

Stage-gates aren’t here to make decisions for you. They’re here to empower better, more informed choices, backed by evidence and real-world learning.

If you’d like to go further:

• Start by reading Service owners in charities

• Pair this mini with the full service lifecycle management for charities guide, so service owners aren’t carrying it alone.

Change doesn’t start with a restructure; it starts with one honest conversation.

Let's Chat

Note: These insights are general guidance based on practitioner experience and are not legal or regulatory advice. Make sure you review your specific funder contracts and data protection policies (e.g. GDPR) before making significant changes to data collection or retention schedules. Examples are for illustrative purposes only; no official affiliation with the organisations or tools mentioned is claimed.