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
  • Setting up the structure
  • Adding details of the parties
  • Creating concepts and datafields
  • Adding space for the signatures
  • Formatting the table
  • Finishing your work
Export as PDF
  1. Clauses
  2. How to: clauses

Creating signature blocks

PreviousCreating cross-referencesNextCreating advanced party introduction clauses

Last updated 1 year ago

Drafting an agreement — or sometimes other types of documents — means that, somewhere in the document, you will have to add a signature block. There should be at least as many signature blocks as there are parties, containing their names and titles. How to go about this?

Let’s go over a step-by-step example. We will be making a signature block for a lease agreement between two parties (legal entities), each being represented by max. two persons (who may be acting in various capacities). We will be working in the Assemble Document mode for the purposes of this How To.

The video above is a more basic introduction to signature blocks and therefore does not follow the structure of the article below.

Setting up the structure

|| || ||
|| || ||
|| || ||
|| || ||

Any new clause will contain a paragraph number already (“1.”). If a clause contains only a table, this number has to be removed. A table on itself cannot be a numbered paragraph — it can, however, be part of a numbered paragraph or clause if text is added before the table and an empty line is left between the text and the table.

Adding details of the parties

Our signature block must contain the following information:

  • the name of each representative

  • the title / capacity of each representative

Creating concepts and datafields

Creating a concept & concept label

Click on #lessor and select create a new Concept.

Adding datafields

Hit the save in library button in the bottom left corner.

Populating the table

Our table is still mostly empty for now, so let’s start giving it some actual content. The first row already contains #Lessor.

Capitalising the first letter of #Lessor makes sure that any article being added in front of it will be capitalised. That is why capitalising a reference to a concept should only be done in the beginning of a sentence (or in any other case where you would want the first letter of the article to be capitalised as well).

|| #Lessor                              ||                                      ||
||                                      ||                                      ||
|| Name: #lessor^representative1-name   || Name: #lessor^representative2-name   ||
|| Title: #lessor^representative1-title || Title: #lessor^representative2-title ||

Tip: when creating a table, the text can start looking messy. However, ClauseBase has a feature to make your source text more easily viewable. Click the three dots in the top right corner of the clause editor and choose reformat tables. Now your source text will be reformatted to look more like the actual table.

Having added the datafields, any user can complete the details of both representatives in the table.

But there are undoubtedly cases where the Lessor will be represented by only one representative (e.g. in case of a power of attorney granted to one person). How can we avoid having a placeholder in our text if the details of only one representative have been completed?

To make our column conditional, we have to add an additional row on top of our table, which contains the condition for a column to be shown in the relevant column.

A condition in ClauseBase is always written between curly brackets ({ }). The condition we will be using is: if #lessor^representative2-name was assigned a value, only then the column should be shown. In ClauseBase grammar, the cell on top of the column would then look as follows: {@assigned(#lessor^representative2-name)}. Technically, @assigned will return “true” if #lessor^representative2-name was assigned a value and “false” if it wasn’t. If the condition evaluates to false, the column will not be shown. Adding this to our table (and reformatting it) results in the following:

||                                      || {@assigned(#lessor^representative2-name)} ||
|| #Lessor                              ||                                           ||
||                                      ||                                           ||
|| Name: #lessor^representative1-name   || Name: #lessor^representative2-name        ||
|| Title: #lessor^representative1-title || Title: #lessor^representative2-title      ||

Adding space for the signatures

Now our table contains an empty row where the signatures should go. However, we need an indicator where each representative should sign.

||                                      || {@assigned(#lessor^representative2-name)} ||
|| #Lessor                              ||                                           ||
|| % signature %                        || % signature %                             ||
|| Name: #lessor^representative1-name   || Name: #lessor^representative2-name        ||
|| Title: #lessor^representative1-title || Title: #lessor^representative2-title      ||

Formatting the table

Now that the content of our table is ready, let’s make sure it looks good as well. For the purposes of our tutorial, we want a table that is aligned to the left, with the name of the party in all caps and bold and without any borders.

To do this, we need to add a new row with one single cell on top of our table. This cell will contain our styling settings for the entire table, each separated by a comma, as follows: || % align left, borders false, borders horizontal false, borders vertical false % ||.

Next we add the bold and all caps deviating styling to our (now) third row between % symbols: % bold true, all caps %. The entire table should now look as follows:

|| % align left, borders false, borders horizontal false, borders vertical false % ||
||                                      || {@assigned(#lessor^representative2-name)} ||
|| % bold true, all caps % #Lessor      ||                                           ||
|| % signature %                        || % signature %                             ||
|| Name: #lessor^representative1-name   || Name: #lessor^representative2-name        ||
|| Title: #lessor^representative1-title || Title: #lessor^representative2-title      ||

Finishing your work

The signature block for the Lessor is now complete. Duplicating it for the Lessee should now be easy: just copy/paste your Lessor table and replace the #lessor concept by #lessee, after having created the relevant datafields.

For a more advanced exercise, you can try to make the signature block repeat itself. This can be handy in case it is possible the agreement will be entered into between multiple lessors and/or lessees.

After having done so, select your clause and click the advanced tab in the operations panel. Under repeat clause, choose a datafield on the basis of which the clause should repeat itself (e.g. the repeating list datafield containing the names of the lessors/lessees). If done correctly, the signature block should now be repeated for as many times as there are inputs assigned to the datafield of your choosing.

Create a new library clause by clicking the button and selecting New library clause. First we must decide how to structure our signature block. Signature blocks are usually structured as two separate blocks next to each other (either for two parties or for two representatives of some party). There should be some space for the actual signature to go. That’s why seems to be the most appropriate way of structuring the signature block. Let’s set up a basic table.

We need at least 4 rows (name of the party, space for the signature, name of the representative and his/her title) and 2 columns (one for each representative). Following the rules of , that would look as follows:

In normal circumstances, you would have already made the concepts and datafields implementing the parties and their information. For the purposes of this tutorial however, we will do it from scratch. If you are familiar with creating concepts and datafields, please skip ahead to .

can be . We will be creating them from inside the Assemble Document mode. The first party signing our agreement will be the lessor, so let’s create a concept for the lessor by typing #Lessor in the top left cell. If this concept does not exist yet, you will be shown a red alert underneath the clause editor:

Now we have to choose a location for our concept. Typically this would be a special concepts folder (which can be created by holding Shift and clicking ) in the appropriate place in your clause library. Browse to the location of your choosing and click select current folder. A new tab will now be opened in our editor to complete the properties of our newly created concept “lessor”. Navigate to the concept labels property of the concept (in the navigation menu on the right).

Add an English concept-label by clicking the button. Singular will be “lessor” and plural “lessors”. Choose “neutral” for the gender. The other options are fine: a defined article (“the”) must be used, by default this concept label should be singular and its capitalization may be adapted to the applicable grammar & styling.

While still in the concept editor, navigate to datafields in the menu on the right. We need four different : one for each representative’s name and one for each representative’s capacity. As these are textual inputs, we will choose text type datafields.

Click the button and select text. Give your datafield a name, e.g. representative1-name. Repeat this for each of the four datafields (representative1-name, representative1-title, representative2-name and representative2-title).

The third and fourth rows should contain the names and capacities of the representatives of the Lessor. The #lessor concept should already contain the relevant datafields (if this is not yet the case, please follow the instructions in ). Add these datafields to the relevant cell by appending the name of the datafield behind #lessor and adding a ^ symbol in between. Our table will now look like this:

We can do this by adding to the details of our second representative. In this case, we want the second column of our table not to be shown unless the name of the second representative has been completed. To achieve this, we will make use of the @assigned special function. This function will evaluate whether a datafield was assigned a value or not and will on that basis return true or false.

We can make use of the % signature % functionality included in ClauseBase. Typing % signature % in both cells of the third row. This will make sure a dotted line is inserted, with sufficient space above and below the line for a (large) signature. Check out the article on for more information.

Alternatively, you could make use of the @tab-u in the third row to create a full line instead of a dotted line.

Adding styling to a table can be done either by modifying the of the clause containing the table or by adding to our table itself. We will go with the second option in this tutorial.

First, replace all text datafields for the names of the lessors/lessees, their representatives and the capacities of their representatives by of type text. This will make sure the input can be different between the various repeating instances of your signature blocks. In addition, instead of only referring to the concept label of #lessor or #lessee, the signature block should probably now also refer to the individual name of the relevant lessor/lessee to make sure on whose behalf the agreement is being signed.

making tables in the ClauseBase grammar
Concepts
created in various ways
datafields
a condition
Special codes
special function
custom styling
deviating styling
repeating list type datafields
Populating the table
Adding datafields
a table