Use this event brief template to agree on the business objective, target audience, message, staff responsibilities, and follow-up rules before your team commits to execution. Copy the working document below, replace the bracketed fields, and have the people responsible for delivery approve the same version.
Picture a booth briefing where marketing expects product demonstrations, sales expects discovery meetings, and the technical specialist has prepared a different use case. Everyone has completed their assigned preparation. The missing piece is a shared agreement about what the event should accomplish.
A useful brief makes those disagreements visible while they’re still easy to resolve. It gives staff a reference for practical decisions: who gets a meeting, which promise they can make, what they must record, and who takes responsibility afterward.
The workflow below is a proposed operating approach. The filled example and all associated amounts, dates, targets, and deadlines are hypothetical planning inputs, not customer results or industry benchmarks.
What is an event brief?
An event brief is a shared decision document that defines an event’s purpose, audience, delivery boundaries, ownership, and success criteria. For B2B sales and marketing, it should also specify what qualifies a conversation for follow-up and how the receiving team accepts responsibility.
Keep the brief focused on decisions that affect multiple teams. Detailed production schedules, campaign tasks, and supplier instructions belong in linked documents. A reader should be able to understand the commercial purpose without searching through booth shipment details.
The event owner maintains the brief, but the people accepting its commitments must review it. Sales approves the qualification and handoff rules. Marketing approves the audience and message. Operations confirms capture readiness, while the budget approver accepts the spending boundaries.
How does an event brief differ from a marketing plan or run of show?
The brief records agreements that guide the other event documents.
Build the campaign schedule with the event marketing plan template. Put onsite sequences in the run of show template. Link both from the brief so changes have an obvious place to go.
Why agree on acceptance criteria before spending?
Acceptance criteria turn broad intentions into decisions your team can inspect.
Consider a hypothetical event with an all-in approved cost of $24,000. If the planning target is 12 sales-accepted follow-ups, the planned cost per accepted follow-up is $2,000. If only six meet the agreed definition, the actual cost becomes $4,000 per accepted follow-up, assuming spending stays unchanged.
That calculation measures an operating outcome; it does not establish financial return. For a hypothetical ROI calculation, assume finance attributes $36,000 in realized contribution before event costs to the event. Using contribution as the return basis, ROI would be ($36,000 − $24,000) ÷ $24,000 × 100 = 50%.
Both calculations depend on definitions agreed in advance. If a badge scan qualifies for one person and an accepted discovery meeting qualifies for another, the final report cannot support a consistent decision.
Write the acceptance rule before setting the target. Specify the required evidence, the person authorized to accept it, and the reporting date. Leave unresolved assumptions visible instead of replacing them with optimistic estimates.
Copy this B2B event brief template
Replace each bracketed field with an agreed decision or an explicit unresolved item. The template is deliberately platform independent: keep it in a shared document, your project workspace, or a repository where the team can identify the current approved version.
An unresolved field needs an owner, a decision deadline, and a statement of what it blocks. “Pending” alone gives the next person no instruction.
Event identity and document control
- Event name, format, location, dates, and time zone: [Details]
- Event owner and deputy: [Named people]
- Status, version, last updated, and canonical location: [Details]
- Approval record: [Approver, scope approved, version, timestamp]
- Related documents: [Marketing plan, run of show, budget, account list]
- Open decisions: [Issue, owner, deadline, blocked activity]
Purpose and acceptance criteria
- Business objective: [Specific commercial outcome]
- Primary outcome and target: [Metric, target, reporting deadline]
- Acceptance definition: [Evidence required and accepting owner]
- Supporting indicators: [Indicators that diagnose progress]
- Exclusions: [Activities or outcomes outside this brief]
- Decision after reporting: [What the results will help decide]
Audience and attendance evidence
- Priority accounts and segments: [Fit criteria and list location]
- Priority roles and business problems: [Who and why]
- Secondary audiences: [Partners, customers, other groups]
- Routing for people outside the priority audience: [Action]
- Attendance evidence: [Source, date checked, confidence status]
- Confirmation responsibility: [Owner and verification method]
Message and meeting offer
- Core message: [Audience problem and supported value statement]
- Conversation opener: [Question that tests relevance]
- Approved proof and assets: [Approved references and locations]
- Meeting offer: [Purpose, participant, format, next step]
- Claims or commitments requiring approval: [Boundaries]
Scope, spending, and cancellation rules
- Included activities and exclusions: [Agreed scope]
- Approved spending cap and budget owner: [Amount and person]
- Committed, recoverable, and avoidable costs: [Budget references]
- Readiness review and go/no-go authority: [Deadline and person]
- Cancellation or reduction triggers: [Observable conditions]
- Decision options: [Proceed, reduce, defer, cancel]
- Notification and rebooking owner: [Person and affected groups]
Staffing and responsibilities
- Event owner: [Person, authority, deputy]
- Sales owner: [Person, qualification and acceptance duties]
- Marketing owner: [Person, message and asset duties]
- Technical specialist: [Person, demo scope, escalation backup]
- Operations owner: [Person, capture checks, routing duties]
- Coverage and escalation: [Run of show reference and channel]
Contact capture schema
- Identity: [Name, company, company domain, role, contact method]
- Record links: [Existing contact/account ID and event ID]
- Interaction: [Timestamp, staff owner, attended/booked/no-show status]
- Qualification: [Audience fit, stated problem, relevant buying role]
- Evidence: [Prospect request, timing if discussed, unknowns]
- Next action: [Agreed action, receiving owner, due date]
- Communication controls: [Source, preferences, permission status]
- Routing status: [Pending, accepted, returned, or excluded]
- Required versus optional fields: [Rules and allowed values]
Handoff and exception rules
- Capture deadline: [When staff complete the record]
- Submission owner and destination: [Person and shared queue]
- Acceptance deadline and criteria: [When and what to verify]
- Return procedure: [Reason, correction owner, due date]
- Existing customer or opportunity routing: [Account owner rule]
- Missing data or unavailable owner: [Fallback and escalation]
- No-show procedure: [Reschedule, alternate contact, or close]
Measurement and review
- Metric definitions: [Numerator, denominator, exclusions]
- Sources of truth: [System or report for each metric]
- Counting rules: [Unique accounts, people, interactions, opportunities]
- Attribution policy: [Sourced/influenced rules and policy owner]
- Review dates: [Operational, pipeline, and financial checkpoints]
- Reporting owner: [Named person]
- Retrospective decision: [Repeat, modify, investigate, or stop]
Release and change log
- Readiness evidence: [Checks completed and evidence location]
- Approvals still required: [Person, decision, deadline]
- Change record: [Version, change, reason, approver, effective time]
- Staff acknowledgment: [Who must confirm material changes]
- Archived versions: [Location and superseded status]
How to turn the template into an approved working brief
Approval should confirm that people can execute the decisions in the document.
Step one: Write an outcome the receiving team can accept
Start with the behavior you want after a relevant conversation. “Build awareness” leaves staff guessing about the next action. A more usable objective names the target audience, the business issue to explore, and the follow-up that sales is prepared to own.
Separate your outcome target from your readiness checks. Sales-accepted follow-ups are an outcome. A tested capture form, an approved demonstration, and assigned coverage are readiness requirements. Passing the readiness checks permits execution; it does not guarantee the outcome.
Ask the receiving sales manager to review a sample record before approval. If the manager cannot decide whether to accept it, tighten the definition. Resolve whether timing, buying role, or a stated problem is required, optional, or legitimately unknown.
Pro Tip: Write an example of a record sales would return. Rejection examples expose ambiguous criteria faster than another sentence about quality.
Step two: Separate audience fit from attendance evidence
A company can fit your audience without having a confirmed representative at the event. Record fit and attendance evidence in separate fields so research assumptions do not become meeting commitments.
Use clear evidence labels such as historical participation, current exhibitor listing, predicted attendance, and direct confirmation. Record the source and when it was checked. A company’s exhibitor listing supports research about that company; it does not confirm that a particular decision-maker will attend.
Choose the message around the priority audience’s problem. For example, a hypothetical software team serving manufacturing operations might offer a discussion about exception handling. A generic company introduction gives booth staff less guidance about which conversations deserve a specialist.
Define a respectful route for secondary audiences as well. Partners, job seekers, suppliers, and existing customers need appropriate responses, even when their interactions do not count toward the primary outcome.
Step three: Assign responsibility at each transfer
A task owner and a receiving owner have different responsibilities. The booth representative records the conversation. Operations checks and routes the record. The receiving seller accepts the next action or returns it with a reason.
Name the person responsible for each transfer, including a deputy. “Sales team” is too broad when someone needs to resolve a missing field or a conflicting account assignment. For agency-supported events, specify which responsibilities remain with your employees.
Give the technical specialist an approved demonstration scope and an escalation route. If a prospect asks for an unsupported integration or an unapproved commercial commitment, staff should know who can answer and what they can promise in the meantime.
Pro Tip: Have the receiving owner explain the handoff back to the sender. Differences in their explanations reveal gaps before prospect records enter the queue.
Step four: Test capture and routing with an imperfect record
The capture schema should preserve enough context for the next conversation. Require identity, account context, the stated problem, the agreed action, and ownership where those details apply. Allow explicit unknown values instead of encouraging staff to invent missing information.
Keep notes factual. “Requested a technical review of approval routing” is useful evidence. “Very interested” is an interpretation that gives the receiving seller little to act on. Store communication preferences and permission status according to your organization’s applicable rules; a scan alone should not determine campaign eligibility.
Test a fictional record with a missing email address and an existing account owner. Confirm that it reaches the right person without creating an unnecessary duplicate. Then test a declined follow-up so the team can distinguish a legitimate exclusion from an incomplete record.
The event data management guide covers the wider capture-to-CRM workflow. Your brief only needs the agreed schema, routing responsibilities, and links to the operating instructions.
Step five: Approve cancellation rules and material changes
Cancellation rules need observable triggers and a named decision-maker. Missing safety requirements, unavailable essential staff, an unusable venue, or inadequate evidence of audience access can each require a different response. Specify whether the response is to pause, reduce scope, reschedule, or cancel.
Review the money still at stake. Separate spending already committed from recoverable deposits and avoidable future costs. Previously incurred spending cannot be recovered by approving additional spending; the decision should consider the remaining cost and expected value of proceeding.
After approval, treat changes to audience, offer, budget, qualification, or ownership as material. Record the change, its approver, and its effective time. Notify affected staff and require acknowledgment when the change alters what they should say or do.
Pro Tip: Put the canonical document location in meeting invitations and staff briefings. Mark old exports as superseded so a saved attachment cannot silently become the operating version.
Filled event brief example for a hypothetical B2B team
This example shows how the decisions fit together in a shortened working brief.
Everything in this example is invented for illustration. The company, event, people, budget, dates, version numbers, deadlines, targets, and financial assumptions are hypothetical. They are not recommended benchmarks or reported results.
Event identity, objective, and audience
Event: Northstar Workflow’s meeting space at the fictional Manufacturing Operations Forum, November 17–18, 2026, in Chicago. All operating deadlines use Central Time. Maya, the event marketing manager, owns the brief; Luis, the sales manager, is her deputy.
Document control: Approved version 1.0 lives in the shared event workspace. Maya owns edits. Luis approves sales commitments, Priya approves spending, and Elena approves demonstration scope. The campaign plan, run of show, budget, and target account sheet are linked from the document.
Objective: Hold useful discovery conversations with manufacturing operations teams experiencing delays in internal exception approvals. The planning target is 12 sales-accepted follow-ups by November 23. Success will inform whether the team should repeat this meeting-space format.
Acceptance definition: The record identifies a relevant account, captures a stated operational problem, and includes an agreed follow-up action with a named seller. The seller must acknowledge ownership. A scan, an unaccepted invitation, or a conversation without a next action does not qualify.
Audience: Prioritize operations directors and process improvement managers at manufacturers with multiple facilities. Route current customers to their account owners. Keep potential partners in a separate queue. The account sheet distinguishes company participation evidence from direct confirmation by a named person.
Message, offer, scope, and spending
Core message: Discuss where exception approvals stall between teams and whether a workflow review would be useful. Staff should ask how the prospect currently routes exceptions before offering a demonstration.
Approved offer: A follow-up workflow mapping session with a seller and technical specialist. The approved demonstration uses synthetic records. Staff may show the approved process but must refer questions about unverified integrations, delivery dates, or commercial terms to the responsible owner.
Scope: The team will operate a meeting space and conduct scheduled discovery conversations. A hosted dinner, broad giveaway campaign, and custom product development are outside the approved scope.
Budget: The hypothetical all-in cap is $24,000. At the readiness review, $9,000 is committed and nonrecoverable, $3,000 is refundable before the contractual deadline, and $12,000 remains avoidable. These categories are reconciled to the budget by Priya before the go/no-go decision.
Reduction rule: If fewer than six directly confirmed priority-account meetings exist at the hypothetical November 6 review, Maya and Luis reassess the format. Priya decides whether to release the refundable meeting space and reduce staffing. The threshold triggers a decision; it does not automatically establish that attendance has no value.
Cancellation rule: If the organizer cancels or the team cannot meet required safety conditions, Maya stops event activity and coordinates notifications. Luis owns prospect rebooking. Priya reviews contractual recovery options before authorizing substitute spending.
Staff responsibilities, capture, and handoffs
Responsibilities: Maya coordinates delivery and changes. Luis accepts or returns follow-up records. Elena handles technical discussions, with an approved backup specialist available remotely. Sam in operations checks required fields, matches existing accounts, and routes records. Coverage details remain in the run of show.
Capture rule: Each representative completes the record before the end of their shift. Required fields are name, company, contact method when provided, event ID, staff owner, stated problem, agreed next action, receiving owner, and communication preference status. Buying timing is optional and remains unknown unless discussed.
Illustrative record: Jordan, an operations manager at fictional Cedar Components, describes delayed approvals across facilities. Jordan requests a workflow mapping session and prefers email scheduling. The seller records that request, assigns the existing account owner, and leaves purchase timing unknown.
Handoff: Sam submits checked records by the next business morning. Luis assigns any unowned records and ensures acceptance or return within one business day. A returned record includes the missing information, the correction owner, and a due date. Records remain pending until accepted.
Exceptions: Existing opportunities return to their current owners. Duplicate contacts are matched before a new record is created. A no-show stays separate from an attended meeting; the assigned seller records whether to offer another appointment or close the event follow-up.
Measurement, release, and changes
Measurement: Maya reports booked meetings, attended meetings, and sales-accepted follow-ups separately. The account report deduplicates companies, while the contact report retains distinct people. Sam preserves the event ID and opportunity associations for later reporting under the existing attribution policy.
Review: The hypothetical operational review occurs November 23; the pipeline checkpoint occurs January 18, 2027. Finance evaluates realized contribution when the relevant business has closed. The report labels incomplete outcomes and keeps open pipeline separate from realized financial return.
Release evidence: Before approval, staff test a fictional record through capture, matching, routing, and acceptance. Elena checks the demonstration. Luis confirms receiving-owner capacity. Unresolved blockers remain visible, and Maya records whether each prevents outreach, spending, or onsite delivery.
Change example: A hypothetical version 1.1 replaces the follow-up workshop with an individual technical review after specialist availability changes. Luis and Elena approve the revised offer. Maya updates the effective time, notifies staff, and replaces the offer in outreach materials before further invitations go out.
How to check the brief before releasing it
Release the brief when the people responsible can act on its decisions.
Use this final review in order:
- Ask a seller to identify the priority audience and explain what qualifies for follow-up.
- Ask a booth representative to deliver the approved message and describe its boundaries.
- Route a fictional contact record through capture, matching, and acceptance.
- Ask the budget owner to explain the next spending decision and cancellation exposure.
- Confirm that staff can find the approved version and identify the escalation owner.
If a reviewer needs an answer that the brief does not contain, add the decision or link to its authoritative source. If reviewers disagree, resolve the disagreement before labeling the document approved. Approval should leave a usable operating agreement.
For the research behind your audience section, Lensmor’s reverse event discovery, attendee prediction, and contact enrichment can support preparation. Keep predicted attendance distinct from direct confirmation in the brief, and give each target account a clear research or outreach action.
Start with the next event already on your calendar. Copy the template, complete the objective and acceptance rule with sales, and test a sample handoff before expanding the document. That first shared decision gives the rest of the brief a practical foundation.
