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.