How do you plan a paid conference during transport strikes?

Your conference venue is open. The speakers are booked, the catering deadline is approaching, and the railway announces a strike. Someone suggests emailing everyone to allow extra time. But extra time won't help a buyer whose train isn't running, or a technician who can't reach the venue before the doors open.

Start by checking whether you can still deliver the conference people bought. Establish which journeys are affected, whether the people needed to run the event can get there, and what realistic alternatives cost. Then choose the programme and buyer options you can actually provide, with a decision time that comes before people commit more money to travelling.

You don't have to cancel every conference affected by a transport strike. You do need more evidence than an open venue and a hopeful attendance forecast. This guide explains how to make that decision, including a worked conference example, a disruption budget and wording you can adapt for ticket buyers.

Establish which journeys have actually changed

The first thing you want to do is check the transport operator's current information. A headline about rail strikes doesn't tell you which services will operate on your event date. The disruption might affect one company, a particular line, an interchange or only part of the day. Record what has been confirmed and what the operator is still working out.

Check the complete journey. A train reaching the city doesn't solve a cancelled underground connection to your venue. An airport service might operate while the onward rail route doesn't. Look at the services attendees were likely to use, the times they need to arrive and the connections they need afterwards. Include the preceding evening and following morning when overnight travel forms part of the plan.

For a conference in Great Britain, National Rail's travel alerts and journey information distinguish future journey planning from live train running information. Use the appropriate tool for the decision in front of you, and check the relevant train company's own notice. An ordinary timetable saved before the announcement isn't confirmation that the same train will run during the strike.

Assign one person to maintain the travel information your team uses. They should record the operator, affected route, event date, source, time checked and next useful check. Keep confirmed cancellations separate from possible disruption. Otherwise a suggestion in a team chat can become a fact in the buyer email without anyone noticing the change.

Avoid publishing a long list of departure times that your team can't maintain. Give attendees the official source and explain which part of the journey they need to recheck. You can identify a practical route once it is confirmed, but you shouldn't imply that an available service has space for everyone or that connections are guaranteed.

The return deserves its own check. A buyer might be able to arrive after a slow morning journey but need to leave before your closing session to catch the last workable connection. If that affects the programme they purchased, it belongs in your decision about the event. It isn't something to discover while the moderator introduces the final speaker.

Keep the scope proportionate. You're assessing travel dependencies for a paid conference, rather than becoming a personal travel agency for every buyer. The useful output is a clear statement of the affected journeys, the alternatives that have been checked and the uncertainties that could change your event decision. Give people a support route for circumstances the general notice doesn't cover.

Find out who can still attend without treating silence as a yes

Ticket sales tell you how many places you've sold. They don't tell you how many people can reach the event during disruption. Start with information you already have permission to use, such as transport reservations or a voluntary travel question. Then ask buyers a short, practical question about what has changed.

A useful response form asks whether someone expects to attend as planned, arrive later, need information about a proposed alternative, or be unable to attend. Include a way to say they're still checking. Ask about the return journey too. Someone who can reach registration but can't get home may need a different option from someone arriving after the opening session.

Explain why you're asking and when you need the reply. Collect the information needed to make the decision, rather than asking for a full home address or copies of travel documents by default. Handle individual assistance requests privately, with access limited to the people arranging support. Your general attendance summary doesn't need to contain someone's medical history.

Count people rather than orders. A group organiser replying for a business may be speaking for several ticket holders, and their travel plans may differ. Give them a way to confirm the number affected. Remove duplicate replies before adding the totals, and distinguish a reported intention from an accepted booking on an alternative service.

Consider a fictional event we'll call the Independent Retail Forum. It has 360 paid attendees. In this planning exercise, 90 report a workable local journey and 80 are staying nearby with their journeys checked. Another 55 report confirmed alternative journeys. A further 45 expect to arrive later but can attend if the opening programme moves. Sixty say they can't attend, and 30 haven't given a usable answer.

Those groups account for all 360 attendees without counting anyone twice. At this point, 225 expect to reach the original start and another 45 could reach a later one. That makes 270 potential attendees under the revised plan, subject to those journeys remaining workable. The 30 unknown replies remain unknown. They haven't become confirmed attendees because the catering deadline is close.

