What Is a Construction Project Brief – and What Isn't?

Why a list of requirements isn't necessarily a brief, and why getting the distinction right matters.

A client approaches a project manager with a clear idea of what they want to build, a budget and a deadline. They may already have architectural drawings and a detailed list of specifications.

They believe they have a project brief. Do they?

Knowing what you want to build isn't necessarily the same as understanding what the building needs to achieve. Nor does it mean that everyone involved agrees about the requirements.

A good construction project brief is more than a document. It is the outcome of questioning, discussion and agreement about what a project needs to deliver, for whom and within what constraints.

What is a construction project brief?

A construction project brief establishes the purpose of a proposed project and the requirements it needs to satisfy. It should provide sufficient clarity to allow the project team to make informed decisions about design, cost, programme and delivery.

Depending on the stage of the project, it might identify:

• The purpose of the project and the outcomes the client wants to achieve.

• The people who will use, operate or be affected by the completed building.

• Essential requirements and areas where there is flexibility.

• Budget, programme and other constraints.

• Statutory, operational and technical considerations.

• The stakeholders involved in making decisions.

• What successful delivery will look like.

The brief doesn't need to contain every detail from the outset.

A client commissioning a new school may initially know how many pupils it needs to accommodate, the educational objectives and the broad budget, without having determined the layout of every classroom.

Similarly, a restaurant operator may know what sort of dining experience they want to offer before deciding precisely how many tables, kitchen appliances or staff facilities are required.

Those details will develop as the project progresses. What matters is that everyone understands the underlying objectives and that decisions about the detail are made in pursuit of them.

What a construction project brief isn't

Clients commonly bring valuable information to a project which doesn't necessarily constitute a complete brief.

A wishlist

A list of rooms, equipment or features tells the project team what someone would like. It doesn't necessarily explain why those things are needed or which are essential.

A restaurant operator might specify 120 covers because that figure underpins their existing business model. However, is 120 the minimum required for the restaurant to be commercially viable? Is it achievable within the proposed premises? Could a different configuration or operating model deliver a better result?

The number matters, but understanding the reasoning behind it matters more.

A budget and completion date

Cost and programme are fundamental constraints. They aren't, however, a substitute for defining the outcome.

A project can have a fixed budget and a clear deadline without anyone having established whether the proposed requirements are achievable within them.

Architectural drawings

Drawings communicate design proposals. They don't necessarily establish whether those proposals satisfy the needs of everyone who will use or operate the building.

A design can be technically competent and still fail to meet an important operational requirement that was never properly identified.

A predetermined solution

Sometimes clients arrive with a solution before the underlying problem has been fully explored.

For example, a business might decide that it needs another meeting room for 12 people. Its actual requirement may be to accommodate confidential meetings involving up to 12 people without disrupting normal operations.

Those are different propositions. The second allows the design team to consider whether existing space could be reconfigured before committing to additional construction.

An unchangeable document

A brief should provide a reliable basis for decision-making, but it need not remain unchanged throughout the project.

Requirements may evolve as information becomes available, stakeholders contribute and design options are tested. There is, however, an important distinction between developing the brief and changing requirements that have already been agreed.

Changes should be considered in the context of their implications for cost, programme and the project's objectives, and approved by those with the appropriate authority.

The questions that make a brief useful

An experienced project manager doesn't necessarily have one brilliant question that transforms a client's understanding of their project.

More often, it takes a series of questions:

• What are you trying to achieve?

• Who needs to use the finished space?

• What is essential, and what is desirable?

• What assumptions have been made?

• Who else needs to be consulted?

• What happens if the budget or programme won't accommodate everything requested?

The purpose isn't to challenge every decision for the sake of it. It is to establish what the client needs, test the assumptions behind the requirements and make the implications of different choices clear.

Darren Hewitt, Iconic's Director of Project Management, places particular emphasis on what happens after those questions have been asked.

The project manager needs to play the brief back to the client, confirming that everyone has the same understanding of what is being delivered.

It sounds straightforward but becomes particularly important when the client isn't a single decision-maker.

On one project, decisions were made through a committee involving several stakeholders. The person who initially commissioned the project provided a reasonable account of its objectives, but that account did not necessarily capture everyone's expectations.

Unless those expectations are established and reconciled, disagreements can remain hidden until the design is well advanced.

The project manager's role is to help bring those differences into the open while there is still an opportunity to address them.

