How to run a paid city scavenger hunt

A paid city scavenger hunt needs a route people can enjoy, clues they can solve without knowing your thinking, and an operating plan that gets every team back safely. Start with a small area and a tested game, then set the ticket price and capacity around the staff, permissions and support that experience actually needs.

So you've found a neighbourhood full of interesting details. There's a great story behind the old station, a strange symbol above a doorway, and a square that would make a lovely finish. You can already picture teams comparing answers over a drink. The difficult part is everything between those moments.

What happens when the doorway is covered by scaffolding? Who helps a team whose phone dies? Can the finish venue handle everyone returning early because it starts raining? These are manageable problems when you design for them before selling tickets.

This guide follows a fictional Saturday hunt through a compact city district. The example timings, prices and capacities are planning assumptions, not industry benchmarks. Use them to work through your own route, then replace them with what your tests and supplier quotes tell you.

Decide what someone is paying to experience

The first thing you want to do is choose your customer and the kind of afternoon you're offering. A couple looking for a relaxed local outing wants something different from a group of puzzle enthusiasts who expect difficult deductions. Both might search for a city scavenger hunt, but they won't judge the experience the same way.

For our example, imagine a ticketed afternoon for adults who enjoy discovering overlooked details with their friends. Teams explore a small district, solve an original local mystery, and return to a hosted finish. Walking and noticing matter more than speed. People can have a satisfying afternoon without completing every optional challenge.

That description helps you reject ideas. A clue that requires extensive historical knowledge doesn't suit newcomers. A long detour to a famous landmark makes the event harder without necessarily making it better. A task that depends on persuading a stranger to perform for a camera introduces an awkward interaction the buyer never asked for.

Write a plain description of the experience before you write a clever name. Explain who can join, whether they bring a team, how much walking is involved, how the game works and what the ticket includes. If those answers keep changing, the offer isn't ready for a sales page.

Make another decision here. Is this a scheduled event with staff and a shared finish, or an activity buyers can start whenever they like? This guide covers the scheduled event. A self guided product needs different support hours, access arrangements and expectations, even if the puzzles look similar.

Keep the first offer narrow enough to deliver well. You can add evening departures, family sessions or tougher puzzles after you understand the original route. Our guide to starting a paid tour guide business develops the wider business decisions if you plan to sell recurring city experiences. Here, the immediate job is to make one hunt worth booking.

Build the route before you polish the clues

Choose a district you can inspect on foot. Start and finish arrangements should influence the route as much as the interesting sights. You need somewhere people can find, receive instructions and wait without obstructing the public. At the finish, you need enough room to receive teams, resolve answers and deliver whatever you've promised.

Walk the entire route at the same time and on the same day of the week as the planned event. A quiet weekday street can become a delivery route or a busy market on Saturday. Record crossings, narrow sections, toilets, seating, shelter and places where a team can stop to read without blocking anyone.

Give each proposed clue a working location and a safe place to solve it. Those can be different places. Teams might observe a detail from a pavement, then move into an open square to discuss the answer. Don't ask them to stand in a doorway because that's where the detail happens to be.

In Great Britain, the Health and Safety Executive's crowd risk guidance includes events on urban streets and open spaces. It identifies issues such as pedestrians sharing space with vehicles and poorly maintained routes. For a hunt, that means judging the movement your game creates, including where teams stop and gather.

Prefer a compact loop for your first run. It makes late arrivals, withdrawals and support visits easier to manage than a route that ends far from the start. Keep optional detours genuinely optional, with a direct route back that doesn't require finishing another puzzle.

Then check what the route asks of different participants. Look for steps, steep slopes, broken surfaces, difficult crossings and toilets people can actually use. Describe the conditions precisely on the event page. A vague promise that the hunt is suitable for everyone tells buyers very little.

The U.S. Department of Justice's small business accessibility guidance explains access obligations for covered businesses and the importance of accessible routes. Check the requirements where you operate and speak to people who can assess the route properly. Changing a clue is much easier now than explaining a preventable barrier after someone has paid.

Confirm permissions without guessing what public space allows

Being allowed to walk down a street doesn't automatically settle whether you can assemble a paid group there, install signs or run commercial activities in an adjacent park. Your planned use matters. Ask the relevant landowner or authority about the actual event, including gathering points, group sizes, advertising, props and recurring dates.

Be specific when you ask. Describe a walking puzzle event with a hosted start and finish, the expected attendance and the places teams will visit. Say whether anything will be attached, hidden or handed out, and whether participants enter businesses. A general question about walking tours can produce an answer that doesn't cover your hunt.

For example, NYC Parks' special event permit guidance says events with more than twenty attendees require a permit. It also identifies commercial signage and other activities that can make permission relevant at smaller sizes. That is a local example, not a threshold you can apply in another city.

