How to avoid competing with your own events in nearby cities

You've got a date selling well in one city, and a venue in the next city offers you a good deal. Same show, short drive, another room to fill. It looks like an easy way to grow until you realise some of the people you expect to buy the second date are already in your forecast for the first.

Before you book nearby cities, compare the audiences who could realistically attend either event, then work out what the second date adds after the sales it takes from the first. Choose the venues, dates and launch plan together. There's no distance or number of weeks that automatically makes two markets separate.

That doesn't mean nearby dates are a bad idea. A local show can reach people who wouldn't travel to your original venue. A different date can serve buyers who couldn't make the first. The decision is whether those additional purchases pay for the additional event, while leaving the combined business result worth the work.

We'll use a fictional two-city show to make that decision concrete. You'll see how to investigate audience overlap, compare the money, test the uncertain parts and coordinate promotion without misleading buyers. If you're choosing a completely new market, start with our guide to researching event demand in a new city. Here, the extra question is what happens to the event you already have.

Decide what would happen without the second date

Start with the first event's current forecast. Use its actual paid sales, the remaining selling time, committed promotion and the price you expect later buyers to pay. Save that forecast before discussing how exciting the second venue looks. Otherwise, it's surprisingly easy to reduce the first city's expectations until the expansion appears harmless.

Write down why people buy the existing event. Is the attraction a particular artist, a professional qualification, a local social scene or the chance to attend with friends? A repeat performance of the same programme gives buyers a choice between dates. Two different workshops in a learning sequence may give them a reason to attend both. Those are different commercial situations.

For this guide, imagine an independently promoted performance with the same programme in fictional Cities A and B. Each event has 400 sellable paid places after production and guest holds. We're considering B after already planning A. The cities are deliberately unnamed, and every sales, cost and journey example is invented. These aren't typical tour results or advice about a real route.

Our working assumption is that most buyers want to see this programme once. Some may return, but we'll include repeat attendance only where there's a reason and supporting evidence. A fan saying the show looks brilliant doesn't tell you they'll pay twice, arrange two evenings out and persuade the same friends to join them again.

Keep three possible sources of B's sales separate. Some people would otherwise attend A and switch. Some wouldn't buy A but will buy B because it suits them better. Others will buy both. A ticket sold in B can belong to any of those groups, and each changes the combined result differently.

You won't identify every person's alternative choice with certainty. The point is to stop treating every B ticket as a new purchase for your business. Write a cautious estimate and a plausible worse case, and record what would make you revise them. You can make a responsible decision with uncertainty. You can't do that if the uncertainty disappears inside one optimistic attendance total.

Map the journeys buyers can actually make

City boundaries won't settle audience overlap. Someone living between the venues may find both convenient, while someone closer in a straight line can't get home after either show. Build your catchment around workable journeys. By catchment, we mean the area from which people can realistically attend this particular event.

Start with existing purchasing records where you have suitable location information and permission to use it for this purpose. Look for broad areas sending buyers to A, especially areas towards B. Check what the location field actually means. A billing address, a work address and a guest's home are not interchangeable, and the person paying may be buying for several people.

Plot broad origins against both venue entrances, then inspect representative journeys for the actual proposed days and times. Check getting there and getting home. Include the walk from the station, parking, connecting services and the likely time people leave the room. Use current transport operator information to verify services, fares and disruption when making a real routing decision.

Google Maps' directions guidance explains selecting different transport modes and changing departure or arrival time to account for estimated traffic and transit schedules. That's useful for an initial comparison. The estimate doesn't establish that an attendee can afford the journey, needs no assistance or will accept a late arrival home.

Make separate notes for different travel situations. A daytime industry seminar with employer-paid travel has different constraints from a late club night. A parent arranging childcare may care more about a reliable finish than the distance. People travelling together can coordinate around the least flexible member of the group, so the organiser's own willingness to drive isn't a sensible default.

Look particularly closely at the area between your venues. Ask which event someone there would choose at the same price, and what changes their answer. A better return service can matter more than a shorter outward trip. If B makes attendance possible for a group that couldn't practically reach A, you've found a credible reason for additional demand.

