How to write a hotel RFP for small meetings

If you're sourcing a 30-person sales offsite, a quarterly leadership meeting, or a one-day client workshop, you've probably noticed something frustrating. Most RFP advice out there was written for 500-person conferences. So you either over-engineer a 40-question RFP for a meeting that needs a boardroom and lunch, or you fire off a three-line email and end up chasing hotels for the details you forgot to ask for.

There's a better way to write a hotel RFP for small meetings. It's tight enough to respect a sales team's inbox, specific enough to get apples-to-apples bids, and clear enough that a hotel can quote it the same day.

This matters more than ever. Small-meeting RFPs (under 100 attendees) now make up a large and growing share of the volume flowing through the Cvent Supplier Network, and the majority of European RFPs are for groups of 100 or fewer. 1.95M small-meeting RFPs via CSN in 2024; 79% of European RFPs for groups of 100 or fewer. Hotel sales teams are fielding more small-meeting bids than ever, which means yours has to stand out for the right reasons, not because it's confusing. This guide walks through exactly what to include, what to cut, how to phrase it, and how to send it so you get strong proposals back fast.

What counts as a "small meeting," and why the RFP looks different

There's no single industry definition, but most planners and hotels treat a small meeting as one with fewer than 100 attendees, one to three meeting rooms, and a short agenda. The defining trait isn't really the attendee count. It's the complexity. A small meeting usually has:

• A short, predictable agenda (one or two days)
• Limited event space needs (boardroom, U-shape, or classroom for 20 to 75)
• A modest room block, sometimes none at all
• Standard F&B (breakfast, breaks, working lunch)
• Few or no production requirements

That changes how you write the RFP. A 40-page document with detailed concession menus and 12 custom questions is overkill, and worse, it slows the hotel's response. Sales teams triage by clarity and effort. The RFPs that get same-day attention are the ones that look easy to quote.

A small-meeting RFP should feel closer to a one-page brief than a procurement document: specific, scannable, and stripped to what actually drives the bid.

Why a tight, well-written RFP wins better small-meeting proposals

When sales managers open an RFP, they're making a quick judgment. Is this real, is it qualified, and how long will it take to respond? The RFPs that earn a thoughtful, competitive bid signal three things in the first 30 seconds: a real budget, a clear timeline, and a planner who knows what they want.

Two practical reasons this matters even more for small meetings.

First, hotels are busy with bigger files. Your 25-room, two-day meeting is competing for a sales manager's attention against a 600-room citywide. A vague or sprawling RFP sinks to the bottom of the stack. The CSN sourcing best practices put it plainly: include only the detail you actually need, and respect the hotel's time on response windows. The standard guidance runs from a minimum of 48 to 72 hours up to about two weeks. Anything tighter needs context.

Second, AI is now in the loop on both sides. Planners are already using AI in sourcing and plan to increase it, and hotels are using AI-assisted response tools too. Structured, specific RFPs feed both systems better. Vague phrasing like "small meeting space needed" gets matched poorly. Clear inputs (peak rooms, set type, dates, budget signals) match accurately and surface stronger options.

A well-written small-meeting RFP isn't longer, it's sharper. Every line earns its place.

What to gather before you start writing

The biggest reason small-meeting RFPs go out half-formed is that planners sit down to write before they've answered the basic questions. Five minutes of prep saves an hour of back-and-forth later.

Before you open the template, pin down these eight things.

The non-negotiables. What absolutely has to be true for a hotel to be a fit? Geography (specific city, neighborhood, or radius from an office or airport), brand standards if your company has them, accessibility requirements, and any sustainability or supplier-diversity criteria. These are your filters, not your nice-to-haves.

Your dates and flexibility. Are dates fixed, or do you have a primary plus one or two alternates? Even one alternate window can change the bids you get back, especially in compressed markets. If you can flex by a week, say so. It gives revenue managers room to find better rates.

Peak room nights. This is the single most important number for hotels with sleeping rooms. Peak is the highest single-night room count, not the total cumulative nights. A 25-person meeting with a one-night stay has 25 peak rooms. A two-night stay has 25 cumulative peak room nights across two nights. Hotels quote off peak.

Meeting space requirements by day. Number of rooms, set type (boardroom, U-shape, classroom, theater, hollow square), and capacity needed. If you need the same room across multiple days with an overnight hold, note it. That's billable space the hotel needs to block.

