Getting the Most Out of Scavenge: A Complete Event Organizer's Guide

Plan host responsibilities for a Scavenge event: joining help, photo approval, fallback, finish and a participant rehearsal before inviting the group.

An organizer’s job continues after the hunt is saved. Someone must explain the rules, help players join, handle ambiguous submissions and call the finish. This guide is a practical host plan for a Scavenge.rs activity, using the product behavior we have actually checked.

For building the task list, follow the main creation walkthrough. For cost and account choices, use the free-creation decision guide. This article covers running the activity and dealing with problems.

Assign the work before inviting the group

Organizer responsibilities that need a named owner
ResponsibilityPrepareRehearse
InstructionsPlaying area, acceptance rules, proposed duration and finish.Ask a tester to explain the first task in their own words.
Joining helpThe saved participant link or code and a host contact channel.Open the actual link in a separate browser and reach Play Now.
Submission reviewExact text answers and the chosen photo-approval arrangement.Submit representative tasks, then check personal completion and approved points separately.
Access and fallbackApproved spaces, current access conditions and a seated, spoken or written alternative.Try the alternative through the same host channel.
ClosingA common finish instruction and a way to report unclear tasks.Complete the final task and return to the agreed meeting point or channel.

For a mixed-location activity, name a remote co-host as well as the room contact. Use the remote-and-room brief for equivalent task rules and roles. These are facilitator responsibilities; they are not promises of automated messaging, live player tracking or built-in video calls.

Choose how photos will be checked

For a friendly guest activity, automatic approval awards points on upload receipt. The host can discuss whether the image fits the prompt through the event’s agreed channel. Receipt approval itself does not assess image content.

If you need the tested manual account queue, use separate signed-in organizer and participant accounts with automatic approval off. In our 10 October internal pilot, the participant uploaded a synthetic object-only image; the organizer opened the saved hunt’s Answers tab and used Approve Photo. The submission went from zero to ten approved points and the result persisted.

A guest upload with approval off can be personally complete with zero approved points, and our fresh guest test did not appear in that organizer account’s queue. An organizer account alone does not make anonymous photos reviewable there. Pilot the actual participant arrangement before attaching prizes or a ranking to it.

Run a short rehearsal from the participant side

  1. Enter a text task, a representative photo and an informational finish using the tested three-task worksheet.
  2. Save the hunt and open the resulting link or code in a separate browser.
  3. Read the displayed hunt title and instructions; reach the actual task controls.
  4. Submit the tasks and check their saved state, including any approval decision.
  5. Record failures and the release decision in the pilot checklist.

Our owned browser tests demonstrate a small workflow. They do not establish signup success, camera quality, a group attendance limit or customer outcomes. Use the actual devices, connection and arrangements your event needs.

Help through the channel you agreed on

Give the host’s contact details and the finish instruction outside the hunt as well. Use your chosen meeting, messaging or spoken channel for reminders. Avoid assuming that all players will notice an edit made during the activity; communicate a changed rule clearly to everyone.

When someone is stuck, identify the failure before changing the whole hunt. A wrong URL, rejected text answer, missing upload and pending approved points need different responses. For phone tasks, the mobile browser guide gives practical checks.

Keep the event’s boundaries clear

Guest creation and play are available in a connected browser. Keep the creator browser’s storage for guest ownership or establish optional account access. Private visibility keeps a hunt out of public discovery; it is not a password. Keep confidential documents and identifiable strangers out of your task examples.

Basic creation is free, while some catalogue hunts and Date Hunt are paid experiences. Venue tickets, travel, food and host time are separate event decisions. A group sharing one device is a facilitation choice, not evidence of automatic team administration or a tested capacity limit.

Close with observations you can use

Ask which instruction needed explanation and record the actual task failures. If you report completion rates, state the number of starters and finishers and the denominator used. Browser sessions are not automatically unique people. Keep observations separate from claims about improved engagement, productivity or retention.

Resolve required failures before reusing or expanding the activity. Create a small practice hunt, use the first-hunt rehearsal and choose the simplest proof rules your host can consistently apply.