Can I make a library clause conditional without affecting other documents?

Yes, you can.

However, making a change to a library clause applies that change to all uses of the clause. Not only all future uses, but also all uses of the clause in existing documents as well. That is why it can be dangerous to change a library clause. There is, however, a way to work around this to make your entire clause conditional for your specific document.

  1. Insert the clause into your document.
  2. Select it and click the pencil icon, then click “convert to independent ad hoc clause”.
  3. Add the condition you want to the “enabled?” property of the ad hoc clause.
  4. Hit save.

After going through these steps, your clause should have become conditional (using the condition in the ad hoc clause).

You can do this for a clause, subclause or even clauses used in an enumeration/bullet list.

Should I make one highly automated clause or two or more alternative clauses instead?

When faced with a complex clause containing many options, you can either:

  • make a highly automated clause the text of which varies on the basis of the input assigned to datafields, its context, other clauses implemented in the document, etc., or
  • make multiple alternative versions of the same clause instead.

The preferable option depends on a number of variables. For example, your company’s policy may prefer one option over the other. 

An important consideration as well is whether the clause(s) should be capable of being used in many different contexts. If that is the case, it may be preferable to split the clause in a number of alternatives without relying too heavily on the context where it will be included or on very document-specific concepts/datafields.

On the other hand, a highly automated clause may be easier to build a questionnaire around as use can be made of the batch create mode of Design Q&A.

Finally, consider the end users of the clause(s) as well. Some users may prefer to choose between a number of alternatives as opposed to one clause that adapts automatically, while some (non-legal users, for example) may prefer to have it the other way around.

What is the difference between library clauses and ad-hoc clauses?

Library clauses are stored in some clause library and can be reused from document to document. For information on how to create library clauses, click here.

You can store clauses in different clause libraries: either your personal library, or your organisation’s central library, or the library of one of the departments/groups you are a member of. More information.

Ad-hoc clauses are document-specific clauses that only appear in the document in which they are created. For more information on how to create ad-hoc clauses, click here.

You should only rely on ad-hoc clauses if the clause you are drafting is so specific that you know you will not be using it in other documents. If there is a possibility that you would use it in other documents, it is better to save it in your personal library so that you can still access it but your organisation’s library does not suffer from the clutter.