Service Registration

A beneficiary may return to the service desk with a document for an application already in progress. The Citizen Service Portal Operator needs the application number and citizen reference before starting another request. Open the existing case, confirm the service being requested and check its current state. A familiar name alone should not decide which application receives the new information.

The Service Applications Workspace keeps the status board beside the selected case. The operator can move from the board into the requirements, pending review decisions and state history without treating each item as a separate service request. The assigned owner remains responsible for preparing the application and explaining the next handoff to a colleague.

• Application identity. Record the application number, descriptive name and citizen reference. Keep the reference consistent with the organization’s accepted beneficiary identification practice so supporting documents reach the intended case.
• Service responsibility. Select the owning organization and service definition, then assign the responsible staff member. Check the service code against that definition before asking a reviewer to consider eligibility evidence.
• Working state. Prepare the request as Draft and submit it when the required information is ready. Submitted identifies work awaiting validation; Verified identifies the revision prepared for independent review.

Agree who issues application numbers and how staff look up an existing beneficiary reference. Decide which organization owns a request when another agency helps collect the documents. The ownership decision affects the service desk handoff and who may work on the case. It should be settled before a staff member begins entering requirements.

Choose a pilot service with a clear policy reference and recognizable evidence requirements. Assign a Citizen Service Portal Operator and a different Citizen Service Portal Reviewer. Review the staff account mapping during setup so the person opening their work queue sees the cases assigned to them. Confirm which users need read access across the pilot organization.

Use an illustrative request for a community assistance service. The operator registers the beneficiary reference and selects the service definition. A supporting document arrives later that day. The operator opens the same application and records the document against it, then checks the requirement outcome before submission.

Ask the next operator to find that application from the board and explain its owner, service and current revision. They should be able to identify the outstanding requirement without asking the first operator to reconstruct the conversation. After submission, inspect the state history and confirm the review refers to the same case. If the service selection was wrong, correct the preparation through the agreed revision process before relying on a decision.

• Service Applications Workspace — Follow application states and open the selected case with its review and execution context.
• My Service Applications — Find the applications assigned to the current operator and check their submission dates.
• Submitted Application Inbox — Inspect submitted requests before the validation handoff.

Continue with application intake and requirements and approval.