How to organise a paid live-action role-play weekend

You've got a setting people want to step into, a few friends who can run the game, and a venue that looks the part. Now you're trying to turn that into a weekend people will pay for. How much story do you need? How many players can you look after? And what happens when the person with the important letter decides to spend the afternoon somewhere else?

To organise a LARP event, start with a complete experience you can explain and test. Give every player something worthwhile to do, agree the practical rules before tickets go on sale, and pay for the people who make the weekend work. Choose the player limit from the experience and the assessed site arrangements, then check whether the resulting ticket income covers the whole job.

LARP means live-action role-play. Participants portray characters and make decisions together in a physical setting. That can involve conversation, exploration or structured conflict, depending on the game. There's no single format that all players expect, which is why a promise of "an immersive weekend" needs considerably more explanation.

For a first paid weekend, I would choose an original setting, an adult audience and clearly scheduled play, with accommodation arranged separately. The example below uses a non-contact fantasy gathering about rebuilding a trading town. It's a fictional planning example, including the USD budget, rather than a claim about what every LARP should cost or allow.

Decide what kind of weekend you're selling

The first thing you want to do is describe the experience without relying on the setting's history. Can a beginner arrive alone? Do players receive characters or create them? Is physical combat part of play? What must they bring, and when can they stop being in character? Those answers will influence almost everything you spend money on.

Our fictional event brings forty adult players together on Saturday and Sunday. They represent four groups negotiating how to rebuild a town after its trade routes have changed. Players bargain over supplies, propose projects and decide which commitments to make. They go home or to independently booked accommodation overnight. There are no public spectators and no physical combat.

That's still plenty of room for an interesting weekend. A player can campaign for a public workshop, negotiate access to a warehouse or persuade another group to support a shared transport route. Different priorities create decisions without requiring elaborate effects or an enormous map. You can develop the setting through the consequences of those decisions.

Choose what beginners need to know before they buy. If the game depends on fast improvisation, say so and explain the support available. If players can speak normally while describing what their character wants, make that clear. Don't tell people they need no experience and then send a rules document that assumes years of familiarity.

Describe the physical experience as carefully as the creative one. State the expected walking, standing, seating and outdoor exposure. Explain whether players can take breaks while the story continues and how they can rejoin. A promise of continuous immersion can make someone think they must keep performing through meals or discomfort.

If your ambition is a combat campaign or a residential event, develop that offer with experienced people who understand the additional requirements. The first version doesn't have to contain every feature you enjoy as a player. It needs enough depth to justify the ticket and enough restraint for your team to deliver it properly.

Write roles that give everyone a reason to participate

A long character biography can be enjoyable to read and surprisingly unhelpful during play. The buyer still needs to know who to approach, what they want and what they can do when their first idea fails. Start the role with those practical invitations, then add background that helps the player make choices.

For the trading-town example, a workshop representative wants access to a suitable building. Another player controls a proposed supply agreement. A third wants the workshop to train newcomers in exchange for support. They have reasons to talk, but none can settle the whole matter alone. Their different interests create play through negotiation.

Give each role more than one useful relationship. If a character's only connection depends on one person attending, an absence can leave that buyer stranded. Add another contact, an independent objective and a route to join a wider decision. A player should be able to have a worthwhile weekend even if their preferred deal falls through.

Watch how you distribute authority. A few leadership roles can make sense, but everyone else needs decisions beyond asking permission. Let players make proposals, commit resources within agreed limits or organise an activity others need. Tell leaders that their job includes inviting participation, then test whether the structure actually allows it.

Keep personal boundaries separate from fictional ambition. A character may want to win a negotiation; the player doesn't have permission to intimidate another person in whatever way produces the result. Explain the difference in the role pack and teach it in the opening workshop. Players need to know how to disagree within the game's rules.

Make essential information available in more than one place. If one player holds the only instruction needed to open the next part of the weekend, the event depends on that person staying available and interpreting it correctly. You can preserve secrets while giving referees a way to recover missing information without forcing a particular outcome.

Before allocating roles publicly, ask a few unfamiliar testers to explain what they would do first. Listen for the person who says, "I suppose I'll wait until someone talks to me." That usually needs a better invitation in the character, a clearer relationship or a change to how the opening scene works.

