Office Utilisation Study starts with a real operational question. An office utilisation study combines observation, occupancy evidence, interviews, and space data to show how a workplace is actually used. The useful output is not a single percentage. It is a set of planning decisions with known confidence and limits. 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 create a large operational problem when it is repeated across a workplace.
What is an office utilisation study?
It is a structured review of who uses which settings, when, for what work, and with what friction. The study can cover desks, meeting rooms, focus rooms, collaboration areas, amenities, storage, circulation, and support spaces.
Define the study boundary before collecting data. A two-week sample of desk presence cannot explain annual project peaks by itself. State the observation dates, floors, teams, access restrictions, and events that may have influenced behaviour.
Which methods should be combined?
Use a mix of floor walks, seat counts, room booking data where available, short user interviews, photographs or annotated plans, and facilities records. Each method answers a different question, so no single feed should be treated as the whole truth.
Observation reveals behaviour that booking systems miss. Interviews reveal why a room is avoided. Plans reveal capacity and adjacency. Together they help distinguish a supply problem from an operating rule, poor furniture choice, or a setting placed in the wrong part of the floor.
How should observations be recorded?
Use a consistent time grid and a simple code for occupied, available, reserved, underused, noisy, blocked, or unsuitable. Record the setting type and relevant context, while avoiding unnecessary personal data.
A repeatable field sheet makes comparisons possible. Note whether a desk is occupied by one person, a team, or equipment. Also record blocked circulation, storage overflow, and improvised meeting behaviour because these are design signals, not visual clutter.
How should the findings be analysed?
Compare demand by day, time, team, setting, and floor zone. Look for recurring peaks and mismatches. A room that is empty on average may still be essential at a predictable weekly peak, while a large desk field may be underused but operationally important.
Show ranges and confidence, not false precision. Separate measured observations from estimates. Mark the assumptions used in any capacity scenario so the client can change them without rebuilding the entire analysis.
How does utilisation affect a test-fit?
Use the findings to adjust setting mix, adjacency, storage, booking rules, room sizes, and peak capacity. Keep safety, accessibility, egress, services, and maintenance requirements visible while exploring density.
The output should show choices. It might recommend fewer assigned desks, more enclosed rooms, better project storage, or a pilot before construction. The recommendation must explain the operational change required for the design to work.
When should a utilisation study be repeated?
Repeat it after a major team change, a relocation, a hybrid-work policy change, or a reconfiguration. After a new fit-out, compare the intended use with lived use and collect feedback before making permanent changes.
A workplace is an operating system. Furniture and walls are only part of it. A short post-occupancy review can identify settings that need a rule, a repair, a relocation, or a different quantity rather than an expensive expansion.
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 short checklist for office utilisation study. It keeps the design decision connected to the people, building, budget, and operating team.
- Purpose and owner: write the problem, desired outcome, decision owner, and approval date.
- Evidence: label measured conditions, stakeholder inputs, source guidance, assumptions, and open questions.
- Plan: test the decision against 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 the evidence required at handover.
- Operations: give facilities and users clear instructions, contacts, maintenance information, and a route for feedback.
- Review: set a post-occupancy check and state what will be measured, who will review it, and what may change.
The checklist is deliberately practical. It does not replace the project brief, engineering design, statutory review, landlord requirements, or the client’s specialist advice. It is a final sense check before a decision becomes difficult to reverse.
Frequently asked questions
Start with the real work, users, building conditions, and operating responsibility. Convert those inputs into a short brief that the design and delivery team can test.
Resolve the direction during briefing and test-fit, then carry it through coordinated design, procurement, construction, commissioning, and handover. Late decisions affect several trades.
Use evidence from the building, users, drawings, samples, site inspections, and operating tests. Record assumptions and exceptions instead of presenting an early estimate as a guarantee.
No. The useful response depends on the service model, floor plate, landlord rules, building systems, users, budget, and programme. A local site and stakeholder review is essential.
Yes. A coordinated team can connect workplace strategy, design, services, procurement, construction, testing, and handover so the decision remains buildable and accountable.
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.