These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Citizen Service Portal
- Features
- Delivery
Delivery
An approved application proceeds through a caseworker decision and delivery.
OverviewDelivered Applications×
Citizen Service Portal · Delivery
New
Delivered Applications
Service applications
| Number | Name | Completed at | Delivery reference | Definition | Status | |
|---|---|---|---|---|---|---|
| SA-78657 | Application 902 | DR-927 | PS-1211 | Delivered | ||
| SA-44109 | Application 820 | DR-497 | PS-7364 | Delivered | ||
| SA-76703 | Application 475 | DR-390 | PS-1692 | Delivered | ||
| SA-92423 | Application 516 | DR-437 | PS-7686 | Delivered | ||
| SA-21488 | Application 629 | DR-863 | PS-4355 | Delivered |
6 of 6 records
Application 902Service applications · SA-78657
DeliveredDelivery referenceDR-927
DefinitionPS-1211
What you can do
Delivery in daily work
An approved application proceeds through a caseworker decision and delivery. The application holds the delivery reference and completion date. Operation runs and ordered steps retain the operation key, source revision, result reference and any external receipt evidence for the action performed. The run records an operation key and source revision; its steps retain input, output and receipt details. Staff compare those records with the application’s delivery reference when an outcome is uncertain.
How the work is organized
- Prepare the case. After an independent approval, the caseworker records the decision and begins delivery. The operation run moves from Queued through Running to an outcome. Its steps carry input and output references. The application becomes Delivered after the delivery result is recorded; the trace lets staff connect that result to the approved revision.
- Keep a named owner. The operator records the caseworker decision after approval and follows the keyed operation before recording delivery.
- Preserve the trace. A failed run or Unknown step stays in the trace. The operation key and provider reference help staff investigate an earlier attempt.
What to agree during setup
Agree which service action constitutes delivery and what result reference proves completion. If a provider returns an uncertain result, staff should inspect the operation key and receipt before deciding whether another attempt is appropriate. Assign responsibility for runs that need reconciliation. Agree which result reference proves delivery for each public service. Name the person who investigates failed runs and uncertain receipts. Rehearse two attempts with the same operation key and confirm staff read the earlier provider reference before a retry.
Check the handoff on an actual case
Choose a delivered application and trace its operation key through the run, steps and any execution attempts. Match the result reference to the application’s delivery reference. Confirm that a failed or uncertain step remains visible and that the team can explain which revision authorized the action. Start at a Delivered application and find the run for its approved revision. Compare its result reference with the delivery reference, then inspect the ordered steps. Repeat with an uncertain attempt and confirm the operator investigates its receipt before taking another action.
What your team sees
- Delivered Applications — Read completion dates and delivery references for finished cases.
- Runs Requiring Reconciliation — Find keyed runs whose result needs investigation.
Follow the work through
See decision to delivery for the approved path and execution reconciliation for uncertain results.
What it keeps track of
Data model- Service applications
- Requests, applications and cases submitted for a public service.
- Operation runs
- Workflow-maintained execution runs with operation key, input hash and persisted result reference.
- Operation steps
- Ordered steps inside an operation run with input, output and external receipt state.
- Execution attempts
- Each recorded attempt to execute an approved action for a service application.
Who uses it
Permissions- Citizen Service Portal Operator
- , Citizen Service Portal Reviewer, Read Only Analyst.
- The operator follows delivery; the reviewer owns the prior approval; the analyst reads completed outcomes.
Set up Citizen Service Portal your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.