Discovery field guide / Industry
How to find AI opportunities in Government & Public Sector
Where should discovery start?
Start with a public service journey and trace what prevents a resident, business, or caseworker from reaching the correct next step. Look for repeated evidence requests, unclear guidance, and handoffs between service teams. Keep administrative assistance separate from eligibility, enforcement, and other decisions affecting rights or access. Compare opportunities on public value, equitable access, and defensibility, not only internal handling time.
The shared framework
Fourteen stages, from objective to portfolio.
Every guide uses this sequence to connect a business problem to an accountable investment. Revisit earlier stages when new evidence changes the assessment.
Stage 1: Business Objective
Name the outcome the organization is trying to move, so every later idea has something to be measured against.
Stage 2: Department
Locate the team that owns the objective and the work that feeds it.
Stage 3: Process
Describe how the work actually runs today: steps, handoffs, systems, and exceptions.
Stage 4: People
Capture who performs and depends on the work, and what they know that no document records.
Stage 5: Problem
State the friction in plain terms: delay, rework, error, cost, or risk, with evidence.
Stage 6: Opportunity
Frame a specific improvement that addresses the problem, not yet tied to any technology.
Stage 7: AI/Automation Fit
Compare AI, RPA, IDP, workflow automation, process redesign, and no technology change.
Stage 8: Value
Estimate benefit in the objective's own terms, with assumptions written down.
Stage 9: Feasibility
Check data, systems, skills, and change capacity needed to deliver.
Stage 10: Risk
Surface compliance, quality, security, and adoption risks and the controls they need.
Stage 11: Scoring
Rate each opportunity on the same dimensions so comparisons are consistent and explainable.
Stage 12: Prioritization
Sequence opportunities by score, dependencies, and capacity, with reasons people can challenge.
Stage 13: Investment
Match approved effort to the sequence; people with budget authority decide what gets funded.
Stage 14: Portfolio
Track opportunities over time as a living set: delivered, in flight, waiting, and retired.
Start with one observable journey
Choose one service within one authority and jurisdiction, such as an application-completeness review. Compare an ordinary case, an incomplete submission, and a case using an assisted or nondigital channel. Map the statutory or policy basis for each required step with the service owner.
Where to look across departments
Service front doors and case administration
Follow applications returned for unclear instructions, missing evidence, or inconsistent case references. Look at contact-center, counter-service, and digital routes together. A simplified form, translated guidance, or fewer unnecessary evidence requirements may address the problem more directly than AI.
Internal policy and evidence preparation
Inspect how caseworkers find current guidance, assemble a file, and prepare a briefing for an authorized decision-maker. Identify the source of each factual statement. Separate retrieving an approved rule from applying discretion or interpreting legal duties in an individual case.
Who to interview and what each person knows
Caseworker, service owner, and service users
Ask a frontline caseworker to reconstruct a returned application and compare the service owner's account. Include an appropriate user-research or representative process for people who face language, disability, or digital barriers. Administrative data alone misses those who never complete an application.
Records, legal, access, and procurement owners
Include information governance, legal, accessibility, security, and procurement leads relevant to the authority. Ask who owns records, complaints, appeals, and supplier oversight. A prototype's technical feasibility does not establish authority to use it for a public function.
What to ask: follow the evidence
Why was this evidence required?
Ask which requirement comes from law, policy, local practice, or an obsolete form. Who can simplify it? Was the information already held and lawfully reusable? Document the distinction instead of assuming every existing step should be automated unchanged.
How can someone understand and challenge the result?
Ask what explanation, records, human contact, and appeal route must be available. What happens when a person cannot use the digital channel? Capture how errors are corrected and which outputs must never be treated as an authorized decision.
Signals of opportunity, and reasons to look elsewhere
Repeated preparation with a clear legal basis
A bounded completeness or source-finding task may merit investigation when staff can verify evidence and the authority can explain the purpose. Inconsistent local guidance or unclear decision ownership is a prerequisite issue. Do not convert discretionary casework into a prediction task simply because historical decisions exist.
Avoidable burden on the public
Repeated requests for the same evidence can show a service-design or data-sharing problem. Check whether a policy change removes the burden altogether. Reduced internal effort is not a sufficient benefit if it shifts more work to residents or excludes people who need assistance.
Industry-specific risks and constraints
Rights, equity, and public accountability
Eligibility, enforcement, and resource-allocation decisions can affect rights and access. Relevant obligations differ by authority and jurisdiction; qualified owners must assess them. Preserve explanations, human accountability, accessible channels, and challenge routes rather than treating them as optional features.
Records and supplier constraints
Assess records retention, disclosure duties, permitted data use, hosting, procurement, security, and supplier exit with the responsible teams. Do not infer a compliance status from a vendor description. Discovery evidence should identify the local requirement and who can verify that it is met.
How to evaluate what you find
Test service access as well as accuracy
Use approved cases with missing evidence, conflicting guidance, and relevant accessibility or language needs. Check source references, omissions, staff review, and a practical nondigital fallback. Assess who benefits and who faces new burdens; an average result may conceal systematic exclusion.
Keep a defensible public-value record
Compare service quality, public effort, staff rework, delivery cost, and ongoing oversight. Record assumptions and alternatives, including simplifying the service without new technology. The authority should be able to explain why the candidate is proportionate before approving a trial.
How to compare, prioritize, and invest
Start with inspectable administrative support
Prefer a bounded task staff can verify before any public-facing consequence. Sequence policy clarification, accessibility fixes, and records foundations first where needed. Keep rights-affecting decisions in a distinct assessment rather than expanding an administrative trial without renewed authorization.
Invest through accountable service governance
Rank candidates by public value, lawful feasibility, inclusive access, and delivery capacity after oversight costs. Name the service owner and approval body. Define stop conditions for exclusion, unsupported guidance, or loss of records, and document why other opportunities were deferred.
Turn observations into a comparable opportunity record
Describe the current process before naming a solution. Record the trigger, owner, input, steps, handoffs, systems, output, and exception path. Separate what you observed from what someone recalled and what you still need to verify. A vivid interview story is a useful lead, not proof that every case behaves the same way. Validate it against a sample of ordinary work and difficult exceptions, with the limits of that sample made explicit.
Measure active work separately from waiting. Note the observation period, case mix, frequency, and source of each estimate. Include the receiving team's effort, checking, correction, and escalation so a local improvement does not merely transfer work. Describe the outcome in operational terms before attaching a monetary value. Capacity released is not automatically a budget saving; explain what can actually change and which manager has authority to make that change.
Compare interventions before selecting a tool
If a rule is explicit and the input is structured, test ordinary workflow automation first. If the task repeats a stable interface action, examine RPA and an integration alternative. If the difficulty is reading documents, consider IDP with source checks. AI may help where language or variable evidence requires interpretation, but its output still needs a task-specific acceptance standard. Process redesign or no technology change may be the right answer when policy, ownership, or an unnecessary step causes the problem.
Write down why each alternative would or would not address the observed cause. Do not compare a carefully controlled AI proposal with an artificially weak version of the current process. Include data repair, access approval, integration, training, review, and upkeep in each feasible option. An unavailable prerequisite is a reason to sequence work or pause, not a detail to hide inside a feasibility score.
Agree on a decision, not just a demonstration
Before a trial, name the business owner, evaluator, permitted data, review boundary, and person who can stop it. Define acceptable outputs and failures that must trigger escalation. Use examples held out from development, including missing information and uncommon cases. Compare the complete task with the baseline, including human verification and downstream consequences. Preserve the evidence behind the result so another owner can challenge the conclusion.
Keep value, feasibility, risk, and evidence confidence visible separately. A candidate with an attractive benefit estimate is not ready if its owner cannot obtain the data or operate the controls. Record the decision to investigate, pilot, wait, reject, or retire, with a reason and a condition for revisiting it. After delivery, compare observed results with assumptions rather than leaving the original estimate in the portfolio as fact.
Use the evaluation guide for the evidence standard and the prioritization guide to compare qualified candidates. Your leaders make funding decisions; a score or a discovery tool supplies structured evidence, not investment authority.
IntakeOS for government
For IntakeOS's public-sector offering and engagement information, continue to the existing government page. This discovery guide covers where to investigate opportunities; the government page remains the product-specific destination.
Continue to IntakeOS for governmentContinue through the discovery framework
Browse all departments and industriesRelated practice notes
For focused interview techniques, examples, and scoring detail alongside this field guide:
Bring a public-service workflow into IntakeOS
Use a sanitized service map, the applicable constraints, and the accountable owner. Explore IntakeOS discovery without submitting personal case files or assuming that qualification replaces your authority's legal, procurement, or investment approvals.
IntakeOS supports structured interviews, qualification, and comparison; it does not make funding decisions or replace professional review. Learn about VARA, review the trust page, or explore the platform before sharing sensitive information.
Explore discovery in an IntakeOS demo