This article provides suggestions for using the article and clause description row to capture information shown in the schedule.
Background: The 'Schedule' tab displays articles and clauses that are tagged as 'Summary schedule'. Any type of article or clause can receive this tag.
For further details about the problems this functionality helps to solve please see the article Schedules in NBS Chorus.
Suggested approach
Step 1 - Summarise the requirements in a description field for earlier in the project.
Step 2 - Later in the project, use this schedule to complete the main clause - then park it away if not appropriate for the tech spec or to avoid the risk of duplication.
Example using a performance clause
For articles and clauses that aren't systems (Uniclass) or products such as system performance clauses, the description row can capture a summary of the performance for the earlier stage of the project - then park this for the technical spec later on.
So, adding a summary description for, e.g., UK RIBA Stage 3 of the project - ignoring, for now, the complexity of the full clause.
Screenshot of a performance clause in Uniclass showing a summary of the performance in the description
This description would come through on the Schedule like this:
Screenshot showing the performance description in the schedule
Park it off for, e.g., RIBA Stage 4 of the project. It is used as a brief for completing the more complex clause.