What is Clause Versioning and how should updates be propagated to templates?

• A. Clauses do not have versions; templates always reference the latest.
• B. Template updates are automatic and require no policy.
• C. Each clause update creates a new version; templates can reference a version or follow the latest; establish policy for updating new templates and existing ones.
• D. Versions are only relevant to external systems.

Answer: (C)

Clause versioning treats every change to a clause as a new version, preserving history and letting you pin contracts to a specific state of the clause. When a clause is updated, a new version is created, so you can decide precisely how that update should affect templates. Templates can be set to reference a particular clause version, which locks the contract to that exact wording, or to follow the latest version, which brings in improvements automatically. Because of this flexibility, it’s essential to establish a policy for updating templates: specify which templates should adopt the latest version and how to handle existing templates that reference older versions. This governance helps balance stability for active contracts with the ability to benefit from improvements in new contracts.

Statements that claim clauses don’t have versions, or that updates happen automatically with no governance, or that versions only matter for external systems, don’t fit the real behavior. Clause versioning exists to manage changes responsibly, and templates need clear rules to decide when to lock to a version versus when to update to the latest.