End-user testing steps

The end-user who is responsible for testing a Weagree-template should create a contract and answer the related questionnaire. When test-answering the questionnaire, carefully review:

  1. Formulation of Q&A questions. Note that it is possible to mention the (short) name of a contracting party.
  2. Guidance notes (the info icon at the right side of a Q&A question).
  3. The default answer.
  4. The ‘if unanswered’ result: if a Q&A 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.
  5. Alternative answer options and the way they are formulated (in a dropdown, radiobutton or checkboxes).
  6. Alert notices. Immediately underneath a Q&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). Such alert notice may also appear upon choosing one specific Q&A option (e.g. an undesirable Incoterm).
  7. While answering a questionnaire, it is recommended that you have the original model contract opened or printed.

Note that next to each Q&A-question is a small balloon enabling the end-user to provide feedback on the above Q&A-elements. If the contract text would require input, there are also communiication balloons next to each clause in the under-water-screen. As you will see, the poup allows the end-user to ‘classify’ their feedback as ‘typo’, comprehensiveness of a clause or question, etc.

Terms of Use

I hereby accept (or reconfirm my acceptance of) Weagree’ Terms of use, in which:

Terms of Use

I hereby accept (or reconfirm my acceptance of) Weagree’ Terms of use, in which: