How to Create a Scavenger Hunt (Step by Step)

How to create a scavenger hunt with the current Scavenge.rs builder: guest creation, clue types, points, review, GPS, QR and a tested sharing checklist.

Build a scavenger hunt by choosing a purpose, writing testable clues, deciding how answers will be reviewed, and sharing the finished hunt with players. On Scavenge.rs you can use the browser builder without downloading an app. Creating a free hunt and playing as a guest are supported; paid hosting requires an account and payment setup.

This walkthrough follows the current Scavenge.rs hunt builder. For an overview of guest play and sharing, see the no-download guide. You can also run the sample below on paper if your group needs a backup.

Ready to follow these steps? Open the guest hunt builder directly. Use the three-task worksheet as a practice activity, or compare app access and free-plan limits first.

1. Plan the event before opening the builder

Write down your audience, venue, time available and one outcome: meeting colleagues, celebrating a birthday or exploring a neighborhood. For a first event, aim for a small set of clear tasks and leave time for instructions and a debrief. A forty-five-minute meeting needs fewer stops than an afternoon walking event.

  • Choose a route or room everyone can use. Check access, opening hours and any venue permissions.
  • List equipment players actually have: one phone per team, paper and pens, or a printed task sheet.
  • Offer an equivalent written task for any photo or movement challenge.
  • Keep tasks away from traffic, private property and personal documents. Get permission before photographing people.
  • Decide who will help players and review submissions during the event.

2. Start a hunt and choose its format

Open Create a hunt, enter a descriptive title and explain what players should expect. Include the meeting point, approximate event time you have planned and any materials. Avoid a title that promises free admission if you intend to configure a paid event.

The builder offers Point Based and Guided Tour formats. Point Based is useful for an event scored by task points; Guided Tour is useful for a sequence of stops. Choose the format that matches your instructions before adding clues. For Point Based hunts, assign a positive point value to every clue before saving.

You can prepare a free hunt as a guest. Guest activity is associated with the browser you used; do not assume it will follow you to a new device or after browser storage is cleared. An account is useful for retaining access across devices. The paid-hunt setting requires signing in and completing the payment setup shown by the builder.

Keep creator access before changing browsers

A hunt’s player link and join code let people reach the activity; they are not creator recovery credentials. In a controlled test on 11 October 2026, the retained creator browser reopened the editor after navigation, while a fresh browser and the same browser after its saved guest credential was removed could not authenticate as that guest owner.

  1. Before clearing site storage or moving devices, reopen your saved hunt in the browser used to create it and confirm you can edit it.
  2. While that browser still has guest access, sign in to the account you intend to use. In our test, normal sign-in linked the owned hunt to the account and removed the old guest credential only after success.
  3. Reopen the intended hunt’s editor while signed in. Confirm its title and tasks before relying on account access elsewhere.

If the original guest credential has already been lost, signing in without it did not demonstrate recovery of the old hunt. Keep your prompts and organizer answers separately, for example with the planning worksheet’s organizer download. That file is a manual preparation record, not an ownership token, automatic import or restore feature. Never share browser access tokens with players.

This was one private test hunt and an existing ordinary test account, not a new-account signup test or a guarantee for expired credentials. The fixture was deactivated and excluded from organic measurements.

3. Write clues with a clear completion rule

Choose a challenge type for each task. The builder supports text, photo, combined text/photo, opinion variants, multiple choice, information, polls, GPS and QR challenges. Use a text answer for a riddle with one intended solution, a photo for something players must show, an information step for instructions and a poll for a choice that has no wrong answer.

Give players enough context to solve a task without guessing what you mean. Write the expected answer or proof before the clue. If two different objects fit the wording, revise it. Use the clue's hint field for one useful nudge; this walkthrough does not rely on hint purchases or configurable hint limits.

For multiple choice, check the choices and selected answer carefully. For a photo task, say what must appear in the image and whether people may be absent. A challenge asking for an office object should not require photographing confidential screens or paperwork.

A two-clue practice hunt