Record the constraint rather than drawing a confident circle around a city. Useful notes might say that a particular corridor can reach both venues on a Saturday, while the proposed weekday B performance requires an overnight stay for people returning by public transport. Verify those statements for the real route. They tell you much more than calling the cities separate markets.

Use travel research as context, then investigate your audience

Loopyah's Event Attendee Insights Report asked 500 US respondents in November 2025 how far they were typically willing to travel for an event. In the single-choice responses, 19.6% selected the same city, 46% selected within two hours, 30% selected a different city within the same country and 4.4% selected international travel.

Those are the survey's answer categories, not four mutually exclusive geographic rings you can put on a map. The question didn't specify your performer, ticket price, transport route or event date. It doesn't tell you that 46% of your audience will travel two hours, or that two venues within that time will lose a particular share of sales to each other.

Use the result to challenge an assumption that buyers only attend events inside their own city. Then investigate your buyers. Look at where earlier attendees came from, which dates they considered and whether they have already travelled to this programme. Keep different event formats separate where their audiences behave differently. A popular annual festival isn't a reliable model for every monthly workshop.

When asking people about the proposed dates, show both choices together with comparable information. Give the location, day, approximate timing and realistic price. Include options for neither and, where relevant, both. Asking separately whether someone likes A and whether they like B lets the same person enthusiastically support two events while intending to purchase only one.

Ask what they would do if B weren't available. Then ask what makes B preferable. A response about avoiding a long journey supports a different interpretation from a response about a cheaper launch price. Both can generate B sales, but the second may simply move someone who was already willing to buy A.

Keep the invitation source beside the answers. A poll of A's existing fans is useful for investigating switching, but says little about the size of B's unfamiliar audience. A local venue's subscribers can reveal another group, although their response still isn't payment. Don't average different recruitment sources into a conversion percentage for the whole region.

The Australian government's market research guidance recommends investigating customers, the local area and competing offers, using existing research alongside direct research. For this decision, give that work a precise question: who will buy B who wouldn't otherwise buy A? A large local population is background information until you have a credible way to reach relevant buyers.

Count people, orders and admissions separately

Overlapping interest lists create a common forecasting mistake. Suppose your fictional A interest list has 600 contacts and B's has 500. If 200 contacts appear on both, the combined list contains 900 distinct contacts, not 1,100. That's a list calculation only. It doesn't mean you have 900 customers, or that the shared 200 will all switch dates.

Keep the duplicate count and the sales forecast in separate fields. A person interested in both dates might buy neither, one or both. An email address can represent a group organiser. The same person may use different addresses. Cleaning exact duplicates helps, but it doesn't magically identify every individual or their companions.

This distinction also matters in website reports. Google Analytics' reporting identity documentation explains how user IDs, device IDs and modelling affect whether activity across devices is treated as one journey. A visitor total therefore depends on what your measurement can identify. Don't add two city page visitor totals and describe the result as two separate pools of paying people.

At checkout, an order for four tickets is one purchasing decision and four admissions sold. For production planning, you need the four admissions. For understanding how many independent groups you've persuaded, the single order matters. For audience overlap, you may know the purchaser has bought both dates while knowing nothing about whether their guests are the same.

Use wording that reflects those limits. Report purchasing accounts that appear across both events as purchasing accounts, not confirmed repeat attendees. If you have valid attendee-level information and a legitimate reason to compare it, describe the comparison accurately. Don't guess identities by matching names or pursue more personal information simply to tidy a planning spreadsheet.

The UK's ICO says personal data should be adequate, relevant and limited to what the purpose requires. Its guidance is under review following UK legislative changes. For a routing discussion, broad area totals will often answer the question better than circulating identifiable buyer addresses. Check the rules applying to your business before reusing or sharing records.

Keep the detailed working file restricted, and give venues or partners only the information they need. Someone helping assess local demand usually needs a count by broad area and an explanation of the method. They rarely need to know which named buyer lives where. Missing location data should remain visible as unknown, rather than being assigned to whichever city improves the forecast.

Calculate the change in profit across both events

Now put the switching assumption into the money. We'll keep the example deliberately simple so you can see the effect. All amounts are US dollars. These invented costs include the work needed to deliver and market the events. They aren't provider quotes, industry benchmarks or an estimate of what your tour should cost.