Food and beverage estimate. You don't need a final menu. You need an order-of-magnitude number: continental breakfast, two coffee breaks, plated lunch for 40, networking reception for 50. Hotels build minimums and concessions around F&B spend, so giving them a realistic shape helps.

Budget signals. You don't have to disclose your full budget, but indicate a target ADR or preferred range, whether you have a not-to-exceed total spend, and whether your organization requires a specific contract type or payment method. Procurement-driven planners often skip this, then watch quotes come back well above what they can approve.

Decision timeline. When you'll review proposals, when you'll shortlist, when you'll make a final decision, and when the contract needs to be signed. Hotels prioritize files with clear timelines because they signal a real booking, not a price check.

Stakeholders and approvals. Who needs to sign off: finance, legal, the executive sponsor, the meeting owner? Knowing this up front lets you set realistic response windows and contracting timelines.

If you can answer those eight things in writing before you start the RFP, the document almost writes itself.

The core sections every small-meeting hotel RFP should include

A small-meeting hotel RFP should fit comfortably on two to three pages. Here's the structure that consistently produces strong, comparable bids, followed by a table of the specific fields hotels need to see.

1. Event overview. Two or three sentences. What the meeting is, who's attending, and the goal. For example: "Annual sales kickoff for 45 regional account executives. Two-day working session with leadership presentations and team breakouts. Goal: align on FY26 territories and product launches." Sales managers read this first to qualify the file. The CSN best-practice guidance on this is direct: personalize the RFP narrative. Explain event goals, attendee profile, and must-haves versus nice-to-haves, because detailed RFPs typically get stronger, more tailored proposals.

2. Key event details. Dates (primary and alternates), arrival and departure pattern, attendee count, decision-maker, and contracting timeline. This is the qualification block, so keep it scannable.

3. Sleeping room block. Peak rooms by night, room type mix (single vs. double occupancy, suites if needed), check-in/check-out pattern, and your target ADR or rate cap. If there's no room block, say so explicitly: "meeting space only, no sleeping rooms required." Hotels price meeting-space-only files differently, and being upfront avoids confusion.

4. Meeting space requirements. Day-by-day breakdown: room name or function (general session, breakout 1, meal function), set type, capacity, hours needed, and whether you need a 24-hour hold. A small table here makes it easy for the hotel to map your needs to their inventory.

5. Food and beverage. By day and by function: breakfast type, AM break, lunch style, PM break, dinner or reception. Note dietary restrictions you already know about. If you have a per-person F&B target, share it.

6. Audiovisual and tech. Most small meetings need basic A/V: one projector or large display, screen, podium mic, and Wi-Fi. Specify what you'll bring versus what you need the hotel (or in-house A/V provider) to supply. Note if you need recording, hybrid streaming, or simultaneous translation, since those carry significant cost.

7. Concessions and value-adds. Be specific and reasonable. Common asks for small meetings include complimentary meeting room rental with an F&B minimum, complimentary Wi-Fi in meeting space, one comp room per X actualized, discounted self-parking, late checkout for VIPs, and waived resort fees. Don't list every concession in the book. Pick three or four that genuinely matter.

8. Contracting requirements. Attrition allowance you expect, cancellation terms your company requires, force majeure language, deposit schedule, and any required vendor compliance documents (W-9, COI, sustainability disclosure). If your legal team requires your paper, say so up front.

9. Custom questions (only if needed). A few targeted questions can sharpen bids: recent renovations, sustainability certifications, group amenity options, any current promotions. The CSN guidance is to add custom questions for the nuances the standard form doesn't cover, but not to overload venues with extras. Include only the must-haves.

10. Response instructions. Response due date and time (with time zone), preferred format, who to send proposals to, and how questions during the bid period should be directed. End with a thank-you and a one-line note about how and when shortlisting will happen.

Quick reference: what each section needs

Writing tips that get faster, more competitive bids

The structure above gets you a complete RFP. These habits get you a competitive one.

Lead with what qualifies the file. Sales managers scan the first half-page to decide whether to invest 30 minutes building a proposal. Put dates, peak rooms, attendee count, and decision date near the top. Even if your overview comes first stylistically, the hard numbers should be visible without scrolling.

Be specific about set type, not just capacity. "Room for 40" can mean a boardroom, U-shape, or classroom. Those are three very different rooms with different rental rates. Specify the set, and the hotel will quote the right space the first time.

