Event

Co-hosting rules on Events: a practical guide

When multiple organizers share an event, liability and revenue splits usually dissolve into spreadsheets—here is how WEVONE enforces host hierarchy programmatically.

Analysis··4 min read·WEVONE Newsroom

Two organizers run a 150-person design workshop in Berlin. Host A secures the venue and sets up ticket sales. Host B manages door check-ins, runs workshop logistics, and handles live messaging. The event yields €4,500 in gross ticket sales. On legacy event platforms, Host A receives 100% of the funds into a private bank account, leaving Host B to chase manual wire transfers, while the platform treats Host B as a glorified commenter with no structural standing. If a refund dispute arises on day two, neither platform nor hosts have a clear legal log of who approved what.

Shared management without explicit multi-party architecture creates financial opacity and operational vulnerability. In WEVONE Event, co-hosting is built on explicit role-based permissions and programmatic payout logic. Rather than treating co-hosts as secondary profile tags, the platform treats them as bound signatories on an event ledger.

Permission Tiers: Primary, Co-Host, and Staff

To prevent administrative collisions, WEVONE Event categorizes organizers into three distinct operational tiers, enforced at the API level.

1. Primary Host (The Anchor)

Every event on WEVONE must have exactly one Primary Host. This entity—whether an individual or a verified company account—bears ultimate structural and legal responsibility for the listing. The Primary Host holds exclusive authority to cancel the event entirely, alter the base ticket inventory, assign or revoke co-hosts, and configure the primary payout parameters. The Primary Host's trust metrics and historical completion rates back the listing in Mia’s search ranking algorithm.

2. Co-Host (Operational Partner)

Co-hosts hold administrative rights without destructive permissions. A co-host can issue attendee updates, scan tickets at entry, moderate discussion threads, edit promotional copy, and respond to attendee inquiries. Crucially, a co-host cannot unilaterally delete the event, alter ticket pricing retroactively, or remove the Primary Host. Up to five co-hosts can be designated per event.

3. Event Staff (Check-In Only)

Designed for door managers or venue personnel, staff tokens allow ticket scanning and real-time attendee list validation through the WEVONE app without granting access to guest contact details, financial analytics, or event editing controls. Staff privileges automatically expire two hours after the scheduled end time of the event.

Financial Routing and Transactional Escrow

Revenue distribution on traditional platforms is an after-the-fact accounting headache. WEVONE solves this through its native transactional escrow engine.

When setting up a paid event, the Primary Host can establish a Split Ruleset prior to ticket publishing. If Host A and Host B agree on a 60/40 revenue split, these parameters are registered on the transaction routing agreement before the first ticket is sold.

Here is how the cash flow executes:

  1. Collection: Attendee ticket payments flow directly into WEVONE’s isolated transactional escrow account.
  2. Dispute Window: Upon event completion, a standard 24-hour dispute window opens. Attendees can lodge claims regarding non-appearance, safety violations, or severe misrepresentation.
  3. Automated Settlement: If no systemic dispute is flagged by Mia or attendees during the 24-hour window, the escrow protocol automatically dispatches payouts. €2,700 flows to Host A’s connected balance, and €1,800 flows to Host B’s connected balance—less platform infrastructure fees.

Once ticket sales go live, altering a Split Ruleset requires cryptographic sign-off from all designated co-hosts within their dashboard. A Primary Host cannot arbitrarily reduce a co-host's split percentage mid-campaign without the co-host explicitly confirming the modification.

Liability, Disputes, and the Contribution Score

Shared authority implies shared accountability, but platform enforcement must remain precise. If an event violates community standards or incurs mass refund requests, WEVONE isolates responsibility based on audit logs recorded in Mia’s context memory.

Consider an instance where an unauthorized broadcast message containing spam or offensive content is sent to 500 ticket holders. WEVONE’s activity log traces the specific authorization token that dispatched the message. If dispatched by Co-Host B, penalties—such as reductions in platform trust ratings or temporary suspension of broadcast privileges—target Co-Host B’s profile directly, rather than nuking the Primary Host’s entire historical standing, provided the Primary Host acts promptly to revoke the compromised access.

However, ultimate financial recourse for physical venue damage or cancellation defaults to the Primary Host. If an event is canceled without force majeure documentation, the refund liability is debited from the Primary Host’s account balance and overall platform contribution score.

Platform Maturity: What Is Live vs. What Is Bet

WEVONE is early, and we are deliberate about distinguishing current engineering capabilities from future roadmaps.

  • Live Today: Granular multi-host permission assignment, automated ticket scanning tokens, programmatic revenue splits via WEVONE transactional escrow, and immutable audit logging for host communications.
  • In Beta: Mia’s multi-party dispute resolution assistant, which cross-references host chat history and check-in logs during attendee refund claims to recommend fair settlement ratios.
  • Planned / A Bet: Cross-universe co-hosting contracts. We are building architecture that will allow a Nest space host (venue owner) and an Event host (organizer) to form an automated joint venture, where venue rental fees settle automatically as a percentage of real-time ticket sales directly inside escrow, eliminating upfront venue deposits.

Practical Rules for Setting Up Co-Hosting

To ensure operational clarity, hosts should follow three baseline rules when configuring multi-organizer events:

  1. Define Split Rules Before Going Public: Set up percentage splits during draft stage. Editing financial splits while tickets are actively selling requires mutual re-verification, which freezes ticket sales until all parties sign.
  2. Isolate Door Access: Do not assign full Co-Host status to temporary door staff. Issue Check-In Only staff tokens to limit privacy exposure and prevent accidental edits to event descriptions during live entry.
  3. Monitor Dispute Windows: Both Primary and Co-hosts have access to the post-event dashboard during the 24-hour settlement hold. If an issue occurs during the event, flag it inside the system immediately so Mia can pause escrow disbursement before automated routing executes.