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
  • Introduction
  • Details
  • Use cases
  • Nesting of square brackets
  • Inheriting the shrinking levels
  • Shrinking an entire document
  • Usage tips
Export as PDF
  1. Clauses

Shrinking clauses

PreviousDeviating table stylingNextAction buttons

Last updated 1 year ago

Introduction

When a part of a paragraph is wrapped in @superfluous, users of the clause can shrink down the clause with the Shrink or expand text button of the menu in the upper right corner, in order to hide that wrapped part.

Example:

Supplier will @superfluous(1, "acknowledge and") agree that timing is of the essence.

When no shrinking is applied, the existence of the special function will simply be ignored, and this clause will be shown in full:

The Supplier will acknowledge and agree that timing is of the essence.

However, when full shrinking is applied, the part within the special function will be dropped:

The Supplier will agree that timing is of the essence.

Details

Shrinking opportunity indicators

Use cases

The typical use case of the clause shrinking feature is to hide text that can be assumed to add relatively little legal content to a paragraph. This may, for example, be the case with:

  • sentences that are inserted “for the avoidance of doubt”

  • synonyms of words that are mainly inserted because of legal tradition

  • text for which all the words may be mandatory / recommended under a certain jurisdiction, but that would be considered extraneous in other jurisdictions (e.g., under many continental European law systems, “acknowledge and agree” instead of simply “agree”)

This way, you can create alternative versions of a single clause, without having to create separate “light”, “medium”, “strong” versions.

Similarly, while datafields can be used to achieve similar effects (and much more), they require more effort to insert.

Nesting of square brackets

Clause9 currently allows up to four levels of nested superfluousness-text. Shrinking level 1 will discard any text within the @superfluous call, while shrinking level 2 will also show the text within the first call, and shrinking level 3 will also show the text within the second (i.e., inner) call. And so on.

By way of example:

This will result in the following possible paragraphs:

  • Shrinking level 1 — The Supplier will agree that timing is of the essence.

  • Shrinking level 2 — The Supplier will acknowledge and agree that timing is of the essence.

  • Shrinking level 3 — The Supplier will explicitly acknowledge and agree that timing is of the essence.

  • Shrinking level 4 — The Supplier will explicitly and before the commencement date acknowledge and agree that timing is of the essence.

  • Full text — The Supplier will explicitly and, if so requested by the Client, before the commencement date acknowledge and agree that timing is of the essence.

Inheriting the shrinking levels

The shrinking level applies to all clauses within a clause file. However, to allow a shrinking level to be applied to many clauses at once, the shrinking levels are inherited between clause files, except if a descendant would define its own shrinking level.

For example, assume that in the following example the five clauses (Alpha, Beta, Gamma, Delta and Epsilon) are all stored in separate files.

Assume that Alpha is set to shrinking level 1. Then both Beta and Gamma will inherit this shrinking level (because they are the descendants of Alpha), and will thus also show their text at shrinking level 1. Delta, on the other hand, is a sibling of Alpha, and will therefore not inherit the shrinking level of Alpha. The same applies to Epsilon.

Now assume that Beta is set to level 3. This will cause its descendant Gamma to also show its text at level 3, except if Gamma would define its own level. Note that changing the level of Beta or Gamma will never impact Alpha, Delta or Epsilon.

Shrinking an entire document

If no clause is selected when changing the shrinking level, then the shrinking level of the entire document will be set. Note that the document acts as an ancestor of all clauses, so that — except if some clause (or one of its ascendants) would define its own shrinking level — all clauses will inherit the shrinking level of the Document. This allows you to quickly “compress” a document.

Usage tips

Avoid superflousness-calls at the beginning of a sentence: if such part would get omitted, then the remaining part of the sentence would be shown without a capital.

Be aware that, if several sets of square brackets would be used in a single clause file, all of those sets will show and omit their text in lockstep.

In the actual document (left side) of Assemble Documents, it is possible to show green indicators, by enabling “clause shrinking opportunities” in the options button at the right side of the toolbar. By default, these indicators are not shown.

If you want to nest multiple square brackets, you must use .

internal snippets