Reconciling Badge Data and Forecasts in a Headquarters Program

The first conflict is the definition of demand: 180 assigned seats is a headcount-based forecast, while the badge study measures attendance. Peak attendance of 168 is only 12 seats below the forecast, but average attendance of 118 suggests the forecast is not a daily space requirement. The second conflict is room supply: four conference rooms plus eight huddle rooms plus a 30-seat training room may be justified by different use patterns, but the sales request is based on perceived scarcity rather than measured utilization.

I would request badge data by day, hour, department, and role; remote-work policy by team; visitor and client counts; training attendance distribution; and existing meeting-room booking and no-show data. I would also ask the CEO to define growth as headcount, peak attendance, or both. Then I would build three test-fit scenarios: a conservative 180-seat plan, a peak-based 170-seat plan with a 10% attendance buffer, and a growth plan that adds 15% to the chosen metric. The badge average should not drive seat count; it should inform unassigned seats and shift patterns. The peak is the better operational number, but it must be tested against department-level peaks, because a company-wide peak can mask a group that is in the office five days a week.

I would start with a seat count near 170 to 180, not 240 and not 118. Peak attendance of 168 plus a modest buffer supports about 175 seats, while the 15% growth allowance should be modeled separately rather than folded silently into the base. If growth means headcount, the client needs a denser plan or more area; if it means peak attendance, the base plan may absorb it.

For meeting rooms, I would not simply grant eight huddle rooms. I would test five or six huddles, four 10-person conference rooms, and one divisible 30-seat training room that can also serve as two smaller rooms. That yields 40 conference seats plus 30 training seats plus 30 to 36 huddle seats, but the training room is used only twice monthly, so making it flexible reduces the need for dedicated conference space. I would validate the huddle request against booking data and propose phone booths or one-person focus rooms for overflow. Because the budget assumes 60% workstation reuse and no new conference technology, I would reuse existing conference tables and casework where possible and spend limited new technology funds on the divisible training room. The sales request should be met through flexibility and scheduling, not by adding rooms that will sit empty.

The growth assumption should be written as two separate metrics, not one percentage. First, headcount growth: base 240 employees plus 15% equals 276 people. Second, peak-attendance growth: base peak 168 plus 15% equals 193 people. The test-fit should show where 193 peak occupants sit and where 276 headcount would sit if the remote ratio changes. The basis of design should state which metric drives seat count and which drives support space.

A measurable expansion trigger could be: a 30-day rolling average of peak daily attendance above 90% of provided seats, or meeting-room utilization above 80% during core hours for four consecutive weeks. A second trigger could be headcount exceeding the plan's assigned-seat capacity for two consecutive months. When either trigger is met, the client should commission a test-fit of the expansion option before leasing additional area. This protects the budget now while giving the client a defensible reason to act later. I would also document that contractors and visitors were excluded from the badge study, so reception and visitor seating are sized separately.