Crypto Event Sponsor Brand-Safety Vetting Playbook 2026

About these numbers

Sponsorship cost ranges and attendee/conversion benchmarks in this post are sourced from FORKOFF operator observations across crypto conference sponsorship engagements (2025-2026), supplemented by publicly reported incident coverage from Fortune, Financial Times, Bloomberg, and PandoraTech cited inline. All figures are directional estimates; individual sponsorship economics vary by event scale and format.

The sponsor check the AI Overview is asking about right now

Type crypto event sponsor brand safety into Google on 2026-05-20 and the AI Overview triggers. The citation set is thin. Fortune coverage of the Consensus Miami (May 14 to 16, 2026) strip-club incident, Financial Times coverage of OKX reconsidering its Consensus sponsorship, Bloomberg and PandoraTech coverage of the Token2049 A7A5 sanctioned stablecoin removal. Zero operator playbooks. The sponsor-budget owner asking the question gets the news cycle but does not get the playbook for how to vet the next $50K check.

That gap is what this post fills. Two active incidents inside a 30-day rolling window crystallized the risk. Consensus Miami (May 14 to 16, 2026) wrapped at E11EVEN nightclub on May 6 2026 with pole routines, OKX told the Financial Times it would reconsider its sponsorship of the conference per Fortune's coverage. Token2049 Singapore (October 7 to 8, 2026) landed A7A5, a Russian-linked stablecoin 51% owned by US-OFAC-sanctioned Ilan Shor, on the sponsor list before organizers quietly removed it mid-event. The first is a reputation-bucket failure. The second is a sanctions-bucket failure. Both could have been caught pre-commit via OpenSanctions screening.

The playbook below is the 14-point sponsor brand-safety vetting checklist FORKOFF runs against every $50K-plus sponsor commit. Both sides. Sponsor-buyer side gets the 6 checks that scope the event before the check goes out. Event-host side gets the 5 checks that scope the sponsor before the public announce. 3 mirror checks run both sides. Each check scores against 1 of 4 risk buckets. Sanctions plus regulatory and reputation are hard-fails. Narrative and financial are negotiate-or-contract-fix.

For the CPQL economics the vetting protects, see the crypto event sponsorship CPQL playbook. Vetting decides whether a $50K commit even gets to the CPQL math. If the host-org reputation fails the 90-day scan, the CPQL is irrelevant because the check should not be written.

The active news cycle, condensed for the sponsor-budget owner

Three concurrent stories anchor the brand-safety conversation as of 2026-05-20.

Consensus Miami at E11EVEN, May 6 2026. Fortune ran the story on May 18, 2 days before this post ships. The after-party at E11EVEN nightclub coincided with the end of the Consensus conference (May 14 to 16, 2026) and featured pole routines and lap dances. OKX told the Financial Times it would reconsider its sponsorship, per the coverage on Coindesk. Consensys issued a "logo appeared, had no role" distancing statement that operator-side crisis-comms analysis rated as plausibly working. Reddit r/CryptoCurrency thread on the Fortune story carries 227 upvotes and 31 comments. The crisis-comms teardown from @Evan_Mann scored the Consensys statement against the broader sponsor pool and noted that the statement's durability depends on whether public sentiment that the E11EVEN event was inappropriate gets louder. The institutional-buyer audience (the audience the sponsors paid to reach) is the audience that drives the durability call.

Token2049 Singapore A7A5, October 2025. A7A5 is a ruble stablecoin marketed as a sanctions-evasion vehicle for Russian trade. The token is 51% owned by Ilan Shor, a US-OFAC-sanctioned individual, and backed by Promsvyazbank, blacklisted in Singapore. A7A5 landed on the Token2049 Singapore sponsor list with a booth and a massage lounge. Organizers quietly removed A7A5 mid-event after PandoraTech News and BitBlitz on X surfaced the beneficial-owner crosswalk. The "quietly removed" optics gave the story 4x the legs it would have had if A7A5 had never appeared on the deck.

Miami meltdown thread, r/dumpsterfiremarketing. The same story crossed into mainstream marketing discourse, with the marketing community noticing the strip-club narrative and the sponsor-distancing pattern. The conversation is no longer crypto-vertical only.

For the macro frame on whether the conference circuit is even worth the spend, the crypto conferences net-negative ROI debate covers the disciplined-vs-undisciplined math. Brand-safety vetting is the first input to that math, not a separate exercise.