These invented figures aren't a turnout benchmark or a rule for proceeding. They show why a single expected-attendance number can hide the decision you need to make. Moving the opening may help the 45 late arrivals, while doing nothing for the 60 who cannot travel. You still need a buyer response for that second group.

Read the comments as well as the totals. Several people may be relying on the same unconfirmed alternative, or planning to drive to a car park that closes before the conference ends. Follow up on assumptions that could change the whole forecast. You don't need to resolve every personal itinerary, but you do need to challenge a weak assumption before spending money around it.

Check the people and services needed to open

Now turn the question around. Can your team deliver the event even if attendees can reach it? List the roles required for setup, admission, the programme and closing, then ask the relevant employers or suppliers how those people will get there and leave. The staff travel problem can begin long before the first buyer sets out.

The venue may have its own disruption plan, but ask what it means for your booking. Which entrances will open, when will the building be ready, and will the agreed support be available? Get the operational answer from the people managing the venue that day. A sales contact saying the building remains open doesn't establish that every contracted service is unchanged.

Check production separately. Your audiovisual supplier might have equipment onsite but be missing the technician who operates it. A late delivery can push testing into the admission window. Agree whether equipment can arrive earlier, whether a qualified replacement is available and what additional access or cost that creates. Don't solve a transport problem by removing preparation your programme depends on.

Include speakers, moderators and access providers in these conversations. Ask whether a speaker can arrive the previous evening, and confirm the hotel and revised travel before announcing that arrangement. If the speaker can't attend, use the conference speaker cancellation guide to assess the programme change. A transport strike doesn't make an untested replacement session an equivalent offer automatically.

Write down what must be true before doors open. That could include the venue's required staffing, a tested presentation system, the agreed access services and a functioning admission team. Your venue and competent advisers should establish the relevant safety requirements. An attendance forecast is useful commercial information, but it doesn't justify opening without the people needed to operate safely.

Build the return and handover into staff arrangements. Booking an early taxi for a technician doesn't resolve their journey home after equipment is packed. If a shift changes, confirm who accepts responsibility, what briefing they need and whether the transport arrangement covers the actual working hours. People shouldn't discover a new closing duty while trying to catch their last service.

Keep these confirmations in the same current event plan. The programme lead needs to know when production is ready; the registration lead needs to know when admission can begin. A supplier email sitting unread in someone else's inbox doesn't help either person. Our event contingency plan provides a broader structure for naming decision makers and recording confirmed alternatives.

Choose alternatives that solve a complete journey

It's tempting to hire a coach as soon as the railway announces disruption. First establish who it will help and where it can collect them. A coach leaving from the same station people can't reach may solve very little. Ask for a specific service proposal against the actual gap, including the outward and return journeys.

In our fictional Forum, 40 of the 55 people reporting alternative journeys have accepted places on one contracted outward-and-return coach. The other 15 have separately confirmed workable travel. The coach group is already included in the attendance forecast. It isn't another 40 people to add to the total when the booking confirmation arrives.

The coach operator must confirm the usable capacity and suitability of the proposed vehicle. Establish how bookings work, what happens when someone changes their plan and whether any assistance arrangements require a different vehicle or boarding method. A spare seat doesn't necessarily meet a particular passenger's needs. Resolve those details before describing the service as available to everyone.

Agree the exact pickup point, permissions, boarding time and latest departure. Include time for passengers to find the vehicle and for the actual boarding process. Confirm the return pickup and destination separately. If you are providing a connection to another service, check that connection rather than treating arrival at a station as the end of your responsibility to plan the service properly.

Britain's Health and Safety Executive advises event organisers to manage onsite vehicle risks and coordinate external traffic arrangements. Its guidance includes keeping people and vehicles apart and planning emergency access. Apply the relevant local requirements with your venue and transport professionals. Hiring a vehicle doesn't authorise your registration volunteers to direct traffic on a public road.

For an organised shuttle with repeated journeys, our festival transport plan explains vehicle cycles, boarding demand and return operations in more detail. A conference rescue service still needs an operating plan, even if it runs only once in each direction. Confirm who checks the passenger list, who contacts the operator and who handles someone missing from the return group.