In City A, suppose each paid admission leaves $50 after the example's applicable taxes and ticketing or payment charges. Serving that attendee costs another $10. Each admission therefore contributes $40 towards the event's fixed costs and profit. A's fixed costs are $8,000, including its planned promotion and costed staff time.

Without B, you forecast 300 retained paid admissions in A. Here, retained means the admission remains paid after refunds. Three hundred multiplied by $40 gives $12,000 towards fixed costs. Subtract $8,000 and A earns $4,000 under these assumptions. That is our comparison case, not a guaranteed result.

Adding B costs $6,000 in additional fixed spending, including its venue, staffing, extra travel and promotion. For clarity, B has the same $40 contribution per admission. Costs already counted in A remain there once. Any genuinely shared saving belongs in the comparison explicitly, rather than appearing as a vague benefit of touring.

Suppose B sells 220 retained paid admissions. Of those, assume 80 would have bought A and switch to B. The remaining 140 are additional admissions across the business. A now sells 220 instead of 300. Together, the events sell 440 admissions, contribute $17,600 and incur $14,000 of fixed costs. Combined profit is $3,600.

B looks profitable by itself. Its 220 admissions contribute $8,800 against $6,000 of additional fixed costs, leaving $2,800. But A loses $3,200 of contribution when those 80 admissions move. The combined result falls $400 below the original $4,000 forecast. You have done another event and earned less in total.

Here's the decision in one calculation. The 140 genuinely additional admissions contribute $5,600, while B adds $6,000 of fixed costs. Expansion reduces profit by $400. A transfer between your own dates adds no admission in this simplified example. It can still change your costs or retained price, which you must include if the dates differ.

To preserve the original profit, B needs 150 additional admissions at $40 each to cover its $6,000 additional fixed cost. With 80 admissions switching, that means 230 B admissions in total. To improve profit by a chosen $2,000, B needs 200 additional admissions, or 280 total with that same switching assumption. Those are decision thresholds for this invented budget only.

Test the assumptions that could reverse the decision

The calculation isn't a forecast until you investigate its inputs. The 80 switching admissions are an assumption, and so are the original 300 A admissions. If you can't support either confidently, test a range. Show what happens when B sells fewer tickets or takes more buyers from A, rather than presenting one neat result as the answer.

Keep B at 220 admissions and change the number switching. With 40 switching, B adds 180 admissions across the business. Their $7,200 contribution exceeds the $6,000 added fixed cost by $1,200, making combined profit $5,200. With 120 switching, B adds only 100 admissions and combined profit falls to $2,000.

Those scenarios explain why finding genuinely local B demand matters. They don't establish which case will happen. Give each assumption a reason: earlier buying patterns, a local partner's actual paid results, or a test with the proposed offer. If the reason is simply that the team wants another date, keep it out of the evidence column.

Also check whether A has room to replace people who switch. A sold-out event with a credible paid waiting audience is different from our example's unsold capacity. A buyer moving to B might release a place another person will purchase. Count that replacement only when you have evidence, and subtract any transfer administration, refund costs or different ticket contribution.

Price differences deserve particular attention. If B's launch offer is cheaper, some people who would happily have paid A's price may move. You can lose contribution even when the total number of admissions stays unchanged. Recalculate using the actual expected mix of ticket prices in each city, rather than assuming that both events retain the same amount.

Check costs that change in steps. A larger room may require another security shift after a certain attendance level. A cheaper venue can require more equipment hire. A route change might add an accommodation night. Our event break-even guide explains the wider ticket calculation; here, make sure the extra city includes every cost it causes.

There may be a strategic reason to accept a lower first-run profit while building B. If so, name the investment, limit the loss and say what evidence would justify another run. Don't describe an intentional $400 reduction as profitable growth simply because both dates individually show a positive result. The team approving the route should understand what it is buying.

Finally, put payment timing beside profit. Two profitable dates can require deposits before usable ticket receipts arrive. Refund exposure can remain after money reaches the bank. Build the combined cash-flow forecast with the actual payment dates, obligations and accessible funds. Better final profit won't solve a cash shortage before the shows happen.

Choose spacing around the buying decision

