Office Attendance Scenario Planning starts with a real operating question. Office attendance scenario planning tests how a workplace behaves across ordinary, busy, low-attendance, and team-coordination days. It gives the design team a range of credible conditions instead of a single optimistic occupancy assumption. The useful answer is to define the need, test it against the building, and carry the decision through delivery.
Keep the decision proportional to the project, but do not skip the evidence. A small unresolved interface can become a large operational problem when it is repeated across a workplace.
What is an attendance scenario?
It is a documented pattern of who arrives, when, why, and what settings they need. A useful scenario includes teams, peak periods, meeting demand, visitors, shifts, storage, and exceptions, not just a percentage of desks occupied.
Name the source and confidence of each input. Badge data, booking data, observation, interviews, and leadership intent answer different questions and should not be blended without explanation.
Which scenarios should a brief test?
At minimum, test a normal day, a coordinated team day, a peak meeting day, a low-attendance day, and a change or growth case. Add shift, visitor, or project scenarios when they affect capacity or security.
Keep the scenarios readable. A decision-maker should see which setting becomes constrained first and what consequence follows when the assumption changes.
How should teams be modelled?
Map attendance by team and work type, then test adjacency, confidential work, equipment, project storage, and collaboration. A blended average can hide a real shortage when several teams arrive together.
Use a matrix that separates people from settings. Ten people do not always mean ten desks, but they may mean a project table, secure storage, or a room at the same time.
How do scenarios affect services and technology?
Translate the occupancy range into loads and operating conditions for HVAC, lighting, power, data, AV, access, cleaning, and support. The appointed engineers and building team must confirm the technical response for the actual premises.
Record base-build limits separately from tenant choices. A flexible workplace cannot create fresh air, electrical capacity, or network resilience that the building does not provide.
How should scenarios be tested with users?
Walk through arrival, finding a setting, meeting, focus work, storage, room release, visitor handling, and fault reporting. Use representative users and facilities staff, and capture the practical friction rather than only preferences.
A scenario is useful when it changes a decision. If the walkthrough reveals a weak assumption, amend the brief and keep the old version in the decision record.
When should the model be reviewed?
Review it after policy changes, relocation, team growth, seasonal peaks, or post-occupancy evidence. Set a review owner and date before construction so the workplace can adapt without losing the original reasoning.
Do not treat a forecast as a guarantee. State the boundary of the model, the risks it does not cover, and the operational action if actual use exceeds the tested range.
A practical decision check
| Layer | Questions to confirm |
|---|---|
| Purpose | What work or operating problem must this solve? |
| Evidence | Which building, user, technical, or source information supports the choice? |
| Coordination | Which drawings, services, suppliers, approvals, or trades are affected? |
| Ownership | Who approves, operates, maintains, and reviews the result? |
| Proof | What test, inspection, record, or handover evidence will show it works? |
Use this check before the decision is released. If one answer is missing, mark it as an open item with an owner and date rather than hiding it inside a general allowance.
Project checklist
Before the work is released, use this checklist to keep the design connected to people, building, budget, and operations.
- Purpose and owner: write the problem, outcome, decision owner, and approval date.
- Evidence: label measured conditions, stakeholder inputs, source guidance, assumptions, and open questions.
- Plan: test adjacency, circulation, capacity, privacy, accessibility, and user journeys.
- Services: coordinate power, data, HVAC, lighting, fire, security, controls, and maintenance access where relevant.
- Procurement: confirm specification, sample, lead time, alternatives, warranty, and cost or programme effect.
- Site: inspect the first representative area, record defects by location, and protect approved work from unreviewed change.
- Commissioning: test normal use, peak or unusual use, controls, failure response, and handover evidence.
- Operations: give facilities and users clear instructions, contacts, maintenance information, and feedback route.
- Review: set a post-occupancy check and state what will be measured, who will review it, and what may change.
The checklist does not replace the project brief, engineering design, statutory review, landlord requirements, or specialist advice. It is a final sense check before a decision becomes difficult to reverse.
Frequently asked questions
Start with the actual users, work, building conditions, and operating responsibility. Turn those inputs into a brief that the design and delivery team can test.
Set the direction during briefing and test-fit, then carry it through coordinated design, procurement, construction, commissioning, and handover. Late decisions affect several trades.
Use building evidence, stakeholder input, drawings, samples, inspections, and operating tests. Record assumptions and exceptions instead of presenting an early estimate as a guarantee.
No. The response depends on the building, users, work model, landlord rules, services, budget, programme, and responsibilities. A project-specific review is essential.
Sources and further reading
These sources provide background guidance for the standards-oriented parts of this article. Project teams should confirm the requirements that apply to the actual building, brief, and jurisdiction.
Plan the next step
Bring the brief, building information, headcount, work patterns, constraints, and decision date. Vektor Spaces can connect this topic to a practical route covering workplace strategy, design, MEP coordination, procurement, construction, and handover.