Should a team get a desk that stays theirs, or one that opens up to whoever needs it that day? The answer changes by team, and getting it wrong in either direction creates a cost someone has to manage later — either an underused assigned desk or a shared desk that nobody can actually use the way their role requires. The decision depends less on space efficiency targets and more on what each role actually needs from its desk on a given day.

Work Patterns That Drive Desk Assignment

The starting question is not how many desks a team needs but what kind of relationship each role has with its desk. Some work depends on the desk holding something between sessions — a physical setup, a piece of equipment, a document or file that stays in reach. Other work treats the desk as a temporary surface: the person arrives, works, and the desk’s specific identity does not matter once they leave. These are different relationships to the same piece of furniture, and the allocation model should follow the relationship rather than a general preference for one model or the other.

Where a role repeats the same task configuration daily — the same monitor arrangement, the same reference materials, the same seating posture built up over time — moving that setup each day introduces friction that a stable desk removes. Where a role instead produces work that does not depend on returning to the same physical spot, the desk becomes interchangeable, and its availability on a given day becomes the more relevant question than its ownership.

Attendance pattern is a separate factor from task repetition, and the two can point in different directions. A role might require a highly repeatable individual setup while also attending in person only a few days a week; in that case the assignment question is not settled by attendance alone, because the setup requirement can still argue for a reserved position even with partial attendance. Conversely, a role with no repeatable setup needs but with high daily attendance does not automatically require an assigned desk either — high attendance with low setup dependency is exactly the condition that free-address systems are built to absorb.

What changes the judgment is the interaction between these two variables, not either alone. A team evaluation that looks only at how often people come in, without asking what each attendance day requires the desk to hold, will systematically misclassify teams whose infrequent attendance still depends on continuity of setup.

Stable Setup Needs Versus Shared-Desk Flexibility

Work requirement or condition	Assigned workstation implication	Free-address implication
Persistent equipment	Supports assigning a position so the equipment can remain with the role	Confirm whether sharing can accommodate the equipment requirement
Controlled records	Supports assigning a position where the records can remain controlled	Confirm how the records requirement will be maintained in a shared setting
Repeatable individual setup	Supports assigning a position where the setup can remain consistent	Confirm that the required setup can be recreated at an available desk
Attendance variation	Does not by itself justify a fixed position	Can support shared allocation when expected attendance and desk availability have been checked

The distinction that matters here is between what a role needs to keep and what a role can recreate. An assigned workstation is easiest to justify where a role depends on persistent equipment, controlled records, or a repeatable individual setup — conditions where moving or reconstructing the work environment each day creates a cost the business is not otherwise accounting for. Persistent equipment that cannot reasonably travel with the person, records that must stay within a controlled location rather than circulate through a shared pool, or a setup whose value comes specifically from staying consistent across sessions — each of these is a condition that favors a fixed position over a shared one.

Free-address flexibility works in the opposite direction: it assumes that what the desk needs to provide on any given day can be supplied fresh, without dependency on what was there the day before. This holds where the work itself does not require continuity of physical setup, where any available desk in the pool can serve the task, and where the team’s attendance pattern leaves enough slack in desk supply that availability is not itself a daily problem.

The conflict appears when a team has some roles that clearly need continuity and others that clearly do not. Treating the whole team as one allocation category in that situation forces a choice that fits part of the team and fails another part. The more useful approach separates the allocation decision by role or sub-function within the team rather than applying a single model to every seat the team occupies.

Where persistent equipment, controlled records, or a repeatable setup apply, that condition argues for assignment regardless of how often the person attends. Where none of those conditions apply, attendance and desk availability become the deciding factors instead, and the team moves toward a shared model — provided the remaining readiness questions about storage, cleaning, and adjustment range are also answered rather than assumed.

Storage, Availability, and Adjustment Questions

Project question	Decision relevance	Project-specific answer
What attendance is expected for the team?	Establishes the attendance variation against which shared allocation is considered	To be confirmed
How many desks will be available when the team attends?	Tests whether the proposed desk availability matches expected attendance	To be confirmed
Where will personal items be stored?	Tests whether the shared arrangement provides a defined personal-storage approach	To be confirmed
Who owns cleaning of shared positions?	Tests whether cleaning ownership is defined for shared use	To be confirmed
What range of user adjustments is required?	Defines the adjustment range that the proposed workstations and seating need to support	To be confirmed

A free-address option should be checked against expected attendance, desk availability, personal storage, cleaning ownership, and the range of user adjustments required before it is adopted, because each of these is a separate condition that can independently make a shared-desk model unworkable even when the underlying task pattern supports sharing in principle.

Expected attendance and desk availability are related but not interchangeable. A team’s attendance pattern describes how many people show up on a given day; desk availability describes how many desks the project has allocated to that pool. A shared model fails not because sharing is the wrong concept for the team but because the ratio between these two numbers has not been checked against the team’s actual pattern — including variation across different days rather than an average.

Personal storage is a separate requirement from desk assignment itself. Removing a fixed desk does not remove the need somewhere for personal items, and a free-address plan that has not defined where those items go during and between sessions leaves a gap the desk allocation decision cannot close by itself. Cleaning ownership raises a related but distinct question: who is responsible for returning a shared position to a usable condition for the next person, since a free-address system depends on that handoff happening reliably between users rather than being managed once per fixed occupant.

The adjustment range required by the group is the condition most directly tied to the physical workstation and seating rather than to the allocation model. A shared desk serving a narrow range of users with similar requirements places fewer demands on the furniture’s adjustability than a shared desk serving a wide range of body sizes, working postures, or equipment needs across different daily occupants. Where the adjustment range required is wide, the furniture specification itself becomes part of the readiness question, not just the scheduling or storage logistics around it. Reference points such as the OSHA Computer Workstations Purchasing Guide describe checks for fit and adjustability relevant to this kind of evaluation, though that guidance addresses workstation-purchasing considerations generally and does not establish that a specific proposed item meets a given team’s adjustment range.

