How to approve partner-run fringe events around your conference

A sponsor wants to host a breakfast before your conference. An industry group wants a dinner, and a local business has offered a workshop down the road. They're paying for their own events, bringing people together and giving your delegates more reasons to make the trip. Then one of them puts your logo above a booking button, and suddenly buyers think you're organising the whole thing.

Approve partner-run fringe events only when you can explain what your approval covers, who delivers the event and what attendees are entitled to. Give partners a defined route into the official programme, with clear rules for timing, branding, tickets, costs and changes. You can offer a valuable fringe programme without taking on every event's production, but the public explanation and the actual arrangement have to agree.

For a paid conference, this is a commercial decision as much as a programming one. A good partner event can add a specialist conversation you couldn't afford to produce yourself. A poorly defined one can compete with the sessions people paid you to attend, consume your team's time and leave your support inbox handling another business's refunds. Here's how I'd decide which proposals to approve and what needs to be settled before their pages go live.

Decide what being part of your fringe programme means

Fringe events are side events held around your conference, often produced by independent hosts. Start by describing the relationship you want to offer those hosts. A listing in a local events directory is a limited promotional service. An approved fringe event carries a stronger association with your conference. A jointly produced event involves shared delivery decisions and potentially shared costs. If your team uses those descriptions interchangeably, partners will make different assumptions about the same offer.

For a first fringe programme, I'd keep a clear distinction between partner-produced events and activities your own team produces. Publish the partner's name prominently, state what your conference provides, and describe any limits on inclusion. An official listing might mean you've accepted the event into the programme under specified conditions. It shouldn't imply that you've booked its venue, trained its staff or promised admission to every delegate unless you have.

Your own after-party raises a different question about what the conference ticket includes and whether the evening should carry a separate price. Our guide to conference after-party tickets develops that decision. Here, we're dealing with independent hosts who want your approval and access to your conference audience while retaining responsibility for their event.

Be equally clear when the proposed arrangement grows. If you start choosing the partner's suppliers, directing its staff and collecting all its ticket money, ask whether the deal has become joint production. The name in your agreement doesn't settle every duty created by the real activities. Have the actual operating and legal responsibilities checked for your jurisdiction, especially where your team controls the venue or sells the offer.

A useful opening rule might say that accepted partners produce their own events, contract with their suppliers and provide the agreed attendee support. Your conference supplies a defined listing and limited permission to use approved wording. Any extra production, ticket collection or promotional service requires a separate agreement. That gives both teams something specific to discuss when a proposal falls outside the ordinary offer.

Don't let the word official do all the explaining. If you use it, follow it with the host and access conditions in the listing itself. Someone scrolling through the programme should be able to tell whether they're looking at a conference session, a partner-run fringe event or an unrelated local activity without opening a long set of terms.

Choose events that add something delegates can use

The first approval question is whether the event helps the audience you sell the conference to. A specialist breakfast for a small group might be a good addition even if it never attracts a large crowd. A broad sales presentation repeating the main programme may offer less value, despite the host's impressive brand or willingness to pay a listing fee.

Ask the partner to describe the intended attendee and what they'll actually do. A workshop should explain the activity, the level of experience required and what participants need to bring. A dinner should say whether it has hosted discussion or is simply a meal with other delegates. These details help you judge the offer and prevent the programme from becoming a collection of interchangeable networking claims.

Consider how it fits the whole conference experience. If every approved event is an expensive late dinner, delegates who leave early or don't want that format have little extra choice. A morning discussion, a practical session and an early evening gathering might serve different needs. Choose formats because they suit your audience and timetable, rather than trying to fill a predetermined set of categories.

Give partners an honest answer about demand. Acceptance doesn't mean your delegates will attend, and a newsletter placement isn't a booking guarantee. Bits & Pretzels' published side-event host guidance makes hosts responsible for registration, operations, insurance and costs, and tells them to promote beyond the conference's own channels. Its stated model also requires free participation for conference attendees. Those are that programme's choices, rather than rules every fringe programme must copy.