Build a story that can survive the players' choices

Players will miss clues, form unexpected alliances and spend time on things you thought were minor. That's part of the attraction. Your preparation should help the event respond coherently, rather than depend on everyone discovering the same information in the same order and choosing the ending you already wrote.

For our example, the central question is which rebuilding commitments the town will accept. Saturday introduces the available resources and competing proposals. Sunday gives players time to revise agreements and present a final plan. The timetable fixes when those stages happen, while the decisions inside them remain open.

Prepare likely consequences for different choices. If a group spends its resources on storage, what becomes easier and what remains unresolved? If nobody agrees to maintain a transport route, how is that consequence communicated? You don't need a separate script for every possibility. You need consistent principles that referees can apply together.

Give the team a way to introduce information when the game stalls. A scheduled council notice can clarify what must be decided next without instructing players how to vote. A supporting character can answer questions about a rule. Avoid solving every difficulty through a powerful character who appears and tells everyone what to do.

Decide what happens at low attendance. Perhaps the story works with fewer representatives per group, provided certain responsibilities are reassigned. Test that version before claiming you can run it. The minimum number for a coherent game and the minimum number for a viable budget answer different questions, and both need to be satisfied.

Write a short operating pack for referees. Include the current situation, the rules they may interpret, changes they may authorise and matters they must refer to the event lead. Use ordinary names for rooms and locations alongside fictional names. A message about a real problem should reach the right place without someone consulting the world map.

If you're used to hosting at a table, our guide to paid tabletop role-playing sessions covers preparation and shared expectations in that setting. A weekend across a physical site adds another task. Different groups can be acting at once, so your team needs to understand what has happened elsewhere before issuing incompatible rulings.

Choose the site around the game you can actually run

A courtyard, a woodland path or a converted hall can suggest wonderful scenes. Visit it with the actual activities in mind before committing to the hire. Where will people negotiate, wait, eat and ask for help? What changes when the ground is wet, another booking arrives next door or someone needs to leave early?

HSE's venue and site design guidance, for Great Britain, considers audience and workforce numbers, access, ground conditions and weather, with responsibilities defined where control is shared. Use the applicable local requirements and competent advice for your site. An attractive location doesn't establish that your proposed event is suitable there.

Before committing to the site, describe the actual programme to the landowner, insurer and relevant local authorities. Confirm the permissions and conditions for the proposed use, food service and any other activities you plan. Use original material or obtain the permissions needed for borrowed text, art and recordings. An event booking doesn't settle those separate questions.

Make the hired boundary explicit. Our example uses a main hall, agreed adjoining rooms and a defined outdoor area. Players can't enter neighbouring land because it looks like part of the setting. Mark real boundaries plainly and explain them before play. A fictional map should help the game without obscuring the limits of the booking.

Separate places for play from places for ordinary life. People need somewhere to rest without being approached in character. Toilets, first aid and the help point must remain easy to identify. Never make a person solve a puzzle or speak to a character to find essential facilities. Keep operational signs understandable throughout the event.

Plan the indoor alternative before you advertise outdoor scenes. Does it preserve a meaningful experience for everyone, or does it require removing most of what you sold? If the event can't continue in particular conditions, agree the decision process and explain the relevant terms. Don't call an empty room a weather plan merely because it has a roof.

Include crew, contractors and accompanying people in the relevant occupancy assessments. Forty player places don't imply permission for any number of extra people. The usable game area and the number of players your referees can support may impose a smaller limit than the site's overall permitted capacity. Work with the lowest applicable limit.

For this first example, accommodation stays outside the booking. Players arrange their own overnight stay and transport, and the event page says so before purchase. If you sell camping or rooms later, assess and resource that operation separately. Our festival campsite planning guide explains why overnight provision creates responsibilities beyond adding a ticket option.

Agree costume, props and contact before someone packs

Costume expectations can make a beginner worry that the ticket is only the start of an expensive purchase. Describe the minimum that works for your game. For the fictional town, simple comfortable clothing in the stated style is enough, with a supplied group marker. Elaborate costume is optional and creates no additional game advantage.