What happens when expectations aren't aligned?

A project doesn't need to begin with a fundamentally inadequate brief for difficulties to emerge. Even a well-understood overall objective can conceal disagreements about the detail.

Iconic encountered this on a substantial commercial refurbishment project.

The project involved two principal client interests: the building's occupiers and a central property management function. Although both were involved in delivering the same project, their expectations and priorities were not fully aligned.

As the project progressed, further requirements were introduced, including changes to the facilities and the extent of the refurbishment. Some areas had initially been regarded as relatively light-touch works, while others required considerably more extensive intervention.

The resulting changes placed pressure on both the budget and the programme, generating repeated discussions about cost, approvals and the final scope of works.

The difficulty wasn't that the client had no idea what it wanted. It was that different stakeholders had different expectations, and the scope continued to develop without those expectations being consistently reconciled.

This experience illustrates why a project brief must do more than describe a proposed building. It must also establish who has authority to make decisions and how changes to the agreed requirements will be managed.

When the detail becomes unexpectedly important

Another example comes from an education development involving a complex planning approval.

The broad objective of the project was well established, but particular design details associated with the planning permission became contentious.

Certain stakeholders were reluctant to implement elements of the approved design that had formed part of the concessions agreed during the planning process. From their perspective, these may have appeared to be relatively minor details. From the planning authority's perspective, they were integral to the approved scheme. Resolving the disagreement required considerable time and effort.

The lesson is that a requirement's importance isn't necessarily proportionate to its physical scale or cost. A relatively small design element may carry significant planning, legal or stakeholder implications.

Developing a brief therefore involves more than recording the client's preferences. It also requires identifying the obligations and constraints within which those preferences must be delivered, and ensuring that the client understands their implications.

The value of getting it right

A well-defined brief doesn't eliminate every difficulty, but it provides a stronger basis for managing them.

Iconic's experience of delivering a nationwide programme of refurbishment works for a high street retail bank illustrates the value of clear requirements and stakeholder engagement.

The programme involved approximately 100–150 projects each year, delivered against a broadly consistent scope of works.

With the requirements clearly established and stakeholders at different management levels engaged, the team could deliver the programme efficiently and consistently across multiple locations.

The benefits of a clear brief aren't limited to avoiding mistakes. They also include more efficient decision-making, consistency and the ability to deliver repeatable programmes without continually revisiting fundamental questions.

Who is responsible for the project brief?

Ultimately, the client owns the project's requirements and the decisions that determine what will be delivered.

The project manager can help develop the brief by asking questions, challenging assumptions, coordinating input and explaining the implications of different options. Architects, engineers and other specialists contribute their expertise as the brief develops into design proposals and technical requirements.

The precise responsibilities will depend on the project and the appointments involved, but there is one important limitation to what a project manager can achieve.

The project manager cannot resolve every disagreement within the client's organisation on the client's behalf.

When a project involves multiple departments, committees or business functions, those stakeholders need to communicate with one another and establish their collective priorities.

Competing interests, internal politics and the need for compromise are often unavoidable.

An effective project manager can facilitate those conversations, provide objective information and help identify the consequences of different decisions. The client must still take ownership of the choices.

Without that ownership, even the most carefully prepared document can become a source of disagreement rather than a shared understanding.

A good brief doesn't need every answer

At the beginning of a construction project, uncertainty is inevitable. The design may still be developing, technical investigations may be outstanding and stakeholders may have legitimate questions that cannot yet be answered.

A good brief doesn't pretend that those uncertainties have disappeared. It establishes what is known, what remains to be decided, who has the authority to make those decisions and how the requirements will develop.

Above all, it creates a shared understanding of what the project is intended to achieve.

There is often pressure to get started: appoint designers, commission surveys, develop drawings and establish a construction programme.

Starting quickly isn't necessarily the same as starting well.

Taking the time to establish and agree the brief gives every subsequent decision a better foundation. That is time well spent.

Author

Lizzie Hewitt

Lizzie is the driving force behind Iconic Project Management. She thrives on crafting creative strategies that set the company apart, ensuring every project delivers maximum value for clients.

Her leadership is built on a people-first approach—empowering the team with the right tools, support, and culture to do what they do best: deliver outstanding projects on time, on budget, and on brief.

Passionate about innovation and continuous improvement, Lizzie is committed to making the construction industry a place where people and projects thrive.