Your conference can choose a different model, including paid partner events, if that suits the offer and the arrangements are clear. But don't sell a partner an audience you can't promise. Describe the actual promotional placements, their deadlines and any eligibility limits. If you know little about demand for the proposed format, start with a smaller commitment the host can support without assuming a full room.

You'll also need a reason to decline proposals. Use audience fit, delivery readiness, programme conflicts and your published eligibility rules. Keep a short decision record so a persuasive sponsor doesn't get an exception nobody can explain later. A commercial partner can be important to your business and still propose the wrong fringe event for this edition.

Collect enough detail to make a real decision

Use one application route, with a named person at the partner business who can commit to the plan. Sales conversations and informal introductions can feed into it, but they shouldn't replace it. Your programme team needs the same facts whether the proposal comes from a longstanding sponsor or somebody approaching you for the first time.

The application should capture the proposed event, host, venue, date, public hours and intended audience. Ask whether places are paid, free, invitation-only or restricted to conference ticket holders. Record the proposed attendee allocation, what the ticket includes, how people book and who answers purchase questions. Include the host's event-day contact and the person responsible for its delivery plan.

Then collect the information that affects your approval. Which speakers are confirmed? Which other sponsors will appear? What conference branding does the host want to use? Will there be filming, alcohol, transport or an activity requiring specialist checks? Ask about access arrangements and the venue's status. A proposal with a venue under discussion needs a different decision from one whose actual space has been confirmed.

You don't need every document at the first enquiry. You do need to say which evidence is required before final approval. For a straightforward breakfast, that may be a confirmed venue arrangement, the relevant insurance evidence, access information, a named host and a checked booking page. A larger off-site production may need a more detailed review by people qualified to assess its activities.

Keep uncertain details visible. An application can say that a speaker invitation is pending. The public listing must not quietly turn that invitation into a confirmed appearance. A partner may be suitable in principle while its event is still unready to announce. Record the distinction and tell the partner what must be resolved, who will check it and when the application expires if nothing changes.

An application fee, if you charge one, also needs a plain explanation. Does it pay for review regardless of the outcome, or does payment happen only after acceptance? Is it credited against a listing charge? What happens if you decline or the host withdraws? Resolve those terms before collecting money, with the appropriate legal and tax review for your actual arrangement.

Review the proposed purchase before final approval

Ask for the booking page and confirmation as an attendee would see them. Follow the link from your draft programme listing and check the host, event name, date and access conditions. Then compare the confirmation with the offer. If a buyer has to search the conference website to discover that their breakfast booking requires a separate conference pass, the explanation needs work before approval.

Have someone outside the partnership conversation do that review. The person who negotiated the arrangement already knows which company handles a cancellation and may read that knowledge into an incomplete page. A colleague approaching the offer cold can tell you what the wording actually communicates. Ask them who they would contact if the venue changed and what they believe they have bought.

Where you need to test the purchase process, use the provider's supported preview or test arrangement and agree any live test with the responsible seller. Check the ticket or reservation, receipt, support route and change message. You don't need to invent every possible exception. You do need to see that an ordinary booking produces the access record and information the host intends to use at the door.

Keep the approved version with the event record. If the partner later removes an eligibility condition or adds a charge, your team can identify the difference and ask for a correction. Also establish what earlier buyers were told. Fixing today's page may prevent more confusion while leaving existing bookings needing a separate explanation or remedy from the responsible seller.

Protect the main programme and the journey between venues

An attractive fringe programme can weaken the conference if it pulls delegates away from the programme you're selling. Decide which conference hours you want to protect, then apply those hours consistently. Include sponsor commitments and your own receptions in the decision, rather than allowing each department to negotiate a different exception.

Write the timing rule with enough detail for partners to use. A restriction on events during conference sessions leaves questions about registration, lunch and the closing reception. If you allow breakfasts, state when they must finish and whether the host needs to plan time for delegates to reach conference registration. A rule that protects the first session but ignores the journey won't protect the attendee experience.

AWS's published sponsor event guidelines provide one example of a tightly controlled arrangement. They require approval for sponsor-hosted ancillary events and limit approval to the requested venue. They also tell sponsors to obtain approval before entering a venue contract. That illustrates why the location and approval sequence matter. Your programme needs its own rules suited to the commitments you're making.

