Lattira Spec and NBS Chorus have been developed to import Microsoft Word-based specifications. This functionality has been developed to import specifications based on Australian, Canadian and USA content sets.

This article sets out which content sets support importing MS Word-based specifications. It also outlines how the MS Word files must be styled to import successfully.


Content sets that support importing Microsoft Word-based specifications


MS Word-based specifications can be imported into the following content sets; 

  1. Australia - Import from MS Word
  2. Australia - SureSpec
  3. Canada - NMS and CMS
  4. Canada - NMS (French)
  5. USA - USMS


Styling hierarchy for MS Word documents


MS Word-based specifications are styled differently in Australia, Canada and the USA. Lattira Spec and NBS Chorus have been developed to parse the different styles to import the specification data into the right fields in the specification editor.

 

This section explains the different styles the MS Word specification must follow for the file to be imported successfully.


Specification dataImporting into 'Australia - Import from MS Word'Importing into 'Australia - SureSpec'Importing into:
'Canada - NMS and CMS'
'Canada 0 NMS (French)
'USA - USMS'
Section code and titleHeading 1
  • It always appears first in the section.
  • The code is up to 11 digits (including spaces and punctuation) and positioned before the title.
  • The Title is case-sensitive (it will import as typed)
Heading, group or part
Styled as Heading 2
Styled as Heading 2
  • 3-part specs with 'part' in the title.
  • Must include either:
    • 'Part 1', 'Part 2, 'Part 3'.
    • 'Partie 1', 'Partie 2', 'Partie 3'.
  • The part title is not case-sensitive (will always appear in sentence case).

Article/ clause numberNot imported.

The platform generates the number as part of the import.
Article/ clause titleStyled as Heading 3
Row title (known as a subclause title)Styled as Heading 4N/A
Row - indent level 0Styled as NormalStyled as Heading 4
Row - indent level 1-5N/A. All rows are imported at level 0.Sub-paragraph styled as Heading 5
Sub-para styled as Heading 6
Sub-para styled as Heading 7
Sub-para styled as Heading 8
Sub-para styled as Heading 9
Guidance notes (hidden text)Styled as Instructions or Optional.
  • Appears as 'Spec notes' against the article/ clause.
  • Guidance notes against articles and clauses are imported. Guidance notes against the whole section or between parts and articles/ clauses should be input manually.


What can be imported from an MS Word-based specification

The platform will import specification section codes and titles, groups, articles/clauses, and rows. It supports:

  • Microsoft Word (.docx) files and Zip files containing .docx files. The total combined size must not exceed 100 MB.
  • Single MS Word files containing a single section or multiple sections. Single files must not exceed 30 MB.


What can be imported?

  • Specification data: Sections, groups, articles/ clause title, article/ clause row text.
  • Text formatting: Bold, italics, underline and external hyperlinks.
  • Guidance note (as hidden text) attached to articles/clauses.
  • Tables*.

*Table data will be imported however, the data will not be formatted as a table. We recommend recreating the tables manually in the specification editor. See Tables – adding, editing and copying tables.


What does not get imported?

  • Guidance notes attached to sections and groups.
  • Headers and footers.
  • Images.
  • Table of contents.


What functionality can be used to manage specification information once it has been imported?

  • Making changes to the specification using the specification editor: parking articles/ clauses, multiple authors, recording who last edited each row.
  • Publishing the specification to PDF and MS Word, submittals reports*, Spec check report.
  • Publishing how the specification has changed with revisions*.
  • Coordinating the specification with the model in Autodesk Revit, Graphisoft Archicad and Vectorworks.

*Submittals reports and revisions are available to Pro (and above) subscriptions.


Steps for importing an MS Word specification

  1. In a project, click on Add specification.
  2. Enter a title for your specification and select the 'Australia - Import from MS Word'*, 'Australia - SureSpec', 'Canada - CMS' or 'USA - USMS' content set.
    • *Please note - this content set will be visible if this feature has been enabled for your organization.
  3. Choose a file.
  4. Click on Save. The platform will process your request and email you when this is complete. This can take a few minutes depending on the file(s) being imported.
  5. You will be sent an email when the file import is complete, or if it is unsuccessful. The email contains a report of what was imported.
  6. Please check the report attachment.
    • Once your files are successfully imported, the report will provide advisory notes on items that may not have been imported, such as images or notes, or on aspects you should verify in the imported specification.
    • If an import fails, the report will specify why the file couldn't be uploaded. It will guide you in reformatting the document to enable a successful reimport.