How to Choose an Office Design Company for a Workplace Project

Start with the workplace outcomes the project must deliver

Choosing an office design company for a London workplace project starts with the outcomes your organisation needs, not the polish of a presentation. Set the objectives before you assess proposed layouts or finishes. That gives you a consistent basis for deciding whether each proposal answers the project brief.

Write down what the office needs to support: for example, the kinds of work your teams do, the balance between collaboration and focused work, and the workplace changes you are planning for. Treat these as requirements to explain, not as a design solution to dictate. A clear objective gives each provider a question to answer: how does this proposal respond to the way your organisation needs to work?

Attendance matters too. A three-day hybrid schedule requires different desk capacity from a fully office-based workforce. State the working pattern you are planning for rather than comparing proposals against an assumed headcount alone.

Turn each objective into a question you can apply consistently. If collaboration matters, identify the kinds of shared settings your teams need; if focused work matters, describe the requirements that follow from it. The point is to make the project purpose clear enough to guide a response without writing the design for the provider.

The useful first test is straightforward: can you connect the proposed workplace to your objectives, expected growth and attendance pattern? If that connection is unclear, note the question before you weigh visual preferences.

Prepare one outcome-led brief for every provider

A shared workplace brief gives each office design company the same requirements to answer. An office fit-out brief communicates your requirements to the project team and provides a foundation for design development, cost planning and procurement decisions. Use one core version when approaching providers; changing the brief between conversations makes their responses harder to compare.

Prepare the information in practical groups:

• Objectives and working pattern: explain what the project needs to achieve, who uses the office, expected team sizes and future growth.
• Workplace needs: list work settings, meeting needs, storage, privacy, technology and any specific requirements for different teams.
• Layout and identity: describe the outcomes you need for layout and branding, plus furniture specifications or special requirements that matter to the project.
• People to consult: gather relevant requirements and preferences from department heads and employees before finalising the brief.
• Known space information: note what you know about the space and identify points that still need investigation rather than presenting assumptions as settled facts.

Keep the document detailed enough to communicate requirements clearly, but focus on the outcomes you need instead of prescribing a particular design approach. That leaves room for providers to explain their proposed response while giving you a common basis for comparison.

For a major project, an office fit-out brief typically runs 10 to 20 pages and covers organisational context, functional requirements, technical needs, budget and schedule. Treat the subject matter as the guide, not the page count: make sure your requirements are clear and the relevant project information is present.

Make the brief easy to use in a conversation. Give each requirement a short description and, where useful, note why it matters to the project. Separate firm requirements from preferences, and label estimates or unconfirmed details as assumptions. This lets you see whether a proposal answers the need itself or depends on information you have not yet established.

Compare how proposals make the workplace and space work

A proposal is easier to assess when its space plan shows how your brief translates into usable capacity. Space planning can test how many people, desks, rooms and shared settings the office can realistically support. Ask each provider to explain the assumptions behind its plan, using the same headcount, attendance pattern and workplace requirements.

Look beyond a headline desk count. Check whether the proposal shows how the required work settings, meeting needs, privacy, storage and shared areas fit together. If two proposals use different assumptions, record the difference before treating their capacity figures as comparable. You are assessing the response to your requirements, not simply which drawing looks fuller.

The condition and limits of the space also affect what can be planned. A project building review can assess the space’s condition, services capacity, landlord constraints and compliance issues. Ask what a provider has considered in these areas, what information its planning relies on and what still needs to be established for your space.

Separate confirmed project information from assumptions. If a proposal relies on a building feature or services capacity that has not yet been established, mark that point as open. Then ask what needs to be assessed before you rely on the proposed layout. This makes the comparison more useful than treating every drawing as a fully tested plan.

Compare the relationship between capacity and the brief, not capacity in isolation. A plan that shows people, desks, rooms and shared settings against the same attendance assumptions is easier to interrogate than a single total. Note which requirements appear in the plan, which are not shown, and which depend on further information about the space. If a requirement is central to your project but its spatial response is unclear, ask for that response to be explained before you use the plan as a basis for selection.

Check technical requirements against site constraints

