Buyer guides
Supplier Document Handover: Define the Data Book Before the Purchase Order
Define supplier data book requirements before the PO: scope, item traceability, revisions, staged delivery, usable files and acceptance responsibilities.
Agree the supplier's document package before issuing the purchase order. Specify what each document must cover, which supplied items it applies to, when it is needed, who reviews it and where the accepted files will live. Include those requirements in the RFQ so suppliers can price the work and identify exceptions before selection.
A manufacturing data book is an indexed collection of records for the supplied equipment, components or materials. Its contents depend on the purchase. For an equipment package, the receiving team may need installation drawings, operating instructions and maintenance information. For a material lot, certificates and inspection records may matter more. A large ZIP file alone says little about whether either team has what it needs.
Begin with the receiving team's work
Ask installation, quality and maintenance colleagues which decisions they must make using the supplier's records. Can they identify the delivered item? Check the relevant test result? Install it correctly? Order its replacement parts?
Build the document list around those tasks. Consider drawings, inspection and test reports, material certificates where applicable, manuals, spare-parts lists, warranty documents and maintenance requirements. Remove irrelevant categories and specify the content of the remaining ones. “Test report” needs a named test, applicable item and required result record.
The U.S. government guide specification UFGS 01 78 00, Closeout Submittals, August 2026 treats revised project documents, warranty management and operation and maintenance (O&M) information as defined closeout subjects. Its opening instructions require project-specific editing. It provides a useful planning reference; it does not automatically impose requirements on a private supplier purchase.
Copy this document requirement record
Complete one record per deliverable, then ask the supplier to confirm it or state an exception. A stable deliverable ID connects the requirement, submitted file and review history without relying on email subject lines.
| Field | Entry to complete |
|---|---|
| Deliverable ID | [Unique reference and document title] |
| Applicable supply | [PO line, equipment tag/model, serial number or lot/piece IDs] |
| Required content | [Scope, attachments and evidence required] |
| Revision | [Revision/date, issue purpose and superseded reference] |
| File and language | [PDF/native format, software version if needed, required language] |
| Planned dates | [Milestone, first submission, review return and corrected final dates] |
| Responsibility | [Supplier preparer, buyer reviewer and acceptance authority] |
| Acceptance checks | [Specific completeness, accuracy and usability checks] |
| Current status | [Missing, received, under review, returned, resubmitted or accepted] |
| Open item | [Comment reference, corrective action, owner and response date] |
| Final destination | [Buyer repository, folder and accepted file reference] |
These are suggested procurement fields, to be adapted to the actual order. Agree who supplies identifiers that become available only during manufacture and when the supplier will add them.
An item is the ordered unit or identifiable component. A serial number distinguishes an individual unit. A lot identifies a defined batch; its boundary must be clear. Where one report covers several units or lots, list that coverage explicitly. A model number alone may identify a product family without identifying the delivered unit.
The identification approach has a concrete reference in UFGS 01 33 00, Submittal Procedures, August 2026, sections 1.6.3–1.6.4: it addresses product identification, drawing revisions, resubmissions and file formats within its government-project scope. The record above is an editorial adaptation for buyer–supplier coordination.
Schedule the information before it is needed
Set dates by working backward from the activity that depends on the document. Allow time for review, correction and resubmission. “With shipment” is too late for a document needed to approve the shipping configuration.
Use the following sequence as a starting point. Omit stages that do not apply and convert each timing description into agreed calendar dates.
| Stage | Information to identify | Timing to agree |
|---|---|---|
| Design review | Interfaces, dimensions and proposed configuration | Before the receiving design decision |
| Production release | Applicable approved documents and closed comments | Before the designated release decision |
| Shipment preparation | Item/lot index, completed inspections and preservation instructions | Before the agreed shipment review |
| Installation and commissioning | Usable manuals, procedures and required settings | Before the relevant site activity |
| Final records | As-supplied/as-built updates and completed commissioning records | After final changes are recorded, by an agreed date |
Identify preliminary versions clearly. A final commissioning report cannot exist before commissioning, but the procedure and reporting template can be agreed earlier. Record which later documents will supplement the shipment package.
UFGS 01 78 23, Operation and Maintenance Data, May 2023 with Change 4 dated August 2026, section 3.2 uses progress, prefinal and final submissions. Its staged approach is useful context; its government-project deadlines are not universal supplier deadlines.
Test the files as a user would
Ask a receiving colleague to open a sample package before the supplier prepares hundreds of files. Check that the index leads to the correct document, drawings remain readable at the intended viewing size and all referenced attachments are included.
Agree searchable PDFs where practical, plus native files where the buyer genuinely needs them and their delivery is agreed. Specify software versions, dependencies and language requirements early. A PDF export may support reading while an editable parts list serves maintenance planning. Check translations against equipment labels and terminology so readers can find the same component in both.
For comparison, UFGS 01 78 23, sections 1.5 and 1.6.3.3 addresses bookmarked electronic manuals and searchable manufacturer information specific to the installed products.
Check the claimed final revision against the configuration actually supplied, including agreed changes. Preserve earlier submissions in a clearly marked history; keep the accepted set easy to identify.
Separate receipt from acceptance
A receipt log answers whether a file arrived. Acceptance records the named reviewer's decision against the agreed checks. Use status meanings consistently:
- Missing: a required submission has not arrived by its due date.
- Received or under review: the file is logged; a decision is pending.
- Returned: identified issues require correction, with comments and a response date.
- Resubmitted: a replacement is received and awaits another review.
- Accepted: the authorized reviewer has recorded acceptance of that specific revision.
Record actual submission and decision dates as well as planned dates. Identify which deliverables need technical acceptance and which require receipt only. Section 1.8 of UFGS 01 33 00 separately addresses information-only submissions and acknowledgment, illustrating why those events deserve distinct records.
For unresolved items, name an owner, required correction and due date. Escalate any affected installation or operating decision to the responsible project authority. Payment consequences depend on the actual contract and appropriate professional advice; this checklist does not establish a right to withhold payment.
Finish in the buyer's repository
Agree the destination before the first submission. Transfer accepted files into the buyer's intended repository, retain the final index and have an intended recipient verify access through their own account. Test links after the transfer. Supplier-hosted downloads and expiring email links should not be the only route to records needed later.
Need to define a supplier document package before ordering? Contact SourceRating with the product, destination, order stage and proposed document list. If you have not selected a supplier, start with the project requirements.