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
  • Cross-references within the same clause file
  • Other numbered sub-clause
  • Cross-references between/across internal snippets
  • Clause as a whole
  • Bullets
  • Cross-references to clauses outside the clause file
  • Using concepts
  • Using cross-tags
  • Cross-references to definitions
  • Cross-references to other subdocuments
  • Relevant styling settings
Export as PDF
  1. Clauses

Cross-references

In Microsoft Word, you refer to other clauses by their numbering. In Clause9, how you refer to other clauses will depend on the location of the target — whether this target is located in the same clause file, or whether it is located in some other file.

Cross-references within the same clause file

In the discussions below, the following sample clause is used:

1. Alpha
2. Beta
2.1 Gamma
* Delta 
* Epsilon
* Eta

because of preceding articles in a hypothetical document, that clause happens to render as follows:

X. Alpha
XI. Beta
A. Gamma
i) Delta
ii) Epsilon
iii) Eta

In the discussions below, we assume that the References Styling for English is set to use “article” for referring to clauses.

Other numbered sub-clause

To refer to some other numbered sub-clause, you use §number. For example, to refer to 2. Beta, you would use §2 . Clause9 will then replace it by a proper cross-reference to that subclause (in the example case “article XI”).

If you want to start this reference with a capital (e.g., at the beginning of a sentence), then use special function @capitalize. In the example above, @capitalize(§2) will result in “Article XI”.

Cross-references between/across internal snippets

It is not possible to refer to numbered sub-clauses across internal snippets. For example, the following will not work:

The reason this does not work, is that each internal snippet can have its own internal numbers, which may perfectly overlap with the numbering of the top-level clause. For example, in the screenshot below, the reference to §1 would be ambiguous if it could also refer to the top-level paragraph.

Clause as a whole

In contracts, you frequently refer to the clause itself, e.g. when expressing “As set forth below in this clause XXX, the Buyer will …”.

To insert such a reference, you use §this to refer to the current numbered subclause, and §this-title to refer to the encompassing title of the entire clause file (assuming that title is currently visible).

For example, if you would insert §this within 2. Beta, the reference would become “this article XI”.

Notice the addition of the word this — in French this would for example, depending on the References Styling, become “cette clause XI” or “cet article XI”. Conversely, when you would insert §this within * Delta, the reference would become “this article 2.1”, because 2.1 is the nearest numbered subclause.

When you insert §this-title, Clause9 will refer to the number of the title associated with the clause file.

If that title is not currently visible, an error will appear.

To capitalise these cross-references, use a capital T. In the example above, §This will for example result in “This article 2.1”.

Bullets

Within a bullet (asterisks) list, you can refer to the current bullet using §*, the next bullet with §*+ and the previous bullet using §*-.

This will only be useful if bullets happen to be styled using iterative numbering such as 1, 2, 3 or a) b), c). If you use symbols that are the same in the entire list (such as a circle or square), Clause9 will rever to literal “the current bullet” or “the next bullet”.

Cross-references to clauses outside the clause file

Using concepts

Concepts are the most powerful method to refer to clauses outside the current clause file. When using §#concept, Clause9 will replace that part of the text with a cross-reference to the first clause that implements that clause, i.e. that contains an implements link towards that Concept.

This is a very powerful mechanism, because it allows you to create cross-references on a subject-basis instead of on a numbering-basis (as is the case in Microsoft Word, which causes much more brittle cross-references). Clause9 will even be as helpful to show a list of those clauses that are accessible to the user and implement the specified concept, when no such clause is yet available in the document.

Using cross-tags

Using concepts and §#concept cross-references is the recommended approach, because it allows you to create a central repository of clauses that implement certain legal subjects.

Sometimes, however, the concepts-approach is somewhat burdensome, because it does require you to create a concept for each and every cross-reference you want to establish towards other clause files.

If all you want is a simple, one-time cross-reference to some specific clause in your document, it is probably easier to use the so-called cross-tags:

  • Assign some cross-tag (e.g., “liability”) to the target clause, using the cross-tags section of the clause. Don’t use any spaces inside a cross-tag.

  • Insert a cross-reference to that cross-tag in some other clause using §tag (e.g. §liability).

Similar to @implemented for concept-based cross-references, there is also a @crosstag-implemented function that returns true when a currently visible clause implements the specified tag.

To capitalise these cross-references, start them with a capitalised letter. In the example above, §Liability will for example result in “Article 2.3” if that article happens to implement tag liability.

Cross-references to definitions

You can insert a cross-reference to the definition of a concept using §$#concept.

Cross-references to other subdocuments

Similar to cross-references to other clauses, you can refer to other subdocuments with a hashtag. For example, if some subdocument is specified to implement Concept #pricing, you can refer to this subdocument with §#pricing.

Clause9 will insert the short document title (or the long document title if the short one is not available) after the article reference. The actual wording will be determined by the References styling.

Relevant styling settings

  • the word to use (e.g., in English, article vs. clause vs. section)

  • how you refer to clauses in other subdocuments (i.e., whether & how the title of that other subdocument should then be shown)

  • whether to use the title between parentheses after the target article’s number — e.g. “see article 5 (liability)“. Note that such part between parentheses will only be inserted if §#concept or §tag references are used, and if the target clause effectively contains a visible title.

PreviousLinksNextIntroduction to tables

Last updated 1 year ago

Read our introductory on this topic.

It can also be helpful to check whether some clause is available in the current document that implements a certain clause: the and its siblings and .

Note that several settings determine the way :

blog post
references are styled
@implemented special function
@implemented-any
@implemented-all