Other alternatives might be more useful. Earlier travel and a hotel can help a speaker whose presence is essential. A different local route may work for nearby attendees. Additional parking can help drivers only if the venue confirms the spaces, permitted hours and access. Get actual availability and terms before presenting any of these as a solution.

Be precise about who pays. If you offer a limited travel contribution, state the eligibility, amount, approval process and what costs are covered before people spend. If you are only sharing a hotel contact, say so. An enthusiastic message about helping with travel can become an expensive disagreement when buyers reasonably understand it as a reimbursement promise.

Adjust the programme around the whole visit

A later start can be sensible when a substantial group can arrive after the original opening. It can also make the return impossible. Check the full day before moving anything. The venue's closing arrangements, speaker availability, supplier duties and attendees' onward travel all constrain the useful options.

For the fictional Forum, registration originally opens at 9am and paid sessions begin at 9:30am. After checking the revised journeys and supplier arrangements, the team considers moving the first paid session to 10:30am. Registration would still open at 9am for people arriving earlier. The published 4:30pm programme finish would stay the same.

That proposal only works if the programme can fit without quietly removing what buyers paid for. The Forum team reviews session lengths and asks each speaker to approve the revised running order. It removes a 30-minute optional networking period from the middle of the day and reduces unallocated changeover gaps by another 30 minutes, after production confirms the remaining changeovers are workable. It keeps the promised sessions and their agreed content. These are fictional choices for this programme, not a general instruction to compress every conference.

If your existing schedule has no such space, admit that. You may have to drop a session, reduce workshop time or change the main attraction. Those are changes to assess and explain. Don't call them a simple timing adjustment because the venue and date are unchanged. Someone buying a practical workshop may value the participation time more than the closing speech.

Keep necessary breaks and access arrangements when reviewing the running order. Check the consequences with the people providing them. A late start shouldn't produce an exhausting sequence of uninterrupted sessions or strand an attendee whose booked assistance is tied to a particular time. Update the detailed schedule used by staff as well as the attractive version buyers see.

Check what that optional period meant in the actual sales description. In our example, the advertised paid offer consists of the retained sessions; the removed period was clearly described as optional free time. If you sold facilitated networking or promised particular meetings, removing that time could change the purchased offer. You would need to assess that change with the rest of the programme, rather than borrowing the Forum's solution because its arithmetic fits.

Give early arrivals a confirmed plan. Tell them when they can enter, which facilities are available and when the programme starts. If you offer refreshments or an informal waiting area, confirm staffing and provision with the venue. People arriving on the original schedule shouldn't have to negotiate access with a receptionist who has only seen the revised opening time.

Plan late admission too. Choose a route and an appropriate moment for people arriving during a session, with staff able to explain what they missed. Provide any agreed materials without suggesting they replace the whole experience. Keep the return notice visible through the day so people can make their own departure decisions before the last practical connection.

Treat remote access as a separate production decision

A streaming link can look like an easy answer when travel fails. Before offering it, establish what the remote buyer will receive. A clear feed of the main stage may provide useful access to talks. It won't automatically provide the workshops, introductions, exhibition visits or conversations included in an in-person conference.

Ask production to test the actual arrangement. That includes the room's audio, camera view, presentation feed, connection and a person responsible for remote participants. Check how questions will reach the moderator and what happens if the connection fails. A speaker's laptop facing the stage is a proposal to test, rather than a finished alternative you can promise in an email.

Get the necessary permissions before streaming or recording. Speaker agreements may cover live presentation without covering remote distribution or later replay. Attendees asking questions may also appear in the feed. Agree the scope with the relevant people and explain the arrangement to participants before using it. Keep the offer within the permissions you have actually obtained.

The World Wide Web Consortium's accessible events checklist covers remote, in-person and hybrid participation. It recommends considering the accessibility of the platform and presentation arrangements. For your fallback, check captions, usable materials and how a remote participant can take part. The fact that someone can open the link doesn't establish that they can use the session.

