SCAVENGE HUNT PILOT CHECKLIST
https://scavenge.rs/resources/hunt-pilot-checklist.html

Organizer: __________  Hunt title: __________
Pilot date: __________  Browser/device: __________
Hunt link or join code (keep private if appropriate): __________
Format: __________  Planned guest/account arrangement: __________

ENTRY
Try: Open the saved hunt URL in a fresh browser without the creator session.
Pass condition: Correct title, admission terms and Play Now control appear.
Result: PASS / REVISE / NOT TESTED
Observed result and next action: __________________________________

JOIN CODE
Try: Open the saved join-code route or enter the code on Join Hunt.
Pass condition: The intended hunt appears. A printed QR also needs a real camera test at your venue.
Result: PASS / REVISE / NOT TESTED
Observed result and next action: __________________________________

CREATOR ACCESS
Try: Return to the creator browser and reopen the saved hunt.
Pass condition: You can manage it using the browser or account arrangement planned for the event.
Result: PASS / REVISE / NOT TESTED
Observed result and next action: __________________________________

TEXT ANSWER
Try: Submit the intended answer, a wrong answer and likely spelling variants.
Pass condition: You can explain which inputs are accepted and revise an ambiguous clue.
Result: PASS / REVISE / NOT TESTED
Observed result and next action: __________________________________

PHOTO RECEIPT
Try: Upload a harmless object image with the planned approval setting.
Pass condition: Record upload, personal completion and approved points separately.
Result: PASS / REVISE / NOT TESTED
Observed result and next action: __________________________________

CONTENT REVIEW
Try: Try your actual organizer and participant arrangement.
Pass condition: A guest-run pilot can use automatic receipt approval plus external discussion. Human approval inside the app requires its own verified account workflow.
Result: PASS / REVISE / NOT TESTED
Observed result and next action: __________________________________

FINAL STEP
Try: Use the final task’s completion action.
Pass condition: Reach the completed-hunt screen; note whether completion persisted after refresh.
Result: PASS / REVISE / NOT TESTED
Observed result and next action: __________________________________

EVENT ALTERNATIVES
Try: Try the written/verbal or host-assisted equivalent.
Pass condition: The facilitator can apply the same event rule; a photo task does not automatically turn into a text task.
Result: PASS / REVISE / NOT TESTED
Observed result and next action: __________________________________

DEVICE AND CONNECTION
Try: Try the actual phone/browser and network at the event.
Pass condition: You can read the tasks and submit work. Browser play requires internet; a paper fallback is separate.
Result: PASS / REVISE / NOT TESTED
Observed result and next action: __________________________________

GROUP INSTRUCTIONS
Try: Read the invitation, time limit and scoring rules aloud.
Pass condition: Participants know whether they share a device, how help works and which awards the host tracks separately.
Result: PASS / REVISE / NOT TESTED
Observed result and next action: __________________________________

RELEASE DECISION
Ready / revise and repeat / use a separate paper activity
Unresolved checks: __________________________________
Host help contact and event fallback: __________________________________

Use this worksheet to record your own test. It is not a promise of capacity, device compatibility or automatic photo-content review. Different browser sessions are not verified different people. A private listing setting is not a password on a shared hunt URL.

Create a free hunt: https://scavenge.rs/create-hunt
Step-by-step tutorial: https://scavenge.rs/blog/how-to-create-a-scavenger-hunt-complete-platform-tutorial
Copyable three-task activity: https://scavenge.rs/resources/three-task-browser-hunt.html