AI governance for Public sector
Industry · Public sector
Public sector: follow a service user’s request between teams
An agent prepares a progress update for a service user and passes their file on. The integrator needs to explain what was received, reviewed and taken on. A message sent to the right service does not establish that last point.
With the service’s operational contact, prepare two decisions: which handover may proceed and what the applicant may be told. The proposed record keeps the case state, the material passed on and the confirmations needed.
In brief
The question and the useful result.
- Question
- Which service handover may proceed, based on which records, and what progress information may be shared with the applicant?
- Useful result
- A handover record with permitted information and two separate outcomes: acceptance of the case and sending the progress update.
AI governance for Public sector
Give each stage of the case a precise meaning
Define useful states with the services involved: request received, file assessed as complete, transfer requested, handover confirmed. Each state points to a source, a date and a specific conclusion.
Also define the scope of the replies being prepared. An agent may be assigned to draft a progress update or a request for a document. That scope does not give it authority to award support, deny an entitlement or determine eligibility.
In the proposed workflow, decisions affecting rights remain outside the coordination mission. Identify the appropriate people or bodies separately and the information they need to receive. An approval in a workflow does not remove the need to examine the decision-maker’s authority, the case and the requirements applicable to the decision.
AI governance for Public sector
Prepare a handover the receiving service can understand
The receiving service needs to find the request, documents examined, missing information and next action expected. Reference the necessary documents and their versions. A full copy is not always useful; a link may be insufficient if the service cannot open it.
Agree with the client which data each service may access and which operations are permitted. Reading a file to prepare its allocation does not authorise changes to the applicant’s request or disclosure of every document to another recipient.
Name the case coordinator, intended service and condition for accepting the handover. You can agree to keep the current contact until the handover is confirmed. The teams need to agree on those responsibilities; they cannot be inferred from a job title.
AI governance for Public sector
Scenario: a transfer was requested, but the handover is unconfirmed
In this illustrative example, a council reception team is following an application for local support. The agent prepares an administrative summary and a list of the documents present for the team that assesses applications. It proposes neither awarding nor refusing support. No validated DUBSAR business-system or email integration is assumed.
The designated person approves the material to be passed on and its recipient. The workflow issues the transfer request. The system returns a submission acknowledgement, but allocation to the assessment team has not been confirmed.
| Available record | Conclusion supported in the scenario |
|---|---|
| The applicant’s request has been recorded | The reception team has an identifiable request; this does not establish that the file is complete. |
| Approval of the summary and documents to pass on | The handover is authorised within that scope. |
| Transfer attempt and submission acknowledgement | The system received the transfer request. |
| Allocation remains unconfirmed | The receiving service’s acceptance of the case still needs to be checked. |
The progress message should therefore not announce that assessment has started. The team retains ‘transfer requested, handover awaiting confirmation’ and assigns the check. Information sent to the applicant reflects only established facts, with the agreed contact for the next step.
AI governance for Public sector
A service handover and applicant update record
This record can be used with the council’s or public body’s existing tools, independently of DUBSAR. It describes neither an available feature nor an automatic product export.
Coordination mission and request reference: …
Latest established state, source and date: …
| Handover stage | Information to record |
|---|---|
| Prepare the file | Purpose of the request, documents examined and their versions, missing documents and the next question to address. |
| Define the data scope | Material needed by the receiving service, permitted access, excluded documents and links it can actually open. |
| Assign the next step | Current case coordinator, intended service, contact for checking the result and agreed condition for accepting the handover. |
| Obtain a decision | Person authorised to approve the transfer or reply where required; material reviewed, decision, limits and date. |
| Take the external action | File transfer or applicant message: the exact action, recipient, content and documents authorised. |
| Examine the evidence | Attempt reference, meaning of the acknowledgement, expected confirmation of allocation or sending; distinguish these two outcomes. |
| Address an unknown | State to retain, authorised check to make, person deciding the next step and review date. |
Handover decision: continue preparation / transfer within the defined scope / request a decision on an unresolved point.
Progress information that may be shared at this stage: …
Decision affecting rights: outside this mission; person or body to refer it to: …
AI governance for Public sector
Do not close the case follow-up on a technical acknowledgement
A transfer may be confirmed while sending the applicant’s message remains uncertain. Keep those outcomes separate so that the receiving service can find the outstanding check.
If the acknowledgement confirms only submission of the request, consult the case state where access is authorised and available. Do not automatically create another case or transfer to obtain a response. If the check remains inconclusive, retain the unknown and have the next step decided.
AI governance for Public sector
Frequently asked questions
Can a progress message announce a decision affecting rights?
It should not turn an administrative state into a decision. If a decision needs to be communicated, retrieve its source, authorised decision-maker, scope and permission to communicate it. The coordination mission described here does not make that decision.
Should every document be passed to the next service?
Define the material needed for its next action and the permitted access. References need to remain accessible. Examine documents with no established purpose in this handover before any transfer.
Does an acknowledgement mean the next service has taken over?
Only if the available response actually confirms that handover according to the system’s verified behaviour. A technical acknowledgement may mean only that the request was submitted. In that case, keep the handover unconfirmed and assign a check.
AI governance for Public sector
Where DUBSAR is intended to fit
DUBSAR is developing a foundation that connects durable mission state, authorisations, human decisions and evidence alongside existing tools. For this workflow, the intended benefit is to recover what was passed on, what was permitted and what the services actually confirmed, while keeping unresolved questions visible during handover.
Selected workflows have been tested; full B2B integration and validation are still underway. Pilots are not currently open.
AI governance for Public sector