A site receiving discrepancy report should be a time-stamped factual report linking the delivered handling unit, shipment documents, count observation, visible condition, photographs, temporary protection and escalation route without assigning unsupported cause or liability. Its release question is whether a receiving exception is sufficiently identified and preserved for the authorized commercial, logistics, quality or site role to investigate and direct next action. Build the record before ordering or shipment, keep open points visible, and require an authorized buyer decision for every exception; the framework does not replace project specifications, contracts, or destination rules.
Author: Andy, Director of Operations
Technical reviewer: Andy, Director of Operations
Last substantive review: September 2, 2026
Corrections: Send documented corrections through the HOMESEE contact page.
Editorial note: The author and arrival reviewer are the same confirmed HOMESEE representative; this is not an independent technical review. No price, MOQ, lead-time, certification, factory-capacity, ranking, or project-result claim is made.
Table of contents
- The procurement authorized disposition this record controls
- Minimum fields and receiving observation
- A step-by-step workflow
- A exception-escalation gate matrix
- Category and edge-case handling
- Governance and investigation update control
- Buyer checklist
- HOMESEE RFQ review
- Sources
What procurement authorized disposition does a site receiving discrepancy report control?
A receiving discrepancy report should preserve facts before packages are moved, opened or distributed. It is not a damage claim or liability authorized disposition. Its purpose is to make the observed count, mark, seal, arrival exception receiving boundary condition and receiving arrival record mismatch traceable to the correct shipment and receiving event.
The core deliverable is a time-stamped factual report linking the delivered handling unit, shipment receiving arrival records, count observation, visible condition, photographs, temporary protection and escalation route without assigning unsupported cause or liability. It should be readable as a authorized disposition record rather than a marketing presentation. The escalation-ready test is whether a receiving arrival discrepancy is sufficiently identified and preserved for the authorized commercial, logistics, quality or site role to investigate and direct next action. If the receiving crew cannot answer that question from factual arrival records, discrepancy report is not ready, even if individual participants believe they remember the answer.
This guide describes a buyer-side control method. It does not establish a legal duty, a technical tolerance, a test method or a destination compliance result. Those come from the signed contract, project specifications, qualified designers, relevant authorities and product-specific receiving observation. HOMESEE should be evaluated only against the receiving boundary and records actually agreed for an RFQ or order.
Start from a stable buyer identity
Keep a buyer-factual arrival exception or authorized disposition ID even when arrival exception source references investigation update. arrival exception source model names, carton numbers and report numbers remain valuable, but they should be mapped to the stable ID rather than replacing it. That approach preserves continuity between a BOQ, a finish schedule, a sample, a drawing, an order, an inspection record and a arrival exception receiving boundary mark.
Keep exception state separate from receiving observation
A exception state such as approved is not receiving observation by itself. Store the approving role, date, applicable receiving boundary, source receiving arrival record and revision. A photograph can show visible condition; it cannot alone prove hidden construction, performance, quantity or authorization. A arrival exception source declaration can identify a claim, but receiving recorder must decide what independent or destination-specific receiving observation arrival discrepancy-escalation gate requires.
Minimum fields for the site receiving discrepancy report
Use a structured register with one discrepancy entry per arrival exception, arrival exception receiving boundary, authorized disposition or arrival discrepancy at the level where the outcome can investigation update independently. The table below is a field model, not a HOMESEE project record.
| Control field | expected treatment | exception-escalation gate test |
|---|---|---|
| Identity | Stable ID plus native references | Can a arrival reviewer find the same arrival exception across arrival records? |
| Basis | Approved source, revision and receiving boundary | Is the received basis distinguishable from a proposal? |
| exception state | Named owner, authorized disposition and date | Is every open point visible and actionable? |
| receiving observation | Linked arrival record and limitation | Does the receiving observation support only the claim being made? |
| Downstream action | discrepant order, inspection, arrival exception receiving boundary or receiving record | Was the authorized disposition propagated? |
Receiving event
Within the discrepancy report, receiving event identifies the arrival arrival discrepancy before the arrival discrepancy-escalation gate. The entry points to a named revision, arrived reference or receiving observation; an unknown value remains an assigned question, not an estimate. The receiving recorder tests the field from BOQ, drawing or schedule to the downstream sample, inspection or arrival exception receiving boundary and back again. exception state and authorization stay separate because holding a arrival record does not prove its content was accepted.
Shipment and vehicle reference
Within the discrepancy report, shipment and vehicle reference identifies the arrival arrival discrepancy before the arrival discrepancy-escalation gate. The entry points to a named revision, arrived reference or receiving observation; an unknown value remains an assigned question, not an estimate. The receiving recorder tests the field from BOQ, drawing or schedule to the downstream sample, inspection or arrival exception receiving boundary and back again. exception state and authorization stay separate because holding a arrival record does not prove its content was accepted.
arrival exception receiving boundary identity
Within the discrepancy report, arrival exception receiving boundary identity identifies the arrival arrival discrepancy before the arrival discrepancy-escalation gate. The entry points to a named revision, arrived reference or receiving observation; an unknown value remains an assigned question, not an estimate. The receiving recorder tests the field from BOQ, drawing or schedule to the downstream sample, inspection or arrival exception receiving boundary and back again. exception state and authorization stay separate because holding a arrival record does not prove its content was accepted.
Documented quantity
Within the discrepancy report, documented quantity identifies the arrival arrival discrepancy before the arrival discrepancy-escalation gate. The entry points to a named revision, arrived reference or receiving observation; an unknown value remains an assigned question, not an estimate. The receiving recorder tests the field from BOQ, drawing or schedule to the downstream sample, inspection or arrival exception receiving boundary and back again. exception state and authorization stay separate because holding a arrival record does not prove its content was accepted.
Observed count
Within the discrepancy report, observed count identifies the arrival arrival discrepancy before the arrival discrepancy-escalation gate. The entry points to a named revision, arrived reference or receiving observation; an unknown value remains an assigned question, not an estimate. The receiving recorder tests the field from BOQ, drawing or schedule to the downstream sample, inspection or arrival exception receiving boundary and back again. exception state and authorization stay separate because holding a arrival record does not prove its content was accepted.
Visible condition
Within the discrepancy report, visible condition identifies the arrival arrival discrepancy before the arrival discrepancy-escalation gate. The entry points to a named revision, arrived reference or receiving observation; an unknown value remains an assigned question, not an estimate. The receiving recorder tests the field from BOQ, drawing or schedule to the downstream sample, inspection or arrival exception receiving boundary and back again. exception state and authorization stay separate because holding a arrival record does not prove its content was accepted.
Photograph sequence
Within the discrepancy report, photograph sequence identifies the arrival arrival discrepancy before the arrival discrepancy-escalation gate. The entry points to a named revision, arrived reference or receiving observation; an unknown value remains an assigned question, not an estimate. The receiving recorder tests the field from BOQ, drawing or schedule to the downstream sample, inspection or arrival exception receiving boundary and back again. exception state and authorization stay separate because holding a arrival record does not prove its content was accepted.
Step-by-step workflow for site receiving discrepancy report
Run the workflow as linked gates. A later gate does not repair an undocumented earlier authorized disposition; it merely makes the missing control harder and more expensive to find. The exact receiving direction titles and contract notices belong to arrival discrepancy-escalation gate, but the sequence below gives procurement teams a reproducible starting point.
Step 1: Prepare receiving references
prepare receiving references. At the opening gate, the receiving recorder checks the discrepancy report against named inputs rather than memory. The arrival arrival discrepancy is traced from its controlling BOQ, drawing or schedule to the downstream reference and back. Differences receive an owner, due action and bounded hold. discrepancy entries satisfying the arrival discrepancy-escalation gate may proceed; every reserved point remains visible. Completion leaves receiving observation, an effective revision and an accountable disposition.
Step 2: Identify the arriving load
identify the arriving load. During the receiving observation pass, the receiving recorder checks the discrepancy report against named inputs rather than memory. The arrival arrival discrepancy is traced from its controlling BOQ, drawing or schedule to the downstream reference and back. Differences receive an owner, due action and bounded hold. discrepancy entries satisfying the arrival discrepancy-escalation gate may proceed; every reserved point remains visible. Completion leaves receiving observation, an effective revision and an accountable disposition.
Step 3: Count handling units before distribution
count handling units before distribution. Before the next handoff, the receiving recorder checks the discrepancy report against named inputs rather than memory. The arrival arrival discrepancy is traced from its controlling BOQ, drawing or schedule to the downstream reference and back. Differences receive an owner, due action and bounded hold. discrepancy entries satisfying the arrival discrepancy-escalation gate may proceed; every reserved point remains visible. Completion leaves receiving observation, an effective revision and an accountable disposition.
Step 4: Record visible condition
record visible condition. At the reconciliation point, the receiving recorder checks the discrepancy report against named inputs rather than memory. The arrival arrival discrepancy is traced from its controlling BOQ, drawing or schedule to the downstream reference and back. Differences receive an owner, due action and bounded hold. discrepancy entries satisfying the arrival discrepancy-escalation gate may proceed; every reserved point remains visible. Completion leaves receiving observation, an effective revision and an accountable disposition.
Step 5: Isolate and protect discrepant packages
isolate and protect discrepant packages. During arrival discrepancy review, the receiving recorder checks the discrepancy report against named inputs rather than memory. The arrival arrival discrepancy is traced from its controlling BOQ, drawing or schedule to the downstream reference and back. Differences receive an owner, due action and bounded hold. discrepancy entries satisfying the arrival discrepancy-escalation gate may proceed; every reserved point remains visible. Completion leaves receiving observation, an effective revision and an accountable disposition.
Step 6: Notify authorized roles
notify authorized roles. At factual receiving closure, the receiving recorder checks the discrepancy report against named inputs rather than memory. The arrival arrival discrepancy is traced from its controlling BOQ, drawing or schedule to the downstream reference and back. Differences receive an owner, due action and bounded hold. discrepancy entries satisfying the arrival discrepancy-escalation gate may proceed; every reserved point remains visible. Completion leaves receiving observation, an effective revision and an accountable disposition.
Edge cases that need an explicit rule
Case 1: A arrival exception receiving boundary appears wet
When a arrival exception receiving boundary appears wet, the receiving recorder preserves the original reference in the discrepancy report. The discrepancy entry names the arrival arrival discrepancy, controlling revision and downstream work at risk. A label, photograph or message supports review but is not automatic receiving direction. The accountable role records proceed, hold, escalate or supersede. Work already produced, inspected, packed or delivered receives its own disposition. receiving closure requires receiving observation and confirmation that active instructions agree.
Case 2: One carton is missing
When one carton is missing, the receiving recorder opens a linked arrival discrepancy in the discrepancy report. The discrepancy entry names the arrival arrival discrepancy, controlling revision and downstream work at risk. A label, photograph or message supports review but is not automatic receiving direction. The accountable role records proceed, hold, escalate or supersede. Work already produced, inspected, packed or delivered receives its own disposition. receiving closure requires receiving observation and confirmation that active instructions agree.
Case 3: The outer mark differs from the packing list
When the outer mark differs from the packing list, the receiving recorder limits the discrepant receiving boundary in the discrepancy report. The discrepancy entry names the arrival arrival discrepancy, controlling revision and downstream work at risk. A label, photograph or message supports review but is not automatic receiving direction. The accountable role records proceed, hold, escalate or supersede. Work already produced, inspected, packed or delivered receives its own disposition. receiving closure requires receiving observation and confirmation that active instructions agree.
Case 4: Goods are unloaded before the count
When goods are unloaded before the count, the receiving recorder requires a fresh comparison in the discrepancy report. The discrepancy entry names the arrival arrival discrepancy, controlling revision and downstream work at risk. A label, photograph or message supports review but is not automatic receiving direction. The accountable role records proceed, hold, escalate or supersede. Work already produced, inspected, packed or delivered receives its own disposition. receiving closure requires receiving observation and confirmation that active instructions agree.
Case 5: Concealed damage appears after opening
When concealed damage appears after opening, the receiving recorder protects the audit trail in the discrepancy report. The discrepancy entry names the arrival arrival discrepancy, controlling revision and downstream work at risk. A label, photograph or message supports review but is not automatic receiving direction. The accountable role records proceed, hold, escalate or supersede. Work already produced, inspected, packed or delivered receives its own disposition. receiving closure requires receiving observation and confirmation that active instructions agree.
Related arrival records and revision governance
For site receiving discrepancy report, keep the operating arrival record connected to the arrival exception source receiving arrival record requirements, HOMESEE sourcing services and project inquiry form. Plan sampling in the project references, state protection in the BOQ normalization guide, and link final placement to the material submittal register guide. Before an order, reconcile the cross-category finish schedule. Commercial context remains in mixed-material AQL plan, project-specific arrival records go through the export packaging specification, and published container-loading receiving observation plan are references rather than guaranteed outcomes.
Issue the site receiving discrepancy report with a revision, date, preparer and accountable approver. A investigation update notice names the discrepant discrepancy entries and downstream arrival records; it never relies on a newer filename alone. Messages and meetings may resolve questions, but their authorized answer returns to the active register. Standards, photographs, declarations and sampling reports retain their own receiving boundary: none becomes a universal compliance statement merely because it is linked to the procurement arrival record.
escalation-ready review exercise
Choose one live discrepancy entry in the discrepancy report. Ask a second arrival reviewer to locate its controlling input, downstream reference, latest disposition and receiving observation. Then begin with the arrival arrival discrepancy and trace backward. Record where the paths diverge, and repeat with one arrival discrepancy and one superseded revision before the arrival discrepancy-escalation gate.
Buyer checklist for site receiving discrepancy report
Complete the checklist against the arrival record set, not from memory:
- A stable buyer-factual ID exists for every discrepant arrival exception or authorized disposition.
- The controlling BOQ, drawing, schedule and specification revisions are named.
- arrival exception source references are mapped without replacing buyer identities.
- Proposed, submitted, approved, rejected and superseded states are distinct.
- Every arrival discrepancy has an owner, due action and authorized authorized disposition route.
- arrived samples and photographs have IDs, dates and stated limitations.
- Quantities and units reconcile at the level needed for the exception-escalation gate authorized disposition.
- Order, inspection, packing, loading and receiving impacts are mapped.
- Destination and contract requirements are assigned to qualified arrival reviewers.
- No price, MOQ, lead time, compliance or capability has been assumed.
- Superseded arrival records are marked and cannot be mistaken for received releases.
- The final record names preparer, approver, issue date and revision.
Request a receiving-report arrival record check
To evaluate this control within a real sourcing arrival exception receiving boundary, use the export packaging specification and upload the BOQ, received drawings, schedules, sample register and any existing site receiving discrepancy report. Include the destination, expected-on-site context and the authorized disposition dates your project has actually approved. Mark unknown information as unknown rather than inserting an estimate.
HOMESEE can then prepare questions around the defined receiving boundary and organize an RFQ discussion against those arrival records. The response should be assessed against arrival discrepancy-escalation gate's technical, contractual and destination requirements. Sending information does not create a claim about price, MOQ, lead time, certification, production capacity or outcome.
Sources
- UNECE/IMO/ILO Code of Practice for Packing Cargo Transport Units
- My Building List carton marks and site receiving checklist
- GS1 Global Traceability Standard
The sources support the general control concepts identified above. Standards and public guidance must be read in their own receiving boundary and received edition. A reference here is not a declaration that a particular product, shipment, arrival exception source or HOMESEE service complies with it.