Definitions are separate files in ClauseBase, much as clauses are and operate in much the same way, both in how they are created and how their content is structured.
A definition file in ClauseBase essentially acts as only the explanatory part of a definition in a traditional contract. Take the following example:
“Director”: a director of the Company;
Just as this example from a Word document has a “concept” part, i.e.: “Director” and a “content” part, i.e.: “a director of the Company”, so too does ClauseBase distinguish between these parts.
In ClauseBase, you create a definition file for the “content” part of the definition and then assign it to a concept, which forms the “concept” part of the definition. When such a concept is used in a clause and that clause is used in a contract, ClauseBase will be able to include it in its overview of used concepts under the terms menu of the operations toolbar. From that menu, you can easily assign a definition to this concept, provided that concept has a (number of possible) definition(s) assigned to it.
It is good practice to store definitions in designated folders, so you can easily distinguish between types of files.
For an overview of how to put this knowledge into practice to create a definition, click here.