Vantly Get a custom quote

How to Brief a Local Event Designer (So They Can Actually Tailor Your Offsite)

By the Vantly team · Research checked October 2026

"Find us somewhere nice for 25 people in the spring" gets you a list of rooms. A one-page brief gets you a plan. The difference is ten fields: the purpose of the offsite, headcount and the private-room rule, dates and flexibility, a budget band, must-haves vs nice-to-haves, dietary and accessibility needs, the privacy level, the WiFi and AV bar, transport from the office or airport, and what you keep in-house. Fill those in, even roughly, and a local event designer can tailor a real quote on the first pass instead of guessing. Below: what to write in each field, why it changes the quote, and a copy-ready template.

Get a custom quoteSee sample events
An overhead view of a workspace with planning materials.
Photo: Mikhail Nilov / Pexels

"Find us somewhere nice for 25 people in the spring" gets you a list of rooms. A one-page brief gets you a plan. The difference is ten fields: the purpose of the offsite, headcount and the private-room rule, dates and flexibility, a budget band, must-haves vs nice-to-haves, dietary and accessibility needs, the privacy level, the WiFi and AV bar, transport from the office or airport, and what you keep in-house. Fill those in, even roughly, and a local event designer can tailor a real quote on the first pass instead of guessing.

Below: what to write in each field, why it changes the quote, and a copy-ready template.

Why the brief decides the quote

A tailor-made event is built from your inputs. Vague inputs force a choice between generic options and a long round of questions. Either way, weeks go by.

The pattern assistants and founders describe when they compare notes on offsite planning goes like this:

  • The ask goes out with a headcount and a month, nothing else.
  • Options come back that look good but miss something basic, like private bedrooms or a meeting room big enough for everyone.
  • The budget was never shared, so half the options are out of range.
  • A privacy requirement (the CEO wants no other guests on site) surfaces after a favorite has been picked.
  • The process restarts.

None of that is anyone's fault. A designer cannot plan around a constraint they do not know about. A good local designer also fills gaps you did not know existed, like which inns share their breakfast room with weekend guests. That local knowledge works best when it is pointed at a clear brief.

The good news: you do not need a polished RFP. One page, written in plain sentences, is enough.

The one-page brief: ten fields

Here are the ten fields, with one line on what to write for each. Copy them into a doc or an email and fill them in.

  • Purpose. Why are you getting together, and what should be true when people leave? (Strategy reset, team bonding, board meeting, kickoff, celebration.)
  • Headcount and room rule. How many people, how sure you are, and whether everyone needs a private bedroom.
  • Dates and flexibility. Preferred dates, acceptable alternatives, and days of the week you cannot do.
  • Budget band. A range you can live with, labeled as an estimate, and what it is meant to cover.
  • Must-haves vs nice-to-haves. The few things that are non-negotiable, kept apart from the wish list.
  • Dietary and accessibility. Known allergies, dietary patterns, mobility needs, and anyone who needs a step-free room.
  • Privacy level. Whether other guests on the property are fine, or you need the whole place.
  • WiFi and AV bar. What the working sessions require: video calls, presentations, breakouts, recording.
  • Transport. Where people are coming from (HQ, an airport, several cities) and how you would like them to arrive.
  • What you keep in-house. The agenda, facilitation, attendee comms, or anything else your team owns.

If you only have time for half of these, prioritize purpose, headcount, dates, budget band and privacy. Those five shape the shortlist more than anything else.

Below are the fields that cause the most back-and-forth.

Headcount and the private-room rule

Headcount sounds simple. It is the field most likely to break a plan.

Count keys, not mattresses. A listing's "sleeps" number often counts bunks, sofa beds and shared beds. Corporate teams usually expect one person per private bedroom with a real door. Tell the designer which you need, in so many words: "Everyone gets their own bedroom; no shared beds." A designer working to that rule will count bedrooms from the floor plan rather than trusting the headline number.

Say who needs single occupancy. If some people can share and others cannot (leadership, board members, anyone who has asked), list that.

Give a range. "22 confirmed, up to 26" is far more useful than "about 25." It shows the designer what happens if the group grows.

Remember there are three capacities. Sleeping, working in the main meeting room, and eating together at one sitting are rarely the same number. Say whether the whole group must fit in one room and at one table; if so, the smallest number is your real limit.