Suppose, in an invented planning example, your conference begins at 9:30am and a partner proposes a breakfast ending at 9:15am. The map shows a short walk between venues. That doesn't tell you how long it takes to finish the discussion, collect belongings, leave the building, travel by an accessible route and get through registration. Ask the host and your operations team to assess that actual transition before accepting the time.

You might require the breakfast to finish earlier, move it closer or place it on a different day. Don't publish a universal travel allowance copied from this example. The suitable gap depends on the route, audience, transport and entry arrangements. Explain the reason to the partner so a later venue change triggers another review of the same problem.

Review the fringe programme as a whole too. Several hosts can independently choose the same attractive slot and target the same small audience. You don't have to eliminate choice, but you should avoid promising each one exclusive access to delegates who can't be in several rooms at once. Offer a different time or a more specific audience where that makes the event useful.

Give limited permission to use your name and branding

Approve the words and assets the partner can actually publish. That includes the event title, the relationship description, the conference logo and the booking page. An approved event can still create confusion if its advertising looks like your main conference or presents the partner as your official producer.

The Apache Software Foundation's third-party event branding policy distinguishes a talk about an Apache project from an event using Apache marks in its name or primary branding. The latter needs permission under its policy. For your own programme, distinguish a mention of the conference from permission to market an event under its identity. Your permission should identify the actual approved use.

Give the host a concise relationship description to use consistently. For example, a fictional listing could identify an event as a partner-run breakfast in the approved fringe programme, organised by Cedar Research. It could then state that separate booking is required and identify the booking contact. Use your actual names and conditions, and check the wording against the agreement before anyone publishes it.

Specify where your approval applies. A logo on the accepted event page doesn't automatically permit use in every paid advertisement, venue sign or future edition. Agree the event, dates, channels and approved assets. Include what happens after the event, such as keeping an accurate historical page while removing live booking claims. If the event recurs, require the host to confirm that its new edition has the necessary approval.

Review the page as a prospective buyer. Which business appears to be selling the place? Which logo is largest? Does the confirmation identify the partner? Would somebody assume a conference ticket includes admission? Clear wording can still be undermined by the rest of the page, so assess the whole presentation rather than approving one sentence in isolation.

Treat substantial changes as new decisions. A different host, venue, title or sponsor can change what you've accepted. Give partners a route to request those changes quickly, and make clear that silence doesn't approve them. Your team needs an authorised person who can decide, especially when a sales contact is keen to reassure a partner before the programme team has checked the revised plan.

Separate ticket eligibility from the right to enter

A conference ticket and a fringe ticket can serve different purposes. The conference ticket may make someone eligible to book the partner event. The fringe booking then gives them a place in the partner's allocation. Explain both steps before purchase. Otherwise delegates may arrive with your conference badge while the partner believes it has sold every available place separately.

Choose an access model for each approved event. It could be open to the public, restricted to conference ticket holders or invitation-only. A free event may still require a reservation. A paid event may still require a valid conference pass. Put the actual rule beside the booking link and repeat it in the partner's confirmation, so the conference programme and door team aren't describing different offers.

Your seller arrangements need the same clarity. Decide which business collects the fringe payment, issues the receipt, manages changes and handles refunds or disputed card payments. A link from your programme to a partner's checkout doesn't settle all those responsibilities. Neither does collecting the money on the partner's behalf. Have the actual sales arrangement and customer terms checked before the offer goes live.

For a first programme of independently produced events, separate partner booking can make the division easier to explain. The host sells its own event, and your listing sends interested delegates to the approved page. That isn't always the best option. A combined conference package may suit some audiences, but it needs reliable access, price allocation and change handling for everything included in the purchase.

Our guide to planning a conference alongside another organiser's event covers more extensive shared arrangements. Don't drift into one through a fringe listing. If you want one checkout or a pass covering multiple hosts, first establish who can promise the inventory, how every host receives the current entry record and what happens when one activity changes.

For the places themselves, use the allocation approved for the event's actual layout and delivery plan. In an invented inventory example, a partner has 80 attendee places after its competent team has separately resolved staff and other occupancy requirements. It reserves 10 for guests and offers 70 bookable places. Those guest places remain part of the 80 until the host actually releases them; they aren't extra capacity.