Show examples you have permission to use and explain the useful qualities. Players need footwear suitable for the real surface, clothing suitable for the weather and enough freedom of movement for the advertised activities. A convincing silhouette isn't a good reason to conceal someone's face or make essential communication harder.

Publish the prop rules before sales open. Our non-contact example excludes weapon props, projectiles, pyrotechnics and open flames. The production supplies the documents and tokens used for game decisions. That choice keeps the offer consistent with what the team has prepared; it isn't a universal rule for LARP or a substitute for assessing other props.

Explain the difference between checking an object and authorising an activity. A decorative item being accepted at arrival doesn't permit contact, climbing, throwing or use in a way the event hasn't approved. Give staff the authority and procedure to reject an unsuitable item and tell players what they can do with it instead.

Choose simple rules for personal belongings. Make clear which objects are game material, which may be moved under the rules and which must never be handled without permission. A player shouldn't have to wonder whether their actual bag has become part of a fictional theft. Keep money, medication and access equipment outside game mechanics.

If you introduce physical combat in a later event, it needs its own experienced design, assessment, equipment rules, training and supervision. Buying padded props doesn't complete that work. Keep the first event's publicity honest about the format you are running, especially if promotional photographs could make people expect battles.

Make boundaries easy to use during play

People can agree to a broad theme and still want to decline a particular interaction. Explain how that works before role allocation and practise it at the start. A player needs a simple way to pause, step back or leave without having to reveal a personal history or win an argument about the character.

The practitioner-written Larp Safety Manifesto asks organisers to consider communication, boundaries, difficult situations and care for the team. It is a discussion framework, not a certification that an event is safe. Use those questions to make your own approach understandable and workable for the actual group.

Choose your game's pause and withdrawal methods with experienced support, explain exactly what they mean and rehearse the response. Don't assume a familiar gesture means the same thing in every LARP community. Players should know whether a signal pauses their immediate interaction or calls for wider assistance, and how to summon staff.

Tell people which themes are present before they buy. Avoid advertising a relaxed beginner event and introducing substantially different content as a surprise. Explain prohibited conduct in plain language and provide a private contact for questions. A person deciding whether to attend needs enough information to make that choice without reading the full story. Declining an interaction must remain possible during play, even if the person agreed to the general theme beforehand.

Decide who responds when a concern involves a referee, organiser or friend of the team. The reporting route needs an alternative to the person concerned. Publish the process and train the people who will use it. A policy that depends on everyone knowing the organiser personally won't serve newcomers well.

Keep complaints about conduct separate from disagreements about game rules. A referee can settle whether a fictional agreement was valid. A report that someone ignored a boundary needs the event's conduct process. Don't require players to continue a scene while staff debate whether their character would have accepted it.

After someone steps out, offer a clear practical route. They might use the quiet area, speak privately with the designated person or leave the event. Rejoining play can be discussed when they want to return. Don't promise therapy, total confidentiality or an outcome your team isn't qualified or authorised to provide.

Recruit the crew for the real workload

A friend who loves playing a memorable character may be excellent story crew. That doesn't automatically make them available to answer booking questions, manage a complaint or cover a long shift outdoors. Describe each job, the hours around it and the experience needed before deciding who will do it.

Our fictional delivery plan has an event lead, a site and arrival coordinator, three referees who also cover supporting story roles, two welfare staff and a medical provider. That's eight crew members for this invented plan, not a recommended ratio for forty players. The actual provision must follow the activities, site, audience and relevant assessments.

Anita Berthold's practitioner account of the work of LARP safety staff recommends making support people visible and, where possible, keeping them free of major game roles. It also distinguishes their advice from organisers' enforcement decisions. Introduce the welfare team at the workshop and identify the event lead responsible for enforcement decisions.

Build cover into the rota. Players need to know where support is available while another staff member takes a break. If one person accompanies someone away from the play area, identify what remains covered and what activity must pause. Don't assume every crew member can replace every other role just because they share a radio.

Agree payment for preparation, rehearsal, arrival, delivery and packdown. Include the time spent learning the rules and reviewing role information. If a contractor supplies medical provision, confirm the actual scope and hours with them. A single budget line doesn't demonstrate that the service matches the event's assessed needs.