Check the advertised route against any conditions you receive. You may need to change a gathering point, remove a prop or use a different date. Keep the written permission and the conditions with the event plan so another person can understand what has been agreed.

If a cafe or shop becomes part of the game, speak to the person responsible for that location. Agree what participants will do, whether buying something is required, when teams may enter and what happens if the business is unexpectedly closed. Staff should know about the event before the first team arrives with a riddle.

Avoid placing physical objects in public space as a default. They can disappear, confuse passersby or create a cleanup problem. A permanent architectural detail often makes a more dependable clue. When props genuinely improve the game, use approved locations and assign someone to place, inspect and remove them.

Discuss the event with your insurer, including walking routes, staffing, participant ages and any partner activities. Don't assume a policy for indoor workshops covers a competitive street game. Your event risk assessment should describe the hunt you are actually selling, including how its rules affect behaviour.

Write clues people can solve without reading your mind

A good clue creates a moment of discovery. It gives players enough information to work out what to look for, then rewards attention or reasoning. Difficulty should come from the intended puzzle, rather than an unclear instruction or a missing detail.

Start with an observable answer and work backwards. Imagine a permitted stop beside a fictional former workshop. The facade has a permanent relief showing a wheel above a doorway. You could ask teams to identify the tool in the relief and use its name in a later answer. Before writing anything, check that the detail is visible from the safe stopping point.

Now separate navigation from solving. Tell people how to reach the correct area plainly enough that they don't wander into unrelated buildings. Once they're there, the puzzle can ask them to notice something. Making every movement a cryptic clue gives you several ways to lose a team before the actual game begins.

Write an answer key alongside each clue. Record the intended answer, reasonable alternatives, the evidence a judge needs and the hint you can give without completing the task for the team. If you can't explain why an alternative answer is wrong, the clue probably needs another edit.

Vary what teams do. Observation, a short deduction and a pattern assembled from earlier answers can provide different kinds of satisfaction. You don't need a separate mechanic at every stop. Too many rules make players spend their afternoon learning instructions instead of enjoying the place.

Build a gentle entry into the game. The opening task should help a new team understand how to submit an answer and request help. Save harder deductions for the point where players trust the instructions. Offer optional challenges for teams who want more, while keeping the main experience achievable for your intended audience.

Avoid trivia that a web search solves immediately unless finding that information is deliberately part of the game. Equally, don't demand obscure knowledge that locals happen to possess. The interesting thing about a city hunt is helping people discover what's around them. Let the street supply meaningful evidence, and let the puzzles connect it.

Avoid making every answer a compulsory key to the next location. One misunderstood word can otherwise stop the entire afternoon. In our example, teams receive the route information independently of the answers. A final puzzle can still use earlier discoveries, but a hint lets a team continue if it misses something. That preserves the satisfaction of connecting the story without trapping participants outside a closed building. Keep a record of which earlier answers the final puzzle uses, so a replacement clue doesn't accidentally make the ending impossible. Check that connection every time you edit the route. If you remove a stop on event day, give every affected team the information it would have contributed and explain how you will handle the scoring.

Test the whole game with people who didn't write it

You can't test a clue by looking at it and deciding it makes sense. You already know the answer. Give the draft to people who resemble your paying audience and watch what happens without rescuing them at the first hesitation.

Run an initial test for clarity, then another after you've corrected the problems. Use different testers when possible. Someone who remembers the answer cannot tell you whether the revised clue works for a newcomer.

Record where each team goes, when it arrives, how long it spends and what help it requests. Ask testers to explain their reasoning after they finish a clue. A correct answer reached through a completely unintended shortcut can reveal a weak puzzle just as clearly as a wrong answer.

Test the unpleasant cases deliberately. Cover a key detail to mimic scaffolding. Turn off mobile data. Have someone arrive late or stop halfway through. Ask a team to return directly to the finish without completing the hunt. You're checking whether the operating plan still works when the original sequence breaks.

For our fictional hunt, suppose the first test takes much longer than expected because teams keep looking at the wrong building. Adding time won't fix that experience. Rewrite the navigation instruction, retest it, and only then decide what duration you can advertise.

Keep notes on enjoyment as well as completion. Which clue made people talk? Which one felt like homework? Where did they want to stay longer? A technically solvable route can still be dull, and a beautiful stop can be a poor game location if teams can't comfortably gather there.

Check the route shortly before the event. Your test doesn't reserve the pavement or prevent building work. Keep a replacement clue for a vulnerable stop and a straightforward explanation if you need to remove it. When a change affects scoring, apply the same decision to every team.

