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

Evidence

Supporting documents stay linked to the application they explain.

OverviewEvidence To Verify
Citizen Service Portal · Evidence

Evidence To Verify

Evidence documents

New
SourceTitleDocument dateAttachmentVerifiedVerified by
SA-65721No ed-63322 OctATT-435No
SA-81762No ed-97026 OctATT-987No
SA-44112No ed-66622 OctATT-940No
SA-17312No ed-61007 OctATT-882No
SA-14573No ed-71722 OctATT-389No
6 of 6 records
No ed-633Evidence documents · ED-63776
No
SourceSA-65721
Document date22 Oct
AttachmentATT-435
Example screen with sample data

What you can do

Evidence in daily work

Supporting documents stay linked to the application they explain. Each evidence record carries a title, attachment, document date, external reference and a verification value. The verifying person is recorded separately from the operator who prepares the application. The attachment and its verification value belong to the same application. A named verifier can be traced through the person reference. The reviewer reads that record with the requirement outcome before making an independent decision on the source revision.

How the work is organized

  • Prepare the case. An operator attaches a document to a submitted request and records its external reference. Its verification value remains No until a named person checks it. The reviewer opens the application and compares the evidence with the relevant requirement outcome before deciding on the frozen revision.
  • Keep a named owner. The operator attaches the document to the correct application and records its date or external reference. A named person checks it and records the verification value.
  • Preserve the trace. The evidence stays linked to the case after a review decision. If a delivered application is corrected, the earlier evidence remains available beside the successor review.

What to agree during setup

Agree which documents are required for each public service and who is authorized to verify them. Define a consistent title and external reference scheme so a later correction can identify the same source. Keep the attachment and its verification record together in the case. Agree which document types matter for each public service and who can verify them. Use a consistent external reference when an attachment arrives from another source. Rehearse the case where a document belongs to the wrong application.

Check the handoff on an actual case

Use one application with an attachment and check its title, date, verification value and verifying person. The requirement line should point to the same case. When the application goes for review, the reviewer should be able to inspect the document alongside the current requirement outcomes and case history. Choose one document marked No and ask the verifier to locate its attachment, date and source application. After verification, ask the reviewer to compare it with the requirement outcome and the pending decision’s source revision.

What your team sees

  • Evidence To Verify — Open documents marked No with their application and verifier.
  • Submitted Applications — Return to the case before deciding whether its evidence is complete.

Follow the work through

See application review for evidence checks before validation and executed revision correction for later changes.

What it keeps track of

Data model
Evidence documents
Uploaded and verified supporting documents and source evidence.
Service applications
Requests, applications and cases submitted for a public service.
People
Staff, officers, reviewers and assigned team members.

Who uses it

Permissions
Citizen Service Portal Operator
, Citizen Service Portal Reviewer.
The operator prepares the document record.
The reviewer reads the verification result as part of the independent case decision.

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