The 4 risk buckets the vetting covers

Every brand-safety check sorts into 1 of 4 buckets. The bucket determines whether a failed check is a hard pass or a contract-fix.

Bucket 1, sanctions plus regulatory. OFAC sponsor screen, beneficial-owner traceback, host-country regulator match. Token2049 A7A5 failed this bucket on every check. Promsvyazbank is on the Singapore Monetary Authority of Singapore (MAS) blacklist, Ilan Shor is on the US-OFAC list, and the host country is Singapore. All three checks would have caught A7A5 in under 4 minutes of public-record lookup against OpenSanctions or Sanctions Scanner. This bucket is HARD-FAIL = SKIP. Any positive screen kills the commit.

Bucket 2, reputation. Last-3-events incident log, after-party venue brief, attendee composition. Consensus Miami failed this bucket on the venue brief. E11EVEN nightclub was not contractually scoped as an off-conference partner-hosted event, which is exactly the gap the sponsors used to distance themselves. This bucket is HARD-FAIL = ESCALATE. Sponsors can negotiate scope changes to clear the check, but unscoped after-parties are the canonical reputation-bucket trap.

Bucket 3, narrative. Co-sponsor crosswalk, side-event partner mix, optics review. Side events are the highest-CPQL surface in the FORKOFF Sponsor Ledger H1 2026 (n=3 clients, $231,500 spend, $457 side-event CPQL vs $1,974 booth CPQL, 4.3x spread). They are also the highest brand-safety exposure surface because the host has lighter editorial control. This bucket is WARN = NEGOTIATE. Side-event partner mix that includes a flagged sponsor triggers a re-scope of the activation, not a hard pass.

Bucket 4, financial. Payment-method screen, refund clause, deposit-funded removal. A7A5 also failed this bucket on payment-method screen, because A7A5 itself was the payment instrument the sponsor used. Sanctioned-stablecoin exposure on the sponsor treasury is the canonical financial-bucket trap. This bucket is WARN = CONTRACT-FIX. Most failed checks here close in the sponsor agreement, not at the commit gate.

Figure 3 below renders the 4 buckets as a decision stack with the gate verdict per row.

The 14-point sponsor brand-safety checklist (sponsor-buyer plus event-host)

The full checklist runs 14 rows split across the 4 buckets. 6 rows are sponsor-buyer-only, 5 are event-host-only, 3 are mirror checks both sides run. Critical-weighted rows are hard-fails. High-weighted rows are escalate-and-fix. Warn-weighted rows are contract-fix.

The 3 mirror checks deserve a closer read. Both sides run them. Both sides catch different angles on the same risk.

Row 03, last-3-events incident log. Sponsor-buyer asks the event host for the log of incidents from the last 3 events the host ran. Event-host produces the log on request, signed by ops. If the event host has no log, that itself is the answer. The buyer hard-passes on no-log events at the $50K-plus tier.

Row 05, side-event partner mix crosswalk. Sponsor-buyer pulls the public co-sponsor list and crosswalks the side-event partner mix against the buyer compliance team. Event-host runs the same crosswalk against the host editorial team before the public announce. The two views catch different flags. Buyer side catches reputation-bucket flags. Host side catches sanctions-bucket flags.

Row 06, co-sponsor crosswalk. Sponsor-buyer screens the co-sponsor list against the buyer compliance team for OFAC, MAS, FCA, DFSA flags. Event-host screens the same list against the host compliance team for the same flags. Token2049 A7A5 would have failed this check if either side had run it.

The backlash-cost scorecard, why sanctions cost 4x more than optics

Different incident types cost different amounts. The scorecard tracks 4 incident types against a 30-day cost band in qualified mentions lost across paid plus earned. Bands are P50 from the FORKOFF events team estimates 2024 to 2026.

The sanctions row is 2 to 6x the optics row because the audience that bolts is different. Optics fails (Consensus Miami E11EVEN) lose tier-2 institutional buyers and some tradfi-curious buyers, both of which can come back inside 90 days if the sponsor handles the crisis-comms cleanly. Sanctions proximity (Token2049 A7A5) loses regulated treasuries and the institutional-buyer audience hard, both of which have a 6-to-18-month re-build cycle. The sponsor pays the audience they were paying to reach, twice.

