AI and automation at a glance
Every request staff have raised for AI or automation help, where it sits, and what it has returned so far.
Requests raised
Being assessed or built
Delivered
Annual benefit identified
Where requests sit today
What staff want help with
Benefits staff expect
Who each request would help
What the pipeline actually contains DEV
Solution-fit diagnostic: the simplest proportionate solution for each open request, assessed before AI is assumed. A non-AI outcome is a successful assessment.
AI readiness of open requests
Readiness = all seven Stage 2 gates passed. "Nearly ready" is one or two gates away — usually a named owner or a confirmed data source.
Where the work is up to
Demand by directorate
Top branches
Requests by month
Key messages
Opportunities
A BA or coach reviews each request, then resolves it or sends it on.
/
Payoff and feasibility of every open request
Stage 2 AI readiness
What's holding requests back
AI benefit register
What delivered work has returned, kept separate from what was estimated at intake. Verified benefits only appear once a business owner has confirmed them.
Delivered
resolved in Halo or marked complete here — closed tickets are not counted
Estimated annual benefit
Verified annual benefit
—
none verified yet
Reusable elsewhere
solutions flagged as transferable
Delivered work
What gets recorded at close-out
A ticket shouldn't move to Closed until the first four are filled in. That is what turns this page from a list into a register.
Benefit types expected across the pipeline
Expected benefits from every open request — the demand signal for what delivered work should be measured against.