Explain the choice in buyer terms. State which sessions are included, whether participation is live, whether questions are supported and whether a recording will follow. If you're offering remote attendance as an alternative to an in-person booking, explain how the buyer accepts it and what happens to their original ticket. Get the relevant refund and contract position checked before presenting the options.

For the fictional Forum's core plan, the team does not announce a livestream. Its production supplier cannot confirm a suitable audience feed within the available preparation time. The organiser continues with the checked later-start proposal and separate buyer options. That is a better decision than selling a replacement experience the team hasn't tested.

You can still send agreed materials afterwards. Describe them accurately and provide a realistic delivery date. Slides or a recording may be useful support for someone affected by disruption. They aren't automatically a substitute for the conference or a reason to close a refund request without considering it.

Set buyer options before you announce the decision

Three situations need different answers. An attendee may be unable to reach a conference that is otherwise proceeding as sold. You may be changing the programme, timing or format. Or you may be postponing or cancelling the event. Don't give all three the same reply about tickets being non-refundable.

Review the booking terms, what was advertised, the actual change and the applicable law with the person responsible for your contracts. A business buying places for staff may have a different contractual position from an individual buying as a consumer. The location matters too. The practical options below help you organise the response; they don't establish a universal entitlement for every transport strike.

In the UK, the Competition and Markets Authority's guidance on cancelling goods or services explains that a cancellation term must be fair to be binding. A term written in your checkout isn't enough by itself to settle a consumer's rights. Get the circumstances checked before relying on a blanket refusal or promising the same remedy to everyone.

You might offer a name change, an accepted transfer to another date, a refund or a defined remote alternative. Establish which options are appropriate and how people request them. State any genuine processing dates clearly, and distinguish an administrative request date from rights that cannot simply be removed by your deadline. Staff need an escalation route when a case doesn't fit the standard response.

For the fictional Forum, assume the organiser has approved full $90 ticket refunds for affected buyers who request them, alongside an optional transfer to a confirmed future edition. This is an invented policy decision for the example. Forty-five of the 60 people reporting that they cannot attend request refunds, while 15 choose the future edition. Those accepted choices do not predict what your own customers will select.

Record the transfer as an obligation to provide a future place. The cash stays with the business, but the customer is still owed something. Confirm the edition, ticket validity and the terms of acceptance. Don't describe a transfer as cost-free rescue income, and don't move a buyer onto a future date without their agreement.

Keep rail-ticket claims separate. National Rail's refund and compensation guidance distinguishes unused disrupted journeys refunded by the original retailer from compensation for travelling and arriving late. Point buyers to the relevant operator or retailer for their journey. That process concerns their rail purchase; it doesn't decide what your conference owes them.

The same care applies to hotels, flights and other expenses. Tell buyers exactly what your event policy covers, and have uncertain claims assessed through the appropriate process. Your customer support team shouldn't promise third-party reimbursements or declare that nobody has any rights beyond the ticket price because they want to answer quickly.

Check the cash before booking a rescue

Once the options are defined, price the plan you can deliver. Separate original event payments from additional disruption costs and buyer refunds. Then check when each payment is due. An apparent saving on catering next month won't fund a coach deposit required today.

For the fictional Forum, use these invented USD amounts for a selected disruption calculation. The outward-and-return coach costs $1,800. Extra production time for the revised running order costs $800, and additional registration and support staffing costs $300. That is $2,900 of new supplier and staffing spending. These are example amounts, rather than market rates or a complete event budget.

The 45 approved refunds at $90 add $4,050. Together, the selected extra spending and refunds require $6,950. Assume finance has confirmed a $14,000 disruption allowance in cash after protecting the original event's outstanding payments and other existing obligations. Paying the $6,950 leaves $7,050 within that allowance.

That remainder isn't the event's profit. The example excludes the wider budget, taxes, payment fees, other claims and future delivery costs for transferred places. The original event bills have already been protected in the allowance assumption. Don't deduct them again in this calculation or forget them when establishing your own available cash.

Now test the unresolved replies. If 15 of the 30 unknown attendees also request the same $90 refund, that adds $1,350. The selected total becomes $8,300, leaving $5,700 of the allowance. This is one sensitivity check, not a forecast or maximum exposure. Model the other credible outcomes, including further disruption to people currently expecting to attend.

