Keep Observation, Requirement and Disposition Separate in a Receiving Report
Build a disposition authority grid that connects received-unit observations to agreed requirements, named approvers and narrowly defined decisions.
A receiving report should let the buyer answer three separate questions: what was observed, which requirement it relates to, and who may decide what happens next. A note saying “minor mark, approved” leaves all three uncertain. It may describe the receiver’s opinion while appearing to record a buyer’s concession.
Use a disposition authority grid to connect each issue to a specific decision. Keep the order requirement unchanged while that decision is pending. The grid is especially useful for a 1688 order passing through a sourcing contact, receiving provider and technical reviewer, because each person may have authority over a different part of the purchase.
Write the observation before assigning a conclusion
Identify the receipt, purchase-order line and units covered. Record the observer, date, relevant evidence references and the limits of the authorized check. Describe the visible feature or reported result without supplying an unverified cause. “Surface mark visible on the lid in photographs P-04 and P-05” is more useful than “careless factory handling.”
If the observation comes from somebody else’s report, identify that source. A buyer reviewing photographs should not write as though they personally inspected the goods. Where the evidence leaves the number of affected units unclear, record that uncertainty instead of extending the finding to the whole delivery.
Separate missing evidence from an observed departure. A material document that has not arrived creates an unresolved documentary requirement. It does not establish that the metal has the wrong composition. A missing measurement likewise cannot be recorded as either a dimensional pass or a measured failure.
Connect the finding to the existing requirement
Add the exact purchase-order, drawing, approved reference or document-delivery requirement, including its revision and relevant location. Where several records conflict, identify the conflict and return it to the authorized requirement owner. Do not select whichever version makes acceptance easiest.
ISO 9001 Auditing Practices Group guidance separates audit evidence, the applicable requirement and the resulting nonconformity statement. That distinction is useful background for clear records, although the paper concerns management-system audits and expressly disclaims formal endorsement. It does not prescribe this receiving workflow. APG guidance, pages 1–2 and disclaimer
For a receiving issue, state whether the available evidence establishes a departure, requires clarification, or remains insufficient for the agreed decision. If no acceptance criterion was agreed for a particular appearance feature, ask the owner to resolve that gap. Avoid inventing a scratch-size limit or borrowing a critical/major/minor classification from an unrelated inspection plan.
Build an authority grid with one decision per row
The following template is an editorial control method. It grants nobody authority by itself. Populate the owner and permission fields from the actual purchase and service arrangements.
| Grid field | Entry to preserve | Question before disposition |
|---|---|---|
| Issue and received scope | Receipt ID, order line, unit or lot IDs and quantity basis | Which goods does this row describe? |
| Observation | Factual description, observer and evidence IDs | What is known, and what remains unseen? |
| Requirement | Controlled reference, revision and relevant criterion | What was actually agreed? |
| Assessment | Departure established, evidence incomplete or clarification required | What conclusion does the evidence support? |
| Authorized owner | Name or role plus authority reference | May this person decide this attribute? |
| Permitted decision | Exact concession, continued hold or other agreed disposition | What action would the decision permit? |
| Dependencies | Other issues and required approvals | What remains open even if this row closes? |
| Decision record | Wording, date, scope and approval evidence | Can another person apply it without guessing? |
A receiving operator may record findings. A purchasing owner may approve a commercial concession within delegated limits. A designer may decide whether a dimensional departure is acceptable. Those are examples of possible roles, not assumptions about the reader’s organization. Ask who actually holds each authority.
Make a concession specific to the attribute and units
A concession records acceptance of an identified departure within an authorized scope. It should name the units, the affected characteristic, the evidence reviewed and any conditions. Avoid broad wording such as “accept the batch” when only one cosmetic issue was considered.
Record what the decision leaves open. Acceptance of an appearance difference does not resolve an undocumented material, a dimensional question or a different product identity. Do not copy a narrow concession into an overall pass field while those dependencies remain unresolved.
If the supplier proposes a changed future specification, keep that proposal separate. Accepting a departure on received goods need not change the requirement for the next order. The authorized owner must explicitly decide whether a new baseline is wanted; the receiver should not edit the drawing or purchase order retrospectively.
Work through a hypothetical two-unit decision
Assume a fictional delivery of passive, non-safety-critical organizer cases. Units U-03 and U-04 are receiver-assigned references, not manufacturer serial numbers. Report R-11 identifies a lid appearance difference against approved reference FIN-A. A separate dimensional record is incomplete, and the agreed material document is still outstanding. No actual goods or receiving records are represented.
Suppose the buyer’s designated cosmetic approver reviews the identified evidence and accepts the appearance difference on U-03 and U-04 only. The grid can record: “Appearance departure in issue D-11 accepted for U-03 and U-04 under this order; approval reference A-11. Dimensional and material-document decisions remain open.”
The receiving administrator updates D-11 but retains the other issue references. The report’s overview says “cosmetic concession recorded; receipt release pending remaining decisions.” It does not say that both cases meet every requirement or that the supplier has passed a general quality review.
If the buyer replies only “fine,” return one concise question identifying the proposed scope. Was the reply about the photographs, the cosmetic concession, or the release of specified goods? A clarification is preferable to letting the broadest possible interpretation become an operational instruction.
Keep acceptance separate from execution
After a decision, identify who is responsible for applying it to the receiving record and who confirms that the instruction was received. A decision sent to a supplier may not have reached the warehouse. Link the instruction to its current revision, especially if earlier messages said to hold the goods.
For any proposed rejection, return, rework or disposal, record the required separate authorization and responsible provider. A status label is not permission to carry out every possible remedy. Payment commitments and settlement terms also require their own decision; this grid does not create contractual rights.
For batteries and other safety-relevant goods, an administrative or cosmetic acceptance cannot establish internal safety, authenticity, compliance, compatibility, transport suitability or installation readiness. Exterior photographs cannot settle those questions. Keep technical approval with the appropriate qualified owner and do not request improvised physical work to complete the report.
Finish each issue with a readable decision or a specific pending question. Someone outside the original chat should be able to identify the affected goods, locate the requirement, find the approval and understand exactly what can proceed.
Frequently asked questions
Can the person writing a receiving report approve a deviation?
Only within authority actually assigned to that person. Record the applicable delegation and decision scope; being the observer does not automatically confer technical or commercial approval authority.
What if the requirement is missing or contradictory?
Keep the affected decision open and ask the authorized requirement owner to clarify the baseline. Do not invent a tolerance or rewrite the order to match the received goods.
Does accepting a cosmetic mark release the whole order?
Only the specifically approved appearance issue is resolved. Other requirements and any separate receipt, shipping or installation approvals remain in force.
Should the original observation be deleted after a concession?
Retain it with the unchanged original requirement and the dated concession. The record should explain what was observed and why a limited departure was accepted.
Sources
Discuss a sourcing request related to this article.Keep Observation, Requirement and Disposition Separate in a Receiving Report