Dates, flexibility and budget band

Dates

Give your preferred dates and your real alternatives. "The week of May 11, Tuesday to Thursday, or the following week" opens up far more options than a single fixed pair of days. If certain days are impossible (a board meeting, a product launch, a holiday that matters to your team), say so up front.

Flexibility is one of the most useful things you can offer a designer. A property booked on your first choice may be open two days later. You just need to say how flexible you can be.

Budget band

Should you share your budget? Yes. Hiding it rarely gets you a better price; it usually gets you options you cannot approve.

You do not need an exact number. A band works:

  • Write it as a range and label it an estimate. For example, "Our working estimate is [low] to [high] for the whole event, pending Finance sign-off."
  • Say what it covers. Lodging, meals, meeting space, activities, transport, AV? Per person or total? Including or excluding taxes and service charges?
  • Say who approves it. If Finance or a leadership sponsor needs to see the quote, mention it, so the quote comes back in a shape they can review.

We are not suggesting a number here, because the right band depends on your destination, dates, headcount and inclusions. A designer who knows the area will tell you plainly what your band can and cannot buy. For more on building the number with Finance, see our guide on leadership retreat budgets.

Must-haves vs nice-to-haves

The fastest way to slow down a quote is a list of twenty requirements, all marked important. Separate the few things you truly cannot do without from everything you would enjoy.

A must-have would make you reject a plan outright. A nice-to-have is something you would trade for budget, location or dates.

Here is an example of how a brief might mark them.

Item | Must or nice | Why

Private bedroom for every attendee | Must | Leadership group; no shared beds

One meeting room that seats the whole group | Must | Daily plenary sessions

Reliable WiFi for video calls from the meeting room | Must | Two remote presenters

Step-free room and access to meeting and dining spaces | Must | One attendee uses a mobility aid

Whole group at one dinner table | Nice | Preferred for the first night, not required

Outdoor space for a team activity | Nice | Would be used if weather allows

Within a short drive of the office | Nice | Can trade for a better property

Hot tub or spa | Nice | Popular, but not a deciding factor

Keep the must-have list short; if everything is a must, nothing is. And explain the "why": "Must: private bedrooms, because this is a board group" tells the designer something about the whole event.

Privacy, AV and transport bar

Late surprises usually come from these fields. A sentence on each saves rework.

Privacy: whole house or a room block?

Be explicit about whether other guests on the property are acceptable. There is a real difference between:

  • Full-house exclusive (a true buyout): your group has the whole property; no other guests.
  • A minimum room commitment: you guarantee a number of rooms, often to keep the meeting space, but the venue may still have other guests.
  • A soft or best-effort room block: rooms are held for you until a release date, while the property operates normally around you.

If your agenda involves board matters, sensitive personnel topics or recognizable leaders, say "we need exclusive use; no other guests on site." If shared spaces are fine, say that too; it widens the options. Our guide on true buyout vs soft room block goes deeper.

WiFi and AV

"Good WiFi" means different things to a quiet strategy session and a workshop with remote presenters dialing in. Describe what you will actually do: how many people on laptops at once, whether anyone presents or joins by video, whether you need screens, microphones, breakout rooms or a wired presenter connection, and whether a backup connection matters. A designer can then check bandwidth in the meeting room itself and plan a fallback. Our guide on how to check venue WiFi for corporate offsites lists the questions in detail.

Transport

Say where people start (one office in Midtown Manhattan, an airport, several cities), whether you want everyone to travel together or drive and use rideshare, any late arrivals, and any equipment that needs space. A designer who knows the destination can tell you realistic door-to-door times and whether a shared vehicle beats a convoy. See our guide on group transport for company offsites.

Dietary and accessibility

Put these in the first brief, not the week before. Known allergies, dietary patterns (vegetarian, vegan, kosher, halal, gluten-free), and accessibility needs (step-free rooms, ground-floor bedrooms, quiet spaces) all affect which properties and dining models work. You do not need names yet; counts and needs are enough at this stage.

Also say how you would like to eat: a house restaurant, a private chef, dinners in town, or a mix. Not every property can host a private chef, so an early preference prevents a mismatch.

What you keep in-house

