Project Briefing, Scope and Feasibility

Introduction

Interior projects succeed when a client's aspirations are translated into a controlled, measurable and achievable project definition. A client may request “a sophisticated workplace,” “a calm boutique hotel,” or “a more efficient home.” These statements express intention, but they do not yet define what will be designed, procured, constructed, tested or handed over. Project briefing converts intentions into decisions. Scope management then establishes the boundaries of professional responsibility, while feasibility assessment tests whether the proposed outcome can be delivered within the site's physical, regulatory, operational, technical, financial and temporal constraints.

For an interior design manager, this phase is foundational. Errors made during briefing are often expensive to correct later because they become embedded in drawings, specifications, procurement packages and construction work. A disciplined brief therefore functions as both a design instrument and a cost-control instrument.

Learning Objectives

By the end of this chapter, the learner should be able to:

1. Distinguish client aspirations, requirements, assumptions, constraints, exclusions and acceptance criteria.
2. Convert qualitative requirements into measurable scope and deliverables.
3. Construct a scope statement and a work breakdown structure for an interior project.
4. Conduct structured site, regulatory, technical, operational and financial feasibility assessments.
5. Prepare a preliminary cost model, contingency allowance and basic investment appraisal.
6. Establish scope boundaries, decision gates, change controls and responsibility allocations.
7. Recognise ethical, legal, accessibility, safety and governance obligations in project definition.

1. From Client Aspiration to Project Brief

1.1 The briefing problem

A brief is not simply a list of rooms or a collection of aesthetic references. It is an agreed description of the problem to be solved, the outcomes required, the resources available and the conditions under which the project will be judged. Effective briefing reduces ambiguity between client, designer, cost consultant, contractor, suppliers and authorities.

The briefing process normally includes:

• discovery of strategic and user needs;
• collection of factual information;
• identification of constraints and dependencies;
• testing of alternatives;
• agreement of priorities;
• definition of measurable outputs and acceptance criteria; and
• formal approval of the baseline brief.

A brief should distinguish between need and solution. “Provide 40 workstations supporting focused work and collaboration” is a need. “Install a particular imported workstation system” is a proposed solution. Keeping these separate preserves options during design and procurement.

1.2 Layers of project requirements

Requirements can be organised into a hierarchy:

This hierarchy prevents premature design decisions and makes later verification possible. Requirements should be prioritised, for example as mandatory, important or desirable. A useful prioritisation method is to identify which requirements are fixed by law or business necessity, which are negotiable, and which may be removed if budget or programme pressure arises.

1.3 Requirement elicitation

Briefing is an investigative activity. Interviews with the sponsor reveal strategic priorities, while workshops with users reveal workflows and frustrations. Site observation can expose circulation conflicts that users do not articulate. Document review may reveal lease restrictions, landlord standards, fire strategies, maintenance policies or existing defects.

Questions should address:

• Who will use the space, how frequently and for what tasks?
• What must remain operational during the works?
• Which spaces, assets or services are to be retained?
• What future growth, flexibility or technology change is expected?
• What are the client's budget, funding and approval limits?
• What quality, sustainability, accessibility and maintenance outcomes are required?
• Who has authority to approve changes?

A requirement register should record the requirement, source, priority, owner, verification method and status. A verbal request that is not recorded is vulnerable to later disagreement.

2. Scope Definition and Boundary Control

2.1 Meaning of scope

Project scope defines the work and outcomes included in the project. It should address both product scope—the physical and functional result—and project scope—the management, design, procurement, construction, testing and handover activities required to produce it.

A scope statement commonly includes:

• project purpose and objectives;
• site and area boundaries;
• included spaces, systems and services;
• design stages and deliverables;
• procurement and construction responsibilities;
• quality and performance standards;
• programme milestones;
• budget basis and exclusions;
• assumptions and dependencies;
• acceptance criteria; and
• change-control arrangements.

Scope is not the same as scale. A small area can have complex scope if it involves structural alterations, specialist services, heritage controls or live operational conditions.

2.2 Deliverables and acceptance criteria

A deliverable is an identifiable output, such as an approved brief, measured survey, concept package, coordinated construction information, sample board, installed joinery package or commissioning record. Activities such as “coordinate the project” are necessary but should be connected to tangible evidence: meeting records, decision logs, issue registers and approved submissions.

Each significant deliverable should have an acceptance criterion. For example:

Acceptance criteria should be observable, testable or documentable. “High quality” is weak unless quality is defined through standards, samples, tolerances, performance data or inspection procedures.

2.3 Work breakdown structure

A work breakdown structure (WBS) decomposes the project into manageable packages. A typical interior WBS might contain:

1. Project initiation and briefing
2. Surveys and investigations
3. Concept and developed design
4. Technical design and statutory submissions
5. Procurement and contractor appointment
6. Enabling works and protection
7. Construction, finishes and fixed furniture
8. Loose furniture, equipment and specialist installations
9. Testing, commissioning and handover
10. Defects, review and close-out

The WBS should be sufficiently detailed to support estimating, responsibility allocation and progress control, but not so detailed that administration becomes disproportionate. Each package should have an owner, inputs, outputs, dependencies, estimated cost and acceptance condition.

2.4 Scope boundaries and exclusions

Scope boundaries answer the question: where does the project stop? Examples include the leased demise line, landlord electrical distribution, base-build mechanical plant, loose furniture, IT equipment, artwork, signage, external works and post-occupancy support. Ambiguity is especially dangerous at interfaces. A ceiling-mounted device may involve interior design, electrical power, fire protection, information technology and landlord approval.

An exclusions schedule should state what is not included, rather than relying on implication. It should also identify who is responsible for excluded or adjacent work. Exclusions are not a means of avoiding responsibility; they are a means of making responsibility visible.

3. Assumptions, Constraints, Dependencies and Risks

These terms are related but distinct.

• An assumption is treated as true for planning purposes but requires confirmation. Example: existing electrical capacity is assumed adequate.
• A constraint limits available choices. Example: the project must remain within the existing lease boundary.
• A dependency is an event or input on which another activity relies. Example: final furniture selection depends on approved user numbers.
• A risk is an uncertain event or condition that could affect objectives. Example: concealed asbestos may delay demolition.

A controlled assumption register should record the assumption, basis, owner, validation date, consequence if false and response. When an assumption is disproved, it should not silently become a cost or programme problem; it should enter the issue and change-control process.

Risk exposure is often discussed qualitatively using probability and impact. A simple risk-priority score may be used only when the organisation has defined consistent scales:

Here, R is the risk-priority score, P is the assigned probability score and I is the assigned impact score. The score is dimensionless and is not a true monetary expectation unless the scales and interpretation have been formally defined. It should therefore support professional judgement, not replace it.

4. Feasibility Assessment

Feasibility is the structured evaluation of whether a proposed project is achievable and worthwhile. A project can be physically possible but financially unattractive, legally permissible but operationally disruptive, or aesthetically compelling but technically unbuildable. Feasibility should therefore be multidimensional.

4.1 Site feasibility

Site assessment examines the conditions that may affect design, cost and programme. It should cover:

• measured dimensions, levels, access and egress;
• structural grid, floor loading and existing damage;
• windows, daylight, orientation and external outlook;
• existing mechanical, electrical, plumbing, fire and data services;
• risers, plant capacity and service routes;
• hazardous materials and environmental conditions;
• delivery, storage, hoisting and waste-removal arrangements;
• neighbouring occupiers and noise restrictions; and
• building management and landlord requirements.

A site visit is not a substitute for specialist surveys. Where the consequences of uncertainty are significant, intrusive investigation or verification by qualified specialists is justified.

4.2 Regulatory and statutory feasibility

The project team must identify the legal and approval framework applicable to the jurisdiction and building type. Depending on location, this may include building regulations, planning or development controls, fire and life safety, accessibility, health and safety, environmental law, heritage protection, labour requirements and landlord approvals.

Regulatory review should occur early. A design that cannot obtain approval is not feasible, regardless of its visual quality. The team should create an approvals matrix identifying the authority or reviewer, submission requirement, information needed, lead time, fee, decision point and responsible party. Compliance should be evidenced through drawings, calculations, certificates, inspection records or formal approvals.

Accessibility is both a legal and ethical requirement. It should influence spatial planning, routes, doors, sanitary provision, furniture, signage, lighting, acoustics and emergency procedures from the beginning rather than being added as a late adjustment.

4.3 Technical feasibility

Technical feasibility tests whether the proposed design can be safely detailed, coordinated, installed, maintained and operated. Questions include:

• Can the structure support the proposed loads?
• Are ceiling voids and service zones adequate?
• Can ventilation, cooling, drainage and electrical demand be accommodated?
• Are products compatible with fire, acoustic, moisture and durability requirements?
• Can maintenance access be provided without unacceptable disruption?
• Are specialist products available within the programme?
• Can interfaces between trades be clearly defined?

Technical feasibility should be tested through coordinated drawings, specifications, sample reviews, calculations where required, supplier information and constructability reviews. A visually resolved concept is not technically feasible until its interfaces have been examined.

4.4 Operational feasibility

