Use only for an actual authorised test. Blank fields are not evidence of completion. Use an event code, not participant names.
Event code / date: ___________________
Operator code / facilitator code: ___________________
Number of adults / number in each crew: ___________________
Mode / devices / print or screen: ___________________
Did the facilitator prepare and start without help from the designer? Yes / No. Help minutes and exact issue: ___________________
| Stage | Start / end | Hints / attempts | Explained or guessed? | Ambiguity / missing instruction |
|---|---|---|---|---|
| P1 | ________ | ________ | ________ | ________ |
| P2 | ________ | ________ | ________ | ________ |
| P3 | ________ | ________ | ________ | ________ |
| P4 | ________ | ________ | ________ | ________ |
| P5 | ________ | ________ | ________ | ________ |
| P6 | ________ | ________ | ________ | ________ |
Actual briefing / play / debrief minutes: ___________________
Who had no useful contribution for a stage? Use role/crew, not names: ___________________
Any access needs or instruction adaptations? ___________________
Could the group explain each dependency, rather than merely report a code? ___________________
Any crash, lost state, unreadable print, or incorrect scoring? Reproduction steps: ___________________
Could the facilitator reset and run a second group without design help? Not tested / Yes / No.
Operator question: where, if anywhere, would this replace an existing rain contingency? ___________________
Do not turn “fun”, an intended future booking, or free replay into a sale. Record a real transaction separately only if one occurs.