Submittals in construction management are shop drawings, material data, samples, and product data. Submittals are required primarily for the architect and engineer to verify that the correct products will be installed on the project (Wikipedia).


Producing submittals for contractors manually from a specification is time-consuming and prone to error. You can export a full list of submittals from your specification, ready to share with your team.


At a glance:

  • The export report is a Microsoft Excel file.

  • It pulls out the parts of the spec which contain the words: submit, submitted, submittals, and submission.

    • For French specifications it pulls out instances of soumettre, soumission, soumis, and soumise.

  • It contains rows for each submittal and whereabouts in the specification this is documented.

  • For Uniclass-based specifications, the submittals are separated for pre-construction and handover.

  • There are different formats suitable for a number of leading Common Data Environments (CDEs); Autodesk, Newforma and Viewpoint. 

  • The report can then be imported straight into these CDEs, and records will be created for each row.



How to export the submittals report

You can export the report for the full specification, or a selection of your specification. 


For a report of the full specification, click on the menu to the right of the specification > Export submittals report.


Animation showing the Export Submittals report


To report on part of the specification, open the specification, make a selection and click on the Actions button > Export submittals report.

Screenshot showing the Export Submittals report for a selection of the spec


What the report contains

The report contains a row for each submittal found in the specification. The Export submittals report pulls out the parts of the spec which contain the trigger words: 

  • English trigger words:

    • submit, submitted, submittals, and submission.

  • French trigger words:

    • soumettre, soumission, soumis, and soumise.

  • Locations:

    • These words could be in the prefix, title or suffix fields of any section/system/article/clause. 

    • They could be in the body of the article or clause. 

    • They can be words you have entered into the specification yourself.

    • The report will ignore trigger words in rows that have been parked.


Additional rules for Uniclass-based specifications:

  • When product clauses (and their linked clauses) containing a trigger word are linked to more than one system, the report produces a row in the report for each system.

  • The report will insert a row for product clauses when they are specified on their own, and not linked to a system.

  • When exporting part of the specification, the report includes only data from your selected clauses and their linked clauses.

    • If you have a system selected and it contains a link to another system, both are checked for trigger words and included in the report.

    • The report is only looking at linked clauses, not parent clauses, so if you have a product linked to two systems, and only one of the systems is in your selection, only the system selected and the products are candidates for the report; the report will not include the other system.

  • The report will have separate rows for pre-construction and handover submittals.

    • Pre-construction submittals - Any trigger words that are in Activity, System Outline, Performance, Product, and Execution clauses.

    • Handover submittals - Any trigger words that are found in the System Completion and System Facilities Management parts of the spec.


How the report is formatted

There are four formats available:


Lattira/ NBS Format - a generic format not designed for import into a CDE, but could be reformatted to suit one.


Autodesk, Newforma, Viewpoint - specifically formatted to match the schema of these CDEs so the report can be imported and records automatically created for the submittals.


The report is given a filename with the format: ProjectCode-SpecificationName-Submittals-YYYY-MM-DD.xslx


Background to Common Data Environments

The UK PAS 1192 series of standards and, subsequently, the ISO 19650 series of standards define the need to have a common data environment (CDE) for collecting, managing and disseminating information throughout BIM projects. The CDE workflow describes the processes to be used, and the CDE solution is the technology supporting these processes. For more information on CDEs please see theNBS.com