Write the coach's payment and cancellation terms beside its quote. If the strike is called off, can the booking be reduced or cancelled, and at what cost? Don't assume you can release a vehicle free of charge because it was hired as a backup. The supplier has reserved resources even if your preferred travel option returns.

Check insurance and supplier recoveries independently. Ask the broker or insurer what the actual policy requires, and preserve the relevant evidence. Until payment is confirmed, don't use a possible recovery as cash available for immediate refunds. Similarly, a venue discussion about a credit isn't a completed agreement to reduce its invoice.

Give the person approving the plan a payment schedule, the remaining uncertainty and a spending limit. If the next quote pushes the plan beyond that authority, escalate before accepting it. Our event contingency budget guide explains how to connect reserves to particular risks and priced responses, rather than choosing a percentage and hoping it covers whatever happens.

Make the decision while alternatives are still available

Waiting for certainty can remove your remaining choices. Find the earliest deadline that matters to your plan. It might be the coach operator's release time, a catering commitment, the point a speaker needs to travel, or when buyers would need to book an extra night. Set your decision review before that deadline, with enough time to tell people what it means.

For the fictional Thursday Forum, the organiser issues an initial travel notice on Tuesday morning. The event lead schedules the main decision for 11am Wednesday, ahead of a 1pm supplier commitment deadline, and promises a public update by 5pm. All times are local to the venue. Those are invented operational times for this example. They aren't a recommended notice period for all strikes, and an earlier announcement would need an earlier response if buyers were already making costly travel decisions.

The review should produce a specific decision. Proceeding with the revised Forum means the staff and suppliers are confirmed, the coach has been accepted by its passengers, the changed programme fits, and the buyer options are funded. Record the evidence and any conditions still being monitored. The event lead should be able to explain why the plan remains workable if a particular assumption changes.

A smaller audience can still receive a strong conference. But check what attendance makes possible within your particular offer. If buyers paid for structured meetings with exhibitors who can no longer attend, filling the main hall doesn't repair that loss. Contact the relevant partners and assess their actual contribution. Don't decide solely by whether the room will look busy in photographs.

If the essential programme cannot be delivered, or the checked travel alternatives are unusable, assess postponement or cancellation. Confirm a replacement date and its dependencies before calling it a confirmed postponement. If a date is still being investigated, say that and explain the available ticket options. Our event postponement email templates cover those two situations separately.

Agree what would reopen the decision. A cancelled coach, unavailable required staff or a further change to the transport timetable could matter after your announcement. Name who reviews the new information and who can approve the response. A published decision should give people something dependable to act on, while allowing an honest correction when the facts change.

Don't quietly abandon the plan if the strike is withdrawn. Recheck actual services with the operator, confirm whether your alternative bookings still run and explain any resulting event change. Buyers may already have accepted transfers or paid for different travel. Deal with those commitments explicitly rather than assuming everyone can return to the original plan immediately.

Tell buyers what to do, and keep every version consistent

Your first notice can acknowledge the strike before you know the final programme decision. State what is confirmed, what you are checking and when the next update will arrive. Tell people where to find official travel information. Avoid reassuring them that everything will proceed normally while your team is still finding out whether it can.

The decision email needs a different level of detail. Put the event name and date in the subject, then explain the confirmed change near the top. State the opening and finishing times, what happens to existing tickets, the available buyer options and how to ask for help. Include the next update time if a consequential detail is still pending.

For the fictional Forum, the main message could read:

Our Independent Retail Forum will go ahead on Thursday at the booked venue. Registration still opens at 9am, and the first paid session will now begin at 10:30am. The programme will finish at 4:30pm as originally advertised. The revised running order is on the event page. Your existing ticket remains valid.

If the strike prevents you attending, reply to this email for the approved full $90 ticket refund or an optional transfer to our confirmed next edition. We will confirm your choice individually. The contracted coach is for passengers who have already received a place confirmation; please don't arrive at its pickup expecting an unbooked seat.

Check your complete outward and return journeys with your transport operators before setting out. If the revised arrangements don't meet an assistance need you have discussed with us, contact our event support team so we can review it with you. We will update the event page by 5pm Wednesday, even if the arrangements remain unchanged.