A brief is also a division of labor. Say clearly what your team owns, so the designer plans around it instead of duplicating it.

Usually kept in-house: the purpose and agenda (you know your strategy; the designer builds the setting around it), facilitation and session content, attendee communications such as invitations and the "why we're doing this" note, and internal approvals from Finance, leadership or HR.

Usually handed to the designer: venue selection and terms, catering and the dining plan, local vendors (activities, AV hire, photography, transport), and on-the-ground logistics and timing.

If you want help with agenda flow or an activity tied to a goal, put it in the brief. The point is that nothing falls into the gap between two teams who each thought the other had it.

A copy-ready brief template

Paste this into an email or doc and fill in the brackets.

Offsite brief: [Team / event name]

Purpose: [Why we are meeting and what should be true when we leave.]

Headcount: [Confirmed number], up to [maximum]. [Everyone needs a private bedroom / these people can share.]

Dates: [Preferred dates]. Alternatives: [options]. Cannot do: [dates or days].

Budget band (estimate): [Low] to [high], covering [what is included]. Approved by [Finance / sponsor].

Must-haves: [Three to five items, each with a reason.]

Nice-to-haves: [Wish list.]

Dietary and accessibility: [Counts and needs.]

Privacy: [Exclusive use needed / other guests fine.]

WiFi and AV: [How sessions will run: laptops, video, screens, breakouts.]

Transport: [Starting points, preferred way to travel, late arrivals.]

We keep in-house: [Agenda, facilitation, comms, approvals.]

Decision timeline: [When we need options, and who decides.]

The last line is optional, but it lets the designer pace the work to your calendar.

Where a local event designer comes in

A brief like this is exactly what Vantly is set up to receive. We pair company teams with independent local event planners who know their destination first-hand: which properties really have private bedrooms for everyone, which meeting rooms hold up under a full day of video calls, and how long the drive takes when everyone leaves the office at once. They read your brief, ask the few questions it does not answer, and design the event around your group rather than handing you a catalog. Our intent is that you work with one point of contact and receive one invoice for the event, instead of coordinating the venue, the caterer and the transport separately. We started in the New York region, so that is where our planner network is deepest today.

If you want a sense of what a designer can build before you write your own brief, see sample events. They are examples a local designer tailors to your group, not fixed packages.

Once your designer sends a quote back, the next step is reading it well. Our companion guide on what to ask in a custom event quote covers inclusions, options and terms.

Frequently asked questions

What should an event brief include?

A useful event brief covers ten things: the purpose, headcount and whether everyone needs a private bedroom, dates and flexibility, a budget band, must-haves and nice-to-haves, dietary and accessibility needs, privacy level, the WiFi and AV bar, transport, and what your team keeps in-house. One page is enough.

How much detail does an event designer need to quote?

Enough to rule properties in or out. Purpose, a headcount range, flexible dates, a budget band and your privacy requirement shape most of the shortlist. The other fields refine it. Plain sentences work better than a long spreadsheet, and a designer will follow up on anything that is unclear.

Should I share my budget with an event designer?

Yes. Share a range, label it an estimate, and say what it should cover and who approves it. Without a budget, a designer has to guess, and quotes often come back out of range. A band lets them show you the best options for what you can actually spend.

What is the difference between must-haves and nice-to-haves?

A must-have is something that would make you reject a plan outright, such as private bedrooms for every attendee or a meeting room that fits the whole group. A nice-to-have is something you would trade for budget, dates or location. Keep the must-have list short and explain why each item matters.

What should stay in-house when you work with an event designer?

Most teams keep the purpose, the agenda, facilitation, attendee communications and internal approvals. The designer typically handles the venue, catering, local vendors, transport and on-the-ground logistics. Write the split into your brief so nothing falls between the two.

How specific should I be about headcount and rooms?

Give a confirmed number, a maximum, and your room rule, for example "everyone gets their own bedroom." Note who needs single occupancy and whether the group must fit in one meeting room and at one dinner table. Sleeping, meeting and dining capacity are different numbers at most properties.

Send it

A rough one-page brief with the ten fields filled in beats a polished request that leaves out the budget or the privacy rule. Send what you have, and let a local event designer who knows the destination tailor the rest. Get a custom quote

Sources