Requirements and evidence

A case may need several pieces of information before a decision can be made. Requirement lines retain their sequence, description, source reference, observation date, quantity, unit and amount when those facts apply. The line also has an outcome: Pending, Accepted or Rejected. That outcome belongs to the line, allowing the team to see which part of the request still needs attention.

Supporting documents have a title, attachment, document date and external reference. Verification is recorded against the document with a named person. The case workspace brings the requirement strip and documents close to the current case. This makes the handoff to an independent reviewer more precise than a message saying an application is complete.

• Requirement lines. Keep each observation or requested item attached to the parent case and in its intended sequence.
• Document evidence. Link the attachment to the same case, with its own verification state and verifying person.
• Decision context. Retain the source reference and reason when a requirement is rejected or sent back for correction.

Agree which service requirements must be recorded as separate lines and which attachments support them. Choose a consistent way to enter source references so the operator and reviewer can locate the original submission. Decide who verifies documents and how the team handles a replacement attachment after a case revision. A verified document should be read with its date and external reference, rather than assumed to support every later revision automatically.

For a representative case, enter a line for each requested item and attach the evidence supplied by the applicant. Mark one line Accepted and leave another Pending while its document is checked. The operator should be able to explain the pending item without marking the entire case as decided. The reviewer should see which evidence was verified and by whom before recording a decision.

Open Pending Requirements and identify the parent case, line description and submission date. Open Documents to Verify for that case and check the document title, date and verifying person. Move back to Cases and Details to confirm the line outcomes and document state alongside the current revision. The reviewer can then determine whether the evidence supports approval, return or rejection of that revision.

If a line is rejected, record a reason that tells the operator what to address. If a new document is received, preserve its distinct source reference and verification state. The follow-up owner should be able to close the outstanding request with a resolution, while the previous line and case history remain available to explain the original decision.

• Pending Requirements — Individual lines waiting for an outcome, grouped by parent case.
• Documents to Verify — Supporting attachments awaiting a named verification action.

See requirement review and the decision handoff.