Loopyah's ticket selling tools provide event pages, ticket types with prices and quantities, and check-in access for door staff. Where you're responsible for the ticketing, those tools help describe and operate the offer you've agreed. Confirm the actual setup before relying on cross-event eligibility or shared access. Your agreement still needs to say what each ticket grants.

Test the awkward cases before launch. Somebody has a conference ticket but no fringe reservation. A colleague transfers their conference place after booking the breakfast. A member of the public buys a fringe place despite a delegate-only rule. Resolve how those cases will be checked, corrected and communicated, with a named person empowered to make the decision at the door.

Make the host's delivery responsibilities specific

A partner saying it will handle everything isn't enough to approve a public event. Ask who handles the venue, suppliers, entry, accessibility requests, food information, incident response and event-day communications. The answers should fit the proposed activity. A discussion in an established meeting room and an outdoor installation need different evidence and different expertise.

Great Britain's Health and Safety Executive says event organisers must maintain overall safety and coordinate activities, including setup and breakdown. That guidance applies in its jurisdiction. It doesn't establish who holds every duty in your particular partnership, but it is a clear reason to examine real control and coordination rather than assuming a partner's promise removes your own responsibilities.

Have your producer identify the parts your conference team controls and where the partner's arrangements connect to them. If a fringe queue forms inside your conference venue, someone must manage that shared space. If the host uses your loading entrance, its delivery must fit the venue's operating plan. Separate businesses still need a coordinated process wherever their activities affect each other.

For accessibility, ask about the actual route, room, toilets, communication and booking process. W3C's accessible events checklist calls for accessible venues and routes, gathering participants' requirements and considering access when scheduling. Use it as a planning resource. A partner repeating that its venue is accessible hasn't yet explained how a delegate reaches the particular room or requests the support they need.

Make a host contact available before booking, and agree how questions move between the conference and partner. You may receive a request because the event appears in your programme. Your team should know who will answer, what information is necessary to pass on and how to confirm that the attendee received a response. Don't make the person repeat sensitive details across several inboxes because nobody owns the question.

Insurance needs review of the actual policy and proposed activity by the appropriate person, rather than a box saying insured. Confirm who checks the evidence, relevant dates, activities and any requirements in the venue or partnership agreement. Your adviser should also explain your own position. Accepting a partner's document doesn't establish that your business is covered or that every contractual requirement has been met.

Conduct arrangements need people behind them too. Require a suitable host policy, a clear reporting route and event-day authority to respond. Decide how a report affecting the wider conference reaches your team and what information can appropriately be shared. A published standard helps only if attendees can find assistance and the host knows how to act when someone needs it.

Check sponsor promises before accepting another logo

Your fringe programme may introduce brands your main sponsorship team hasn't considered. A partner can propose a perfectly relevant event while bringing a supporting sponsor whose rights conflict with something you've already sold. Review those commitments before approving the public page, especially if your conference logo appears beside the new sponsor's name.

Ask the partner to list every supporting organisation and what each receives. That could include naming, venue signs, speaking time, product demonstrations or an acknowledgement in the listing. Check the actual main-conference agreements and the wording of any exclusivity. Don't infer that every restriction covers every independent event in the city, or that an off-site location automatically puts the activity outside the agreement.

Our guide to managing competing event sponsors develops the category decisions. For a fringe programme, the extra task is checking rights granted by several independent hosts against the commitments you control. Your sponsorship lead needs a record of approved uses, the reasons for exceptions and who can authorise them.

Keep programme access and audience data separate from sponsorship recognition. Buying the top fringe package shouldn't quietly give a partner the conference attendee list, a guaranteed speaker appearance or permission to use another sponsor's branding. Each benefit needs its own authority and delivery method. If you can't deliver it reliably and appropriately, remove it from the offer before the partner pays.

Make the same check when a host adds a supporter late. If the new sponsor changes the event's title, purpose or prominence in your programme, send that change to the person who can review the affected commitments. Explain the result directly to the partner. A last-minute commercial conversation shouldn't leave your entry staff trying to decide whether they can display a sponsor's sign.