Legal-grey activity is the highest band ($500K-plus) because it pulls all audiences. Regulator action against an event partner inside the sponsor earned-media radius creates the kind of search-result snippet that locks the sponsor logo into the story for 6 to 18 months.

ROI-poisoning attendee mismatch is the lowest-cost row ($25K to $80K) because the audience that bolts is the buyer audience the sponsor was hoping to reach. Opportunity cost, not reputation cost. Most sponsors recover the brand position inside the next-cycle commit, and the durability question reduces to whether the events team rebuilds the qualification protocol for the next event in the same vertical.

r/CryptoCurrency• u/fortune

A strip club scandal at a major crypto industry event triggers sponsor backlash

Crypto firms are rushing to distance themselves from a controversial party that capped a major industry event in Miami. The shindig, which took place on May 6 and coincided with the end of the Consensus conference, took place at a well-heeled night club called E11EVEN and featured female dancers performing… Show more

227

31

Event-host side, the sponsor-vetting policy that prevents the mid-event removal

Event hosts run the same 14-point checklist mirror-flipped, plus 3 host-side-only clauses in the sponsor agreement. Sanctions screen the incoming sponsor before the public announce, not after. Token2049 caught A7A5 mid-event because the screen was reactive, not pre-commit. The resulting "quietly removed" optics gave the story 4x the legs.

The sponsor agreement carries 6 clauses that cover roughly 80% of the brand-safety surface. The clauses below are the standard FORKOFF events-team contract template for the host side, written into every sponsor agreement above $25K.

The 3 host-side-only clauses deserve a closer read.

Discretionary-removal clause keyed to public sanctions or regulatory action. The host has the discretionary right to remove a sponsor from the deck and the venue if a public sanctions or regulatory action is disclosed against the sponsor entity or its beneficial owners, with the removal funded by the sponsor deposit. Token2049 would have removed A7A5 cleanly under this clause instead of "quietly removed."

After-party scope clause (venue type, programming, photography rights). The host scopes the after-party in the sponsor agreement. Venue type, programming format, photography rights, post-event reporting SLA. Consensus did not contractually scope E11EVEN, which is exactly the gap the sponsors used to distance themselves.

Sanctions warranty from the sponsor. The sponsor represents and warrants that the sponsor entity, its beneficial owners, and its treasury are not on OFAC, MAS, FCA, or DFSA lists at the time of agreement and for the duration of the sponsor cycle. Breach voids the agreement and forfeits the deposit.

For the macro CPQL economics of the side-event vs booth decision (which the brand-safety vetting protects), see the crypto event sponsorship CPQL playbook and the 4-event sponsor decision matrix.

Evan Mann

@Evan_Mann

