Requirements & Documents

Keep requirement observations and document checks attached to the request. The team should be able to start at a request and reach the branch, material, people and evidence that explain the next decision. The main work screen is the Loan Requests Workspace, where the status board and selection-driven request detail keep the current case beside its history, requirements and pending decisions.

A loan request needs evidence for a lending condition. The operator records a requirement description, its source record ID and outcome, then attaches a supporting document to the same request. A verifier records whether the document was checked and who performed that check.

• Ownership. Operators collect and correct evidence. Reviewers read the requirement outcomes and document checks when judging the revision; administrators read the records when an intake rule needs clarification.
• Evidence. Keep the request’s linked records and source revision together so a later reader can reconstruct the action.
• Status. Read the saved status and decision values before moving the case forward or assigning a correction.

Agree which requirement outcomes staff use for incomplete and accepted material. Decide what belongs in the source reference, what attachment types staff will accept and how they will identify a document already present on the request. Keep the checks tied to the current request revision so a later correction is understood.

Each requirement line carries an outcome and source record ID. The Library Circulation Operator can compare those lines with the supporting attachment and its verification value. A line marked Accepted should still point to the source that supports it, while a rejected line needs a clear next action before review.

Choose one submitted request and inspect every requirement line. Each source record ID should identify a distinct observed item. Open the attached document, confirm its title and date, and verify that the person named as verifier performed the check. Compare the completed requirement count with the lines before moving the request to verified.

Give a second operator the request number and ask them to reconcile the requirement outcomes with the attached document. They should identify the source of each line, the person who verified the attachment and any line still Pending or Rejected. A completed count is useful only when it agrees with the recorded line outcomes.

• Unverified Supporting Documents — Attachments waiting for a recorded verification decision.
• Loan Request Board — Requests grouped by their current status for a quick handoff check.

Follow request intake, evidence review and decision and delivery. Use the data model to check record ownership and references during setup.