Keep the order line, delivered quantity, usable quantity, damage, and outstanding quantity together. A procurement SOP should explain who checks the evidence and who handles the discrepancy, while preserving the original request and order references.
Connect the request to the actual authority and order
SUNY's requisition procedure describes an authorized request and checking received quantities and condition against the issued purchase order. Its specific institutional payment and document-routing rules are not transferred to this example. Use your organization's own authority and receiving instructions. SUNY's purchase requisition procedure
The original fictional request REQ1 identifies a need for office paper packets, with unit packet and quantity 20. An approved-request record is supplied for illustration, and PO1 line 1 is recorded as issued by a designated fictional buying role. These demonstration records do not mean this review approved a request or placed an order.
For an actual reusable SOP, put the requester, authorized approver, designated buyer, receiver, and discrepancy contact beside the records each role uses. Their names, authority reference, approved request location, and issued order reference must come from the organization. A request prepared for approval is not an approved request. An approval record is not an issued purchase order.
Preserve item, unit, and line identity at receiving
Before counting, compare the delivered item and unit with PO1 line 1. Do not combine another order line or a different unit into the total. Record delivery D1 against the same request, PO, and line, then separate the supplied quantities:
| Quantity category | Packets | Meaning in the fictional record |
|---|---|---|
| Ordered on PO1 line 1 | 20 | Original line quantity |
| Arrived in D1 | 14 | Includes usable and damaged packets |
| Recorded usable | 12 | Usable portion of this delivery |
| Recorded damaged | 2 | Arrived, with damage recorded |
| Not yet arrived | 6 | Outstanding portion of the original line |
The delivery reconciles as 14 = 12 + 2. The original order reconciles as 20 = 12 + 2 + 6. The damaged packets have arrived, so they are not part of the six that have not arrived. Neither fourteen arrived nor twelve usable means the twenty-packet order is fully received.
This is an illustrative quantity record, not an actual physical inspection. In maintained records, attach the real observation, date, receiver, and authorized condition decision. Do not infer supplier fault from a damage count alone.
Route the discrepancy without resolving it by assumption
The receiver records D1's partial delivery and damage against the exact order line. Then the designated buying role reviews the discrepancy using the actual organization's process. A complete query draft for review is:
Delivery D1 for REQ1, PO1 line 1, records 14 of 20 paper packets arrived: 12 usable and 2 damaged. Six packets have not arrived. Please confirm the authorized next steps for the damaged packets and the evidence needed to follow up on the outstanding six. No full-receipt claim has been recorded.
This draft has not been sent. Leave the actual query recipient, response, agreed next step, and follow-up date blank until supplied. Do not promise replacement, disposal, return, or a new delivery date. Those decisions need the relevant evidence and authority.
When another delivery occurs, preserve D1 and add a separately identified delivery record for the same PO line. Check what arrived and its condition before changing the outstanding quantity. Avoid creating a second order or counting the first fourteen again. Damage resolution should remain separate from the missing-delivery follow-up unless the actual records establish a connection.
Use explicit record gates
The procedure runs from intake to authority check, issued-order reference, same-line receiving, discrepancy record, authorized handoff, and remaining-delivery check. Missing approval or order evidence blocks a claim that those steps occurred. Missing follow-up evidence remains missing; a walkthrough is not a completed transaction.
The companion reveals REQ1, PO1 line 1, and D1 in sequence and showss the partial-delivery branch. Its purpose would be to make the quantities and blank follow-up evidence inspectable. It should not update stock or offer order, send, or pay controls. Actual purchasing actions and maintained records remain outside the companion.
Copy this prompt for the partial-delivery SOP
Create one complete, self-contained US-English HTML companion for “REQ1 / PO1 • partial receiving packet”. Return the full HTML document, with inline CSS and any JavaScript needed for the local interactions. Use the original scenario, named records, numbers and expected cases below.
Design the page for this task: use clearly labeled input or source records, a readable result or worked example, and an adjacent explanation of the evidence. Use a restrained visual hierarchy, left-aligned text, readable tables or stacked records, and a responsive layout at 720px and 360px. Provide meaningful labeled controls for 1 · Request; 2 · Issued order record; 3 · Receiving; Review quantity packet; Restore D1 specimen; Select query text; Prepare text; Select text. Use keyboard-accessible native controls and visible focus. Keep the complete content readable without an external dependency.
The following brief supplies the substantive content and constraints. Native-format requests describe the material to represent or copy manually; this HTML must not pretend to create DOCX, XLSX, PDF, PPTX, H5P or another native file, run Python/Flask/Django/Snowflake/Power BI, connect a live service, send messages, or perform an authorized real-world action. Where the task requires a native source, actual observation or separate approval, retain that requirement and leave unsupplied evidence blank.
Prepare a complete US English procurement SOP review packet for an original fictional paper-packet order. Include roles/authority references to confirm, a request-order-delivery walkthrough, quantity reconciliation, discrepancy query draft and blank follow-up record. Do not purchase,approve,send,pay or update stock. REQ1 identifies need/item paper packets,unit packet,quantity20. Approved-request record is supplied for illustration only. PO1 line1 is recorded as issued by designated fictional buyer; actual authority/order evidence is required in real use. D1 arrives against the same item/unit/line:14arrived=12usable+2damaged. Sixnotarrived. Ordered20=12usable+2damaged+6outstanding. Arrived is not all usable and not full receipt. Keep requestID,POID,lineID,deliveryID,item/unit and originalquantity traceable. Steps: intake,check actual authority/reference,record issued order,inspect same line,item andunit,record partial delivery/damage,route query to authorized buying role,check remainingdelivery. Missing approval/order reference blocks the claim that it occurred. Actual condition evidence and decisions must be supplied; no supplier-fault assumption. Give complete review query naming all quantities and requesting authorized damaged-packet steps and outstanding-six follow-up. Leave actualrecipient,response,acceptednextstep anddate blank. Futuredelivery uses newrecord,sameline and no doublecount;preserveD1. Do not promise replacement,return,disposal or deliverydate. Use actual organization receipt workflow; do not invent thresholds,contract/legal/invoice/payment/reimbursement rules. Proposed HTML walkthrough/partial branch requires construction/testing,with noorder/send/pay buttons. Original purchasing record system remains authoritative.
COMPLETE AUTHORED SCENARIO AND EXPECTED CASES
The following is the supplied reading/teaching/calculation record to represent in the companion. Preserve its particular content, examples, source references and unknowns. Wording about a future native implementation refers to that native task, not permission to omit this HTML companion.
# A Procurement SOP Template for Recording a Partial Delivery Correctly
The order calls for twenty paper packets. Fourteen arrive, and two of those are damaged. A receiving note that says “14 received” leaves the next person guessing whether fourteen are usable and whether the order is complete.
Keep the order line, delivered quantity, usable quantity, damage, and outstanding quantity together. A procurement SOP should explain who checks the evidence and who handles the discrepancy, while preserving the original request and order references.
## Connect the request to the actual authority and order
SUNY's requisition procedure describes an authorized request and checking received quantities and condition against the issued purchase order. Its specific institutional payment and document-routing rules are not transferred to this example. Use your organization's own authority and receiving instructions. [SUNY's purchase requisition procedure](https://system.suny.edu/purchasing/requisitions/)
The original fictional request REQ1 identifies a need for office paper packets, with unit `packet` and quantity 20. An approved-request record is supplied for illustration, and PO1 line 1 is recorded as issued by a designated fictional buying role. These demonstration records do not mean this review approved a request or placed an order.
For an actual reusable SOP, put the requester, authorized approver, designated buyer, receiver, and discrepancy contact beside the records each role uses. Their names, authority reference, approved request location, and issued order reference must come from the organization. A request prepared for approval is not an approved request. An approval record is not an issued purchase order.
## Preserve item, unit, and line identity at receiving
Before counting, compare the delivered item and unit with PO1 line 1. Do not combine another order line or a different unit into the total. Record delivery D1 against the same request, PO, and line, then separate the supplied quantities:
| Quantity category | Packets | Meaning in the fictional record |
| --- | --- | --- |
| Ordered on PO1 line 1 | 20 | Original line quantity |
| Arrived in D1 | 14 | Includes usable and damaged packets |
| Recorded usable | 12 | Usable portion of this delivery |
| Recorded damaged | 2 | Arrived, with damage recorded |
| Not yet arrived | 6 | Outstanding portion of the original line |
The delivery reconciles as `14 = 12 + 2`. The original order reconciles as `20 = 12 + 2 + 6`. The damaged packets have arrived, so they are not part of the six that have not arrived. Neither fourteen arrived nor twelve usable means the twenty-packet order is fully received.
This is an illustrative quantity record, not an actual physical inspection. In maintained records, attach the real observation, date, receiver, and authorized condition decision. Do not infer supplier fault from a damage count alone.
## Route the discrepancy without resolving it by assumption
The receiver records D1's partial delivery and damage against the exact order line. Then the designated buying role reviews the discrepancy using the actual organization's process. A complete query draft for review is:
> Delivery D1 for REQ1, PO1 line 1, records 14 of 20 paper packets arrived: 12 usable and 2 damaged. Six packets have not arrived. Please confirm the authorized next steps for the damaged packets and the evidence needed to follow up on the outstanding six. No full-receipt claim has been recorded.
This draft has not been sent. Leave the actual query recipient, response, agreed next step, and follow-up date blank until supplied. Do not promise replacement, disposal, return, or a new delivery date. Those decisions need the relevant evidence and authority.
When another delivery occurs, preserve D1 and add a separately identified delivery record for the same PO line. Check what arrived and its condition before changing the outstanding quantity. Avoid creating a second order or counting the first fourteen again. Damage resolution should remain separate from the missing-delivery follow-up unless the actual records establish a connection.
## Use explicit record gates
The procedure runs from intake to authority check, issued-order reference, same-line receiving, discrepancy record, authorized handoff, and remaining-delivery check. Missing approval or order evidence blocks a claim that those steps occurred. Missing follow-up evidence remains missing; a walkthrough is not a completed transaction.
The companion reveals REQ1, PO1 line 1, and D1 in sequence and showss the partial-delivery branch. Its purpose would be to make the quantities and blank follow-up evidence inspectable. It should not update stock or offer order, send, or pay controls. Actual purchasing actions and maintained records remain outside the companion.
Implement the local companion rather than returning a text-only plan. Preserve every numerical fixture and the distinction between illustrative expectations and actual evidence. Any native-runtime or classroom tests mentioned above remain tests to perform in the proper environment; do not mark them passed. Keep edits and practice responses in this open page only, without claiming persistent storage. Provide invalid/missing-input feedback and reset behavior that agree with this specific brief. Do not claim accessibility certification, learning gains, real approvals or test results that were not observed.
Review the handoff
Use the HTML companion to check that fourteen arrived remains distinct from twelve usable, two damaged, and six outstanding. Keep actual authority, ordering, receiving, and subsequent decisions in the original purchasing workflow.
End the receiving review with the line reconciled and both the damaged two and outstanding six visibly awaiting their documented next steps.