Distinguish must-haves from preferences. A simple "Required" versus "Preferred" tag next to each ask saves multiple rounds of back-and-forth. Hotels can stretch on preferences if they have to win the must-haves. Without that signal, they assume everything is required and either overprice or pass.

Give a real budget signal. You don't have to share your full budget. A target ADR range, a not-to-exceed total, or even "comparable to last year's spend at [chain]" anchors the proposal in reality. Files with no budget signal often get the highest opening rates because the hotel has nothing to negotiate against.

Write the F&B section like a planner, not a procurement form. "Hot breakfast buffet, two breaks with coffee and snacks, plated lunch with three protein options, networking reception with passed appetizers and two-hour open bar" gets a cleaner quote than a blank "F&B as needed." If you genuinely don't know yet, say so, and give a per-person target so the hotel can build a realistic minimum.

Set a response window that respects the hotel's process. The recommended floor is 48 to 72 hours minimum, with a maximum of about two weeks. If you need a 24-hour turnaround for a last-minute meeting, explain why and note that you're making a fast decision. Tight windows without context get deprioritized. Tight windows with context get respected.

Use plain language, not procurement-speak. Contractions are fine. So is a friendly closing line. The hotel sales manager is a human reading dozens of files a day, and a clearly written RFP from a planner who sounds reasonable gets a better proposal than a stiff document that reads like a legal pleading.

Personalize the narrative when it helps. If this is your fifth meeting with a brand and the team knows you, a single line earns goodwill and often surfaces stronger concessions: "We've worked with three properties in the [Brand] portfolio over the past year and would love to consider this property next."

Avoid the everything-bagel approach to concessions. Asking for 12 concessions on a 25-room meeting signals that you're shopping, not booking. Pick three or four that genuinely matter (waived meeting room rental, comp Wi-Fi, late checkout, parking discount) and let the rest be negotiable in contracting.

Tell the hotel how you'll decide. A quick sentence moves the file up the queue: "We'll shortlist by [date], conduct site visits the following week, and award by [date]." Hotels work harder for opportunities that have a real path to contract.

Mistakes that kill small-meeting RFPs

Most weak proposals trace back to a small set of avoidable problems. Here are the ones that come up over and over.

Sending to too many hotels. Volume doesn't equal options. It equals lower-quality bids and irritated sales managers. The CSN best-practice guidance is unambiguous: shortlist smartly, not widely. Aim for a curated set of well-qualified venues per RFP rather than blasting a long list. Sending RFPs to dozens of hotels at once is poor practice and often signals that the planner is struggling to find the right venues. For a small meeting, six to ten qualified hotels is the sweet spot.

Asking too many questions. A 30-question custom section on a 40-person meeting tells a sales team the file isn't worth the time. Add custom questions only for nuances the standard form doesn't cover, and keep them to the must-haves.

Confusing peak rooms with total room nights. This is the most common technical mistake in small-meeting RFPs, and it produces inflated rate quotes. Peak is your highest single-night count. Total is the sum across all nights. Hotels build proposals off peak. Get this wrong and every comparison you do afterward is off.

Skipping the budget signal. No budget signal means the hotel has no anchor. You'll get a wide spread of rates, mostly higher than necessary, and you'll spend rounds on negotiation that a single line of guidance could have avoided.

Vague meeting space asks. "We need a meeting room for 40" without set type, hours, or hold pattern forces the hotel to guess, and they'll guess in their favor. Specify the set, the hours, and whether you need an overnight hold.

Forgetting the decision timeline. RFPs without a clear decision date sit in the "follow up later" pile. Hotels triage by certainty, and certainty starts with a date.

Unrealistic response windows. A 24-hour turnaround on a small file with no explanation tells the hotel either you don't understand their process or you're not a serious buyer. Hotels can't realistically respond to every RFP in 24 to 48 hours. Best practice is a 48-to-72-hour minimum and a two-week maximum. 

Bypassing your chain contacts. If your company has relationships with NSO/GSO contacts at major brands, looping them in usually gets you faster, better-priced responses across the brand's portfolio. The planner guidance is to use your NSOs, not bypass them. Add them as recipients when it makes sense.

