A clause that is not intended to be reused outside the document/binder in which it is contained. In other words, a clause that is so specific that it has little usefulness outside the specific document/binder in which it is inserted.
Unlike a library clause, an ad-hoc clause cannot be searched on, and is not directly visible inside the file browser, because it is stored inside its document/binder. (Advanced users can, however, dig into a document/binder to reveal the internal structure and the ad-hoc clauses.)
The opposite of an ancestor clause is a descendant clause.
Any paragraph that is not a heading. A body paragraph can optionally have a (single-level) number.
User whose rights are limited to completing Q&A sessions. Typically such user will not have legal expertise.
see also: legal user and clause author
(sometimes also called a “clause file” to avoid confusion) One of the file types available in ClauseBase, that will contain text. A “clause”, in ClauseBase terminology, can be as short as a single word, and almost as long as you want (e.g., spanning multiple pages of text, with various headings, body-paragraphs, sub-headings, etc).
see also: ad-hoc clause and library clause
Legally trained user who will not only use pre-existing clauses, but also draft new clauses. Consequently, clause authors should have a good understanding of the ClauseBase Grammar. Typically, clause authors will also create new Q&A sessions.
see also: business user and legal user
The opposite of an ancestor clause is an ancestor clause.
(also called the “ClauseBase Grammar”) The special codes inserted in the text of a clause, in order to enrich it with special features — such as making a part of the text conditional, or automatically inserting today’s date.
Any paragraph that will be formatted with the heading numbering styling — so typically in a larger font, bold, etc.
From a technical perspective, a heading is a paragraph within a clause that is numbered with legal-style numbering (1., 1.1, 1.1.1, etc) within the ClauseBase Grammar.
see also: body paragraphs
Legally trained user who uses the Assemble Documents Mode (and maybe occassionally also the Design Q&A Mode), but who will generally not draft new clauses.
see also: business user and clause author
Clause that — unlike ad-hoc clauses — is intended to be reused in multiple documents. Library clauses can be stored in a personal library, a group library, or the customer library.
A special mode in which clauses may get replaced by shorter versions of themselves, or even left out. Typically, these shorter versions will also be written without any “legalese”, so as to increase the readability for business users who are not legally trained.
For example, in a company’s standard sales agreement, the reporting mode can be used to leave out standard clauses, or replace them with a short title and “company standard clause about … “. This way, when business users (including, in particular, executive management) would have to review a contract that was modified after negotiations with a customer, they will not be distracted by the standard clauses that were left untouched.