Requirements and Evidence

A service application can contain the correct beneficiary reference and still need more evidence before review. The Citizen Service Portal Operator records each requirement against its parent application, with a description and sequence that another staff member can follow. Pending means the check still needs attention. Accepted and Rejected record the result of that requirement check.

Supporting documents carry their own verification state. A document marked Yes for verification identifies a completed evidence check with a named verifier. The operator should still explain how that document supports the application requirement. The independent reviewer needs enough context to assess the request without guessing why an attachment was included.

• Requirement detail. Capture the observation date and source record identifier with the requirement description. Where the service calls for quantity or amount information, enter it with the relevant unit and retain the source reference.
• Document verification. Keep the attachment, document date and external reference together. Name the staff member responsible for verification and record Yes or No according to the actual check.
• Review preparation. Resolve outstanding requirement questions and explain rejected evidence before validation. The requirement outcome and application decision remain separate parts of the case record.

Agree the requirement wording for the pilot service and the evidence the operator will inspect. Decide how source identifiers are assigned to requirement lines and what staff should write when an attachment is unreadable or belongs to another application. Use a consistent explanation so the next person can understand the issue from the case.

Choose who may verify documents and how a replacement attachment is handled before submission. The Citizen Service Portal Reviewer needs the evidence for the revision being decided. If the underlying evidence changes after that review, use the agreed correction route. Keep the prior decision and its evidence available to explain what was considered at the time.

Rehearse an application whose address document is initially unreadable. The operator records a Pending requirement and marks the document No for verification. An assigned follow-up requests a readable copy. When it arrives, the operator checks the attachment against the application and records the verification outcome with the responsible person.

Before validation, ask the reviewer to trace the accepted requirement back to the document. They should see which application it supports and why it was accepted. Repeat with a document belonging to a different beneficiary: the operator should explain the rejection and keep the application from reaching the review handoff as if the evidence were complete. This rehearsal tests the team’s evidence practice as well as its use of the screen.

• Requirements Awaiting Review — Work through Pending requirement checks with their source identifiers and reasons.
• Unverified Evidence — Inspect documents still marked No and identify the responsible verifier.
• Submitted Application Inbox — Check the submitted revision before validating its requirements.

Use requirements and approval for the decision handoff and follow-up and correction when evidence changes later.