This article details what data can be imported into Chorus from an NBS Building/ Landscape file.

On importing a file you will receive an email containing a report which details what has and has not been imported - as below: 

What does get imported:

  • All sections both NBS and user-created including:
    • Headings (also referred to as groups or parts)
    • Clauses
      • Entered text
      • Hyperlinks
      • Text formatting - bold, Italic, Underline, Strikeout.
    • User added clause items (rows)
    • Excluded (parked) status
    • Links to external standards
    • User guidance notes - excluding images.


These clauses will be indicated by a TRUE in the Imported column of the report.

Clauses that are not imported will be indicated by a FALSE in the Imported column of the report.


What does not get imported:

Anything that currently does not have a home in NBS Chorus will not be imported:

  • Revisions recorded in NBS Building/ Landscape
  • User Guidance Notes - Images found in user guidance notes will not be imported. We recommend transferring them into Chorus manually. When an image is detected this is noted on the import report.
  • Embedded objects - where an object such as an image or table is detected this is noted on the import report but not imported.
  • Stylesheets - saved against that clause in NBS Building/ Landscape. Chorus manages stylesheets differently to NBS Building/ Landscape.
  • Any validate notifications against a clause that have not been actioned in NBS Building/ Landscape prior to import - where possible the import report provides an indication that the clause is up-to-date or should be checked.
  • Current sources (defined in NBS Building/ Landscape)