Price the work your conference team will actually do

A partner paying its own venue bill can still create costs for your business. Applications need review, listings need checking, attendees ask questions and somebody needs to be available during the fringe programme. Estimate that work before deciding whether the programme is included in existing sponsorship, separately charged or deliberately subsidised.

The following budget uses invented USD amounts to explain the decision. These are planning assumptions, not market rates, Loopyah charges or reported results. Assume your conference offers an agreed listing and approval service to eight hosts. Each host pays $500 retained by your business after relevant transaction costs and sales taxes. Partner event ticket sales and the hosts' own production costs are outside this calculation.

Your fixed programme cost is $2,600. That includes 32 hours of review and administration at a fully costed $35 per hour, or $1,120; $480 for programme page and listing work; $600 for the agreed duty cover; and a $400 contingency allowance. Assume another $80 of support cost per accepted host. Check that the hours and duties don't count the same work twice when replacing these assumptions with your actual budget.

With eight hosts, income is $4,000. Costs are $2,600 plus $640, totalling $3,240. That leaves $760 towards wider business costs and profit. It's the programme's contribution under these assumptions, before business income tax and financing, rather than the conference's overall profit. The contingency is included as a cost allowance even if the final spending turns out lower.

Four accepted hosts produce $2,000 of income against $2,920 of costs, leaving a $920 shortfall. Each additional ordinary host contributes $420 after its $80 support cost. Six hosts leave an $80 shortfall, while seven leave $340. You therefore need seven at the assumed price to cover this particular cost plan. That isn't a recommended minimum size for every conference fringe programme.

Now consider a demanding eighth host that requires $900 of extra work beyond the ordinary allowance. The eight-host result falls from a $760 surplus to a $140 shortfall. More accepted events haven't improved the outcome because you've accepted more service than the price covers. Quote the additional work separately, reduce the promised service or decline the proposal if it can't fit your available staff.

You can choose to fund the programme from the main conference budget instead. Perhaps useful partner events strengthen the trip for delegates. State the planned subsidy and judge it against that purpose. Don't invent extra conference ticket sales to make the spreadsheet balance, or count money already included in a sponsorship agreement again as new fringe income. The event budget guide helps connect this smaller calculation to the whole event.

Payment timing needs its own check. Your costs may start before hosts pay their acceptance invoices. Agree what starts review, what starts listing work and when payment becomes due. Match cancellation terms to the actual commitments and applicable rules. A budget that eventually earns money can still require cash your business doesn't have when staff or suppliers must be paid.

Share the information each event needs

Start with the operational purpose. A partner may need to confirm that someone booking has a valid conference pass. That doesn't necessarily require a full export of every attendee's name, employer, contact details and purchase history. Choose the smallest workable process, and have the privacy responsibilities and lawful basis checked for the places and people involved.

The UK's Information Commissioner's Office recommends data sharing agreements to explain the purpose, handling and responsibilities for shared information. Its guidance also says such an agreement doesn't provide immunity from legal breaches. The guidance is under review following UK legislative changes, so check the current position when applying it. Treat a written agreement as part of the work, rather than permission to share whatever a host requests.

Decide what happens when information changes. If conference eligibility affects fringe admission, the host needs an appropriate way to handle a cancelled or transferred conference ticket. Agree the necessary checks, authorised recipients and timing. A process that depends on one exported list can fail after the next order change, even if the list was accurate when sent.

Separate booking administration from future promotion. The partner needs to explain the uses of information it collects through its own registration. Your conference needs to explain its uses too. Appearing together in a programme doesn't make every attendee available for every host's marketing. Tell partners what promotion you can provide through your own channels instead of using an attendee export as the default benefit.

Agree who sends each operational update. A changed breakfast venue primarily needs to reach people booked for that breakfast. A changed conference opening time may affect several hosts and their guests. Keep an approved version of the new information, name the sender and confirm the relevant people received the message through the appropriate process. Updating a public listing alone may leave booked attendees following their original confirmation.

Approve a specific edition and control later changes

Use a short written approval record that identifies the event you're accepting. It should point to the agreed plan and any signed terms, and record the conditions that still need to be met. It can help your team operate the arrangement, but it doesn't replace properly reviewed contracts, venue permissions or the host's production planning.