Give supporting characters limits on what they can promise. A performer should know which fictional commitments they can make and when to consult a referee. Staff also need to recognise when someone is asking a real question. A player looking for their lift home deserves an ordinary answer, even if the nearest crew member is portraying a town official.

Finish the briefing with a few practical rehearsals. A player arrives with an excluded prop. Two referees have issued conflicting rulings. Someone wants to report a concern about a crew member. Follow each situation through the actual contact route and decision, then fix anything that depends on finding the organiser by luck.

Price the weekend after paying for preparation

Start the budget with the event you can deliver, including work that happens before players arrive. Writing forty usable roles, answering questions and rehearsing the opening can take substantial time. If you record only the venue and the public hours, the apparent profit may simply be payment you forgot to allow for yourself.

Here is a fictional USD budget for our non-residential weekend. Venue hire costs $1,600. Writing and producer time cost $1,400. Referees cost $1,200, welfare and medical provision $900, and site and arrival coordination $600. Props and printing cost $500, promotion $300, and insurance, travel, crew meals and cleaning another $500. Those fixed costs total $7,000.

These amounts are invented allowances, not market rates or recommended staffing prices. The labour figures include the agreed preparation, rehearsal, setup and packdown for their respective jobs. The venue allowance includes the trial access and public event access. Applicable purchase taxes and delivery are included in the expenses. Replace every allowance with a quote for your actual requirements.

Suppose each paid ticket leaves you $220 after sales taxes, ticketing and payment costs. Separately, food and participant materials cost $20 for each booked player, paid or complimentary. That leaves $200 per paying player towards the $7,000 fixed budget when there are no complimentary places. Accommodation, personal costume and player travel are outside this offer.

At twenty-eight paid players, the event loses $1,400. At thirty-two, it loses $600. Thirty-five covers the stated event costs exactly, while thirty-six leaves $200 and forty leaves $1,000. Those results are before income tax and borrowing costs. They assume no sponsorship, bar income or later bookings, and every stated cost is paid as budgeted.

A sellout therefore doesn't leave an enormous allowance for surprises. Ten buyers receiving a discount that reduces your retained amount by $20 each lower the forty-player result to $800. An extra $600 supplier invoice lowers the original result to $400. Apply both changes and only $200 remains. Decide whether that return justifies the work and exposure before opening sales.

Complimentary places matter too. Forty players made up of thirty-eight paying buyers and two complimentary guests leave $560 under these assumptions. You receive $8,360, pay $800 in player costs and pay the same $7,000 fixed bill. A free place uses part of the forty-player allocation even though it produces no ticket income.

Use the event budget guide to work through your own costs and sales assumptions. If the required price won't sell, reduce the production scope, negotiate costs or redesign the offer. Increasing the number of players is sensible only if you can still deliver the experience within the assessed arrangements.

Separate a profitable forecast from money you can use

Next, put the payment dates beside the budget. The venue may require a deposit before you have a sales page. Writers and crew may need payment before the event. Ticket money may become available on a different schedule from the one you imagined. Check the arrangements that apply to your account and contracts.

Suppose the fictional venue takes a $1,000 deposit towards its $1,600 hire charge. The deposit is part of that expense, so you don't add it to the budget again. You do need to show when it leaves your bank account and how you will fund it before later ticket income becomes available.

Set a go-ahead date before the next large commitment becomes unavoidable. At that point, check paid bookings, the tested minimum player group and the actual cost of cancelling or continuing. A person saying they intend to buy isn't a booking. Treat any deliberate subsidy as a capped business expense with an owner, rather than quietly assuming it will disappear.

Food and participant materials need a final quantity deadline. Our calculation uses the number booked when those orders are committed. If you later accept a cancellation without recovering the related expense, rerun the result using the money refunded and costs still payable. A no-show doesn't automatically return money you already paid to a caterer.

Keep money for disruption separate from profit. The example has no separate contingency expense included in its $7,000, so you need to decide what additional reserve the business can fund. Work through plausible refunds, replacement staff and cancellation charges. An unspent reserve remains available money; it doesn't become an expense merely because you've set it aside.