TaskBuilder setupAnswer or review rule
I have numbered days and months, but I am not a clock. What am I?Text answer, 10 points; hint: look for dates.Expected answer: calendar. Test capitalization and the exact answer format in your player preview.
Show an object used to write a note. Keep faces, names and documents out of frame. A written description is the event's alternative.Photo task, 10 points; explain the alternative in the instructions.For a guest-run pilot, enable automatic photo approval to count receipt, then discuss whether a pen or pencil is visible outside the app. Automatic approval does not inspect photo content. Review a written alternative separately under the same event rule.

For the text clue: enter the numbered-days-and-months question above, choose a text challenge, set the accepted answer to CALENDAR and the hint to “look for dates,” then enable automatic answer checking. In the saved 10 October test, submitting calendar was accepted and a completion timestamp persisted; CALENDAR. was rejected. The variant table below gives the tested boundaries. This result applies to that configured text task, not every challenge type.

This practice plan has twenty possible points. The written alternative is an organizer rule, not a claim that one photo clue automatically changes its submission type. If your players need a text version inside the product, create a suitable text or opinion task and explain which version each team should use.

Rehearse the answer variants your players might type

In a controlled Scavenge test on 10 October 2026, one private text task used CALENDAR as its configured answer with automatic answer checking. Six fresh test-class guest sessions submitted answers through the actual API; the accepted or rejected result was also checked in saved progress.

Tested inputObserved resultOrganizer action
CALENDAR, calendar, and CALENDAR with two spaces before and afterAccepted in the configured taskTest the answer players are likely to type; letter case and outer spaces did not block these examples.
CALENDAR.RejectedDo not assume punctuation is ignored. Tell players what format is intended.
CALENDARS and diaryRejectedA plural or a plausible alternative is not automatically accepted. Revise an ambiguous clue rather than expecting semantic matching.

This is a software answer-checking rehearsal, not a human difficulty study or a result for every challenge type. It does not test keyboard behavior on every phone. The test hunt was deactivated and excluded from organic measurements. Ask a fresh reader to try your actual clue, intended answer and likely variants before inviting the group.

4. Set review, visibility and guest access deliberately

Check the builder’s automatic approval settings for each relevant clue. Our three-task guest pilot used automatic photo approval and persisted the upload, points and final completion. This confirms receipt, not that the image satisfies the instructions. For a guest-run event, discuss image content separately. Turning automatic approval off is not a complete moderation workflow: the guest creator cannot use the signed-in review queue, and a guest player’s personal completion can differ from approved points. If you need in-app human approval, establish and test the organizer and participant account workflow before the event.

Choose public or private visibility according to your event. A private setting is not a substitute for avoiding sensitive content: do not include personal information, internal passwords or restricted locations in clues or uploads. A private hunt is omitted from public discovery; do not treat its shared URL or join code as a password. Test participation using the actual account or guest arrangement your event needs.

Tell players how you will break ties before the start. If you want speed bonuses, creative awards or penalties, keep a separate host scoring sheet and explain those rules. Do not assume there is a builder control for every custom scoring idea.

5. Test GPS and QR tasks at the real location

Use a GPS task only where players can safely reach the target and receive location permission on their phone. Set coordinates for the actual accessible spot, not the middle of a building or road. Test with the same kind of phone players will use. The current GPS submission check uses a twenty-meter distance threshold; the builder does not offer the configurable twenty-five-to-one-hundred-meter geofence described in older versions of this guide. Device accuracy, buildings and denied permission can still affect a result.

For QR tasks, print the code at a readable size and test the placed copy in the venue's lighting. Keep the code where players have permission to stand. Have a written clue or a host-assisted alternative ready if a camera or location permission fails.

Do you need a scavenger hunt registration form?

A scavenger hunt registration form helps a host organize attendance before the event; it is separate from the link players use to join a hunt. For a small activity, a simple RSVP list may be enough. If you use a form, ask only for information you actually need: a participant or team name, expected attendance and a way to send event instructions. Make optional questions clear and avoid collecting unnecessary personal details.

