1. Citizen Service Portal
  2. Features
  3. Corrections
Feature · Corrections

Corrections

A delivered application can need a documented correction.

OverviewVerified Applications
Citizen Service Portal · Corrections

Verified Applications

Service applications

New
NumberNameRevisionStatusOwnerDefinition
SA-49963Application 664750VerifiedPS-2793
SA-79788Application 182730VerifiedPS-6259
SA-84675Application 322310VerifiedPS-4145
SA-34280Application 395860VerifiedPS-8821
SA-47558Application 590850VerifiedPS-3448
6 of 6 records
Application 664Service applications · SA-49963
Verified
Revision750
DefinitionPS-2793
Example screen with sample data

What you can do

Corrections in daily work

A delivered application can need a documented correction. The correction workflow preserves the earlier revision, completed operation steps, evidence and decisions. It creates a successor revision for independent review and a compensating follow-up action when delivery is superseded. The original delivery reference and completed steps remain readable after a change. The correction workflow creates a successor revision with a Pending review decision and a compensating follow-up when delivery is superseded.

How the work is organized

  • Prepare the case. A case was delivered, then an operator finds a source detail that changes the outcome. The operator documents the reason, links a follow-up action to the application and sends the successor revision to a reviewer. The previous delivery reference and operation trace remain available to explain what happened first.
  • Keep a named owner. The operator documents why the delivered result must change and inspects the earlier action before preparing the successor.
  • Preserve the trace. The earlier decision, evidence and completed steps stay with the case so the reviewer can distinguish them from the new revision.

What to agree during setup

Agree who can start a correction, how a reason is written and who owns compensating work. A correction must be distinguishable from routine editing of a Draft case. Decide how staff will reconcile any external action already carried out before the replacement decision is acted on. Agree who can start a correction and how its reason identifies the earlier delivery. Name the person who owns compensating work and when it is due. Rehearse an external action that already completed before the replacement decision is reviewed.

Check the handoff on an actual case

Start from one delivered case and read its state history. Follow the earlier review decision and operation steps, then inspect the successor revision and its Pending decision. The follow-up should identify an assignee and due date. Confirm that the original action remains traceable after the new review. Start with a Delivered application and locate its earlier decision, run and completed steps. Then inspect the successor revision and Pending decision. Ask the assigned person to explain the compensating follow-up without changing the earlier action.

What your team sees

  • Open Follow Ups — Find corrective actions with an assignee and due date.
  • My Follow Ups — See the assigned person’s own correction work.

Follow the work through

See executed revision correction for successor review and execution reconciliation for an uncertain earlier result.

What it keeps track of

Data model
Service applications
Requests, applications and cases submitted for a public service.
State history
Immutable workflow-written status transition history for each case.
Review decisions
Independent reviewer decisions recorded against an exact source revision.
Follow up actions
Assigned outstanding actions, corrections and outstanding requests for a case.

Who uses it

Permissions
Citizen Service Portal Operator
, Citizen Service Portal Reviewer.
The operator documents the correction and owns follow-up; the reviewer independently decides on its successor revision.

Set up Citizen Service Portal your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started