Don't sell a full capacity event to discover whether your game works. A small paid pilot can test the commercial experience after the basic route and safety checks pass. Tell buyers what kind of event they're booking and deliver the service you advertise.

Set rules that encourage the behaviour you want

Players follow the incentives you create. If the winner is whoever returns first, some people will run, rush crossings or stop reading carefully. For a relaxed walking hunt, score the answers and use a published submission deadline rather than rewarding the fastest route completion.

Explain which tasks count, what evidence is acceptable and how hints affect the score. If hints are free, say so. If a hint carries a penalty, make the penalty clear before departure and apply it consistently. Nobody enjoys learning at the prize announcement that another team received different treatment.

Choose a tie procedure you can operate. A short puzzle at the finish can work if tied teams have time to take part. A random draw has different implications and may require local checks, especially when prizes or entry payments are involved. Don't improvise the deciding rule after seeing who has tied.

State the practical boundaries in ordinary language. Teams stay together, use designated crossings and avoid entering unlisted premises. They don't climb, remove objects or interrupt strangers to complete a challenge. Remove any task that makes breaking those rules seem like the easiest way to win.

Make the missed deadline rule proportionate. A score penalty can be part of the game, but support remains available after scoring closes. A late team is still a group you need to account for. If a team withdraws, give them an easy way to tell the event team they've stopped playing.

Think carefully about photo evidence. A picture of a permitted architectural detail may prove an answer without including anyone's face. The UK Information Commissioner's Office guidance on data minimisation says personal information should be limited to what is necessary for its purpose. Collect only what you need to operate the event and handle it under the rules that apply to your business.

Explain how submitted material will be used and when it will be removed. Entering a photo to verify an answer shouldn't quietly become permission to use it in advertising. Keep marketing permissions separate and offer an answer method that doesn't require public social posting.

Price the hunt around the cost of running it

Decide whether your ticket covers a person or an entire team. A team price makes the booking simple for a group organiser, but you need a clear minimum and maximum team size. Individual tickets require a clear explanation of whether people join existing teams or form their own.

Our fictional event sells team tickets, each covering up to four adults. The example uses a maximum of twelve teams, so the highest possible attendance is forty eight people. That maximum must fit the gathering places and route. Selling team tickets doesn't make participant capacity disappear.

For a worked budget in USD, assume the event has $720 of departure costs before team materials. That includes paid delivery and preparation time, the finish arrangement and allocated costs for permissions, insurance and equipment. Assume another $10 for each team. These are invented inputs to explain the calculation, not suggested supplier prices.

At $100 per team, each sale leaves $90 after that team's materials. Eight teams cover the $720 departure costs exactly. Ten teams produce $1,000 of revenue and $820 of these costs, leaving $180 before tax and any costs omitted from the example. Twelve teams leave $360 on the same basis.

Fictional USD example from the calculation above: $100 per team, $10 of materials per team and $720 of departure costs. Results exclude tax and any omitted costs.

Now add any payment charges, acquisition spending or additional support your real event needs. If those change with bookings, include them in the cost of each sale before calculating how many teams cover the departure. Our event budget guide can help you organise the full calculation.

The temptation is to remove staff time until the spreadsheet looks healthier. That doesn't reduce the work. It means you are doing unpaid work or asking the remaining staff to cover more than the plan allows. Price the event around delivery you can stand behind, then decide whether enough customers will buy that offer.

Set the minimum sales decision and its date before launch. Buyers need enough notice if you cancel a departure, and suppliers need clear commitments. Explain your cancellation and refund terms before payment. Treat a first run as a test of whether the offer pays for its real costs.

Capacity also depends on how teams occupy each stop. During testing, watch how long a group needs to observe the detail and move away. If several teams arrive together, the safe waiting area matters as much as the puzzle's difficulty. You might vary their starting clues, separate departures or remove that stop entirely. Don't solve crowding by asking a business to absorb waiting teams unless that arrangement is agreed. A route that works for a handful of testers may need a smaller sales cap than your budget initially assumed. Recalculate the price using that cap before you sell tickets. The capacity decision should survive a busy public afternoon, with ordinary pedestrians still using the same streets, shops and crossings around your players.

Assign staff to the moments that need them

Start with the jobs, then decide how many people you need. Someone must check bookings, explain the rules, provide route support, monitor changing conditions, receive returning teams and judge submissions. Some jobs can share a person at different times. Others happen together.

For the example event, imagine a host responsible for the start and finish, a dedicated support person monitoring team contacts, and a route marshal covering an identified difficult area. That is an illustrative arrangement. Your route assessment, attendance and venue arrangements may require something different.

Don't assume the host can leave the finish to help a lost team while also judging arrivals. Write down who takes over each job if someone needs to move. If there is nobody available, change the route, reduce capacity or budget for more help.

