When NBS Create files are imported into Chorus, Chorus will transform the clause codes and titles into Uniclass.
We only recommend keeping the NBS Create clause codes and titles for project that are well advanced and cross referenced in other project documentation.
However, for ongoing projects where changing the classification is undesirable Chorus provides the option to retain the NBS Create codes and titles. This removes the need to manually add or change cross-references used on drawings, schedules, or related documentation.
After a successful import, the Create codes will be respected in NBS Chorus, and will also continue to synchronise with NBS guidance (although the guidance will show Uniclass references.) Published documents generated from the imported specification clauses will respect the structure and ordering of the NBS Create codes.
Once imported the Create codes cannot be amended.
Note that new clauses added to your specification in NBS Chorus will use the Uniclass classifications, and the Chorus search engine will not provide results using NBS Create codes.
How to keep the NBS Create codes and titles.
At the point you are importing your NBS Create file you should select the option to 'keep NBS Create clause codes and titles' as shown below.