Plan submittal reviews around procurement and installation

For each submittal, identify what depends on it: equipment order, fabrication release, interface design, installation or testing. Record the required-on-site or required-for-decision date and work backwards through review, preparation and possible resubmission time.

Use the contract and project procedure to establish required reviewers and response periods. Do not assume that an internal target is a contractual commitment. Show both where they differ, and give the coordinator a basis for escalation before the downstream activity is affected.

Long-lead packages may need several information releases. A vendor can provide preliminary interface data before a full manufacturing package, but the permissible use and limitations must be clear. Preliminary information should not acquire final status merely because another discipline needs it urgently.

A single equipment package may contain drawings, calculations, data sheets, procedures and certificates with different review paths. Group related information for coordination while retaining item-level status where decisions differ.

Autodesk's submittal workflow documentation describes review steps and response records. Its response settings also distinguish approval and resubmission categories. Project teams should define what their chosen labels permit under the applicable procedure.

A status such as “accepted with comments” needs an operational definition. Some comments may require incorporation before manufacture; others may permit work subject to a later record update. The reviewer must state the conditions, and the receiving owner must understand their effect. Software colour alone cannot express that distinction reliably.

In this illustrative pump package, the vendor submits a motor data sheet and foundation loading information. The motor data is accepted for its stated purpose. The loading information is returned for revision because a required operating case is missing.

The package should not be displayed as wholly accepted. Nor should the accepted motor data disappear into an undifferentiated rejected package. The register needs to preserve both conclusions and identify the specific activity still blocked.

If the vendor later revises the motor selection, reassess whether the previously accepted loads or electrical interfaces remain valid. Acceptance of one revision does not automatically extend to a changed design. Link dependent items so the coordinator can identify the required rereview.

Every resubmission should state the previous review reference, the changes made and the response to comments. Preserve the earlier files and comments. Reviewers should be able to see whether each issue was resolved without searching through an entire package from the beginning.

Record the actual submission, receipt, response and resubmission dates. Distinguish time with the preparer from time with reviewers. This helps identify whether delay comes from late initial preparation, incomplete submissions, review capacity or repeated unresolved comments.

Avoid resetting the original required date whenever a package is late. Keep the current forecast response date as a separate field. The difference shows the schedule risk and supports an informed decision about expediting or resequencing.

A reviewed document must reach procurement, fabrication and site teams in its correct revision. Record the distribution or controlled document reference and any acknowledgement required for critical information.

Check that the purchase order or fabrication release cites the applicable information. A vendor receiving an old attachment can manufacture to a superseded requirement even while the register shows the latest revision accepted. The process should reconcile the issued package with the register before release.

At site, remove or clearly supersede obsolete information according to document-control procedures. Keep historical revisions available for traceability without allowing them to appear as the default instruction for new work. The distinction between accessible history and current working information is essential.

Sometimes a project needs to release a defined portion of work before the entire submittal package is complete. The authorised reviewer should identify the permitted scope, assumptions, restrictions and unresolved interfaces. Record the decision and who received it.

A partial release should be specific enough that the execution team can recognise its boundary. “Proceed where possible” leaves too much interpretation at the work front. State which items or locations can proceed and which remain held.

Review the cost and schedule consequences of proceeding on limited information. The project may accept a controlled risk, but that decision should be made by the appropriate authority and retained with the release. Urgency does not turn a provisional document into an approved final design.

A useful weekly view shows upcoming decision needs, late initial submissions, items awaiting review, resubmissions and unresolved conditions affecting near-term work. Group by consequence as well as age so the team does not spend all its attention on the oldest low-impact item.

Look at repeated review cycles. They may indicate unclear enquiry requirements, poor vendor coordination or comments that were not specific enough to close. Discuss the pattern with the relevant parties and improve the submission standard or review interface.

Test the register with a partly accepted package and a revision that affects a previously accepted interface. Verify that the blocked downstream activity remains visible and that a new revision does not inherit approval without the required review.

The submittal process is working when procurement and construction receive the right information before their decisions are due. Review status, revision and permitted use must travel together.

1. Link each submittal to the decision or activity that needs it.
2. Set preparation and review dates from that downstream need.
3. Track separate response outcomes where package items differ.
4. Preserve resubmission history and explicitly close review comments.
5. Verify the current accepted revision at procurement, fabrication and site release.