After confirming attendance, send players the hunt’s share link or QR code with the meeting time, internet connection requirements and your contact instructions. Rehearse guest entry before the event. A form response does not automatically create a Scavenge.rs participant or import a team. Keep the private creator/edit link separate from the player invitation.

Build the activity in the guest builder, then use the hunt pilot checklist to check the invitation and first task before sharing it.

6. Save, inspect the player view and share

Review your title, description, clues, point values and approval choices before saving. Open the resulting hunt page and use its actual play link or join code when inviting players. Copy the finished URL rather than inventing a title-shaped address. Test the link in a separate browser session so you see what a new player sees.

  • Confirm that the intended guest or signed-in route works.
  • Read the displayed admission terms. A paid public hunt is not made free by sharing its link.
  • Check every clue and any uploaded reference image.
  • Confirm how players get back to the hunt if they close the page.
  • Try the route outdoors before promising a distance, duration or accessibility level.

7. Run a short pilot, then host the event

Ask one person who did not write the clues to try them. Note where they hesitate, what answer they expect and whether the hint helps. Revise ambiguous wording and remove tasks that take too long. A ten-minute pilot is more useful than publishing a large untested task list.

At the start, explain the deadline, scoring, photo consent and help contact. During play, answer questions and review submissions using the event rules. Keep a printed copy and a manual score sheet available if a participant loses connectivity. Afterward, collect feedback about confusing clues and practical access issues before reusing the hunt.

Fix common setup problems before inviting players

What you seeWhat to checkPass condition for your pilot
A player cannot find the hunt by title.Use the saved hunt’s actual link or join code rather than a made-up title URL. Private visibility affects discovery.A fresh browser opens the intended title and shows its Play Now control.
The photo task is complete but its score is missing.Check the clue’s approval setting. Guest personal completion is different from approved points.You can explain whether the event uses automatic receipt approval, external host discussion, or a separately tested account review workflow.
A text answer is rejected.Read the saved answer and try exactly that value. Then test the variants your group is likely to type.One intended answer works; misleading alternatives are removed or explained in the hint.
The creator cannot manage a hunt on another device.Guest ownership is stored in the creator browser. Retain that browser or use the account-linking controls before changing devices.The organizer can reopen and edit the intended hunt through the arrangement tested for the event.
A player cannot finish the last instruction.Use the informational task’s Complete Task action. Our guest pilot verified that this persisted final completion.The final action reaches the completed-hunt screen; opening the task alone is not your completion test.

These checks come from a small internal browser pilot and the current builder, not a school deployment, large-group benchmark or compatibility test of every device. Browser play needs an internet connection. Prepare paper instructions and host scoring as an event fallback; this does not make the web application work offline.

Use the printable hunt pilot checklist to record the actual result, device and date. For help choosing task formats before you build, see the digital hunt task design guide.

Choose a planning worksheet

For ready-to-adapt organizer rules, use the office scavenger hunt worksheet, the team event plan or the clue bank with answers and hints. Check those examples against your venue and group before publishing your own hunt.

When you need a person to approve photos

Our 10 October 2026 internal pilot used separate signed-in organizer and participant accounts, a private test hunt and automatic photo approval turned off. The participant uploaded a synthetic object-only image through the photo control. The organizer opened the saved hunt’s Answers tab and used Approve Photo. The submission changed from zero to ten approved points; the saved result was checked afterward.

A fresh guest submission with approval off behaved differently: its task was personally complete, with zero approved points, and it did not appear in that organizer account’s review queue. Having an organizer account alone therefore does not supply a manual review path for anonymous players. Use the signed-in participant arrangement when your event depends on the account review queue, and pilot it with your actual task settings.

This was a small owned test with ordinary accounts and synthetic images, not a customer event, a camera-quality check, a signup test or a group-capacity benchmark. For a guest-run activity, the tested simple alternative remains automatic receipt approval plus host discussion of image content. Follow the creation and review walkthrough and record your own outcome in the pilot checklist.