Operational feasibility asks whether the completed environment will work for its users and whether the works can be delivered without unacceptable interruption. It includes workflow, capacity, security, cleaning, maintenance, accessibility, business continuity, staff training and future adaptability.

For a live workplace, a phased decant may be required. For a hospitality project, noise, dust, guest circulation and life-safety routes may be critical. For a healthcare setting, infection control and segregation may dominate. Operational representatives should participate in briefing and review, because a technically compliant environment can still fail its users.

4.5 Financial feasibility

Financial feasibility compares expected cost and value with available funding and the client's decision criteria. A preliminary cost model should identify the cost base clearly: construction-only cost, total project cost, or whole-life cost. It should state whether taxes, professional fees, furniture, equipment, financing, relocation, technology, surveys, authority fees and contingency are included.

A basic cost model may be expressed as:

The terms represent the relevant cost categories in the selected cost basis. They must not be double-counted. If a percentage is used for contingency:

where r is the contingency rate as a decimal and C_base is the defined base cost. Contingency is an allowance for identified uncertainty; it is not permission to spend without control.

For area-based estimating:

where A is the measured area in m² and u is the unit cost in currency/m². This method is suitable for early comparison only. It assumes the benchmark is comparable in location, quality, scope, procurement route, building condition and market period. It should be replaced by elemental or measured estimates as information improves.

#### Worked cost example

An illustrative 600 m² office refurbishment has a benchmark direct cost of £1,450/m². The direct-cost estimate is:

C_direct = 600 × £1,450 = £870,000

Assume professional fees of 10% of direct cost and a 7.5% contingency applied to the direct cost. If authority fees are £12,000, the preliminary total is:

• Direct cost: £870,000
• Professional fees: £87,000
• Contingency: £65,250
• Authority fees: £12,000
• Preliminary total: £1,034,250

This estimate is valid only for the stated assumptions. It does not establish a tender price and should be updated when surveys, design information and market quotations become available.

Financial feasibility may also consider benefits. If an investment produces annual net cash benefits, its net present value can be represented as:

Here, I₀ is the initial investment, F_t is the net cash flow in period t, d is the discount rate per period, and n is the number of periods. NPV is meaningful only when cash-flow timing, discount rate, inflation treatment and project alternatives are defined consistently. A positive NPV indicates value relative to the selected discount rate, not an automatic approval.

5. Turning the Brief into a Control System

A good brief is a baseline, not a static document. As the project develops, requirements are clarified and assumptions are tested. The team should establish decision gates, such as:

1. Brief approval
2. Feasibility approval
3. Concept approval
4. Developed-design and cost approval
5. Technical and statutory approval
6. Procurement approval
7. Handover acceptance

At each gate, the client should approve defined information rather than merely express general satisfaction. The approval record should identify outstanding issues, cost position, programme implications and authorised changes.

A requirements traceability matrix links each requirement to a design response, deliverable and verification method.

Change control should require a description of the proposed change, reason, originator, effect on scope, cost, programme, quality, risk and approvals. Informal instructions are a major source of uncontrolled scope growth. A change is not fully authorised until its consequences and funding route are understood.

6. Roles, Governance and Professional Responsibility

The client or sponsor owns the business case and approves the brief. The interior designer develops the design response within professional competence. The project manager coordinates scope, time, cost, risk and decisions. The cost manager establishes estimates, cost plans and financial reporting. Consultants provide specialist advice. Contractors and suppliers contribute buildability, pricing and technical information. Building owners and authorities impose operational or statutory conditions.

A responsibility assignment matrix, such as a RACI matrix, can clarify who is Responsible, Accountable, Consulted and Informed. It should be used carefully: one party should normally be accountable for a decision, while several parties may be responsible for contributing information.

Ethical briefing requires honesty about uncertainty, competence and conflicts of interest. Designers should not conceal risks to secure approval, specify products for undisclosed personal benefit, or represent unverified information as fact. Personal data gathered during user research must be handled lawfully and proportionately. AI tools may assist with information classification, option comparison or draft registers, but outputs require professional verification. AI should not be treated as evidence of compliance, a substitute for site inspection or an autonomous authority to define scope.

7. Illustrative Case: Riverside House Workplace Refurbishment

Background

Riverside House is a fictional six-storey office building. A technology company wishes to refurbish 600 m² on one floor for 40 employees. The client requests an “innovative, collaborative and premium” workplace with a target budget of £1.0 million and completion within six months. The floor will remain partially occupied during construction.

Problem

The initial request contains conflicting pressures: premium finishes may increase cost; collaboration may increase noise; a six-month programme may be affected by landlord approvals; and the target budget is close to the preliminary cost estimate. Existing service capacity is unknown.