Write the actual cancellation and transfer terms with suitable local advice. Our event refund policy guide covers the choices you need to explain. The public wording should match the decisions you can honour, including what happens if you cancel, materially change the offer or don't reach the required booking level.

Make ticket choices reflect the experience

For the first example, one player ticket covers both scheduled days, a prepared role and the opening workshop. Lunch on both days, drinking water and the stated participant materials are included too. It doesn't include accommodation, costume purchases or transport. Put those inclusions near the price. The buyer should be able to work out their likely overall commitment before reaching checkout.

Don't add spectator tickets as an easy way to increase revenue. Someone watching can affect how comfortable players feel, use facilities and interrupt scenes that weren't designed for an audience. Our example has no public spectator offer. If you later create one, design its access, boundaries and value deliberately before selling it.

Decide how role allocation relates to the sale. You can collect preferences and allocate roles after a stated deadline, provided buyers understand what is and isn't guaranteed. Don't sell a named character you may later replace without explaining that possibility. Keep a clear process for discussing a role that doesn't fit the player's disclosed requirements.

Ask whether the player prefers public speaking, small conversations or a quieter practical role, and whether they want to be grouped with a friend. Explain which preferences you can guarantee and which you will try to accommodate. Check the whole allocation before sending it, so one group doesn't receive all the confident negotiators while another has nobody comfortable making an opening proposal.

Loopyah's ticket selling tools let you set ticket types and releases with their own prices and quantities. For this example, you could release ten early places and thirty later places within the forty-player allocation. Your team still owns role assignment, the site limit and any accommodation arrangements. Test the combined quantities before sharing the sales link.

A valid ticket also doesn't establish that someone has attended the workshop or completed a required prop check. Decide how the arrival team records those steps and informs referees. Keep the process simple enough to use with the actual booking records and staffing you have, including when someone buys on behalf of another player.

Ask an unfamiliar person to read the page and tell you what they expect. Listen for misunderstandings about overnight play, combat, food, costume costs and whether friends will share a group. Fix the description before treating those questions as something the joining email can explain later.

Help players prepare without giving them homework they can't finish

Send the role pack early enough for the preparation you require. Keep essential instructions short and clearly separate from optional setting material. A player needs the event address, timetable, practical rules and first actions even if they never read the history of the town. Tell people honestly how much advance reading the experience requires.

Provide a private way to discuss access requirements and role fit. Ask about what the player needs to participate rather than collecting personal information out of curiosity. Confirm what you can arrange and explain any unresolved limits before the relevant purchase or travel decision. Don't promise that every role works for everyone unless you've checked the actual activities.

W3C's accessible event checklist is written for meetings, presentations and training. Its advice about accessible materials, explanations and breaks is useful for the opening workshop and joining information. It doesn't certify the rest of a LARP site or replace reviewing the activities players will undertake.

For example, explain important symbols in words as well as colour. Make the role information available in a usable digital format and provide readable printed copies where needed. During the workshop, explain a rule aloud and demonstrate it, then allow questions. Test whether someone can follow the explanation without already knowing how your group plays.

Keep operational updates in ordinary language. Loopyah's attendee email tools support updates to ticket holders and a test email before sending. Use the update to communicate the confirmed entrance, workshop start, equipment restrictions and contact details. Share individual role information through an appropriate private process, rather than exposing everyone's material in a group message.

If one buyer books for friends, explain how the actual players receive their joining information. The purchaser may handle payment while someone else needs to prepare a character. Confirm receipt of essential practical information through the process you have chosen, especially where an unanswered question could affect whether someone can participate.

Give the weekend a timetable people can rely on

Your schedule should make room for learning, meals and returning to ordinary life. Continuous play can sound impressive on a sales page, but a first event benefits from clear starts and stops. Players need to know whether a conversation at lunch is part of the story and when the crew will no longer be running it.

Here's an illustrative Saturday for our fictional weekend. Arrival runs from 9am to 10am. The rules workshop and introductions run until 11am, followed by play until 12.30pm. Lunch lasts until 1.30pm, then play continues until 3pm. A break lasts until 3.30pm, with the final play block ending at 5pm. A closing check-out finishes at 5.30pm.