Treating small meetings like one-offs instead of a program. If you run dozens of small meetings a year, sourcing them ad hoc by email costs you. Centralizing them gives you negotiating leverage, better data on total meeting spend, and consistency across your team. Even smaller meetings benefit from centralized sourcing through standardized RFPs, time savings, and better visibility into total meeting spend.

A sample small-meeting hotel RFP template you can copy

Use this as your working draft. Drop it into a Word doc or your sourcing tool, swap in your details, and you'll have a clean, scannable RFP a hotel sales team can quote the same day.

[COMPANY NAME] — Hotel RFP: [Meeting Name]

Submitted by: [Your name, title, email, phone]

Response due: [Date and time, with time zone]

Send proposals to: [Email]

1. Event overview

[2 to 3 sentences. What the meeting is, who's attending, the goal. Example: "Q2 leadership offsite for 35 senior leaders. Two-day working session focused on FY26 planning and team alignment. Attendees travel in from across North America."]

2. Key event details

3. Sleeping room block

• Peak rooms: [Number] on [night]
• Pattern: [e.g., 25 rooms Sun arrival, 30 rooms Mon, 30 rooms Tue, 5 rooms Wed]
• Occupancy: [e.g., all single, or X singles / Y doubles]
• Suites: [If needed, specify number and type]
• Target ADR: [Range or cap]
• Or: "Meeting space only, no sleeping rooms required"

4. Meeting space requirements

5. Food and beverage

Dietary notes: [Vegetarian, gluten-free, allergy considerations]

6. Audiovisual and tech

• Required from venue or in-house A/V: [Projector + screen, lavalier mic, podium mic, Wi-Fi for 35]
• Bringing onsite: [Laptops, clickers, recording equipment]
• Hybrid/streaming needs: [None, or specify]

7. Concessions requested

1. Complimentary meeting room rental with F&B minimum met
2. Complimentary Wi-Fi in meeting space and guest rooms
3. One complimentary room per [X] actualized
4. Discounted self-parking or complimentary parking for day attendees
5. [Any one additional priority: late checkout, waived resort fee, etc.]

Mark each: Required or Preferred

8. Contracting requirements

• Attrition allowance: [%]
• Cancellation: [Sliding scale, or company standard]
• Force majeure: [Standard or company language required]
• Deposit schedule: [Specify or "TBD per company terms"]
• Required documents: [W-9, COI, sustainability disclosure, etc.]
• Contract: [Hotel paper acceptable, or company paper required]

9. Custom questions (keep to 3 to 5)

• What renovations have been completed in the past 24 months?
• Do you have any current group amenity packages or promotions?
• What sustainability certifications does the property hold?
• [Add only if it changes your decision]

10. Response instructions

Please submit proposals by [date and time, time zone] to [email]. Direct any questions during the bid period to [contact]. We'll shortlist by [date], conduct site visits or virtual tours the following week, and award by [date]. Thank you for your time and interest. We look forward to your proposal.

How to send and shortlist

Writing the RFP is half the job. How you send it and manage responses determines how good the bids actually get.

Build your shortlist before you send. Use filters (capacity, location, brand standards, sustainability, ratings) to narrow the field to event venues that genuinely fit before you add anyone to the RFP. The CSN best-practice guidance is to apply filters before you send, so you build a curated list of venues that actually fit your requirements. For a small meeting, six to ten qualified properties is plenty.

Loop in your NSO/GSO contacts when relevant. If you have a relationship with a chain's national sales office, copy them on RFPs going to multiple properties in the brand. They'll often surface options you didn't think of and accelerate the response from each property.

Set realistic milestones in writing. Send date, response due date, shortlist date, site visit window, decision date. Hotels work harder when the path to contract is clear.

Compare bids on the same metrics. Build a simple comparison grid: ADR, total rooms revenue, F&B minimum, meeting room rental, total concession value, and one or two factors specific to your meeting (location convenience, brand fit, sustainability). Apples-to-apples comparison is hard if your RFP wasn't structured, which is why the template above matters.

Decline politely and quickly. Hotels remember planners who close the loop. A short "thank you, we've gone in another direction" message keeps the relationship warm for next time.

Track patterns over time. If you run small meetings regularly, run sourcing and bid-comparison reports to spot which markets, brands, and concession asks consistently produce the strongest bids. Use those reports to tell your sourcing story: track savings, response rates, and award patterns to justify venue choices and budgets.

Sourcing event venues in specific cities

The RFP structure above works anywhere, but the city you choose shapes your peak-room math, your budget signal, and how far ahead you need to send. A few notes on popular US markets for small meetings, plus how to start your venue search in each. When you begin, filter for real fits first, then send your RFP to a shortlist of event venues rather than blasting the whole market.

Event venues in Orlando. 

Orlando is built for groups, so even a 40-person meeting has deep options across convention-district hotels, resorts, and independent event spaces. Rates soften outside peak convention weeks, so a flexible date window pays off here. If your attendees are extending the trip, a short line pointing them to a travel guide for Orlando (theme parks, dining, airport transfers) is a nice touch.

Event venues in New York. 

New York runs tight on space and high on rate, so your budget signal matters more than almost anywhere else. Be precise about set type and peak rooms, and give hotels a realistic ADR range up front. Boutique properties and restaurant venues in New York can be strong picks for a 20-to-50-person dinner or reception when a full ballroom isn't needed. 

Event venues in Dallas. 

Dallas offers strong value for small meetings, with a wide spread of full-service hotels and conference space at rates that usually beat the coasts. Central location and easy air access make it a favorite for teams flying in from across the country.

Event venues in Denver. 

Denver works well for Outdoorsy offsites and leadership retreats, with walkable downtown hotels and mountain-adjacent resorts within easy reach. Seasonality matters, so flag your date flexibility. If people are visiting Denver for the first time, a quick travel guide for Denver covering altitude, weather, and getting around is genuinely useful.

Event venues in San Antonio. 

San Antonio pairs affordability with a walkable River Walk that keeps attendees close to dinner and downtime. It's a strong pick when you want a compact footprint and easy evening options near the hotel. Restaurant venues in San Antonio along the River Walk handle small receptions well.

Event venues in Las Vegas. 

Las Vegas has the widest range of event space per square mile of any US market, from intimate boardrooms to resort meeting floors, often at surprisingly competitive rates midweek. Peak-room pricing swings hard around big cities, so alternate dates are worth listing. For attendees visiting Las Vegas beyond the meeting, a light travel guide for Las Vegas (shows, dining, getting around the Strip) rounds out the invite. 

To narrow any of these markets fast, the Cvent toplist of top meeting hotels and destinations is a good starting point for spotting well-qualified properties before you build your RFP shortlist.

Tools that take the busywork out of small-meeting sourcing

For a one-off small meeting, a Word doc and email work fine. For a program of small meetings (quarterly leadership offsites, monthly client workshops, repeatable field events), that approach starts costing you in time, data, and missed savings.

The Cvent Supplier Network lets you send your RFP to multiple hotels at once and brings the bids back into a comparable format. It also gives you reporting on total meeting spend, response rates, and award patterns across the program, the kind of data that's almost impossible to pull together from email threads.

The point isn't the tool, it's getting your time back. A small-meeting RFP shouldn't take half a day to write and another half-day to compare bids on.

Final checklist before you hit send

Run through this in 60 seconds before any small-meeting RFP goes out.

• ☐ Event overview is two or three specific sentences with a clear goal
• ☐ Primary dates plus at least one alternate are listed
• ☐ Peak rooms (not total room nights) are clearly stated
• ☐ Meeting space breakdown includes set type, capacity, hours, and hold needs
• ☐ F&B is mapped function-by-function with a per-person target
• ☐ Concession asks are limited to 3 to 5, marked Required or Preferred
• ☐ Response window is at least 48 to 72 hours
• ☐ Decision timeline (shortlist, site visits, award, contract) is in writing
• ☐ Custom questions are limited to the few that change your decision
• ☐ You're sending to 6 to 10 qualified hotels, not 30
• ☐ NSO/GSO contacts are looped in for chain properties when relevant
• ☐ Contact info and Q&A channel are clearly listed at the top

If every box is checked, the bids will come back faster and stronger.

Make small-meeting sourcing the easy part of your week

Small meetings are where most planners spend the bulk of their sourcing time and the least of their negotiating leverage. A clear, well-structured RFP flips that. You spend less time writing, hotels spend less time guessing, and the proposals you get back are the kind you can actually compare. If you're running enough small meetings to call them a program, centralize them.

Start with Cvent Supplier Network, send your next small-meeting RFP, compare bids in one place, and see what your sourcing is actually delivering.