Last edited 20 Jul 2021

Project brief for design and construction



[edit] Introduction

The project brief is the final stage in the process of defining the client's requirements for the development of a built asset:

The project brief will evolve through the project brief stage and the concept design stage with the benefit of information gained from consultations with the client and other stakeholders and ongoing design development.

[edit] Preparation

Preparation of the project brief is likely to be coordinated by the lead consultant.

As well as gathering information about physical requirements, the briefing process should:

It may be developed based upon:

[edit] Inclusions

The project brief may include:

[edit] A description of the client

  1. A description of the client's brand, culture and organisation.
  2. A description of the client's vision, mission and objectives.
  3. A description of the client's priorities and the criteria that will be used to measure success.
  4. Organisational structure and decision making processes.
  5. Changes to the client that the project will bring about.
  6. Interfaces with other projects.
  7. Client policies that may be applicable to the project (for example; transport policy, energy policy, natural ventilation policy, sustainability policy).
  8. Client preferences for the project (for example; image, use of local materials, use of landscape, etc.), and quality expectations (including health and safety, sustainability and design quality).
  9. A description of the principles that will be adopted in the development of the design.

[edit] Site information

  1. Building surveys.
  2. Site surveys.
  3. Information about ground conditions.
  4. The location and capacity of utilities.
  5. Access and other constraints.
  6. Legislative constraints.
  7. Existing planning consents.

[edit] Spatial requirements

  1. Schedules of accommodation, areas and special requirements.
  2. Schedules of users (including external users), their numbers, departments, functions, organisational structure and operational characteristics.
  3. Spatial policies (for example, open plan or cellular offices, daylighting requirements, temperature ranges and acoustic standards).
  4. Required adjacencies, groupings and separations.
  5. Zoning.
  6. Circulation guidelines and identification of major circulation flows.
  7. Phasing.

[edit] Technical requirements

  1. Structural strategy (columns and gridlines to be adopted, special loads, floor-to-ceiling heights).
  2. Servicing requirements, including specialist requirements.
  3. Comfort conditions and level of user control.
  4. Acoustic requirements.
  5. Equipment requirements.
  6. Specialist requirements for furniture, finishes, fixtures and fittings.
  7. Information and communications technology (ICT) requirements.
  8. Requirements for specialist processes and plant.
  9. Fire compartments.
  10. Maintenance and cleaning requirements.
  11. Likelihood of future change (for example, staff numbers) and flexibility required.
  12. Sustainability objectives and energy use targets.
  13. Safety and security requirements.
  14. Resilience to potential hazards or threats.
  15. Waste and water management.
  16. Pollution control.
  17. Flexibility and future uses.
  18. Durability and lifespan.
  19. Other performance requirements.
  20. Benchmarking information.

[edit] Component requirements

  1. Long-lead items.
  2. Potential requirement for specialist design or specialist contractors design.
  3. Cladding strategy and materials selection procedures.

[edit] Project requirements and other issues

  1. Planning requirements.
  2. Outcome of any consultation processes.
  3. Budget.
  4. Project programme and key milestones.
  5. Known risks.
  6. Targets for post occupancy evaluation outcomes and other performance targets.

The project brief will become increasingly detailed throughout the project brief and concept design stages, and may ultimately include very specific information such as room data information for each room.

The project brief should be frozen at the end of the concept design stage and change control procedures introduced to prevent further changes without appropriate justification and authorisation.

[edit] Presentation

The project brief is likely to be presented as a report, however, where possible, information and requirements should be scheduled in a database or spreadsheet format that will be easy to expand and will be easy to use to test whether proposals satisfy requirements later in the project.

On projects that adopt building information modelling (BIM), the employer's information requirements (EIR) may be considered a parallel document to the project brief. Whereas, the project brief sets out the requirements for the physical built asset, the employers information requirements define the information the employer needs to procure to enable them to develop and operate the built asset.

For more information, see Employer's information requirements.

DBWCTA Deltek 001.png

[edit] Related articles on Designing Buildings Wiki

[edit] External references


Designing Buildings Anywhere

Get the Firefox add-on to access 20,000 definitions direct from any website

Find out more Accept cookies and
don't show me this again