Which teams need an assigned desk, which can share one, and what has to sit around that decision before a desk count gets approved? This is a planning judgment, not a subtraction problem: removing a fixed desk changes what a person needs from storage, scheduling, and the settings around them, and it changes demand on the rest of the floor. The mix only holds up if each of those downstream effects is checked before the allocation is signed off.
Team Conditions That Favor Assigned or Shared Desks
| Team condition | Desk direction | Evidence to check |
|---|---|---|
| The team needs a stable individual setup | Favor assigned desks | Identify the required equipment or records that depend on a stable individual position |
| The role can share a position without losing required equipment or records | Shared desks may be suitable | Verify that the required equipment and records remain available under the shared arrangement |
The starting question is not how many desks a team wants but what depends on a stable individual position. Where a role requires equipment that stays set up, reference material that stays in reach, or records that must remain at a fixed location during the working day, an assigned desk exists to protect that continuity. Moving the person to a different position each day breaks the link between the person and whatever physical or procedural requirement depends on staying put. That is a structural condition, not a preference, and it should be identified before any desk-sharing ratio is proposed.
Shared desks become appropriate under a different condition: the role’s required equipment and records travel with the person, or are available from a shared or personal storage point regardless of which desk is occupied. If the equipment or records can move without loss of function, the position itself no longer needs to be fixed. This is where the judgment becomes conditional rather than categorical. The same job title in one project may need an assigned desk because of what it keeps at the desk, while the same title in another project may share freely because its supporting material is stored and issued independently of any one desk.
The test the project team applies is whether the required equipment or records survive the change in desk arrangement. If a team’s work depends on something that cannot be relocated, packed, or reissued without disruption, that team sits on the assigned side regardless of how often its members are physically present. If the dependency does not exist, or has already been resolved through separate storage or digital access, the team is a candidate for sharing. Conflating “present less often” with “can share a desk” skips this check. A role can attend rarely and still need an assigned desk, if what it depends on cannot be decoupled from a fixed position. A role can attend daily and still share, if nothing it needs is tied to a specific desk.
This distinction also determines how the rest of the desk mix is read. A proposed ratio of assigned to shared positions is only as sound as the team-by-team check behind it; a ratio built on attendance patterns alone, without confirming what each team needs to keep in place, is not yet a supportable allocation.
Support Settings Needed Around the Desk Mix
| Support setting | Need represented in the mix | Planning boundary |
|---|---|---|
| Focus settings | Coverage for work requiring focus | Demand may increase when another workstation type is reduced |
| Meeting settings | Coverage for collaboration | Demand may increase when another workstation type is reduced |
| Storage | Personal storage support around shared desks | A lower desk count does not by itself resolve storage needs |
| Touchdown settings | Touchdown support alongside assigned and shared desks | The required provision depends on the project-specific setting mix |
Reducing one workstation type does not remove the demand that workstation type was serving; it relocates that demand elsewhere in the setting mix. Where a team moves from assigned to shared desks, the volume of work that previously happened at a fixed desk still needs somewhere to happen, and the character of that work determines which support setting absorbs it. Work that requires sustained individual focus places demand on focus settings. Work that involves discussion or coordination places demand on meeting settings. Short, unscheduled work between other activities places demand on touchdown settings. None of these are substitutes for one another, and a mix that assumes shared desks alone will absorb all of this displaced demand is incomplete.
The planning consequence is that the desk mix and the support setting mix have to be evaluated together, not sequentially. If the assigned-to-shared conversion is decided first and the support settings are sized afterward based on whatever space remains, the support settings may be undersized for the activity they are meant to carry. The more defensible order is to identify the activities that no longer have a fixed desk attached to them, classify those activities by the setting type they need, and then confirm that the proposed focus, meeting, and touchdown provision can carry that reclassified demand alongside its existing load.
Storage follows the same logic but for a different reason: a lower desk count does not resolve where personal materials go when the desk is not assigned. That is addressed separately later in this planning sequence, but it belongs on the same list of things a reduced desk count creates a new requirement for, rather than something the desk reduction already accounts for.
Where the project also includes open-plan or coworking arrangements, the same principle applies to open-plan office furniture layouts and hybrid and coworking furniture planning: a lower fixed-desk count changes what the surrounding settings are asked to carry, and that shift has to be sized on its own terms.
Storage, Adjustment, and Upkeep for Shared Positions
| Shared-position issue | The support plan must establish | Decision consequence if unresolved |
|---|---|---|
| Personal storage | How personal storage is provided without relying on an assigned desk | The shared arrangement does not yet cover personal storage needs |
| Adjustment | How the shared position can be adjusted for its users | Suitability for the intended users remains unconfirmed |
| Availability | How required shared positions will be available when needed | The proposed desk reduction remains unsupported |
| Upkeep | How shared positions will be maintained for continued use | The operational support for sharing remains incomplete |
A shared desk is not a complete answer until four separate questions about it have been answered, and treating a lower desk count as self-sufficient skips all four. The first is personal storage: if a person no longer has an assigned desk, where do their materials live between sessions at different desks. This has to be resolved independently of the desk itself, because a shared desk by definition cannot hold someone’s materials for them between uses.
The second is adjustment. A desk shared among different users has to accommodate those different users, and the mechanism for doing that — whether the desk itself adjusts, or the user’s own equipment adjusts, or seating and accessories compensate — has to be established for the specific people who will use the position. A shared desk sized or fixed for one user’s preferences does not automatically suit the next.
The third is availability: whether enough shared positions exist, and are actually free, at the times people need them. A shared-desk ratio calculated on average attendance can still fail on a given day if attendance clusters rather than spreading evenly, and the project has to confirm how the proposed ratio behaves under the pattern of attendance the organization actually has, not only its average.
The fourth is upkeep: who is responsible for returning a shared position to a usable condition between users, and what that responsibility requires in terms of time, process, or equipment. A shared desk that is not reliably reset between users degrades in practical usability even if it remains structurally identical to an assigned one.
Where all four of these are established, a shared-desk allocation is a supported planning decision. Where one remains open, the desk count reduction it was meant to justify is not yet fully supported, because the desk count was never the complete requirement — the support conditions around it were.
Furniture Evidence Across the Proposed Categories
Once the assigned, shared, and support setting mix is established, the furniture proposed for each category needs its own evidence, and that evidence does not transfer automatically from one category to another. A desking system proposed for assigned positions, a table proposed for shared positions, and storage or cabinetry proposed to support both are different product categories, and claims about load capacity, durability, or other performance characteristics attach to the specific product in its specific category rather than to the setting mix as a whole.
Public descriptions of category-specific test standards, such as those BIFMA maintains for desks, tables, and other office furniture, identify which kind of standard applies to which kind of product. That identification is useful for knowing what category of evidence to ask for. It is not itself confirmation that a particular proposed product has been tested to, or passes, the standard that description refers to. The current version of the relevant standard and a test report for the specific product being proposed are what establish a pass or compliance claim; a general public description of the standard’s scope does not substitute for either.
This matters most where the desk mix decision changes which categories are actually in scope. If a project reduces assigned desks and increases shared desks, storage, and touchdown furniture, the evidence requirement expands to cover each of those categories individually, rather than staying limited to whatever category the original assigned-desk proposal covered. A project team that collected evidence for the assigned-desk product early in planning, then added shared desks, storage, and support furniture later without repeating the same evidence step for each addition, has an incomplete evidence package relative to the final mix, even if the original category was fully documented.
The practical implication for a project review is that evidence collection follows the final setting mix, not the first category proposed. Where the mix changes after the initial furniture selection, the evidence list has to be revisited against the categories actually present in the revised mix.
Approved Mix and Documented Exceptions
| Decision area | Approved project entry | Exception to document |
|---|---|---|
| Assigned desks | The approved coverage for teams needing stable individual setups | Any such team not covered by the approved allocation |
| Shared desks | The approved coverage for roles able to share without losing required equipment or records | Any role whose equipment or record needs are not supported by sharing |
| Focus and meeting settings | The approved support for focus and collaboration demand | Any task-coverage gap created by reducing a workstation type |
| Storage, adjustment, availability, and upkeep | The approved support plan for shared positions | Any unresolved shared-position support issue |
| Furniture evidence | The exact current category-specific standard and proposed-product report used for a pass or compliance claim | Any category for which only a public standards description is available |
The output of this planning process is not a single ratio but a record that shows which condition placed each team or role on the assigned or shared side, what support settings were sized to absorb displaced demand, what shared-position support issues were resolved, and what furniture evidence was confirmed for each category in the final mix. Recording only the final ratio without the reasoning behind it makes the mix difficult to revisit if conditions change after approval.
Equally important is what the record does not resolve. A team identified as needing an assigned desk because of an equipment or record dependency, but not covered by the approved allocation, is a documented exception, not an implied acceptance of the gap. A role assigned to shared desks whose equipment or record needs turn out not to be supported by the sharing arrangement is the same kind of exception on the shared side. A support-setting shortfall created by a workstation reduction, and a shared-position support issue — storage, adjustment, availability, or upkeep — left unresolved at approval, belong in the same record rather than being carried forward informally.
This is also the point in planning where the project information assembled through the earlier sections — the team-by-team assigned/shared determination, the support setting sizing, the shared-position support plan, and the category-specific evidence check — becomes the basis for a configuration or quotation review with the furniture supplier. George works from the project’s own setting mix and supporting requirements rather than a fixed catalogue configuration, so the completeness of this record directly affects how well a proposed configuration can be matched to what the project has actually established.
Where the record is complete, the approved mix can be treated as a stable reference for procurement and layout. Where exceptions remain open, they should stay visible in the record until each is resolved, rather than being absorbed into the approved figures. A mix approved with unresolved exceptions is not wrong to proceed with, provided the exceptions are tracked rather than dropped; it is only wrong to present as fully resolved when it is not. For teams whose needs fall outside a standard assigned/shared split, the same exception-tracking approach applies when reviewing options such as those covered under inclusive furniture planning for diverse users, where a documented gap in the standard mix is the trigger for that review rather than a reason to leave the gap unrecorded.
Frequently Asked Questions
Q: Should every team follow the same assigned or shared desk policy?
A: No. Favor assigned desks where a stable individual setup is required, and consider shared desks only where equipment and records remain available without a dedicated position.
Q: What project information should be collected before planning the desk mix?
A: Record each team’s required equipment, record-access needs, and dependence on a stable setup, then identify expected needs for focus, collaboration, storage, and touchdown settings.
Q: When is a shared-desk proposal ready for approval?
A: It is ready only after the plan explains personal storage, user adjustment, position availability, and ongoing upkeep. Any unresolved item should remain a documented exception rather than being hidden by a lower desk count.
Q: Can reducing one workstation type be evaluated on desk numbers alone?
A: No. Review whether the change increases demand for focus, meeting, storage, or touchdown settings and confirm that the complete setting mix still covers required tasks.
Q: What evidence is needed before making a furniture pass or compliance claim?
A: Confirm the exact current standard for each proposed furniture category and obtain the report for the proposed product. A public standards description alone does not establish that a specific product passes or complies.