This article explains how to convert shared sections and clauses into new instances. This guide is intended for updating our existing 2016 Uniclass Preliminaries clauses to create 2024 versions.


Background

The 'UK - Uniclass Preliminaries' content set is unique because it contains multiple contracts, each with several versions, e.g., 2016 vs. 2024. Clauses can be shared among different versions of the same contract, as well as between different contracts.


In comparison, in 'UK - CAWS Preliminaries,' every contract has its own distinct set of clauses. Clauses are not shared between contracts and versions.


Chorus CAP allows clauses to be tagged with their relevant contract(s). It also allows you to convert an existing section and clause, e.g. a 2016 PM_55 section, into an entirely new 2024 version. 


This process enables multiple contracts to be authored within the same bundle simultaneously, preventing a single contract from being authored end-to-end and deployed sequentially.


How to mark up clauses for the JCT 2024 contracts

Follow these steps to create 2024 instances of existing sections, new 2024 clauses, and to share clauses between contracts and versions.

  1. Create the bundle.
  2. Add the section(s) to the bundle.

  3. 'Convert to new section' - use this to take an existing 2016 section and create an entirely new instance to become the 2024 version.
    1. Assign the new section with the 2024 contract chip.
    2. Change the clause text to 2024.

  4. 'Convert to new clause' - same as above, for clauses within the 2024 section.

  5. Add and remove contract chips for supporting clauses. Clauses that will be shared amongst both 2016 and 2024 contracts.
    1. Please be aware: You must apply a contract chip to section heading clauses and clauses.

  6. Before you deploy the bundle, you'll need to ask the Dev team to update the Chorus database with the ID's of the newly converted sections. This must be done before deploying to Proofing and again before deploying the Production+Sandbox.
The section code, title and general guidance is shared. So you must not change this to be unique to a single contract.