Give the team one current set of instructions. It should include the route, answer key, accepted alternatives, support contacts, withdrawal process, weather decisions and meeting points. Number the version so an old clue sheet doesn't stay in circulation after a correction.

Rehearse the support conversation. A participant may say they're beside a red door when there are several red doors nearby. Staff need a calm way to establish the team's location without encouraging anyone to stare at a phone while walking. Put clearly identifiable help locations into the participant information.

Plan for communication failure. Printed team information should carry the finish address, a contact number and the essential rules. Staff need access to the team list and a way to record departures and returns if the normal system is unavailable. Test the equipment you'll actually use on the route. Test that contact number before including it in the final reminder.

Brief the finish venue separately. Agree when teams may arrive, where they wait, which facilities are available and who deals with a complaint. If the venue sells refreshments, explain whether those are included in the ticket or bought separately. Nobody should discover an unexpected purchase requirement after completing the hunt.

Put a named person in charge of the decision to pause or stop. Everyone working the event needs to know how that instruction reaches teams and what they should do next.

Give buyers practical information before they arrive

Your event page should help a group decide whether the afternoon suits them. Describe the theme without revealing the answers, then explain the duration, walking conditions, team size, age policy and what is included. Show the total buying terms clearly and explain anything participants must bring.

A mystery can be part of the entertainment. The meeting location shouldn't be. Give the exact address, an identifiable landmark and arrival instructions that work for someone unfamiliar with the district. Mention the nearest useful transport information without promising parking you don't control.

Explain the phone requirement honestly. Does each team need one charged smartphone with mobile data, or can they use a paper pack? Will they need to install something beforehand? If a digital tool carries the game, test the whole participant journey and explain the fallback before the first booking.

Tell buyers how support works and what happens in unsuitable weather. Make it easy to ask about access before purchasing. Specific route information lets someone decide for themselves, while a named contact can discuss requirements that a general description doesn't cover.

Send a practical reminder close enough to the event that it is useful. Repeat the arrival time, meeting point, team arrangements and contact details. Don't bury a major change in a promotional email. If the route or schedule has materially changed, explain the change directly and deal with affected bookings under your stated terms.

Sell the experience with a sample that demonstrates the level of thinking without revealing a live answer. An original practice clue can show whether this is gentle observation or demanding puzzle solving. Describe the hosted finish and the support included, because those are part of what the ticket buys. Ask local partners which customers would actually enjoy the event rather than requesting a recommendation to everyone. For a first departure, keep the date selection limited enough that sales can gather around a viable session. Record where paid bookings came from, then compare those sales with the cost of reaching them. Interest is encouraging, but completed bookings tell you whether the description, price and date work together for the people you want to attract.

At check in, reconcile people and teams with the booking. A purchaser may have booked for friends who arrive separately. Establish when the team is ready, hand over the correct pack and record that it has departed. Keep payment questions separate from the host's game briefing so neither conversation has to be rushed.

The briefing should demonstrate how an answer is submitted and how help is requested. Give teams a simple practice task while they are still near staff. You'll find misunderstandings before they spread across the district.

Then release teams according to the route plan. A shared briefing doesn't require everyone to crowd around the same first clue. Different starting tasks can spread arrivals if you've tested that each order works fairly.

Plan the finish and the decision to stop

Work backwards from the time the venue must be clear. Allow for teams returning, checking submissions, resolving a disputed answer and presenting prizes. Publish the scoring deadline separately from the time you expect the hosted finish to end.

Don't give the last team the entire advertised playing time and then expect everyone else to wait indefinitely for results. Either departures and deadlines are shared, or each team's timing is clearly defined. Explain your method and test whether the finish can process the arrivals it creates.

Have somewhere teams can wait comfortably while judging happens. A host can discuss favourite clues and explain answers without announcing a winner too early. Confirm the result before you ask the venue to make an announcement.

Weather decisions need the same clarity. The National Weather Service's guidance for organised outdoor activities recommends a specific lightning plan, including who monitors conditions, where people go and when activity stops. It warns that small rain shelters aren't safe lightning shelters. Apply appropriate local weather advice and identify usable shelter before departure.

Give teams an instruction they can act on immediately if you stop the hunt. A message saying the event is paused is incomplete if participants don't know where to go. Account for teams that don't acknowledge the message, and keep support available while people leave the route.

After the event, compare the promised experience with what happened. Review actual hours and costs, completion times, support requests and the clues people disputed. Ask buyers where they felt lost or rushed, and whether the finish justified staying for it.

Fix the clearest problems before opening the next date. A city hunt becomes easier to repeat when another member of staff can follow the plan and deliver the same experience. Start there, with a route you can operate confidently and an afternoon customers would recommend to their friends.