Nobody in the public sector needs telling that AI could help. The question that actually decides things is narrower: what can you use it on, given information governance, procurement and the fact that you cannot adopt tools unilaterally? The honest answer is: more than most people think, provided you choose the work with the constraint in mind rather than against it.
Governance is the design brief
The private-sector framing - pick your most painful task and automate it - fails in a trust or a council, because the most painful task usually involves personal data, an individual’s circumstances, or a decision someone must be accountable for. Start instead from what your organisation’s rules already permit, and the field is still surprisingly large:
- Papers and reports assembled from public material. Board papers, committee briefings and strategy documents are mostly synthesis of documents that are already public or internal-but-unrestricted. A workflow that gathers, structures and drafts against your house style removes the assembly without touching a single record.
- Consultation and engagement synthesis. Hundreds of free-text responses, grouped by theme with disagreements flagged and every claim traceable to a response - the kind of work that eats a fortnight and suits a pipeline exactly.
- Meeting notes into minutes and actions. In your organisation’s own approved tools, a drafter-and-checker pair turns notes into consistent minutes with an action list, ready for a human to correct rather than compose.
- First drafts against a template. Job descriptions, service specifications, policy summaries - anywhere the structure is fixed and the content is unrestricted, a draft-then-review workflow earns its keep.
The work that stays out of scope
Decisions about individuals: eligibility, safeguarding, anything clinical. Not because a workflow could not produce an output, but because accountability for those decisions cannot be delegated, and being subtly wrong about a person is the failure mode your governance exists to prevent. The same goes for feeding personal or patient data into tools that have not been through your organisation’s approval process. If the task needs data you would not put in an email to an external supplier, it is not the task to learn on.
None of this is a limitation unique to AI. It is the same line your organisation already draws, applied consistently.
Budgets are an argument for method, not against it
Public-sector budgets do not stretch to speculative platforms, and they do not need to. An agentic workflow is a method - a sequence of narrow steps with a check at the end - built in tools your organisation may already licence. The investment is a day of learning the pattern, not a procurement exercise. And the wins, while smaller-scoped than a vendor deck would claim, are real: hours back each week on assembly work, applied by the person who understands the service.
Where this gets practical
The gap between agreeing with all this and having a working example is the part that rarely closes on its own. That is what a day at the Oxford Agentic Bootcamp is for: bring one real task - a paper, a synthesis, a template draft, chosen with your own governance in mind - and build a working agentic workflow against it, with someone on hand when you get stuck. No coding, and nothing about the day requires putting restricted data anywhere it should not be.