Buyer guides
Received, Reviewed, Approved or Released? Keep Procurement Documents in the Right State
Track procurement submittals with clear document states, expected-item registers, review conditions and evidence of authorized fabrication release.
A procurement document needs a recorded status, a defined purpose and evidence of the decision behind it. Log receipt separately from technical review, and connect any permission to proceed to the authorized person's response and the work it covers. Include expected documents that have not arrived, so a missing submission cannot disappear from the register.
A file uploaded to a shared folder can be visible to everyone while remaining unreviewed. Equally, a drawing can be accepted for one defined purpose while other work still depends on unresolved information. The useful question is: which decision has actually been made about this revision, by whom, and for which activity?
Agree what the status words mean
Use the meanings established in the contract and project procedures. Record the reviewer’s actual response as well as any simplified tracking label. Do not overwrite a qualified response with a broad “approved” status because the spreadsheet has only three choices.
The U.S. government guide specification UFGS 01 33 00, Submittal Procedures, August 2026 distinguishes review classifications and action codes, including acknowledgment of receipt. It also explains the meaning of particular review notations within its scope. Its opening instructions require project-specific editing, so its labels and consequences should not be applied automatically to another project's purchasing process.
The following is an example working vocabulary to adapt:
| Example state | What the record establishes | What to identify next |
|---|---|---|
| Expected | A submission is required | Owner and due date |
| Received | A specific revision arrived | Completeness and review route |
| Under review | Assigned review is underway | Reviewer and response date |
| Returned for revision | Corrections have been requested | Comments and resubmission owner |
| Accepted for stated purpose | Authorized response covers a defined use | Conditions and dependent work |
| Released for defined activity | Permission is evidenced under the agreed procedure | Covered scope and current documents |
Some projects use one authorized review response as permission to proceed. Others require a separate release. Make that relationship explicit rather than creating an unnecessary extra approval or assuming one exists.
Record the documents you expect, not just the files you have
Start with the applicable purchase and project requirements. Ask the responsible technical and project leads to identify the expected submissions, required reviews and affected activities. Allocate a stable submittal ID before the file arrives.
An inbox-derived list cannot reveal a drawing that nobody submitted. An expected-item register can. Record a submission as not applicable only with the basis and appropriate confirmation; deleting a row hides the decision.
A compact register can look like this:
| Expected ID and item | Required review | Due/submitted dates | Current revision and status | Owner and record link |
|---|---|---|---|---|
| ___ | ___ | ___ | ___ | ___ |
Attach the detailed conditions and release record to each row. Keep the date last checked so readers can see whether the register reflects the most recent response. Add newly identified requirements through the agreed process rather than assuming the first list was complete.
For each received package, check whether all referenced sheets, attachments and calculations are present for the assigned review. Administrative completeness is useful, but it does not establish technical acceptance. Route the package to the person designated for that review.
Connect the document to the affected work
A status is more useful when it identifies the operation that depends on it. List the purchase lines, equipment tags, lots or work packages affected. Where necessary, distinguish material ordering, tooling manufacture, fabrication, shipment and installation.
For an illustrative equipment package, a supplier may submit a foundation-interface drawing and a control-system drawing separately. A recorded response to the foundation drawing does not establish that the control-system submission has also been reviewed. Nor does it necessarily resolve all prerequisites for the equipment's fabrication release.
Have the responsible project team define those dependencies. The register should show them; it should not invent engineering hold points or grant authority that the project has not assigned.
Use a short decision record where the relationship would otherwise be unclear:
| Decision field | Record to retain |
|---|---|
| Document identity | Submittal ID, drawing number and revision |
| Review response | Exact response, date, reviewer and attachment |
| Conditions | Open comments, required action and owner |
| Affected work | Specific items, lots or activities |
| Authority | Person or role empowered under the project procedure |
| Release evidence | Decision reference, permitted scope and effective date |
| Current check | Last reconciliation with the register and working documents |
Read conditional and partial responses carefully
A response may contain qualifications that matter to the next activity. Keep the comments with the reviewed document, assign each action and identify who confirms closure. Where resubmission is required, record the replacement and its new review status rather than assuming the original response carries forward unchanged.
If only part of a package is covered, identify the exact sheets, items or activities. Avoid using an overall green status that hides an unresolved dependency. Ask the authorized reviewer or project lead to clarify any ambiguity in the permitted scope.
Within its government-project context, UFGS 01 33 00, section 1.12.1, assigns different consequences to its review notations and qualified responses. That is a concrete reason to read the governing procedure instead of relying on the everyday meaning of a stamp.
A missed response date also needs a defined action. Follow the project's expressly agreed response and escalation provisions; do not invent acceptance from silence or create a new rule through a tracking spreadsheet.
When a missing review is discovered after work has begun
First establish the facts: what document or response is missing, which revision is in use, what work has occurred and which activities may be affected. Preserve the relevant records and report the uncertainty promptly through the approved project route.
The authorized engineer, project lead and contract owner should determine the appropriate disposition within their responsibilities. That may require additional technical information or review of the work already performed. A generic article cannot decide whether a particular operation should stop or continue.
Follow applicable site safety and escalation procedures immediately where there is a safety concern. Do not backdate a submission, infer an approval to close a record, or change a status merely to make the register appear complete. Record the actual corrective decision and its evidence.
Keep the working record aligned with the decision
After each review or release, reconcile the status, revision, conditions and affected scope. Make the authorized working documents easy to identify while retaining earlier versions as history. Check that the supplier and the receiving project team can locate the same response.
For help clarifying a procurement document trail, contact SourceRating with the expected-submittal list, relevant responses, current revisions and the decision that remains unclear. State the affected purchase or production activity so the review can focus on the missing evidence and responsible authority.