The pattern of the public sector firm in 2026 — what's actually broken
I've spent the better part of a year sitting across from heads of digital, IT directors, and operations leads in councils, semi-states, and central government bodies. The pattern is consistent enough that I can describe the day before they describe it to me.
The morning is parliamentary questions, freedom-of-information requests, councillor queries, and a steering group that wants a paper by Thursday. The afternoon is a procurement review, a GDPR data subject access request that's been sitting for nine days, and a policy consultation response that needs to land before the Oireachtas committee meets. Somewhere in there, somebody is meant to be running the actual service.
The bit that's broken isn't the people. The people are fine. The bit that's broken is that institutional knowledge — every previous PQ answer, every prior FOI response, every policy paper drafted in the last fifteen years, every Section 38/39 funding letter — sits in shared drives, mailboxes, and the heads of three people who are within five years of retirement. When a new query lands, half the work is finding what was already said. The other half is making sure what's said now doesn't contradict it.
That's where AI helps. Retrieval, summarisation, drafting against a known house style, and consistency-checking against your own prior positions. That's the shape of the problem.
Where it would obviously not help: anything involving a statutory decision, anything involving a vulnerable citizen's case file, anything where a public servant's professional judgement is the legal instrument. The Intelligence Brain isn't there to make decisions. It's there to make sure the person making the decision has every relevant prior position, precedent, and policy in front of them in the first ninety seconds.
The seven workflows that pay for the project in month one
These are the seven I keep seeing land first in council AI and semi-state AI deployments. Pick three to start.
- Parliamentary Question drafting. Ingest every PQ your body has answered in the last decade. New PQ comes in, the Brain returns the three closest prior answers, the relevant policy position, and a draft that matches your house style. The drafter edits, doesn't write from scratch.
- FOI triage and redaction support. Incoming request gets categorised against Section 15, 29, 30, 31, 32, 35, 36, 37 exemptions automatically. The Brain flags candidate redactions and surfaces every prior FOI on the same subject so you stay consistent. The decision-maker still decides.
- Councillor and Oireachtas member correspondence. Same logic as PQs. Match the query to prior responses, prior commitments, and current operational status. Draft goes to the named officer.
- Policy consultation response synthesis. When two hundred submissions land on a public consultation, the Brain clusters them by theme, surfaces the outliers, and produces a defensible analytical summary that a human signs off on.
- Procurement query handling. Tender clarifications, prior-information notices, and supplier questions matched against your own previous tenders and the OGP frameworks you sit on.
- GDPR data subject access requests. Locate the data, log the location, draft the response letter, flag third-party data that needs redaction. The DPO reviews and releases.
- Internal audit and Comptroller & Auditor General preparation. When the C&AG comes in, every document request gets answered the same day instead of the same fortnight.
The data-residency posture for Irish public sector AI
This is the bit where most off-the-shelf tools fall over for an Irish public sector firm. The Brain runs on-premise or in a sovereign Irish or EU-region tenancy. No data leaves the jurisdiction. No prompts, no completions, no embeddings, no logs.
The specifics that matter:
- GDPR and the Data Protection Act 2018. Lawful basis is documented per workflow, not per tool. DPIAs are produced before each workflow goes live, not after.
- The Public Service Data Strategy and the Data Sharing and Governance Act 2019. Where the Brain touches data shared between public bodies, the data-sharing agreement governs the access pattern, not the tool.
- NIS2 and the forthcoming national transposition. Logging, incident response, and supply-chain attestation are built in.
- The EU AI Act. Most public sector workflows fall into limited-risk or high-risk categories. The Brain ships with the technical documentation, conformity logging, and human-oversight controls the Act requires.
- Records management under the National Archives Act. Retention schedules are enforced inside the Brain, not bolted on.
The Office of the Government Chief Information Officer guidance, the NCSC baseline, and your own departmental ICT security policy are the floor, not the ceiling.
The deployment cadence — thirty-two weeks, four gates
I run the same cadence for every government intelligence brain deployment. Eight weeks per phase, a formal gate at the end of each.
Weeks 1–8: Ingest
I map every source — SharePoint, file shares, case management, email archives, the policy library, the FOI register. Nothing is moved yet. At the gate, you see a complete data inventory, a classification map, and the DPIA for the first three workflows.
Weeks 9–16: Structure
The data is brought into the Brain, classified, embedded, and indexed. At this gate, you see the first working retrieval against your own corpus. You ask it about a 2019 policy position and it returns the paper, the minister's statement, and the subsequent PQ answers.
Weeks 17–24: Swarm
The agents that run the seven workflows are stood up, tested against historical cases where you already know the right answer, and tuned. At this gate, you see drafted PQ responses, FOI triage decisions, and consultation summaries running against live work, with a human in the loop on every output.
Weeks 25–32: Audit
The full audit posture goes live — every prompt, every retrieval, every output logged, attributable, and reviewable. The internal audit team and the DPO get their own console. At this gate, you have everything the C&AG, the Data Protection Commission, or an Oireachtas committee could ask for.
What to bring to the assessment call
If you've read this far and you're considering a call, three things make the first conversation useful rather than exploratory:
- A list of the three workflows that hurt most this quarter.
Frequently asked questions — Public Sector
Is the Intelligence Brain on-premise or cloud?
Default is on-premise — the firm's own server, the firm's own data, the firm's own model weights. We support private-cloud (your AWS, your GCP, your Azure tenant) when on-prem hardware isn't a fit. We do not run a multi-tenant SaaS.
How long is the rollout?
About six months from kick-off to live use. Four eight-week stages — ingest, structure, swarm, audit. The swarm runs in shadow mode for the first ninety days alongside your team; only at day ninety, with the audit logs to back it up, does the swarm earn the right to run a tool live.
What does it cost?
Per-firm engagement, scoped from a free thirty-minute assessment. Firms vary too widely for a public list price — a five-partner law firm and a forty-person SME need different scoping. Book a slot via Calendly and we will scope it together.
Can it write contracts / draft accounts / produce clinical letters automatically?
It can produce a first pass that a qualified human reviews before anything is signed, filed, or sent. Tool-layer authorisation is a hard architectural boundary in the brain — the swarm reads everything and signs nothing.
What about hallucination?
The auditor agent's job is to catch hallucination before output reaches a human. Every claim in every output is required to be cited; every cite has to be reachable; every cite has to load. If the auditor cannot verify, the output is rejected as a build-failure signal — not corrected.
What's specific about public sector firms in the rollout?
The public sector vertical brings its own data-residency, professional-body, and audit-trail constraints. The methodology is the same; the structure-stage and swarm-stage prompts are vertical-specific.
Do you understand the public sector regulatory environment in Ireland?
I have worked with firms in this vertical and I bring the regulatory posture into the architecture from day one. The compliance pack at delivery includes DPIA, LIA, and EU AI Act tier-mapping, all reviewed against the vertical's specific framework.