Skip to main content
Documents are operational records. They should be linked to the lot, run, supplier, report, import, export, or shipment they support instead of living in a separate folder process.

Document rules

Document typeTriggerLinked targetNormal status pathQA note
COAReceivingLotMissing to uploaded to reviewedQA verifies supplier lot, item, dates, and required specs.
Supplier docSupplier onboarding or QA uploadSupplier, item, or lotUploaded or reviewedUse for approvals, spec sheets, and recurring supplier documents.
Batch attachmentProductionProduction runUploaded or reviewedUse for traveler scans, photos, deviations, and supporting records.
Audit fileManual QA or export processOrganization, lot, run, or reportUploaded or reviewedUse for third-party audit evidence and compliance packets.
ExportReports, traceability, jobsReport, traceability export, import/export jobUploaded or reviewedUse for generated files the team may need to send externally.
Shipment docOrdersShipmentMissing or uploadedUse for packing lists, bills of lading, or shipment evidence.

Status meanings

StatusMeaningWhat to do
MissingBatchlane knows the file is required but it has not been accepted yet.Upload the file or resolve why it is required.
UploadedA file or placeholder exists but still needs QA review.QA accepts or rejects the version.
ReviewedQA accepted the file for operational use.No action unless a replacement is needed.
RejectedQA found the file unacceptable.Upload a corrected replacement or document the rejection.
RetiredFile is retained historically but removed from active review.Restore only if it needs active review again.

Review flow

  1. Open Documents.
  2. Filter for missing, uploaded, rejected, or retained work.
  3. Open the linked record before reviewing the file.
  4. Accept the current version only when it matches the source record.
  5. Reject with a reason that tells the uploader what to correct.
  6. Retire documents only when the team has a retention reason.

Common QA issues

  • Upload a file before accepting a missing document.
  • Review the current document version. If someone uploads a replacement while you are reviewing, reload the document.
  • Retired documents cannot be accepted or rejected until restored.
  • Rejected documents create follow-up work until a replacement is accepted.
  • COAs should be reviewed before consuming lots whenever the customer’s food safety program requires it.
Related pages: Receiving, Production, Reports, Common errors.