LogoLogo
ClausesDatafieldsSpecial FunctionsStylingQ&AAPI
  • Welcome!
  • Getting started
    • What is Clause9?
    • Structuring your clause library
    • Structuring your clauses
    • Drafting modes in Clause9
    • Creating a questionnaire
    • Sample clauses
    • Videos
      • Concepts and datafields
      • Conditions
      • Q&As
      • Binders
      • Styling
      • Enumerations
      • Tables
      • Definitions
      • Snippets
      • Cross-references
      • Special functions
      • Examples of common clauses
      • Import clauses from MS Word
      • Grammatical conjugations
      • Action buttons
      • Alternative clauses
  • Assemble document
    • Document toolbar
    • Clause hierarchies
    • Focus Mode
    • Bulk generation of documents
    • Exporting documents
    • Assemble Document - FAQ
    • How to: Assemble Document
      • Insert images
  • Assemble Document Operations Panel
    • Operations panel
    • File pane
    • Edit pane
    • Document pane
    • Binder pane in the operations panel
    • Search pane
    • Browse pane
    • Terms pane
    • Data dashboard
    • Advanced pane
    • Styling pane
    • Miscellaneous pane
    • Visibility settings & actions menu
  • Binders
    • Binders: general
    • Styling cross-references to subdocuments
    • Global and local definition lists
    • Document and binder properties
    • Styling of a Binder versus subdocuments
    • (Un)locking documents in a binder
    • Binders - FAQ
    • How to: binders
      • Make a subdocument in a binder conditional
  • Clauses
    • Introduction to clauses
    • Clause structure
    • Grammar sheet
    • Writing conditions
    • Examples of conditions
    • Using codes instead of text fragments
    • Bold, italic and underline
    • Special codes
    • Enabled?
    • Links
    • Cross-references
    • Introduction to tables
    • Deviating table styling
    • Shrinking clauses
    • Action buttons
    • Enumerations
    • File position
    • Snippets
    • Parameters
    • Conjugations
    • Mixing data types
    • For-loops
    • Clause versioning
    • Abstract article references
    • Advanced multi-language features
    • Clauses - FAQ
    • How to: clauses
      • Create an ad-hoc clause
      • Create a library clause
      • Make a clause repeat
      • Make a paragraph within a clause conditional
      • Use a shortcut to refer to a concept
      • Insert a line break or page break
      • Creating a list with both predefined options and free input
      • Defining alternative clauses
      • Creating cross-references
      • Creating signature blocks
      • Creating advanced party introduction clauses
      • Automatically numbered annexes or schedules
      • Reuse any clause in a different context
      • Setting MS Word document properties
      • Add action buttons to clauses
      • Electronically signing documents
  • concepts
    • Introduction to concepts
    • Creating concepts
    • Concept labels
    • Links
    • Organising concepts
    • Concepts - FAQ
    • How to: concepts
      • Add predefines to a datafield
  • Datafields
    • Introduction to datafields
    • Types of datafields
    • Rules of thumb for using datafields
    • Data-expressions
    • Datafield aliases
    • Datafield labels
    • Datafield special tags
    • Datafield descriptions
    • Repeating list datafields
    • Datafield predefines
    • Datafields - FAQ
    • How to: datafields
      • Change datafield type
      • Change the datafield's name or alias
  • Definitions
    • Introduction to definitions
    • How to: definitions
      • How do definitions work?
      • Create a definition
  • Files
    • How files are organised
    • Browse files
    • File types
    • Custom styling
    • Legal comments
    • File description
    • Attributes
    • Reporting
    • File name
    • File category
    • Access rights
    • How to: files
      • Creating advanced folders
      • Naming your files
      • Shortcuts to folders or files
  • Q&A
    • About cards
    • Cards pane
    • About changes
    • Changes pane
    • Types of changes
    • Adding conditions
    • Question options
    • Copying & pasting answers
    • Comments, notes & documentation
    • Interactive Q&A inspection
    • Embedding questions into a document
    • “Changes” button
    • Batch create pane
    • Identifiers pane
    • Import pane
    • Edit clauses pane
    • Q&A options
    • Q&A - FAQ
    • How to: Q&A
      • Create predefined answers to a question
      • Add disclaimers
      • Create categories of questions
      • Modify the exported filename
      • Create a question to change the language of a document
      • Send a questionnaire to someone without a ClauseBase account
      • Create questions for repeating list datafields
      • Selecting legal entities & addresses
      • Create a questionnaire using "batch create"
      • Launch other Q&As
    • Leveraging ClauseBuddy Smart Templates in Clause9
  • Import
    • Introduction to importing clauses
    • Uploading clauses
    • Defined terms in Import mode
    • Datafields in Import mode
    • Cross-references in Import mode
    • Assigning folders
    • Conversion process
    • Exporting
    • Stashing intermediate results
    • Tips, tricks & limitations
  • Styling
    • Styling overview
    • Base styling
    • Numbering
    • Definitions styling
    • Enumerations styling
    • Locale styling
    • References styling
    • Page styling
    • Styling of a Binder versus subdocuments
    • Styling: tips and tricks
    • Advanced styling topics
    • Copying headers and footers from an MS Word file
    • How to: styling
      • Using custom fonts
      • Change bullet styling
  • Special functions
    • Introduction
    • Calculations
    • Concepts
    • Conditions
    • Conjugations
    • Content Control Elements
    • Datafields
    • Dates & durations
    • Languages
    • Lists
    • Numbers
    • References
    • Repeating (looping)
    • Special items
    • Text structure
    • Text modification
    • User
    • Q&A
  • Settings
    • Account
    • Preferences
    • Access bundles
    • Favourites
    • Saved searches
    • Saved datafields
    • Styles
    • Default styles
  • Admin
    • General
    • Users
    • User rights
    • Profiles
    • Groups
    • Styles
    • Default styles
    • Attribute models
    • Usage page
    • Custom homepage
    • Global placeholders
    • Access rights
    • How to: admin
      • Adding a new user
      • Disabling a user
      • Managing group memberships
  • Miscellaneous
    • Advanced tips & tricks
    • Typing special symbols on your keyboard
    • Shortcuts
    • Grammar style guide
    • Inserting MS Word files
    • Globo-panel
    • Creating high-quality documents
    • Excel calculations and lookups
  • Integrations
    • Overview
    • Spreadbases
    • E-signing documents
    • Drag & drop integrations
  • For developers
    • Clause9 API
    • Custom functions
    • Example custom functions