Quick thoughts on different crypto brands' strip club crisis comms: 1) Consensys made this statement to create distance ("our logo appeared"/"had no role") and it looks like it's working. But depending on how things evolve (like, if public sentiment that the E11even event was in… Show more

The 3 crisis-comms patterns that work, and the 1 that fails

Sponsors who skip the pre-commit vetting still have a crisis-comms surface. Three patterns work, one fails.

Pattern 1, the Consensys "logo appeared, no role" distancing statement. Works for tier-2 sponsors with thin on-the-ground presence. The AdAge and Crypto Twitter audience reads the statement as plausible. The Consensus Miami response from Consensys followed this pattern and operator-side analysis rated it as working in the first 72 hours. Durability depends on whether the public sentiment escalates.

Pattern 2, the OKX "reconsidering sponsorship" statement. Works for tier-1 sponsors with active retainers. The Financial Times audience reads the statement as values-led, signaling that the sponsor is willing to walk on principle. OKX used this pattern in the Consensus Miami cycle. The reconsider language is calibrated, the sponsor leaves room to come back, but the immediate optics protect the institutional-buyer audience.

Pattern 3, the silent withdraw plus future-event commitment. Works for tier-3 sponsors who can wait out the news cycle. No public statement. Withdraw from the current event, commit to a different event in the next cycle, let the story decay out of the timeline. Trade-off is brand goodwill with the event host, which can foreclose future co-sponsorships.

The failure pattern, the over-explain plus excuse. Extends the news cycle. Locks the sponsor logo into the search-result snippet for 6 to 18 months. The institutional-buyer audience reads the over-explain as either tone-deaf or evasive. The longer the statement, the worse the optics. The crisis-comms teardown from @Evan_Mann scored 3 sponsors against this pattern in the Consensus Miami cycle. None of them held up past 14 days.

For external operator-side conference recap and sponsor-side review content, the ETHGlobal YouTube channel is the canonical reference. Side-event activation recaps, sponsor demo content, and post-event reporting all run through that surface. The ETH NYC (June 8 to 10, 2026) cycle will carry the next live test of the brand-safety vetting playbook against an active sponsor-decision window. The ETH NYC 2026 side-events directory tracks the side-event slate and the sponsor mix as they finalize T-19.

When the brand-safety vet kills the repeat-sponsor decision

Three conditions kill the repeat-sponsor decision regardless of the underlying CPQL economics. The sponsor institutional-buyer audience (the one the sponsor was paying to reach) names the event in a public criticism post inside 30 days. The sponsor CEO or CMO is asked about the incident in a press interview, even off-the-record. The sponsor compliance team writes a memo flagging the event for the audit-committee log.

Any 2 of these 3 conditions kills the next-cycle commit. The renewal becomes a board-level conversation, not a marketing-budget conversation. FORKOFF events team escalates to founder-level on any sponsor repeat decision where 1 of these 3 conditions has fired in the prior cycle.

The three conditions sit on the FORKOFF events team audit ledger as a per-cycle row, signed by the events lead and the sponsor compliance lead, and stored alongside the sponsor file for the active cycle. The audit ledger entry runs roughly 4 sentences per condition, with the source URL or transcript reference for each signal, and the verdict (fired or did not fire) per row. Sponsors running the ledger discipline catch the second-condition fire inside 72 hours of the first, which is the operating window where the next-cycle commit decision still has optionality. Sponsors without the ledger discipline tend to surface the second-condition fire 30 to 60 days after the first, at which point the renewal calendar is already in motion and the unwind is materially more expensive.

The historic FORKOFF events team data across 17 sponsor cycles in 2024 and 2025 shows the kill-rate against the 3 conditions runs roughly 11 percent of cycles. 2 of 17 cycles fired 2 of 3 conditions and triggered the founder-level escalation. Both renewals were killed at the board layer. 1 of the 2 sponsors recommitted to a different event in the next cycle and the brand position recovered inside the 90-day window. The other moved the entire events spend to the dinner format covered in the dinner vs booth ROI breakdown and the recovery ran across 2 cycles before the institutional-buyer audience signaled the rebuild was complete. The pattern is robust across the 17-cycle dataset and the 2026 cohort to date: 2 conditions firing is the renewal-killing threshold, 1 condition firing is the contract-fix threshold, 0 conditions firing is the standard repeat-sponsor decision.

For the 67% repeat-sponsor rate benchmark vs the 30 to 40% walk-up benchmark, see the CPQL playbook. The repeat rate is the durability proof for the activation stack, and brand-safety vetting is the first input to the durability call.

The beneficial-owner traceback, step-by-step on a live sponsor entity

Beneficial-owner traceback is the single highest-leverage check in the entire 14-point playbook. The Token2049 A7A5 incident would have been caught in roughly 4 minutes of public-record lookup. The traceback runs across 3 data layers and produces a sponsor-ready memo that the compliance team signs before the check goes out.

Layer 1, registered-entity lookup. Pull the sponsor entity off the public corporate registry of the jurisdiction of incorporation. Singapore ACRA for SG entities, Companies House for UK entities, Delaware SOS for US entities, ADGM and DIFC public registries for UAE entities. The pull surfaces the registered directors, the registered shareholders above the 5% threshold, and the registered office. A7A5 was registered with Promsvyazbank disclosed on the public deck, which is the first signal a compliance team should have caught before the booth was paid for.

Layer 2, sanctions-list crosswalk. Run the entity name, the director names, and the shareholder names against OpenSanctions, Sanctions Scanner, and the OFAC SDN list. OpenSanctions runs free for non-commercial lookups and aggregates roughly 130 sanctions lists across OFAC, MAS, FCA, DFSA, EU, and UN regimes. Sanctions Scanner sits on the commercial tier and adds adverse-media plus PEP coverage. Ilan Shor sits on the OFAC SDN list with a public effective date, the crosswalk surfaces him in under 90 seconds. A positive crosswalk on any name kills the commit at the gate.

Layer 3, beneficial-owner traceback. For any entity that passes Layer 2 cleanly but sits in a jurisdiction with thin shareholder disclosure (BVI, Cayman, Seychelles), traceback the beneficial owners through the corporate registry of the parent entity. Most sanctions evasion runs through a 2 to 3 layer corporate stack with the sanctioned beneficial owner at the top. The traceback follows the ownership chain until it hits a natural person or a publicly-listed entity. Any natural person on a sanctions list at any layer kills the commit. Any publicly-listed entity gets cross-checked against the regulator-disclosed substantial-shareholder filings of that listing venue.

The full traceback runs in roughly 20 to 45 minutes for a clean entity and roughly 60 to 90 minutes for an entity with a multi-layer corporate stack. Output is a 1-page memo with the 3-layer trace, the sanctions-list crosswalk results, the gate verdict, and the signature line for the compliance lead. The memo sits in the sponsor file forever as the audit-committee artifact.

How the host-country regulator match changes the gate verdict

The host-country regulator match is the under-appreciated check in the 14-point playbook. Sponsors think OFAC is the only list that matters. The host-country regulator matters more, because the host-country regulator is the one that publishes the enforcement action that lands in the search-result snippet.

MAS Singapore. Token2049 sits in Singapore. The Monetary Authority of Singapore publishes a public investor-alert list and a financial-institution-not-licensed list. Promsvyazbank sits on the FI-not-licensed list because of the broader Russia sanctions program. Any sponsor entity tied to a Promsvyazbank shareholder or directorship triggers a MAS flag that ranks higher than an OFAC flag for a Singapore-resident event, because MAS is the regulator with active jurisdiction. The host gate verdict moves to HARD-FAIL on a MAS flag for any SG-hosted event.

FCA UK. ETHCC has a London pillar and London side-events run on the FCA financial-promotions regime. The FCA publishes a warning-list of unauthorized firms and an unregistered-crypto-firm list. Sponsors operating crypto products without FCA registration who are promoting at a UK-resident event sit on the warning list radius. The host gate verdict moves to HARD-FAIL on any sponsor on the FCA warning list for a UK-hosted event, regardless of the OFAC status.

FinCEN US. ETHConf NYC and Permissionless sit in US jurisdiction. FinCEN runs the Money Services Business registry and the 314(a) information-sharing list. Crypto sponsors operating as MSBs without FinCEN registration sit outside the regulatory perimeter and pose a contract-fix risk for a US-hosted event. The host gate verdict moves to ESCALATE on an MSB-registration gap and to HARD-FAIL on a 314(a) hit.

DFSA UAE. Token2049 Dubai, DMCC Crypto Centre events, and ADGM-hosted side events run on the DFSA and FSRA regulator perimeter. DFSA publishes a registered-firm list and a regulatory-alert list. The host gate verdict moves to HARD-FAIL on any sponsor on the DFSA regulatory-alert list for a UAE-hosted event.

The 4-regulator crosswalk runs in roughly 8 to 12 minutes per sponsor. Output is a row on the sponsor file with the regulator-status flag, the source URL, and the date of last refresh. The crosswalk refreshes monthly during the active sponsor cycle.

The 3 sponsor-side internal artifacts the compliance team expects

Sponsor-budget owners running the vetting alone produce 3 internal artifacts that the compliance team and the audit committee expect on file. The artifacts are the durability layer for the sponsor decision and the documentary defense for any post-incident audit.

Artifact 1, the sponsor-vetting memo. A 1-to-2-page memo with the 14-point checklist scored row-by-row, the 4-bucket gate verdict, and the recommended action (sign, contract-fix, hard pass). The memo is signed by the events lead and the compliance lead. Stored in the sponsor file under the event-cycle folder. The artifact is the primary audit-committee defense if a post-event incident triggers an internal review.

Artifact 2, the after-party scope statement. A 1-page statement covering the after-party venue type, the programming format, the photography rights, the post-event reporting SLA, and the sponsor-vs-host responsibility split. The statement is filed alongside the sponsor agreement and incorporated by reference. Consensus Miami sponsors who had this artifact on file used it as the source for their distancing statement and the public narrative held up. Sponsors without the artifact had no source for the distancing and the optics held them on the story for 14-plus days.

Artifact 3, the crisis-comms scope clause acknowledgment. A short clause inside the sponsor agreement (or a separate side-letter) acknowledging that the sponsor reserves the right to issue a distancing statement on the event without breach. The clause is non-disparagement carve-out language and protects the sponsor optionality during a live incident. Sponsors without the carve-out face the choice of breaching the agreement or staying silent, both of which extend the news cycle.

The 3 artifacts run alongside the sponsor agreement and produce a complete sponsor file that survives any audit-committee or board-level review. The events team produces all 3 as standard for every sponsor commit above $25K.

The post-incident reputation-rebuild stack for sponsors who skip the gate

Sponsors who skip the pre-commit vetting and land in a live incident face a 90-day reputation-rebuild window. The stack runs across 4 layers and runs roughly $40K to $120K in operator-side spend depending on the incident severity. The math is materially worse than the $4K to $6K pre-commit vetting cost.

Layer 1, the 72-hour optics protect. The first 72 hours decide the durability of the news cycle. The sponsor issues the distancing statement, the CEO or CMO does not give an unprepared press interview, the compliance team produces the OFAC-clean memo for the press team to reference. Operator-side spend runs roughly $8K to $15K on press-team time plus crisis-comms retainer.

Layer 2, the 30-day institutional-buyer outreach. The institutional-buyer audience (the audience the sponsor was paying to reach) gets a private outreach with the sponsor compliance and events leads. The outreach is not a public statement, it is a private 1-to-1 with the top-20 institutional accounts on the sponsor pipeline. Operator-side spend runs roughly $12K to $30K on senior-time across the events and compliance teams.

Layer 3, the 60-day earned-media reset. The sponsor places 2 to 4 earned-media stories on the sponsor compliance program, the OFAC screening cadence, and the post-incident vetting upgrade. The reset stories displace the incident snippet on the first page of search results for the sponsor brand plus event-name pair. Operator-side spend runs roughly $15K to $40K on PR retainer plus earned-media placement cost.

Layer 4, the 90-day repeat-sponsor decision. The sponsor either commits to a different event in the next cycle (clean break) or commits to the same event with the published vetting upgrade (recovery). Both paths work, but the recovery path requires the published vetting upgrade as the durability proof. Operator-side spend runs roughly $5K to $35K on the event-vetting program build plus the publication of the program.

Total reputation-rebuild stack runs roughly $40K to $120K against a pre-commit vetting cost of $4K to $6K. The math is binary. Sponsors who skip the gate pay 10x to 20x the vetting cost on the rebuild.

The 5-step pre-commit gate FORKOFF runs before signing any sponsor retainer

Step 1, OFAC + MAS + FCA + DFSA screen against the sponsor entity and the top-5 co-sponsors on the public list. Under 4 minutes of public-record lookup. Any positive screen, hard pass.

Step 2, last-3-events incident log request from the event host. No log shared, hard pass. Log shared and clean, proceed. Log shared and flagged, escalate to bucket-2 reputation review.

Step 3, after-party venue brief and side-event partner mix crosswalk. Venue type plus programming format. Side-event partner mix against the buyer compliance team. Any flag, contract-fix in the sponsor agreement scope clause.

Step 4, sponsor agreement clause review. The 6 must-have clauses above. Any clause missing, contract-fix before commit. The agreement is the durability layer for everything that happens after the check goes out.

Step 5, gate decision. Buckets 1 and 2 clean, buckets 3 and 4 contract-fixed, sign the retainer. Any bucket-1 or bucket-2 flag unresolved, do not sign. The math is binary at the gate.

The 5 steps take roughly 6 to 8 hours of work for a $50K-plus sponsor commit. That is roughly $4K to $6K of opportunity cost against a $200K to $500K reputation-cost band on a sanctions-bucket failure. The vetting pays for itself on the first prevented incident, and most cohorts run roughly 1 prevented incident per 8 sponsor commits in the active 2026 news cycle.

For the format-side decision the brand-safety vet sits on top of, the dinner vs booth ROI breakdown shows where vetting matters most. Sponsored dinners run the highest pre-commit ICP qualification work and the lowest brand-safety surface. Booth-only sponsorships run the lowest pre-commit work and the highest brand-safety exposure, which is the inverse of the CPQL economics. Both the sponsor-buyer and the event-host books should rank vetting against the format being signed.

The brand-safety vetting playbook is now standard on every FORKOFF events retainer, sponsor-buyer side and event-host side. The 14-point checklist, the 4-bucket gate, the 6-clause sponsor agreement, the 5-step pre-commit, all run before any CPQL conversation. Vetting is the first input to the math, not a separate exercise.