The average arrival was never standing in our reception queue

## Find the concentration inside the total

We expected 480 residents across five days, and I approved a reception plan built around the daily average of 96. The calculation was correct. The operating picture was incomplete. In one four-hour window 236 people arrived, with luggage, questions and travel arrangements built around dates we had confirmed. The team did not experience an average day spread conveniently across the planning period. It experienced a concentrated task for which I had not required a sufficiently detailed account.

A total is useful for several decisions. It helps estimate the overall work, prepare supplies and understand the scale of the intake. It does not by itself tell a manager when the work will arrive or how much must happen at the same time. I had treated the simple division as if it settled that second question. The mistake became visible through people waiting, but it began in the earlier approval of a planning unit that was too broad for the service being promised.

Residents had reasonable reasons for arriving together. Their travel, academic or employment arrangements did not exist to smooth our operating schedule. The company had accepted their arrival dates and needed to examine the pattern those commitments were likely to create. A reception plan that works only if customers behave in a way we have not agreed with them is not yet a supported plan. Experience at the front desk can help manage variation, but it should not be used as an invisible substitute for capacity management has chosen not to provide.

I asked property managers to describe the actual sequence of reception work. Which tasks could be prepared earlier? Which required the resident's presence? What information needed another responsible person's decision? Those questions were intended to improve the arrangement, not simply pressure colleagues to complete each interaction faster. Some steps served a necessary purpose and could not be removed because the queue was uncomfortable. Qualified facilities and other responsible owners retained the conditions for access and use of the premises.

The account also needed to recognise variation between people. One resident might need a straightforward confirmation; another might have a question about the room or require practical assistance. A common process can support both without pretending that every interaction takes the same form. The operating leader should understand the work well enough to resource it, while leaving room for the colleague facing a real person to respond appropriately. A plan that regards every difference as a failure of compliance will misread ordinary service.

## Coordinate without rewriting the resident's agreement

One proposal was to assign every resident a tight arrival slot. The attraction was clear: a controlled pattern would be easier to staff. I supported better communication and voluntary coordination, but not the assumption that an internal schedule could unilaterally rewrite arrangements already made. Residents needed to understand what we were suggesting and what the actual agreement allowed. Some would have limited travel choices. A person arriving outside a preferred window still needed a proportionate response rather than an explanation that the spreadsheet had reserved attention for someone else.

We spent₹ 18 lakh on additional reception cover and arrival coordination. The expenditure addressed capacity as well as information. I did not want the entire correction to consist of asking residents to organise their journeys more conveniently for us. Property managers prepared for the expected concentrations and identified unresolved arrangements requiring a conversation before arrival where possible. The work took more planning than dividing the total by five, and the additional cover made the revised approach more expensive than the original one.

The managers' concern about control remained relevant. If we made no effort to understand or coordinate the pattern, even additional staff could be placed at the wrong time. The answer was to connect communication with a realistic capacity account. An indication of intended arrival was useful information, not an assurance that every journey would occur exactly as stated. The plan needed room for changes and a clear responsibility for responding when the pattern differed. It should not become brittle merely because the company had collected more precise-looking times.

I also kept the correction with my own decision. The team had worked from a plan I approved, and residents had acted on commitments the company made. It would have been unfair to explain the problem entirely through late information or people arriving together. Those conditions were part of the business we operated. The useful executive question was what evidence I should have asked for before confirming that the staffing was adequate. Acknowledging that question made the additional cost easier to discuss honestly.

The programme did not create authority to bypass normal checks or treat reception speed as the sole measure of a successful arrival. A quick interaction that leaves the resident with an unresolved room commitment is not necessarily a better service. The operating review therefore needed both the flow of people and the quality of the response. I did not ask for one favourable number that would make every aspect of the intake appear settled. The service contained several responsibilities, and the plan needed to preserve them.

## Keep the remaining wait in the result

A later, separate intake comprised 510 residents. Its busiest four-hour window had 148 arrivals, and fourteen people still waited more than forty-five minutes. These figures were useful to the next operating review. They were not a controlled experiment proving that our programme alone caused a particular improvement. The cohorts, their circumstances and the arrival patterns differed. I kept those limits in the account rather than turn two observations into a precise claim about the intervention's effect.

The fourteen longer waits mattered even alongside a smaller peak. A management presentation could have focused on the reduction from 236 to 148 and stopped there. That would tell only part of the story and invite an unsupported conclusion that the service problem had ended. The remaining waits needed examination in their own circumstances. The purpose of the review was to improve the next arrangement, not to defend the correction as successful in every respect because management had already spent money on it.

We also avoided treating every wait as evidence of the same cause. A resident awaiting a decision about accommodation may face a different problem from someone waiting for the next available reception colleague. The operating record should make that distinction where the evidence supports it. Otherwise a general instruction to add more staff can become the answer to a problem involving an unresolved promise or missing authority. More capacity can be valuable while still being insufficient for a task nobody in the room is authorised to complete.

For directors, the lesson is about the relationship between a business volume and the capacity assumed to deliver it. A plan may use averages appropriately in one part of its account and inappropriately in another. The board can ask where demand concentrates, what conditions management has agreed with customers and which responsibilities become constrained during those periods. It does not need to design the reception roster. It needs confidence that management has examined the service at the point where the promise is experienced.

For my own practice, the change is to ask what the total hides before accepting what it explains. The 480-person intake was not an inaccurate forecast. The daily average was not bad arithmetic. The error was allowing those facts to settle a question about a particular four-hour period without enough evidence. I would still use totals and averages. I would also require the operating account that sits beneath them, because the resident waiting with a suitcase is experiencing a real moment that the average never had to live through.