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
- Decisions
Decisions
The validation workflow freezes the submitted application revision and routes it to an independent reviewer.
OverviewPending Review Decisions×
Citizen Service Portal · Decisions
New
Pending Review Decisions
Approval conditions
| Source | Source revision | Reviewer | Decision | Evidence reference | |
|---|---|---|---|---|---|
| SA-85142 | 100 | Pending | ER-388 | ||
| SA-53377 | 580 | Pending | ER-751 | ||
| SA-70461 | 300 | Pending | ER-163 | ||
| SA-25667 | 630 | Pending | ER-601 | ||
| SA-16951 | 210 | Pending | ER-454 |
6 of 6 records
ER-388Review decisions · RD-44164
PendingSourceSA-85142
Source revision100
What you can do
Decisions in daily work
The validation workflow freezes the submitted application revision and routes it to an independent reviewer. The review record names that revision, its reviewer, a Pending, Approved, Returned or Rejected decision, the decision date and the reason. The reviewer must be independent of the person preparing the case. The pending decision names the exact source revision and reviewer. They read requirement outcomes and evidence before choosing Approved, Returned or Rejected. A reason on a returned or rejected decision tells the operator what to address.
How the work is organized
- Prepare the case. An operator validates a submitted application after its requirements and evidence are checked. The reviewer receives a pending decision for that source revision. If something needs correction, the reviewer records Returned with a reason; after the operator changes the application, the successor revision goes through review again.
- Keep a named owner. The reviewer compares the pending decision’s source revision with the application revision and records a reason when sending work back.
- Preserve the trace. The earlier decision remains readable when a successor revision goes for review.
What to agree during setup
Agree who can review each organization’s applications and how independence is checked. Decide what a useful reason must contain for Returned or Rejected decisions. A change to the application after review should start a new revision rather than silently changing the record on which the approval was based. Agree which reviewers can act for each organization and how staff check independence from preparation. A Returned or Rejected reason should identify the specific requirement or document needing work. Test a changed application whose old review record still points to an earlier revision.
Check the handoff on an actual case
Open a verified application and its pending review record. Compare the source revision with the case revision and confirm that the reviewer is a different person from the preparer. Record the decision and inspect the state history. A later correction should leave the original decision readable. Give the reviewer a Verified application and its Pending decision. Ask them to compare source revision, requirement outcomes and verified evidence before deciding. On a Returned result, ask the operator to explain the next action using only the recorded reason.
What your team sees
- Pending Review Decisions — Find decisions waiting for the assigned reviewer.
- Verified Applications — Check the application revision and owner beside the review record.
Follow the work through
See application review for the first decision and decision to delivery for approved work.
What it keeps track of
Data model- Review decisions
- Independent reviewer decisions recorded against an exact source revision.
- Service applications
- Requests, applications and cases submitted for a public service.
- People
- Staff, officers, reviewers and assigned team members.
- State history
- Immutable workflow-written status transition history for each case.
Who uses it
Permissions- Citizen Service Portal Reviewer
- , Citizen Service Portal Operator.
- The reviewer decides independently; the operator prepares a successor revision when work is returned.
Set up Citizen Service Portal your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.