Once you understand the shared audience, review the dates. There's no standard gap that protects every event. The same programme a fortnight apart might feel interchangeable to one audience. Two complementary sessions within a week might work for another. Start with the reason someone would pay again and the practical limits on doing so.

Ask whether the audience has time and money for both experiences. A repeat buyer may need another payday, another childcare arrangement or approval from the same employer. A fan could afford both tickets but only travel on one of the dates. Moving the second event further away in the calendar can help, but it can also add touring costs or lose the performer.

Distinguish show spacing from launch spacing. Show spacing is the time between attendance dates. Launch spacing is the time between announcements or sales openings. Staggering two announcements doesn't make the audiences independent. It changes which option buyers see when they decide, and possibly how long you have to sell the later date.

If both dates are confirmed alternatives, I would usually make that choice visible when buyers need it. You can give each city a distinct local promotional push while maintaining an accurate tour page. Concealing a nearer confirmed date to force people into the first city may improve early sales while creating avoidable disappointment when the second announcement appears.

Sometimes you genuinely cannot confirm B yet. Describe only what is confirmed, and don't advertise a speculative stop as a promise. Agree how you will handle questions and any later transfer requests. If the commercial plan relies on keeping confirmed information secret from existing buyers, reconsider the plan before your support team inherits the consequences.

Put provisional holds, artist approval, announcement restrictions, on-sale dates and venue payment deadlines on one calendar. Check the exact contracts rather than assuming a nearby booking is allowed. Any restriction on other appearances needs suitable advice for the actual agreement and market. A manageable audience forecast doesn't override a commitment you've already made.

The travel schedule must work for the delivery team as well. A financially attractive date is useless if the artist or instructor cannot arrive rested and prepared. Once you've decided which markets belong together, our multi-city workshop tour guide covers that operational planning in detail. Keep audience approval and delivery approval as separate questions that both need an answer.

Give each city a clear offer without inventing a difference

Nearby dates need accurate local information. Put the city, venue, date and start time where someone sharing a link can see them immediately. Use a separate event page for each performance, and check every local detail before a partner begins promotion. A familiar tour name makes it easier to overlook a copied address or old finishing time.

Explain the real differences. Perhaps B is a seated afternoon performance and A is a standing evening show. Perhaps one workshop serves beginners and another serves experienced practitioners. Those differences can support different buying decisions if they're true and reflected in delivery. A new poster colour doesn't make the same programme a new experience.

Be careful with words such as exclusive, only and final. Their meaning needs to match the actual bookings and geography. An event can't honestly be the only nearby chance to see a programme if you've already confirmed another nearby performance. Ask someone outside the planning conversation to read the claim as a buyer would.

Price the local offer on its own economics, then inspect how the prices look together. A higher A price may have a sound reason, such as a longer programme or an included benefit. Explain it. If the events are materially the same, assume buyers can compare the prices and may choose the cheaper one even when its journey is slightly less convenient.

Use real quantities and release terms. Loopyah's ticket-selling tools let you set multiple releases with their own prices and quantities, with the next release opening when the previous one sells out. That handles the ticket release mechanics. You still need to decide whether the price differences make sense across the route and what they do to the forecast.

Local partners also need the whole relevant picture. Tell them which date their link sells, what they can claim and where nearby alternatives are explained. If you pay commission, include it in the contribution calculation for those admissions. Our guide to promoter commission per ticket helps with the cost of that arrangement.

Decide how enquiries move between teams. Someone asking about B through A's page should get an accurate answer, even if their purchase will make A's individual report look worse. Set team targets that recognise the combined business result. Otherwise, you can end up paying people to compete over the same buyer while overlooking the people neither event has reached.

Coordinate promotion around one business result

Give one person responsibility for the regional plan, even when local teams run the campaigns. They should see the budgets, ticket sales, main messages and scheduled sends for both cities. Their job is to catch conflicts early and judge the combined outcome, while allowing local people to use what they know about their audience.

Keep overlapping audiences visible. If both dates are relevant to the same subscriber, you can explain the choice clearly in one message rather than sending competing last-chance emails. For people who have already booked A, a B sales offer needs a real purpose. It might be useful for a genuinely different programme, but a cheaper copy of the same show can create transfer questions.