Proposed-Item Evidence for Workstations and Chairs

Evidence check	What to request	What the check can support	What it does not establish
Workstation fit and adjustability	Evidence for the actual proposed workstation or desk against the required user adjustments	Review of whether the proposed item addresses the identified fit and adjustment needs	The allocation model or general ergonomic guidance does not prove actual-item fit, certification, test status, or injury prevention
Seating fit and adjustability	Evidence for the actual proposed chair against the required user adjustments	Review of whether the proposed seating addresses the identified fit and adjustment needs	The allocation model alone does not establish chair fit or test status
Category-specific test status	The exact current applicable standard and the report for the proposed desk, table, chair, or other relevant furniture item	Review of the result and scope documented for that proposed product	Public standard descriptions do not establish a pass or compliance conclusion for the proposed item

Once an allocation decision is reasoned through — assigned, shared, or a mix by role — a separate question remains: whether the actual workstation and seating being proposed for that allocation can do what the allocation model assumes they can do. Request workstation and seating evidence for the actual proposed items, because the allocation model does not establish their fit or test status. These are two distinct evaluations, and resolving the first does not resolve the second.

An assigned-desk decision based on a role’s repeatable setup still needs the proposed desk and chair checked against the specific adjustment range and equipment accommodation that setup requires. A free-address decision based on attendance and desk-pool math still needs the proposed shared workstations checked against the adjustment range required across the pool’s actual range of users, since a shared desk has to serve more varied individual requirements across a single day than an assigned desk serving one consistent occupant.

Category-specific test standards are a further, separate layer. BIFMA’s Standards Short Descriptions identify category-specific test standards relevant to desks, tables, and other office furniture, but these are public descriptions of standard categories rather than a pass or compliance conclusion for any particular product. Confirming that a proposed desk or chair carries a result against the exact current applicable standard requires the specific test report for that item, not an inference from the general category description or from the allocation model chosen for the team.

This is where project-specific information supplied to a furniture provider functions differently from the planning decisions made earlier. GEORGE’s project configuration process reviews the workstation and seating requirements the buyer specifies — including the adjustment range and equipment needs identified during allocation planning — against the actual proposed products, rather than assuming that an allocation model alone determines product suitability. The dimensions, attendance pattern, and role requirements established earlier become the input that this review works from; they do not substitute for it.

Team-by-Team Allocation Decision Record

Team	Expected attendance	Persistent equipment, controlled records, or repeatable setup	Desk availability	Personal storage approach	Cleaning ownership	Required user adjustments	Proposed-item evidence checked	Allocation decision
Project-specific team	To be confirmed	To be confirmed	To be confirmed	To be confirmed	To be confirmed	To be confirmed	To be confirmed	Assigned, free address, or project-specific combination

Bringing the allocation decision to a usable conclusion means recording it at the level where the variation actually occurs — by team, and where a team contains mixed roles, by sub-function within the team. A single organization-wide allocation rule obscures the conditions established earlier: that persistent equipment, controlled records, or repeatable setup argue for assignment independent of attendance, while the absence of those conditions shifts the decision toward attendance and availability instead.

For each team, the supported inputs are the expected attendance pattern, whether persistent equipment, controlled records, or a repeatable setup apply, the desk availability the project has allocated, the storage and cleaning approach defined for shared use, and the adjustment range the group’s users require. Where any of these remain unconfirmed, the allocation decision for that team is not yet supported — a team cannot be assigned a shared-desk model, for instance, on the basis of attendance alone if desk availability for that team’s peak attendance day has not been checked, and it cannot be assigned a fixed-desk model purely by default where no role in the team actually depends on persistent equipment or controlled records.

The proposed-item evidence status belongs in the same record rather than as a separate afterthought, because a team’s allocation decision and the fit of its proposed workstations and seating are both conditions of the same deployment and both need to be true before the configuration is final. A team evaluated as suited to free address still needs its proposed shared desks and chairs checked against its adjustment range; a team assigned fixed positions still needs the same check against its individual setup requirements.

Where every input is confirmed for a team, the allocation decision follows directly from the conditions already reasoned through — assignment where persistent equipment, controlled records, or repeatable setup apply; free address where attendance, availability, storage, cleaning, and adjustment range have each been separately verified as workable; or a project-specific combination where a team’s roles do not fall uniformly into either pattern. Where inputs remain unconfirmed for a given team, that gap — not a default assumption in either direction — is what the project record should show.

Frequently Asked Questions

Q: Can different teams use different desk allocation models?
A: Yes. Record the decision separately for each team, and use assigned desks, free address, or a project-specific combination based on that team’s work patterns and setup requirements.

Q: When does attendance variation support free-address desks?
A: Attendance variation supports consideration of free address only after expected attendance is compared with desk availability. Personal storage, cleaning ownership, and required user adjustments must also be resolved.

Q: Which roles are stronger candidates for assigned workstations?
A: Roles that depend on persistent equipment, controlled records, or a repeatable individual setup are stronger candidates. Document the specific requirement and whether it could be maintained reliably in a shared setting before deciding.

Q: Does choosing assigned or free-address desks establish workstation suitability?
A: No. The allocation model does not prove fit, adjustability, certification, test status, or injury prevention; review evidence for the actual proposed workstations and chairs against the team’s required user adjustments.

Q: What evidence should be checked before approving proposed desks and chairs?
A: Request product-specific evidence covering the relevant fit, adjustability, and category-specific test requirements. Confirm the exact applicable standard, report scope, and proposed item rather than relying on general guidance or public standard descriptions.