One or more end user should be designated for testing the contract template. End-user testing requires creating a contract and answering the related questionnaire. When testing the questionnaire, carefully review:
a. Formulation of Q&A questions. Note that it is possible to mention the (short) name of a contracting party.
b. Guidance notes (the info icon at the right side of a Q&A question).
c. The default answer.
d. The ‘if unanswered’ result: if a question remains unanswered (empty field), a text can be inserted that may trigger the user to complete the contract after the Word-document is generated. Weagree’s approach is to insert a ‘blob’ between square brackets ( [●] ) or leave an all-caps instruction between square brackets.
e. Alternative answer options and the way they are formulated (in a dropdown, radiobutton or checkboxes).
f. Alert notices. Immediately underneath a question, an alert notice or warning may be added (for example that ‘legal’ or ‘tax’ must be involved, or that in certain cases, selecting an option may trigger competition law concerns). An alert notice can also appear upon choosing one specific answer option (e.g. an undesirable Incoterm).
g. While answering a questionnaire, it is recommended that you have the original model contract on hand for reference (printed or opened in Word).
Note: in the questionnaire, a speech balloon appears next to each question. This enables the end user to provide feedback on the above Q&A elements. Speech balloons also appear next to paragraphs in the WYSIWYG view (‘underwater screen’) for feedback on the contract text.
