1. Beneficiary Tracking
  2. Features
  3. Follow-up and Corrections
Feature · Follow-up and Corrections

Follow-up and Corrections

Assign outstanding case work and preserve the history when an executed revision needs correction.

OverviewMy Follow-up Actions
Beneficiary Tracking · Follow-up and Corrections

My Follow-up Actions

Follow up actions

New
TitleSourceDue dateStatusCompleted atResolution
Open fua-655SA-7172708 OctOpenRSL-767
In progress fua-412SA-1964026 OctIn progressRSL-217
Completed fua-603SA-8062607 OctCompleted11 OctRSL-988
Cancelled fua-876SA-5476722 OctOpenRSL-903
Open fua-412SA-3062125 OctIn progressRSL-918
6 of 6 records
Open fua-655Follow up actions · FUA-82999
Open
SourceSA-71727
Due date08 Oct
ResolutionRSL-767
Example screen with sample data

What you can do

Keep the outstanding action with the case

A missing document or an uncertain delivery result needs a responsible person and a due date. The Citizen Service Portal Operator creates an action against the service application and assigns it to a staff member. The person receiving the work can read the case context and record a resolution when the issue is addressed. This keeps the next step visible when the original operator is away.

Some follow-up changes an application that has already been executed. The correction process preserves the earlier revision, completed steps, evidence and review decisions. A successor revision goes to independent review. When the correction supersedes a delivery, an explicit compensating action records the work needed to address the earlier service outcome.

How the work is organized

  • Assigned action. Record a clear title, responsible person and due date. Keep an action Open while it waits to begin, then track the work in progress as staff handle it. The linked application supplies the beneficiary and service context.
  • Recorded resolution. Complete the action with a resolution and completion time when the requested work is done. If the action is withdrawn, use Cancelled and explain why it no longer needs attention.
  • Controlled correction. Describe why an executed revision needs to change. Preserve the earlier record, route the successor for a new review and retain the compensating action when delivery is superseded.

What to agree during setup

Agree who assigns follow-up work and how staff choose a due date. A document request and a delivery investigation may need different handling, but both need a description that the assignee can act on. Review due work with the person responsible for each case rather than assuming an assignment alone resolves it.

Define the circumstances that require a correction to an executed revision. Ask the service owner what practical action follows when a delivered service is superseded. That may require contact with a separate fulfillment system or another team. Record the responsible person and the resolution in the case; configure any external connection as part of implementation.

Check the handoff on an actual case

Take an illustrative application delivered under the wrong service reference. The operator records the correction reason and starts the successor revision. The earlier delivery evidence remains available so the reviewer can understand the change. A separate action identifies who will investigate the effect of superseding the earlier delivery and when they will report back.

The Citizen Service Portal Reviewer considers the corrected revision independently. After the decision, the operator follows the appropriate delivery work and completes the compensating action only when its resolution is known. Ask a colleague to compare the old and new history. They should see why the change occurred, which revision was approved and whether any corrective work is still outstanding.

What your team sees

  • My Follow-up Actions — Find assigned work with its due date, current state and resolution.
  • Due Follow-up Actions — Review open or ongoing work due today or earlier with the responsible staff member.
  • Application State History — Trace state changes and their recorded actor, reason and revision.

Follow the work through

Rehearse follow-up and correction, then revisit requirements and approval for the successor decision.

What it keeps track of

Data model
Follow up actions
Assigned outstanding actions, corrections and outstanding requests for a case.
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.
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.
Evidence documents
Uploaded and verified supporting documents and source evidence.
People
Staff, officers, reviewers and assigned team members.

Who uses it

Permissions
Citizen Service Portal Operator
, Citizen Service Portal Reviewer, Read Only Analyst.
The operator manages corrective work; the reviewer decides the successor revision.

Set up Beneficiary Tracking your way.

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

How to get started