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
  • What are concepts?
  • Breakdown of concept information
Export as PDF
  1. concepts

Introduction to concepts

What are concepts, why are they so important, and which elements of data do they store?

PreviousElectronically signing documentsNextCreating concepts

Last updated 1 year ago

What are concepts?

Concepts are central to the functioning of Clause9. They have a dual purpose:

  • They represent defined terms in a legal document (typically words that get capitalised in formally drafted contracts, e.g.: “the Employee”, “the Commencement Date”, “Confidential Information”, etc.)

  • They provide a central storage location for datafields.

Both purposes will often — but certainly not always — overlap. Hence, a concept should be created either because that word would typically be written with a capital, or because you need to define a few centralised storage locations related to that concept. Both purposes at the same time will also happen very frequently.

For example, a typical employment agreement will almost certainly have to use the concepts #employer and #employee — not only because both words would typically be written with a capital in formally drafted contracts, but also because various datafields relating to an employer or an employee will be relevant (e.g., an employer’s address, an employee’s function, an employee’s commencement date, etc).

Breakdown of concept information

When you create a new concept, you are presented with several options to provide information about them (see the column on the right-hand side in the image above). Below, we go over each pane.

  • File name — The pane shown in the screenshot above. It allows you to set the file name of the concept's file, optionally in multiple languages. Similar to the filenames you would use on your Windows pc or Mac, file names should not be too long, to allow users to quickly glance over lists of files.

  • Description — An optional pane that allows you to provide a description for a concept, for example in which kind of documents this concept should be used, or how this Concept is different from another concept. This content can later be searched on. Unlike file names, there is no real limit to the length of the description you can provide.

  • Category — Allows you to group different concepts into common categories. If a document simultaneously refers to many different concepts, it may get difficult to find the concept you are looking for. Grouping into categories can then help.

  • Links — Allows you to link the concept to clauses and other concepts to express relationships.

  • Datafields — Remember the second purpose of a concept in Clause9? This pane will allow you to attach dynamically updated information to a concept (such as names, addresses, company numbers, etc.).

  • Concept labels — This pane relates to the first purpose of concepts in Clause9, which is to provide a tool to show defined terms in a legal document (typically in capitals). Which term will actually be used for a certain concept can be freely defined by the legal user who assembles a document, but in general it is a good idea to provide a small collection of predefined terms for each concept (e.g.: for the concept “contract”, we could provide concept-labels of “contract”, “agreement”, “master services agreement”, “non-disclosure agreement”, “share purchase agreement”, etc.).

  • Access rights — manually determine who the owner of a concept will be (if you want to designate someone other than yourself) who will then have editing rights over this file. You can also determine access rights for everyone except the owner.

Data expressions — A "data expression" is an advanced functionality. Its purpose is to avoid having to recreate certain calculations across different clauses and will only be available to legal engineer user profiles. For more information, click .

here