In a real send, replace the example references with the exact event page, monitored reply address and confirmed future date. Have someone test every link and read the message as a buyer who missed the earlier notice. They should be able to work out what is happening without searching through a chain of emails.

Loopyah's attendee email tools support event updates and test sends. Use a test to check the timing, wording and links before the buyer message goes out. Your team still needs to supply the verified travel information, approve the options and keep the event page current. An email tool can't establish whether a train will run or a proposed coach can carry a particular passenger.

Update the places still selling the original offer. That includes the event page, scheduled promotion and partner listings your team controls. Give partners the approved facts and ask them to correct their copy. A new buyer shouldn't purchase a 9:30am opening after existing ticket holders have been told the first session starts at 10:30am.

Think about who actually receives the notice. A company administrator may have bought several tickets while individual attendees hold the travel bookings. Ask the booking contact to pass the operational update to the people attending, and use the attendee contact details you are authorised to use where available. Don't assume the person receiving the purchase receipt will be travelling. Put the same information on the public event page so a forwarded message still leads to current facts.

If sales continue, make the changed arrangements clear before the next purchase. State the later programme start and the transport uncertainty where a prospective buyer can assess them. Keep the contracted coach separate from the general admission offer unless you are actually selling or allocating further places. Otherwise a new buyer may reasonably believe the headline transport solution comes with their ticket. When you cannot describe a dependable offer, pause new sales while the decision is resolved. Someone must own that pause and its later reversal.

Prepare the support reply at the same time. Staff need the current decision, the approved options, the information required to process them and the person who handles exceptions. Check requests from group buyers carefully so a refund or transfer applies to the intended ticket holders. Record the action against the booking, with enough context that another teammate can continue the conversation.

Give the event team a short working brief

The full planning file holds contracts and background. The day team needs a brief it can use while people are arriving. Keep a current version available to the people on duty, including an offline copy where appropriate. Mark its update time so an older printout doesn't become the authority when someone's phone loses signal.

Use this outline and replace every prompt with the actual arrangement:

• Event decision and programme: confirmed date, venue, registration opening, first paid session and finish time, with the current running order.

• Travel information: official sources, last check time, known affected journeys and the person monitoring further changes.

• Organised transport: confirmed operator, pickup permissions, passenger list owner, departure times, return arrangements and contact details.

• Opening requirements: venue, production, admission and access-provider confirmations, with any condition that prevents opening.

• Buyer response: approved ticket choices, monitored support contact, processing owner and the route for unusual cases.

• Money and authority: approved commitments, remaining allowance, payment deadlines and who can authorise further spending.

• Updates and handover: next public update, staff briefing time, decision lead, deputy and the person accepting each later shift.

Walk through the awkward cases with the actual staff. An attendee arrives at the original time and asks where the first session is. A coach passenger wants to leave early. A group organiser says one colleague transferred but another still needs admission. A speaker's revised journey fails after the decision email. Ask who acts and which record they check.

Test the support contact as part of that walkthrough. A monitored inbox on Wednesday is little use if nobody covers it while the event team is busy on Thursday morning. Agree which person handles incoming travel questions during admission, how they reach the decision lead and who takes over while they are on a break. Include a response for someone already en route who has received conflicting instructions. Staff should be able to acknowledge the problem and obtain a checked answer without inventing a new departure time.

The exercise should reveal a next action, rather than invite people to improvise a policy at the desk. If support must decide whether a buyer can transfer, the registration worker needs to know how to reach support and what to tell the buyer while waiting. If the coach operator reports a problem, someone must have authority to assess it before the departure time passes.

After the conference, compare the attendance responses with what happened. Review actual arrivals, programme changes, transport use, refunds, transfers and additional spending. Keep the reasons behind the differences. A low coach count caused by an unclear confirmation email calls for a different fix from a low count because the railway resumed service.

Leave transferred bookings visible in the next edition's planning. Confirm that those customers have the promised places and receive the relevant information. Close outstanding supplier bills and buyer requests with named owners. Before closing the disruption file, assign an owner and a response date to every unresolved refund, transfer and supplier query.