Loopyah's attendee email tools keep buyers' event and purchase history in contacts and let you segment by what people bought. Promotions exclude opt-outs, while operational event updates are handled separately. Use that purchase context when planning relevant messages. It doesn't establish which city someone lives in or whether they want another performance.

Don't send a sales pitch as an essential update simply because you want every ticket holder to receive it. An operational message explains something about the booking they already hold. A new-city offer asks for another purchase. Keep the purpose accurate, and follow the email rules and permissions that apply to the recipient and your business.

For paid media, ask the campaign owner to check how both plans reach the shared audience. Separate event budgets can still target many of the same people. Review geography, existing-buyer treatment, creative and the meaning of each conversion report. Don't assume that two campaigns caused twice the demand because each platform or local team takes credit for a sale.

Use consistent campaign names and links so you can investigate the records. Google's campaign URL guidance describes tagging referral links with source, medium and campaign information. Those tags identify reported traffic sources. They don't prove that the campaign created a purchase that would otherwise never have happened, or that a buyer would have skipped A without seeing B.

Put the reporting limitation in ordinary language at the review. B has sold tickets through the campaign. Some may be additional, some may have switched, and some may have bought anyway. Compare those records with regional sales and the earlier forecast. A confident attribution label is useful for tracing activity, but it isn't an answer to every commercial question.

Review both sales curves before spending more

Save a dated snapshot when B is announced. Record A's paid admissions, refunds, prices, remaining inventory and expected sales at that point. Add B's launch activity and any simultaneous changes to A. Without that record, you can end up comparing a remembered strong first city with a very precisely measured second one.

Look for changes across the region, not just a weak week in A. Did combined retained sales rise? Did the geographical mix change? Are existing buyers asking to move? Is B selling to purchasers you haven't seen before? Those are useful clues, but take care with the last one. A new purchasing account can still represent someone who previously attended as a guest.

An A slowdown immediately after B's announcement is a reason to investigate. It isn't automatic proof of switching. A's early release may have ended, its main partner may have already emailed, or another local event may have announced that week. Keep a record of these changes rather than attributing every movement to whichever decision you're currently worried about.

Ask a small number of purchasers about the choice where appropriate, without leading them towards the answer you want. Did they consider both dates? What would they have done without B? Keep the responses as contextual evidence, with their recruitment method and limits. Don't publish a precise regional switching rate from a handful of enthusiastic replies.

Review the next spending decision before it becomes unavoidable. If B needs another campaign, calculate what extra sales must contribute after any likely movement from A. Our event marketing budget guide explains setting an affordable campaign allowance. For nearby events, include the effect on both dates when deciding whether that allowance is worthwhile.

Keep a reserve for the outcome you can reasonably face. If the worse case leaves both rooms underfilled and the cash balance negative, a hopeful average isn't enough. Reduce the commitment, revise the offer or postpone the expansion while those options remain available. The purpose of the review is to change a decision, not produce a reassuring report after the money is spent.

If both dates are already selling, change the next decision

You might be reading this with two venues booked and sales open. In that situation, rebuilding the original forecast is still useful, but it doesn't tell you to cancel B. Some costs are already committed, and cancellation creates its own costs and obligations. Compare the options available now using the money, work and buyer promises each option changes.

Separate money already spent from bills you can still avoid. If the venue keeps its deposit, stopping doesn't recover it. If delivering B requires a remaining production balance and substantial staff time, proceeding isn't free either. Add refunds, unrecovered transaction costs, communication work and any effect on other bookings before choosing.

You may be able to make a targeted improvement. Clarify the city choice, reach an under-served local audience or adjust an optional spend that hasn't been committed. Avoid starting with a blanket discount in B. If that draws people from A, you could reduce contribution across the route while the second city's sales report looks healthier.

Handle transfer requests against the actual buyer terms and applicable requirements. Confirm the destination date has suitable inventory, explain any price treatment and record what happened to the original admission. A move should not leave two valid admissions when the buyer paid for one. Nor should it silently cancel a companion's booking because one person purchased the whole group.

Keep transfers visible in reporting. An existing A admission moved to B is a movement between events, not a new regional sale. If a destination ticket is issued and the original refunded, reconcile both records before judging growth. Record any costs that remain after the refund so the financial result reflects the work you've actually done.