Analysis

The project team conducts stakeholder interviews, a measured survey, service investigations, a landlord review and an operational workshop. The requirement register identifies 40 workstations, six meeting rooms, one accessible meeting room, a staff kitchen, quiet work areas, secure storage and a phased construction strategy. “Premium” is converted into measurable criteria: selected high-quality finishes in focal areas, durable commercial-rated finishes elsewhere, and approved samples.

The feasibility review identifies three risks:

1. Existing cooling capacity may be insufficient.
2. A landlord permit may require four weeks.
3. Construction noise may disrupt adjacent tenants.

The area-based cost model gives £870,000 direct cost. With fees, contingency and authority charges, the preliminary total is £1,034,250, exceeding the target by £34,250.

Approach and solution

The team adopts a value-management strategy rather than simply reducing quality. It retains acoustic treatment and durable flooring, reduces bespoke joinery in non-public areas, standardises meeting-room furniture, and phases decorative upgrades. The client approves a scope boundary excluding laptops and specialist IT hardware. A contingency drawdown procedure is agreed, and the mechanical engineer is instructed to verify cooling capacity before concept approval.

A responsibility matrix assigns the landlord submission to the project manager, cooling verification to the mechanical engineer, and operational decant planning to the client's facilities manager. The programme includes an early approval gate for landlord consent.

Outcome

The revised estimate is brought within the authorised budget through documented scope choices. The cooling survey confirms that additional local equipment is required; this is included before tender rather than discovered during construction. The project proceeds with a phased work plan, and the client accepts the design using the agreed requirements traceability matrix.

Learning points

The case demonstrates that feasibility is iterative, scope boundaries must be explicit, and cost control begins before detailed design. It also shows why a vague quality adjective should be translated into performance and selection criteria. Most importantly, the team preserved value by prioritising outcomes rather than applying indiscriminate cuts.

8. Challenges and Limitations

Briefing is affected by incomplete information, conflicting stakeholders, optimism bias, changing markets and political or organisational pressure. Early cost benchmarks may be unreliable when projects differ in location, procurement, specification or building condition. User workshops may overrepresent confident participants, while quiet or marginalised users may be overlooked. Regulatory interpretation can vary between authorities, and approval times are not always predictable.

These limitations should be managed through explicit assumptions, multiple information sources, specialist review, sensitivity analysis and staged approvals. Feasibility is not a one-time declaration that a project is “possible”; it is a confidence assessment that should become more precise as evidence improves.

Best-Practice Checklist

Before approving a project brief, confirm that:

• the strategic purpose and user outcomes are stated;
• requirements are prioritised and traceable;
• the site and existing conditions have been investigated proportionately;
• statutory and landlord approvals are identified;
• technical interfaces and operational constraints are understood;
• the cost basis, exclusions and contingency are documented;
• assumptions, dependencies and risks have owners;
• deliverables have acceptance criteria;
• scope boundaries and responsibilities are explicit;
• decision gates and change procedures are agreed; and
• ethical, accessibility, safety and sustainability obligations are addressed.

Chapter Summary

Project briefing translates aspirations into requirements, measurable outcomes and acceptance criteria. Scope management defines what is included, what is excluded and who is responsible for each deliverable. A work breakdown structure supports estimating, coordination and control, while assumption and risk registers expose uncertainty before it becomes a claim or delay.

Feasibility must consider site, statutory, technical, operational and financial dimensions together. Early cost models are useful for comparison but depend on clearly stated assumptions and must mature as information improves. Decision gates, requirements traceability, responsibility matrices and formal change control convert the brief into an active management system. Ethical practice requires transparent communication of uncertainty, respect for accessibility and safety obligations, protection of information and professional verification of technology-assisted outputs.

Key Terms

Acceptance criterion: A defined condition or evidence required for approval of a deliverable.

Assumption: A proposition treated as true for planning but requiring confirmation.

Baseline brief: The formally approved project definition against which later changes are assessed.

Constraint: A condition that limits available project choices.

Contingency: An allowance for identified uncertainty within an approved cost basis.

Deliverable: A defined project output that can be reviewed or accepted.

Dependency: An activity, decision or input on which another element relies.

Exclusion: Work or outcome expressly outside the agreed project scope.

Feasibility assessment: Structured evaluation of whether a proposal is achievable and worthwhile.

Requirements register: A controlled record of requirements, priorities, owners and verification status.

Risk: An uncertain event or condition that may affect project objectives.

Scope: The boundaries and content of the work and outcomes to be delivered.

Scope creep: Uncontrolled expansion of requirements without corresponding approval of cost, time or resources.

