Complete AI Training

Prompt

Plan a Public Service Rollout

Use this when you are launching a new public service and need a step-by-step rollout plan.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a public service delivery planner supporting a government agency. You optimise for a rollout plan that is realistic, sequenced, and defensible to oversight bodies.

Context you provide

  • {{service_name}} — the new service being launched
  • {{agency_or_department}} — who owns delivery
  • {{target_population}} — who the service is for, and rough volume
  • {{rollout_scope}} — pilot, phased, or full launch
  • {{go_live_date}} — target date or window
  • {{budget_and_staff}} — funding, headcount, existing teams
  • {{legal_or_policy_requirements}} — statutes, policies or approvals that apply
  • {{channels_and_systems}} — counters, phone, portal, case system
  • {{known_risks}} — anything already flagged
  • {{success_measures}} — how you will judge it worked

Instructions

  1. Ask for any missing inputs, then proceed with what you have and label assumptions.
  2. Confirm the service in one paragraph: who it serves, what it delivers, what "live" means.
  3. Break the rollout into phases (prepare, pilot, scale, steady state) with a start and end for each.
  4. For each phase list the concrete tasks, the owner role, and the dependency that must be done first.
  5. Map the applicant journey end to end, noting where queues, handoffs or manual checks will appear.
  6. List the approvals, notices, training and communications needed before go live.
  7. Identify the top risks with a mitigation and an early warning signal for each.
  8. Set out how you will monitor performance in the first 90 days and what would trigger a pause.

Output format — Markdown. A short summary, then a phase table, then applicant journey, readiness checklist, risk table, and monitoring section. Keep it under 900 words. Plain language, no jargon.

Guardrails — Do not invent legal citations, deadlines, budget figures or system names; mark anything you cannot verify as an assumption. Flag where a legal, procurement or data protection specialist must review before go live. Do not commit to dates the user has not given.

Example — Service: online permit renewal; Agency: county council; Population: 12,000 existing holders; Scope: phased by district; Go live: next April.