Powered by GitBook
On this page
  • Party description
  • Lease clause
  • Notice clause
  • Using mapping
  • Mapping concepts
Export as PDF
  1. Clauses
  2. How to: clauses

Reuse any clause in a different context

PreviousAutomatically numbered annexes or schedulesNextSetting MS Word document properties

Last updated 1 year ago

Let’s say you are drafting a lease agreement and you are looking for a notice clause. Using the inside the Assemble Document mode, you find the perfect clause. But there’s one problem. That clause was written for a share purchase agreement, with parties being referred to as the Seller and the Buyer…

No problem! In Clause9, you can easily adapt your clause to the document you are drafting by using .

To avoid cluttering your production account, it is advisable following these steps in your Clause9 Sandbox account. If you do not have such Sandbox account, please contact your administrator.

For the purposes of this How To, please create the following clauses and any concepts (with concept labels) and datafields included in there:

Party description

* #lessor^name residing at #lessor^street-number, #lessor^postal-code #lessor^city (as #lessor); and

* #lessee^name residing at #lessee^street-number, #lessee^postal-code #lessee^city (as #lessee)

Lease clause

Clause title: “Lease”

1. #Lessor agrees to lease the premises (as described below) to #lessee.

Notice clause

Clause title: “Notices”

1. Any notice to be sent to #?party under #°agreement shall be sent by registered mail to the address listed below:

1.1. For #seller:

|| % align left, borders false, borders horizontal false % ||
|| #seller^street-number ||
|| #seller^postal-code #seller^city ||

1.2. For #buyer:

|| % align left, borders false, borders horizontal false % ||
|| #buyer^street-and-number ||
|| #buyer^postal-code #buyer^city ||

Insert both clauses in a new document.

Using mapping

Mapping concepts

What we want to accomplish now is that the notice clause we inserted refers to “the Lessor” and “the Lessee” instead of “the Buyer” and “the Seller”. This can be done by using a technique called “mapping”. We can make a concept in a clause (or an entire document) map to another concept, i.e. act as if it were another concept. How do we do this?

Now check out your clause again. Where it said “the Seller”, it will now say “the Lessor”! Do the same for buyer and lessee.

You will notice that in this case the datafields in #buyer and #seller were mapped automatically to the relevant #lessor and #lessee datafields as well. Clause9 will automatically do this if the datafields have the same name and are of the same type.

This underlines the importance of having a consistent naming policy throughout your organisation for concepts and datafields. Datafields will be mapped automatically to other datafields.

Datafields can be mapped manually as well if their names are not identical. The mapping tab contains a map datafields section under the map concepts section. Similarly to mapping concepts, you can select a datafield (in map from) that should act as another datafield (in map to), i.e. take any inputs given to that other datafield.

Mapping datafields will remove the need to enter the same information multiple times in the same document, further adding to time saved by automating your documents!

First, select the notice clause, i.e. the clause you want to adapt itself. Selecting the clause will reveal a new pane in the on the right: the pane. This pane has two tabs: Layout (selected by default) and Mapping. Click on Mapping.

In the Mapping tab, we can choose to map concepts and datafields. In this case, we want the #buyer and #seller concepts to act as if they were #lessor and #lessee. The Map from selector lets you choose a concept that should be changed into another concept (selected in map to). Let’s start with the #seller concept. In Map from, select seller. In Map to, select lessor. To apply the mapping from seller to lessor, click the button.

operations panel
advanced
search functionalities
mapping