P2P

39 I L T A N E T . O R G presentation of the questions and the ways in which you can use the responses to control language in the document. A B I L I T Y T O C A L C U L AT E R E S U LT S For most types of documents, it would be nice if the platform had the ability to calculate text, dates or numbers based upon previous inputs. With this functionality, if the answer to a subsequent question could be calculated or inferred based upon prior responses, then the questionnaire wouldn't need to ask the question at all. For example, identifying a party as male could automatically calculate and insert the he/his/him pronouns without separately asking those questions. If you enter the term, principal amount and interest rate for a promissory note, then it could automatically calculate (and round) the payment amount. If you provided the commencement date, it would be able to calculate the maturity date based upon the term. Some DA platforms have the ability to calculate almost anything you can think of based upon inputs. The more sophisticated this capability (if it exists), the faster you'll be able to assemble complex documents and the less margin for error you'll have to deal with. I view this capability as essential for most documents. A B I L I T Y T O H A N D L E C O N D I T I O N A L L O G I C Ideally, you would have the ability to include or exclude any text based upon single or multiple conditions (sometimes referred to as business rules). For example, a provision may be included (or not) based upon the response to a single true/ false variable such as "Include guardianship provisions?" Another provision may be included or excluded based upon the response to a multiple choice such as "Type of will: Simple Pour-over." Still other provisions might be included based upon a compound test such as a) the client is married, b) it's a pour-over will, and c) the client's spouse is appointed as initial or successor Executor. Finally, text may be conditional based upon a calculated result such as if the number of Co-Trustees entered is greater than 2. The ability to conditionally include text based upon simple or complex tests is typically required for automating reasonably complicated documents. This functionality also allows you to present users with a laundry list of possible clauses or phrases to include. For example, see the "permissible appointees" question below: Finally, you will need the ability to handle nested logic which is sub-logic contained within larger, optional segments of the document. For example, you may have conditional logic surrounding a Guardianship provision in a will. If it is included, then you may have versions of the language for sole guardians or co-guardians which need to be conditionally included based upon the number of initial guardians entered. Further, if co-guardians are appointed, there may be optional language for what happens if one of the co-guardians is unable to serve. For example, the text will be different if the remaining co-guardian can serve alone, or if a new guardian must be immediately appointed to replace the one unable to serve (so there are always co- guardians). A B I L I T Y T O G AT H E R A N D P R O C E S S L I S T S / R E P E AT S Nearly all legal documents have parties and in most, the possibility exists that you may have more than one. Lists or repeats provide the ability of the platform to allow a user to enter an unlimited number of records (grantors, grantees,

• Cover