Food traceabilityReceiving and suppliers
Supplier document reviews: separate a stored file from an approval
A supplier document register should identify the file, its scope, review and status. Uploading a document does not establish that it was assessed, applies to the product supplied or satisfies the site’s approval procedure.
At a glance
A supplier document register should identify the file, its scope, review and status. Uploading a document does not establish that it was assessed, applies to the product supplied or satisfies the site’s approval procedure.
Define the decision behind the record
Define who reviews each document type and what information they need. Keep dates, versions and relevant product or site scope accessible. Do not describe a supplier as approved merely because a file field is no longer empty.
Separate document storage, review and approval scope
Identify the document, supplier, products or activity covered and the purpose of review. Record its version or effective information and who is authorised to assess it. A supplier account can hold several documents with different scopes; a single account-level approved flag may conceal those differences.
Capture the review date, checks performed, decision, questions and supporting references. Keep a newly uploaded file distinct from a reviewed revision. If the evidence does not cover a particular product or site, preserve that boundary rather than expanding approval to everything the supplier provides.
Test a changed document and a product outside its scope. A colleague should identify which version was reviewed, what decision it supports and what remains open. Define relevant review triggers under the business procedure and retain superseded evidence needed to interpret historical receipts or decisions.
Worked example
A supplier sends a replacement specification. The team stores the file with its version and scope, assigns review and records the decision. Earlier deliveries can still be linked to the information that applied when they were accepted.
Build a usable record
Use the fields below to capture the facts needed for this particular decision. Keep the actual observation separate from any later correction or approval.
- Supplier and document type
- Product or site scope
- Version and relevant dates
- Reviewer and assessment
- Status and next action
Example record and review decision
Fictional record example: DOC-01-v2: supplier evidence; REVIEW-01: scope, reviewer, decision and next review trigger.
Determine what was checked and for which product or supplier scope. File upload and approval are separate events.
A current upload date does not mean the contents were reviewed or that the document covers every supplied product.
Test the review, not just the form
Retrieve the basis for a particular approval decision. Confirm the reviewer can open the actual file and distinguish it from a newer replacement. A reminder date is useful only when the team knows what review it triggers.
A few useful answers
Does an uploaded certificate prove supplier approval?
No. Record the assessment and decision required by your approval process.
Does a recent upload date mean the supplier was reassessed?
No. It shows file activity unless a separate review record explains the assessment. Preserve the reviewed version, scope, decision and accountable role rather than treating storage as approval.
Sources and further reading
MarkdownExplore starter templates
Start with a useful checklist
English
