Requirements

Each service application can carry ordered requirement lines. A line records its description, observation date, source reference and outcome. The operator can keep a pending line visible while evidence arrives, then record Accepted or Rejected with a reason where needed. The child lines appear with the selected application in the Service Applications Workspace. The operator can compare a line’s sequence, outcome and source reference before validation. A Pending line remains visible so the next person knows which evidence or explanation is still needed.

• Prepare the case. For a submitted application, the operator checks the service requirement lines. One line remains Pending because its source reference needs clarification. The operator assigns a follow-up action with a due date and the person responsible. After the correction, the line is reviewed again before the application is validated.
• Keep a named owner. The operator assigns an unresolved request to a named person in a follow-up action. Its due date gives the next shift a concrete item to check before validation.
• Preserve the trace. The line outcome stays tied to its parent application. A rejected line’s decision reason helps the reviewer understand why the operator did not accept it.

Agree how a requirement is described, which source reference supports it and when an outcome can change. Decide how the operator records a rejected line and what evidence a reviewer needs to understand the decision. Keep the completed requirement count aligned with the actual child lines. Agree how staff identify a requirement line, what source reference supports it, and who can mark an outcome Accepted or Rejected. Reconcile the completed requirement count with the child lines before submitting a case for validation.

Open a submitted case and inspect its pending requirements in sequence. Compare each outcome with the source reference and any decision reason. Confirm that a follow-up assigned to a person is attached to the same application. A reviewer should see the unresolved line before making a decision on the revision. Give the reviewer the application number and a line left Pending. Ask them to find the line, its source reference and the related follow-up. After the operator resolves it, compare the revised outcome with the application revision sent for review.

• Pending Requirements — Find unresolved lines by parent application and sequence.
• Rejected Requirements — Read each rejected line with its recorded reason.

See application review for the validation handoff and executed revision correction when an earlier outcome changes after delivery.