Make essential buyer communication clear and prompt. Explain confirmed changes, available options and how to get help. Don't tell ticket holders the route has been improved when their own date has been removed. If you need to cancel or materially change an event, get the appropriate advice and fulfil the obligations applying to those bookings.

Ask local partners for evidence you can use

A venue or local promoter may be certain that B will sell. Rather than arguing about confidence, ask them to describe the buyers and how they will reach them. You want something you can put into the decision page without turning an informal promise into a guaranteed sale.

Start with the closest relevant event they can discuss. Ask what the programme was, which neighbourhoods supplied buyers, how people heard about it and whether nearby performances were available. Establish whether their figures describe paid admissions, orders, registrations or total attendance including guests. A full room can be useful evidence without supporting the paid-ticket forecast you've been given.

Then ask what they can actually do for B. A useful commitment names the placement, audience, delivery date, person responsible and cost. If they plan to email subscribers, ask about relevant audience fit and the permission to send. You don't need their subscriber list to assess the proposal, and access to that list should never quietly become a condition of working together.

Check how much the audience overlaps with people already receiving A's promotion. A local partner may have excellent reach among the same regional fans you know. That can help sell tickets, but it doesn't establish an independent pool of new buyers. Ask whether their reach extends to a group whose travel or scheduling constraints make B a genuinely better fit.

For a first conversation, use this short request and adapt it to the proposed event:

• Which comparable paid event best supports your estimate, and what did its sales records measure?

• Which local audience can you reach that is unlikely to attend A, and why?

• What promotion will you deliver, on what date, at what cost, and who confirms it happened?

• What would you change if the first release sells mainly to people already considering A?

Keep the answers in their original meaning. If the partner says they expect a hundred admissions, record that as their estimate and the reasons offered. Don't translate it into a committed group purchase. If an organisation really is buying a block, record the agreed quantity, payment conditions and cancellation treatment separately from the promotional estimate.

Also ask who answers customer questions after their placement runs. A local post can create enquiries about accessibility, transport or the difference between dates. Supply accurate information and a contact route. A partner who improvises answers may unintentionally promise something you haven't budgeted to deliver, especially when the same programme looks different in two venues.

Once sales begin, compare the agreed activity with what happened. A late email leaves less selling time; a different audience changes what the result tells you. Update the forecast accordingly without blaming the whole city for a test that wasn't delivered as planned. If the partner reaches the intended audience and sales remain weak, that's useful evidence too.

This work should produce a specific next decision. You might confirm the partnership, revise its scope, cap the test spend or remove its forecast sales from the approval case. You aren't asking someone to prove the future. You're asking them to make the proposed route to paying buyers concrete enough that your business can decide what to risk.

Write the routing decision so the team can challenge it

Before committing, put the decision on one page. Name the two offers, the people each can reach and the evidence for the shared audience. State the original A forecast, the additional cost of B and the expected contribution from each kind of admission. Keep confirmed purchases separate from hoped-for remaining sales.

Use the fictional example as a model of the questions, not a set of numbers to copy. What supports 300 A admissions without B? Why do you expect 220 in B? How many would otherwise buy A? What changes if that number is 40 or 120? Who can reach the additional buyers, and what has that route actually produced before?

Write the decision condition in a complete sentence. For our invented budget, adding B preserves A's forecast profit only when it adds at least 150 admissions across the business at the assumed $40 contribution, with no other changes. If you need another $2,000 to justify the work and risk, the requirement becomes 200 additional admissions. A different price or cost changes both conditions.

Attach the calendar showing when the assumptions can still affect the plan. Name the person reviewing paid sales before the next irreversible commitment, and the options they can approve. Include the cash limit, the contractual conditions and the delivery requirements. A good audience forecast cannot compensate for failing one of those conditions.

You may choose one regional date, two smaller local events, a longer gap or a different programme in B. Judge each against what buyers can attend and what the business retains after the work. The useful outcome is a route whose extra dates have a clear reason to exist and enough additional paid demand to support them.

After the shows, compare the actual combined result with the decision page. Update costs, refunds, admissions and the evidence about people choosing between dates. Keep what you still can't know explicit. That record gives the next routing conversation something better than a memory that one city felt busy, and helps you decide where the next event belongs.