Here's an original example for the fictional breakfast. The names, allocation and times are invented planning choices. The breakfast has 80 attendee places under its separately assessed plan, including 10 reserved guests and 70 bookable places. Assume the host and your operations team have checked the real transition and agreed an 8:30am finish ahead of the 9:30am conference start.

• Cedar Research is the organiser and seller of the breakfast. Its booking page identifies Cedar, the confirmed venue, inclusions and purchase support contact. It handles its supplier contracts and the agreed delivery responsibilities.

• A valid conference pass makes someone eligible to book, but doesn't itself reserve a breakfast place. The host publishes the verification method and what happens if conference eligibility changes.

• Your conference provides one listing in the fringe programme, using the accepted description and approved booking link. The host's fee follows the fictional $500 retained-income assumption above, with actual invoicing, tax treatment and payment dates settled separately. Extra advertising and guaranteed bookings aren't included. The host may use only the agreed conference assets for this edition and approved channels.

• The programme and sponsorship leads have accepted the final topic, confirmed speakers and disclosed supporters. Adding a sponsor, changing the venue or changing the access model requires another decision before publication.

• The host confirms the required venue and activity permissions with the relevant responsible bodies and supplies the agreed delivery evidence by the named deadline. Your producer checks the connections with conference operations, and the designated reviewer checks the relevant insurance evidence.

• The host and conference each have a named event-day lead and an alternative contact. The agreed response plan identifies who can stop entry, seek emergency assistance, remove the official listing and notify booked attendees.

Complete the record with actual dates, documents and names before relying on it. A phrase such as relevant insurance evidence still needs the particular requirements agreed for this event. Likewise, the response plan needs real contact details and a usable procedure. The example helps you identify decisions; it doesn't make those decisions for you.

Give each host a clear outcome. You can approve, decline or accept a proposal in principle while withholding public listing until specified conditions are met. If you use conditional acceptance, say exactly what the host may do at that stage. Don't let an encouraging email become an assumed right to announce the event or use your logo before the checks are finished.

After approval, keep one current record and a history of material changes. A replacement venue can affect travel, accessibility, capacity, supplier arrangements and buyer rights. Review those effects together, then update the approval and attendee information. The host's permission to amend a booking page shouldn't become permission to change the event you've accepted without telling your team.

Prepare for withdrawal, complaints and event-day decisions

Before the programme goes live, agree what happens if a host cancels, fails a condition or stops answering. Your team may need to remove the listing and conference branding. Attendees may need a message, a refund or another response from the responsible seller. Those actions are connected, but one doesn't automatically complete the others.

Your agreement should distinguish losing official programme status from cancelling the partner's event. You may have authority to withdraw your own listing without authority to close an independent venue. Equally, competent people may need to stop an unsafe activity under the applicable arrangements. Have the actual rights and responsibilities checked and give staff the response steps they can use, rather than a broad promise that your conference can control everything.

Run a few cases with the team. A partner moves to a venue that hasn't been reviewed. A delegate reports harassment at an approved event. A host cancels while your programme still shows its booking link. In each case, identify the immediate action, the responsible contact and how affected attendees receive accurate information. Work through the actual communication, rather than stopping after someone says they'll investigate.

Keep a short record of decisions and evidence, with access restricted where appropriate. Note what was reported, who assessed it, what action followed and which attendee messages were sent. Avoid broadcasting personal information across a general partner chat. Your team needs enough information to act and follow up without turning a difficult incident into another avoidable problem.

After the conference, review the programme against the reason you created it. How much work did approval and support take? Did hosts deliver the promised events? Were booking rules clear, and did delegates use the opportunities? Separate unique people from total fringe visits, since one delegate can attend several events. A busy fringe programme doesn't by itself prove that it sold more conference tickets.

Before inviting hosts back, resolve the specific problems their edition exposed. Adjust the service and price if review work exceeded the budget. Change the scheduling rule if delegates missed sessions. Require a better booking explanation where people arrived without places. Open the next application round only when you can tell partners what your approval includes and your team can deliver that offer.