Saeed Azarshab

Procurement and materials

Submittal Reviews and Procurement Release in Construction

Tie technical submittals to supplier lead times and make the handoff from review to purchase traceable.

Published · Example for training

When a supplier quotes an eight-week lead time, check the date from which that clock actually runs. It might start when the technical option is accepted, the order is authorised and the supplier confirms its manufacturing slot. In the programme, give each of those decisions a date. Otherwise an apparently early order can still arrive late.

Build the review backwards from need on site

Start with the planned installation date. Allow for receiving checks, access restrictions, delivery and fabrication. Work backwards to the order date and to the preceding review and resubmission windows. Then match each submittal to the relevant specification, selected product variant, drawing revision and intended location. Give the reviewer a short comparison of requirements and any proposed departures. A generic product brochure often leaves temperature ratings, finishes, interfaces or accessories unanswered.

Worked example — doorset hardware

A proposed handle appears in the supplier's catalogue, but the procurement team needs evidence that the submitted hardware configuration satisfies the project specification for the particular assembly. Assign a competent technical reviewer. Track the exact assembly and component identifiers in the submittal and record any restrictions in the review. If approval is conditional on a revised set of details, confirm when that condition is discharged and who then authorises purchase. The goods-in inspector later needs the accepted configuration to verify what was delivered.

Use the tool to protect decision dates

Autodesk's November release describes additional reviewer capacity in Forma Build and a way for a submittal manager to submit an item on behalf of a contractor. Agree which reviews genuinely need to happen in parallel and who consolidates conflicting comments. Keep the technical review outcome, approval conditions and permission to place an order as identifiable decisions. Screen labels and available options depend on your configuration.

Release checks

Video walkthrough

Start with Participants and Permissions, then look at the reviewing lesson. Map the review actions to your own responsibility matrix before configuring a workflow.

Watch: Submittals tutorials in Forma Build

Sources

Continue with a practical example