Why the hotel does not want your block
A room block is a contract in which the hotel takes inventory off sale and holds it for your attendees, and you accept some form of liability if those rooms go unsold. From the hotel's side that is a trade: it gives up the chance to sell the rooms to anyone else in exchange for a group that will probably fill them. The trade only works when the group is large enough to matter. Below a certain number of rooms a night, the sales office is being asked to do contract work, reporting work and a reservation code for a handful of bookings it would have received anyway, and it will usually decline or quote terms that make declining the better option.
This is not a rejection of your event. It is a mismatch of scale, and the honest response is not to inflate your numbers to get over the line. Organizers who promise more rooms than their attendees will use end up with the one outcome that is worse than having no block: a contract with an attrition clause, a pickup number that falls short, and a bill for the difference. A small event that signs a full block is taking on the risk of a large event without the audience to absorb it.
The better starting point is to accept that the classic block is a tool for a size you may not be, and to look at the structures that exist below it. There are several, they commit you to much less, and for most small and mid-size events they produce a better result for attendees than a block would have.
The courtesy block: held rooms without the guarantee
A courtesy block is a set of rooms the hotel holds under your event's name at an agreed rate, released back to general sale on a cutoff date, with no financial guarantee from you. If the rooms sell, your attendees get the rate and the hotel gets the business. If they do not, the hotel puts them back on sale and nothing is owed. It is the structure most small events should ask for first, and the one many organizers do not know to ask for, because every template and checklist they have seen assumes a guaranteed block.
What you give up is leverage. A hotel holding rooms at no risk to you will hold fewer of them, for a shorter window, and at a rate closer to its ordinary group pricing. It may also quietly stop honouring the arrangement if it fills up from other business, and a courtesy block will rarely survive a genuinely busy weekend in the market. That is a fair trade for an event whose room count is uncertain: you are paying for flexibility with a thinner discount, rather than paying for a discount with a liability.
The practical asks are simple. Get the rate, the cutoff date and the number of held rooms in writing, even in an email, so that your attendees and the front desk are working from the same facts. Ask what happens to a booking made after the cutoff, since most hotels will still honour the rate on a space-available basis if asked. And put the reservation instructions somewhere your attendees will actually see them, because a courtesy block with nobody booking into it is just a hotel doing you a favour it will not repeat next year.
Group rates and codes: a discount, not a contract
The next step down is a group rate with no held rooms at all. The hotel gives you a code or a booking link; attendees who use it get a rate, subject to availability, and nothing is reserved for anyone. This is what many organizers actually have when they believe they have a block, and the difference matters. A group rate makes no promise that there will be a room when your attendee goes to book. It simply changes the price if there is one.
For a small event that can be enough. The rate is a real benefit to attendees who book early, it costs you nothing, and it gives your lodging page and confirmation email something concrete to point at. The weakness shows up late in the cycle. Because nothing is held, the rate disappears as soon as the hotel sells through its ordinary inventory, and it does so precisely when your attendees are most likely to be booking. A group rate serves the organized minority who decide early and abandons the rest.
The rule is to know which of the two you have signed. A group rate is a discount; a courtesy block is held rooms without a guarantee; a full block is held rooms with one. Each one shifts a little more risk from the attendee to you in exchange for a little more certainty. Small events should generally sit at the lighter end of that scale, and should describe what they have accurately, so that attendees are not told rooms are reserved for them when they are not.
Where your attendees will actually stay
Whatever structure you choose, it will cover only part of your audience. The pattern Bookend measures directly in the mid-size events market is instructive even for smaller events. Across one peak event weekend, about 550 room-nights were booked around the event, and around 70% of the lodging money was committed inside the final 30 days. A courtesy block or group rate reaches the early deciders. The larger group, deciding late, will find the rate gone or the hotel full and will book on the open market instead.
For a small event this is not a failure of the plan. It is the plan. Your attendees are going to spread across the hotels near the venue, the rentals in the surrounding streets and whatever their budget and party size point them toward, and no arrangement you could sign at your size would change that. What you can change is whether they find those options through you or through a search engine. The where-to-stay question is going to be asked either way; the only variable is who gets to answer it.
That reframes the job. Instead of trying to capture attendees inside a structure you cannot fill, a small event's lodging plan should aim to be the place attendees go to find whatever they end up booking. A single page that lists the courtesy rate alongside a live view of what else is available near the venue does more for a small audience than a block ever would, because it serves the late majority and the early minority with the same link.
Answering the question without running a housing desk
Small events have less staff, not fewer lodging questions. If anything the questions are more personal, because the organizer is reachable, and the same handful of them arrive by email, by message and at registration every cycle. Is there a hotel you recommend. Is there a rate. Can we stay somewhere together. Is it walkable. Each one is a person about to spend money on a trip, asking you to point them somewhere, and each one answered by hand is a few minutes you will spend again next year.
The efficient answer is to write it once, in the place attendees look first, and to make it bookable rather than descriptive. A lodging page that says which hotels are close and how to get the rate is good. A lodging page that lets an attendee see what is available on the event dates and book it without leaving is better, because it finishes the task the question started. The confirmation page and confirmation email are the highest-value places to link that page from, since every buyer sees them at the exact moment the trip becomes real.
None of this requires inventory, a housing bureau or a contract. It requires that the event's answer to the lodging question be a link that works, that the link be placed where buyers are, and that it stay useful in the final month when the courtesy rate has expired and most of the booking is happening. That is the whole lodging operation for a small event, and it is one page and two placements.
Earning from lodging at a size no hotel will contract with
Organizers of small events tend to assume that lodging revenue belongs to events large enough to negotiate for it. The mechanics point the other way. Lodging commissions are paid by the property on bookings the event sends it, typically in the 15-20% range, and they do not depend on a block, a minimum or a contract with any one hotel. They depend on the booking being traceable to the event. A small event with a lodging page that its attendees actually use is in the same position as a large one, just with fewer bookings on the page.
This is where the earlier sections come together. A courtesy block or group rate gives early bookers a reason to use your page. A live open-market view keeps the page useful for the late majority after the rate is gone. Placing the link on the confirmation page and in the confirmation email makes sure attendees find it when they are planning. Each of those steps helps attendees first, and each one also makes the event the referrer of record for a booking it would otherwise have watched go to a search engine.
The scale is honest. A small event will not fund itself on lodging commissions, and it should not be promised that it will. What it can do is turn a support task it was already doing for free into a line that covers a real cost, without signing for a single room. For an event that has spent years treating the lodging question as overhead, that is a reasonable place to end up.
A lodging plan for a small event, in order
Start by estimating travelling attendees rather than total attendees, and then be conservative with the number. Most of the damage in small-event lodging comes from an optimistic room count offered to a hotel that then wrote it into a contract. If the honest number is below what a hotel will hold, do not stretch it; move to a lighter structure instead.
Ask the nearest suitable hotel for a courtesy block first, and settle for a group rate if the hotel will not hold rooms. Get whichever one you have in writing with the rate, the cutoff and the booking instructions. Describe it accurately to attendees: held rooms are held, a rate is a rate. Then build the lodging page around it, with the courtesy option at the top and a bookable view of everything else near the venue beneath it, so the page keeps working after the rate expires.
Finally, link the page from the confirmation page and the confirmation email, and leave it alone. The plan has now covered the early bookers with a rate, the late bookers with a live view, and the organizer with a single answer to the question they were going to be asked anyway. That is more than most small events manage, and it commits them to nothing they cannot deliver.