Busy days and quiet averages

A business can have plenty of unused capacity and still be unable to serve the customers who want it. The empty places may exist on different days, at different hours or in a form those customers cannot use.

In the restaurant chapters of Infinite Upside, staffing has to fit the rush rather than simply produce a low payroll total. Later, the hotel example asks whether a smaller opening can accommodate the nights people actually want. The scale changes; a schedule remains more revealing than an average alone.

A week that looks comfortable in total

Consider an invented ten-room hotel for one week. It has seventy available room-nights: ten rooms multiplied by seven nights. One room-night means one room available or occupied for one night.

Suppose customers request forty-nine room-nights. That is seventy percent of the week's capacity. For this example, every request is for a single room for one night, all rooms are interchangeable, and customers cannot change their dates. There are no cancellations or additional requests. These are invented assumptions, not a hotel forecast or figures from the book.

The hotel can accommodate only forty-one of the requested room-nights. Eight requested room-nights cannot be accommodated on the two busy nights, while twenty-nine room-nights remain empty elsewhere in the week. Those empty rooms and refused requests are compatible facts.

If a model assumes all forty-nine requests can be served because forty-nine is less than seventy, it has quietly moved some customers to dates they did not request. The nightly table exposes the assumption. No room price or profit calculation is needed to find it.

Find the capacity the customer can use

The simple example makes every room equivalent. Real offers can have additional constraints. A group may need rooms together, a guest may need several consecutive nights, or a particular room type may be required. The development chapter asks readers to consider the complete visit. A total that fits can still describe the wrong collection of spaces.

A room for both nights

Matching a request can require changing a provisional assignment, even when nobody changes their stay. Consider a separate invented two-room guesthouse for Friday and Saturday nights. Birch has one double bed; Cedar has two single beds. The confirmed housekeeping schedule can reset either room between one guest's checkout and the next guest's check-in on Saturday. No additional rooms or beds are available.

Lea has a confirmed Friday-night booking and has agreed that either room is suitable. The staff have penciled her into Birch, but no particular room has been promised. Rafi has a confirmed Saturday-night booking requiring two single beds, so his room must be Cedar. These are the only existing stays.

A new guest, Mo, requests both nights in one room, with no move between them. Either bed arrangement suits Mo. That request remains unconfirmed.

Invented initial room plan before Mo's request is accepted

Scroll across to see every column. Use the arrow keys when the table is focused.

There are two empty room-nights. Mo needs two room-nights. In the initial plan, however, no room is empty for both nights. Adding the empty cells does not yet produce the stay requested.

Move Lea's provisional assignment to Cedar for Friday. Cedar can then be reset for Rafi on Saturday, using the confirmed housekeeping arrangement. Birch becomes available for Mo on both nights. The four room-nights now hold Lea for one, Rafi for one and Mo for two. Nobody changes dates, accepts a different bed arrangement or moves during a stay.

This works because Lea accepted either room; the pencil mark had not become a promise of Birch. Rafi's requirement cannot be shifted into Birch to make the grid look tidy. The rooms are not interchangeable for every guest, even though they are for Lea and Mo.

Now change only Lea's original booking: suppose Birch itself was specifically promised. The same reassignment is no longer available on the supplied terms. Staff would need an accepted change from Lea before relying on it. Alternatively, they could ask whether Mo would accept Cedar on Friday and Birch on Saturday. That would change Mo's no-move request; it cannot be counted as accepted already.

Without either change, Mo's requested stay does not fit. The two spare room-nights still exist. What is missing is a continuous room the guest can use under the current promises.

Before deciding the property needs more rooms, distinguish the bookings from the internal assignments. Which requirements are fixed, which allocations can still move and who would need to agree to a different offer? A feasible new plan must preserve the stays already promised, including the work between guests.

The same question can be asked of a service schedule. A team may have unused hours early in the day while its promised collections coincide in the afternoon. A machine may be available when the person who operates it is not. Listing each resource's spare time separately can conceal the absence of a period when all are available together.

Start with what the customer needs to complete, then identify the resources that must coincide. Where does the constraint actually fall: inventory, staffing, preparation, access or the time promised? Adding to a resource that is already available may leave the bottleneck untouched.

Do not assume every request is immovable either. Some customers may prefer another date if a real alternative is offered. Others are attending a fixed event or working to a deadline. Find out which circumstance applies before treating flexibility as part of the plan. An untested hope that customers will spread themselves evenly is not a revised schedule.

Change the offer before changing the average

For the invented hotel, the eight unserved requests identify two busy nights. They do not, by themselves, justify more rooms. The owner would still need to examine how often that pattern occurs, the cost and timing of additional capacity and what happens during quiet periods.

A different offer might attract guests who want quieter dates, but that demand has not been supplied by this table. A smaller opening might reduce some costs while refusing more peak-night requests. A partnership might provide overflow space only if the alternative is actually available and fits the guest's booking. Each possibility needs its own evidence.

For an operation you know, make a short calendar at the interval where service is promised. Use nights for stays, appointment slots for appointments or the relevant dispatch windows for deliveries. Put requests beside usable capacity at each interval. Preserve the type, location or duration where it changes what can be served.

Then choose the busiest interval and trace one request through preparation, delivery and readiness for the next customer. This can reveal a staffing or turnaround problem even when the inventory count seems adequate.

The cost of serving the next customer is another question. A new hire or asset can arrive as a block of expense. The schedule asks first whether the proposed resources would be present at the moment the promise requires them. Both questions belong in the decision; neither is answered by a quiet average.