Sunday arrival begins at 9am, with a short briefing from 9.30am to 10am. Play runs until noon, followed by lunch until 1pm. The final play block finishes at 2.30pm. The group leaves character and discusses the experience until 3pm, and players leave the site by 3.30pm. Crew setup and packdown have separate paid access windows agreed with the venue.

That's four and a half hours of play on Saturday and three and a half on Sunday, eight hours altogether. The remaining time supports the event through preparation, meals, breaks and closing. Describe that honestly. A weekend ticket doesn't mean every hour of two days is active play, and players shouldn't discover the distinction after purchase.

The fiction ends each day at the stated time. Players can socialise independently afterwards, but the ticket doesn't include an overnight game or staff supervision at their accommodation. Make that boundary clear in the programme and closing announcement. Don't send secret midnight tasks if your public offer says the day has finished.

Plan late arrival before it happens. Someone missing the workshop needs a proper briefing before joining play, so set a staffed joining point and tell buyers what to do if delayed. If your team can't deliver that briefing during a particular scene, explain when joining becomes possible. Avoid making other players responsible for teaching essential rules while trying to enjoy the event.

Rehearse what happens when the plan changes

Run a practical trial with people who didn't write the material. Give them the same information players will receive and watch their first decisions. Can they find someone to talk to? Can the referees answer questions consistently? Does a quiet player have a useful way to contribute without being pushed into a performance they don't want?

Test an absence. Remove a role holding an important responsibility and see whether the remaining group can still act. Then test a player taking a long break. The response might involve a referee sharing information or transferring a fictional responsibility under an agreed rule. It shouldn't depend on pressuring the person to stay in play.

Try the busiest ordinary moment too. Everyone arrives while a costume question, a booking problem and a private concern need attention. The site coordinator shouldn't have to abandon arrivals to locate the only person who can answer all three. Rehearsal may reveal that you need a different opening sequence or more support before it reveals a need for more plot.

HSE's incident and emergency planning guidance, for Great Britain, covers clear roles, stopping an event and testing communication. Apply the relevant local requirements to the actual activities and site. The game pause method and the event emergency procedure need to be distinguishable, with staff trained in both.

Walk through the actual communication method in every occupied area. Agree who can stop activity, who contacts the appropriate assistance and who decides whether restarting is possible. Keep public wording clear enough that players recognise a real instruction. Use the real location names staff and responders can find, regardless of what those rooms represent in the story.

Also rehearse an ordinary creative failure. Suppose the same few people dominate the council meeting and others have nothing to do. Can referees invite separate proposals or create smaller discussions within the prepared structure? A successful event needs more than reaching the ending on time. Test whether the design gives the whole paying group a worthwhile experience.

Record what failed, who will change it and when you will test again. Agree the final version your team has actually rehearsed before opening. A last-minute new scene can change rules, workload and physical movement, so review it properly rather than assuming more content always improves the ticket's value.

Decide whether to run another weekend

Collect feedback privately as well as during the closing discussion. Some players will need time to think, and others won't want to criticise the event in front of the crew. Ask which parts helped them join the story, where they felt excluded and whether the practical information matched the experience they received.

Review roles individually. A generally happy group can still contain a player who spent most of the weekend waiting for another person's permission. Compare what the role was meant to offer with what happened. Improve the relationships, information or decision structure before carrying that same role into the next paid event.

Ask crew about the work around play. How many questions arrived before the weekend? Which rules needed repeated explanation? Who missed breaks, and which jobs continued after the published finish? Put the real hours and invoices into the budget. A reused setting may reduce some writing next time, but it doesn't remove player communication or support during the event.

Keep serious concerns in the process you promised. Don't treat a conduct report as a suggestion to make the next story friendlier, or average it into positive feedback about the venue. Assign the appropriate response and follow through. Separately, collect the ordinary design changes the creative team can make for another run.

Then decide whether another date is justified at the price and player number you can support. If the first event needs more paid crew time, price that version before offering a repeat. If the game works beautifully at a smaller group, build the next budget around that finding. Open the next booking when you can explain both what players will enjoy and how the business will pay for delivering it.