A technical proposal should be read against the actual building and how the work can be carried out there. Compare each response against the same list of project requirements, and note where the provider explains its approach, relies on an assumption or leaves a point unanswered.

For the technical scope, ask whether the proposal addresses:

• mechanical and electrical alterations;
• lighting, ventilation and cooling;
• acoustic performance; and
• IT, audio-visual and security requirements.

These items are prompts for your comparison, not a substitute for defining what your project needs. If a requirement matters to your organisation, state it in the brief and look for a corresponding response in the proposal. Where the proposal uses a general description, ask what that means for the requirement you have identified.

Then consider the site conditions that may affect delivery. Assess building access, working hours and site restrictions; if the office will remain occupied during the work, include any phasing requirements in your comparison. Ask each provider to identify which conditions it has allowed for and which still need to be understood.

Keep technical scope and site constraints visible as separate lines in your notes. A response that addresses a technical requirement does not, by itself, explain how access or working hours will be handled. Record each unresolved item and ask the provider a specific follow-up question before treating the proposal as aligned with your brief.

For each item, make a simple record of the requirement, the response given and any assumption or open question. This helps you distinguish a proposal that addresses a stated need from one that refers to the topic without showing how it applies to your project. If a site restriction changes what you are asking the provider to plan for, state that condition alongside the relevant requirement so the response can be considered in context.

Make delivery responsibility explicit across the project team

Procurement route is part of your comparison, but its label does not tell you who owns each project task. The route can be a design-and-build partner, a traditional consultant-led approach or a hybrid. Compare the responsibilities described for your project rather than assuming that a route name settles them.

Ask for responsibilities to be made clear in the proposal, including any handovers or interfaces involving other project parties. If a task has no named owner, or two parties appear to assume the other will handle it, record that as an open point. Ask for clarification before comparing the routes as though they offer the same scope.

You can make this check concrete by listing the project tasks relevant to your brief, then noting the proposed responsible party beside each one. Add a separate line for handovers and coordination between parties. Where the proposal does not make an owner or interface clear, leave it unresolved in your comparison rather than assigning responsibility yourself.

Your aim is not to choose a route from its label alone. It is to understand what each proposed team will do, how responsibilities connect and what your organisation would still need to arrange.

Compare cost assumptions and programme stages like for like

Cost and programme belong in the same comparison because a design proposal is difficult to assess without a view of both. Use the same project scope as the basis for each response, then note the assumptions and gaps rather than comparing headline totals in isolation.

A project cost plan can allow for:

• construction and furniture;
• professional fees and technology;
• statutory approvals;
• contingencies; and
• VAT, where applicable.

Ask how the proposed cost plan accounts for these areas and which items are included, assumed or still to be priced. Keep any unanswered item visible in your comparison. This helps you distinguish a cost plan that addresses the stated project categories from one whose boundaries are not yet clear; it does not turn an estimate into a confirmed price.

For programme, map the stages from design through approvals, procurement and construction to move-in and handover. Ask each provider to show how its proposed programme covers those stages and to identify assumptions or dependencies that affect the sequence. Compare like with like: if one response includes a stage or activity that another does not address, record the difference rather than treating the timelines as equivalent.

Separate proposal evidence from claims that still need checking

A comparison scorecard helps you separate detail you can see in a proposal from points that remain open. Use the same rows for each provider, and label each response addressed, partly addressed or open. These labels record how fully the proposal answers your brief; they are not a provider ranking or independent verification.

Keep evidence and assertion distinct in your notes. A proposal may state that it addresses a requirement; your scorecard should show whether it explains how the requirement is handled and what assumptions remain. Do not turn a polished presentation, a broad promise or a completed scorecard into proof of credentials or a guarantee of project performance.

Use the three response labels consistently. Mark an item addressed when the proposal responds to the requirement you set out; use partly addressed when it responds but leaves a material detail or assumption unresolved; and mark it open when you cannot find a relevant response. Add a short note showing what you based the label on, so the status remains tied to the proposal rather than your overall impression.

Then use the status to choose a proportionate follow-up:

• Addressed: keep the proposal detail beside the corresponding brief item and compare it with the other responses.
• Partly addressed: identify the missing detail and ask for clarification on that point.
• Open: decide whether the unanswered requirement matters to your project. If it does, request a response before relying on the proposal for that decision; if it does not, record the boundary of your comparison.

Do not add the labels together as a score or use them to claim that one provider is objectively superior. They help you see what each proposal answers, where the comparison is incomplete and which questions should shape the next conversation. The method cannot rank providers or verify their credentials.

Assemble the brief and questions for a focused first conversation

A focused first brief gives providers the project facts and questions they need to respond to. Before you approach them, assemble one concise pack with clear distinctions between requirements, known conditions and points that still need to be established.

Use this checklist:

• Project purpose: state what the office project needs to achieve and the objectives you will use to assess proposals.
• People and working pattern: provide team sizes and attendance assumptions. If your working pattern is hybrid, describe it rather than relying on a fully office-based assumption.
• Functional requirements: list the work settings, meeting needs, storage, privacy, technology and any requirements specific to teams or activities.
• Layout and fit-out needs: describe the outcomes you need for layout and branding, furniture specifications and other special requirements. Consult relevant department heads and employees when gathering requirements and preferences.
• Space and building information: share what you know about the condition of the space, services capacity, landlord constraints, compliance issues, access and site restrictions. Mark unknowns as unknowns.
• Technical scope: identify applicable requirements for mechanical and electrical alterations, lighting, ventilation, cooling, acoustics, IT, audio-visual and security.
• Commercial and delivery questions: specify the cost categories you expect the plan to address and ask for a programme covering design, approvals, procurement, construction, move-in and handover.

Use one set of questions for every provider. Ask each to explain how its proposal responds to the same workplace requirements, which building and technical conditions it has considered, what route and responsibilities it proposes, and how its cost assumptions and programme cover the stated scope.

Before the conversation, sort your material into three groups: requirements you have set, information you currently know about the space, and open questions. This prevents an assumption from being presented as a confirmed building condition and shows the provider where a response needs to address an uncertainty. Include the project objectives and working pattern at the front of the brief so the other details can be read against them.

After each conversation, update the same comparison record. Note the response, any assumptions and the next question in separate fields. That gives you a focused way to decide whom to progress and what needs to be established before you make that decision.

Turn the comparison into a clear next step for your project

Your decision should rest on a like-for-like comparison of workplace outcomes, site conditions, delivery responsibilities, cost assumptions and programme. A clear fit-out brief communicates your requirements to the project team and supports design development, cost planning and procurement decisions. Keep it focused on outcomes, and use unanswered questions to shape the next discussion.

A comparison is ready to progress when you can explain how each proposal responds to the same brief and distinguish answered points from those still to be established. That gives you a practical basis for deciding what to do next.

What should you clarify before approaching an office design company?

What should you include in a brief for office design companies?

Set out the project objectives, team sizes and attendance assumptions, growth plans, work settings, meeting needs, storage, privacy and technology requirements. Add known information about the space, technical or site constraints, budget categories and programme expectations. Mark estimates and unknowns clearly, and describe the outcomes you need rather than prescribing a design solution.

How can you compare design-only, design-and-build and hybrid proposals?

Compare the stated tasks and responsibilities, not the route label. Ask who owns each design and delivery task, how handovers and coordination between parties will work, and what falls outside the proposed scope. Keep unclear ownership as an open question until it is clarified.

What should you ask about a proposed office fit-out budget and programme?

Ask which cost categories are included, assumed or still to be priced, including construction, furniture, professional fees, technology, approvals, contingencies and VAT where applicable. Request a programme covering design, approvals, procurement, construction, move-in and handover, and note the assumptions or dependencies affecting it. An estimate is not a confirmed price.

How should you handle building or compliance questions before choosing a provider?

Ask what the proposal has considered about the space’s condition, services capacity, landlord constraints and compliance issues, and what still needs assessment. Treat unresolved points as open rather than assuming the proposed plan is fully tested. Ask relevant project professionals which compliance issues need assessment for this space.