Co-hosting rules on Events: a practical guide

When an event fails, the argument is rarely about the sound system or the catering. It is about who holds the administrative keys and who absorbs the financial blow. Last October, an independent pop-up dinner in Brussels collected €3,400 in ticket sales through a primary organizer's personal account. When the co-hosting chef pulled out six hours before service due to a kitchen injury, ticket holders demanded full refunds. The primary host had already spent €1,200 on non-refundable venue deposits. Without a structural agreement governing liability, the dispute spent three months in small-claims arbitration, freezing both parties out of future platform bookings.

Most event platforms treat co-hosting as a simple cosmetic badge—a profile picture attached to a listing. WEVONE Event treats co-hosting as a multi-signature financial and operational contract. Before a single ticket goes live, the primary host and co-hosts define operational boundaries, access controls, and automated payout splits.

The Three Permission Tiers

Granting full account access to a co-host creates structural vulnerability. WEVONE Event categorizes co-host access into three distinct, non-overlapping roles:

1. Administrative Co-Host: Possesses symmetric controls with the primary creator. Can modify ticket pricing, alter dates, issue refunds, and adjust revenue splits (requires multi-signature approval from all primary holders).
2. Operational Co-Host: Manages attendee communication, edits event descriptions, updates schedule agendas, and responds to venue queries. Operational co-hosts cannot alter bank payout details, change ticket prices, or initiate event cancellations.
3. Gatekeeper (Access Control): Limited strictly to check-in functionality. Gatekeepers can scan QR tickets, view attendee names, and mark arrivals via the WEVONE mobile client, but cannot access attendee contact details, revenue figures, or administrative controls.

This separation prevents accidental scope creep. A guest speaker assigned to manage attendee Q&A cannot inadvertently alter the refund window or redirect ticket revenue.

Financial Architecture: Escrow and Automated Revenue Splits

The central point of failure in co-organized events is capital distribution. On legacy channels, ticket proceeds flow to a single bank account, requiring manual transfers, tax re-invoicing, and implicit trust.

Under WEVONE Event, ticket proceeds do not enter either host's personal balance during the sales cycle. Instead, incoming payments—whether processed in fiat or platform utility tokens like WEVAR—are held in a transactional escrow vault tied to the specific event ID on the univers ledger.

During setup, the primary host configures the Payout Split Matrix. For example:

• Primary Host (Venue Operator): 55%
• Co-Host A (Event Curator): 35%
• Co-Host B (Sound Technician): 10%

When a ticket is sold for €50, the platform escrow ledger logs the exact allocation. Funds remain locked until the 48-Hour Post-Event Settlement Window expires. If no systematic dispute is filed by attendees or co-hosts within 48 hours of event completion, the engine automatically releases the funds into each participant’s designated balance or bank account.

If an event utilizes WEVAR tokens for discounted community access or local micro-sponsorships, these are converted or split using the same ratio at the precise moment of settlement, eliminating manual ledger adjustments.

Worked Example: The Lyon Artisanal Workshop

To observe the framework in action, consider L’Atelier du Pain, a joint workshop organized by Marc (a master baker) and Elena (a specialty coffee roaster) in Lyon.

1. Drafting and Proposal: Marc creates the event draft in the WEVONE Event universe. He adds Elena as an Administrative Co-Host and sets a 50/50 revenue split.
2. Multi-Signature Confirmation: Elena receives an in-app prompt requiring cryptographic confirmation of the terms, including the cancellation policy (70% refund up to 48 hours prior) and the dispute arbitration parameters.
3. Sales Phase: 40 tickets sell at €40 each, generating a gross escrow pool of €1,600.
4. Execution: On the day of the event, Marc and Elena assign two apprentices as Gatekeepers. The apprentices download the check-in interface, scanning 38 attending guests without gaining visibility into the total €1,600 pool revenue.
5. Settlement: 48 hours post-event, with zero filed complaints, the WEVONE escrow protocol executes the split. €800 minus platform transaction fees posts directly to Marc’s account, and €800 posts to Elena’s. Neither party issues an invoice to the other; tax receipts are auto-generated per recipient by the platform ledger.

Handling Cancellations and Disputes

When things break, the co-hosting framework shifts from operational management to risk containment.

If a co-host requests an event cancellation, the system requires secondary confirmation from all Administrative Co-Hosts. If a unilateral cancellation is forced by the primary host, the platform initiates an automated refund loop from the escrow vault. Non-refundable costs already distributed (such as verified upfront supplier payouts arranged via WEVONE Mission) are evaluated against the initial risk clause selected during setup.

WEVONE's underlying infrastructure uses Mia, our contextual intelligence engine, to analyze dispute logs. If an attendee files a claim asserting that an advertised co-host failed to appear, Mia cross-references the check-in ledger, location verification, and co-host activity logs. Rather than freezing the entire event wallet, the system isolates only the disputed portion—for instance, freezing the missing co-host’s 35% share while releasing the venue owner’s 55% share on schedule.

Structural Limitations and Edge Cases

The current framework is designed for digital-first operational accountability, but real-world complexity presents clear limitations.

First, off-platform expenditures remain a blind spot. If a primary host purchases physical ingredients or equipment using cash outside the WEVONE architecture, those expenses cannot be automatically factored into the escrow split unless logged and signed as a preliminary expense contract through WEVONE Tools or Mission beforehand.

Second, non-monetary contribution valuation is inherently subjective. If a co-host agrees to promote an event to 10,000 newsletter subscribers in exchange for a 20% revenue share, but fails to send the email, the software cannot measure the quality of promotional effort without explicit trackable links generated inside WEVONE. We recommend that performance-contingent co-hosting agreements use trackable affiliate referral keys rather than static percentage splits.

Finally, WEVONE Event's automated multi-signature mechanisms are currently live across standard fiat and WEVAR transactions in beta across EU markets. Multi-party tax auto-withholding for non-EU entities remains in development and requires manual reporting under current regional cross-border commerce regulations.

Co-hosting works best when trust is backed by unambiguous code. By moving permissions, financial splits, and risk allocation onto the WEVONE ledger before tickets go on sale, creators can focus on execution rather than administrative self-defense.