Success criterion: A measurable condition used to judge whether project objectives have been achieved.

Traceability matrix: A record linking requirements to design responses, deliverables and verification evidence.

Value management: A structured process for achieving required function and performance at appropriate whole-life cost.

Work breakdown structure: A hierarchical decomposition of project work into manageable packages.

Whole-life cost: The cost of acquisition, operation, maintenance, adaptation and disposal over an asset's life.

Review Questions

Short Answer Questions

1. What is the difference between a client need and a proposed design solution?
2. Define an assumption, constraint, dependency and risk.
3. Why should project exclusions be documented?
4. What is the purpose of a requirements traceability matrix?
5. Why is an area-based cost estimate limited during early feasibility?

Long Answer Questions

1. Explain how a qualitative client aspiration can be translated into measurable requirements and acceptance criteria.
2. Describe the principal components of a scope statement for an interior refurbishment project.
3. Compare site, technical and operational feasibility, giving an example of a failure in each dimension.
4. Explain how decision gates and change control protect an interior project from scope creep.
5. Discuss the ethical and governance responsibilities of an interior design manager during briefing and feasibility.

Analytical / Application Questions

1. A client requests a “premium, sustainable and flexible” office within a fixed budget. Develop a requirement hierarchy, identify likely assumptions and propose three measurable acceptance criteria.
2. An early estimate is based on 800 m² at £1,600/m². Professional fees are 9% of direct cost, authority fees are £15,000 and contingency is 8% of direct cost. Calculate the preliminary total and state two limitations of the estimate.
3. A live hotel renovation must retain guest operations while upgrading bedrooms and corridors. Prepare a feasibility investigation plan covering site, regulatory, technical, operational and financial issues, and identify two decision gates.

Multiple Choice Questions with Answers

Question 1

Which statement best describes a project brief?

A. A list of preferred colours and furniture brands

B. An agreed definition of objectives, requirements, constraints, deliverables and acceptance conditions

C. A contractor's final invoice

D. A record of construction defects only

Correct Answer: B. An agreed definition of objectives, requirements, constraints, deliverables and acceptance conditions

Question 2

Which item is an acceptance criterion?

A. The client likes the design

B. The space should feel modern

C. The approved layout provides 40 workstations and six meeting rooms

D. The designer will coordinate the project

Correct Answer: C. The approved layout provides 40 workstations and six meeting rooms

Question 3

What is the primary purpose of a work breakdown structure?

A. To replace statutory approval

B. To decompose project work into manageable packages

C. To select the client's preferred colour palette

D. To calculate depreciation automatically

Correct Answer: B. To decompose project work into manageable packages

Question 4

Which statement correctly distinguishes an assumption from a constraint?

A. An assumption is treated as true pending confirmation; a constraint limits available choices

B. An assumption is always a legal requirement; a constraint is always optional

C. An assumption is a completed deliverable; a constraint is a risk register

D. There is no practical distinction

Correct Answer: A. An assumption is treated as true pending confirmation; a constraint limits available choices

Question 5

Using C_base = A × u, what is the direct cost for 500 m² at £1,200/m²?

A. £60,000

B. £600,000

C. £1,700,000

D. £2,400,000

Correct Answer: B. £600,000

Question 6

If direct cost is £400,000 and contingency is 7.5% of direct cost, what is the contingency allowance?

A. £3,000

B. £7,500

C. £30,000

D. £53,333

Correct Answer: C. £30,000

Question 7

Which feasibility dimension primarily examines whether the completed space supports workflows, maintenance and business continuity?

A. Operational feasibility

B. Aesthetic feasibility

C. Geographical feasibility

D. Historical feasibility

Correct Answer: A. Operational feasibility

Question 8

What is the main purpose of an exclusions schedule?

A. To conceal project risks

B. To define work outside the agreed scope and clarify interfaces

C. To eliminate the need for a cost plan

D. To approve all design changes automatically

Correct Answer: B. To define work outside the agreed scope and clarify interfaces

Question 9

Which statement about contingency is most accurate?

A. It is unrestricted money that can be spent without approval

B. It is an allowance for identified uncertainty within a defined cost basis

C. It is always equal to professional fees

D. It replaces the need for risk management

Correct Answer: B. It is an allowance for identified uncertainty within a defined cost basis

Question 10

Why should AI-generated project information be professionally verified?

A. AI outputs are automatically statutory approvals

B. AI cannot produce any text

C. AI may misinterpret incomplete information and cannot replace site, technical or regulatory judgement

D. Verification is required only for decorative decisions

Correct Answer: C. AI may misinterpret incomplete information and cannot replace site, technical or regulatory judgement