Service pilot review
Assembles demand, delivery and cost evidence for a pilot decision and a separate launch decision.
Improve the practice
The saved work
A service test compared with the existing process
Bounded internal test plan. End-client decision: which workstream commitments may responsibly be proposed for the next fortnight, which need a client decision, and which lack a verified evidence basis. The competent comparator is the existing monthly steering meeting and action register, with the four issue questions added manually to the ordinary pre-read. The proposed extra input is one versioned cross-period exception brief separating changed, unchanged and uncertain evidence, naming the responsible checker, and connecting each item to a decision. It does not replace the meeting or require software.
Included hypothetical per-cycle planning costs are preserved. Existing: Reviewer 0.75 hour at AUD180 = AUD135; Associate 1 hour at AUD90 = AUD90; total AUD225. Proposed: Reviewer 1 hour at AUD180 = AUD180; Associate 3 hours at AUD90 = AUD270; Upkeep 0.5 hour at AUD120 = AUD60; Tools one cycle at AUD25 = AUD25; total AUD535. Incremental planning cost: AUD310. Included items are only those listed. Setup, integration, overhead, support, extra assurance, tax and contingency are excluded or unverified. These are not a fee, savings, spend, capacity release, purchase, or approval; the tools allowance is not a purchase obligation.
A related local example. It shows the stated part of the work, not every step in this design. Read it in saved outputs
- Starts when
- A W32 service idea has enough evidence for an authorised pilot
- What it works from
- Demand evidence, pilot scope, method, delivery costs, acceptance and feedback
- What it prepares
- Pilot design or results review, operating requirements and launch/stop options
- What your team decides
- Partner commissions the pilot and separately decides whether to offer the service
What this helps your team do
This path has been checked in the fictional local build.
Responsibilities connected
See what each agent is responsible for preparing in this workflow. These are designs and local examples, not a set of independently running agents.
When it stops and asks
Unclear reuse rights, weak demand or a client-specific exception stays a candidate; it is not promoted to firm policy or a launched service.
Supported scope, source access and authority are agreed for each installation.