Define the procedure boundary

Define the procedure boundary — guided practice

Identify the reader, trigger, and completion evidence for a loan request.

Fictional date-counting rule: duration equals return date minus pickup date, using elapsed calendar days. June 3 to June 8 is 5 days; June 3 to June 10 is 7 days and passes the duration limit; June 3 to June 11 is 8 days and goes to Lee. Use a text editor, a free document editor, or paper. Start from the following fictional records; they reset this lesson even if your earlier answer differed. North Room lends display stands. Assistant Jo processes requests. Policy: a request needs a member ID, pickup date, return date and quantity. Maximum loan is 3 stands for 7 days. Missing fields go back for clarification; excess quantity or duration goes to supervisor Lee. The procedure ends with either a confirmed reservation ID or a logged pending reason. Request R1: member M7, pickup June 3, return June 8, quantity 2.

1. 1. Name the reader

   Write who performs this procedure and what they already need access to.

   You should see: Assistant Jo, with the request form, availability list and reservation log.

   A named reader prevents instructions that silently assume manager authority.

2. 2. Mark the trigger

   Write the exact event that starts the work.

   You should see: A new stand-loan request arrives.

   A repeatable trigger makes work easy to find and assign.

3. 3. Define the finish

   Write the two allowed ending states and their evidence.

   You should see: Confirmed with reservation ID, or pending with reason and owner.

   A request can be handled correctly even when it cannot be approved.

4. 4. Trace R1

   Check the policy fields and identify the next check without reserving stock yet.

   You should see: R1 is complete and within the quantity/duration limits; check availability next.

   Completeness and policy eligibility do not prove stock is available.