Introduction
Every building begins as a conversation before it becomes a drawing. Somewhere, a person or an institution says: “We need this, for these people, on this site, for this much money, by this date.” When that conversation is written down, shared and agreed, it becomes a project brief. It is the least glamorous document in the life of a building, and one of the most consequential. Architects can produce brilliant drawings in response to a poor brief, but the building will still struggle. Conversely, a clear brief can steer an average design team toward a useful, buildable and loved result.
This article works through eight questions: what a project brief is; how it relates to architecture; who writes it; for whom it is written; what it contains; why it matters; whether it differs from country to country; and what examples exist from Europe, the United States, Asia and the United Arab Emirates. In every section, the argument is anchored in a real project or a well-known piece of practice. Cost and date figures are quoted from widely reported public sources and are approximate, so please verify them before citing in formal work.
What is a project brief?
A project brief is the written statement of what a client wants to achieve with a building project and the conditions under which it must be achieved. It records the purpose, the users, the activities to be accommodated, the quality expected, the budget, the program and the constraints. It is the point of departure for design, and it is the document against which the finished building will later be judged.
The word has several close relatives, and the terminology varies. In the United Kingdom, the client brief, initial project brief and final project brief are standard terms. In the United States, practitioners usually speak of the program or the owner’s project requirements. In France, the equivalent is the program; in the Netherlands, the programma van eisen; in Germany, the Raumprogramm and the Auslobung (the competition brief). In China, the corresponding instrument is often called a design task book (设计任务书). These are not identical documents, but they play the same role: translating a need into an instruction a design team can act on.
The brief should be distinguished from two things it is often confused with. First, it is not the design. The brief says what problem must be solved; the design proposes how. Second, it is not the contract. A contract allocates responsibilities and fees; a brief defines the objectives those responsibilities serve, although it is commonly attached to the contract as a schedule.
Example from practice: Maggie’s Centres. One of the most celebrated briefs in contemporary architecture was not written by a developer or a government agency but by a cancer patient. In 1994, Maggie Keswick Jencks, treated for cancer in Edinburgh, wrote an essay titled A View from the Front Line. In it she described what a place of support next to a hospital should feel like: welcoming, domestic in scale, with a kitchen table at its heart, views of the outdoors, and spaces to be alone or with others. After her death in 1995, her husband, the architectural theorist Charles Jencks, and her nurse Laura Lee turned this text into the founding brief for the first Maggie’s Centre in Edinburgh, which opened in 1996. Architects including Frank Gehry, Zaha Hadid, Richard Rogers and Steven Holl have since designed Maggie’s Centres, each starting from the same brief. A two-page, humane text became a design instrument for a whole building type, which shows what a brief is at its best: a clear statement of purpose that leaves the design response open. The architectural brief given to every Maggie’s architect, and Maggie Keswick Jencks’s founding essay, can be downloaded from the charity’s publications page (Edinburgh, Scotland): maggies.org/about-us/publications.
What is its relation to architecture?
Architecture is often described as the resolution of a problem, and the brief is the formal statement of that problem. Without it, design has no criteria; a building can be beautiful but have no way of being judged right or wrong. The relationship is therefore one of problem and response, but it is not a simple one-way street. In practice, briefing and designing influence each other. Designers test the brief by sketching; sketches reveal that the brief is incomplete, contradictory or unrealistic; and the brief is revised.
This interplay has been formalised in the discipline of architectural programming. In the United States, the Houston firm CRS (Caudill Rowlett Scott), working from the 1950s, and in particular William Peña, developed a method of separating “problem seeking” from “problem solving”. The idea, later published in the book Problem Seeking: An Architectural Programming Primer by Peña and Steven Parshall, is that the architect’s first task is to establish the facts, goals, needs and future conditions of the client, and to state the real problem before drawing a line. CRS applied this approach to schools and hospitals, where the program was developed with teachers, doctors and administrators before design began.
The brief also has a legal and procedural relationship to architecture. In the United States, the American Institute of Architects (AIA) standard owner–architect agreement (B101) assumes that the owner supplies a program before schematic design begins, and treats detailed programming as an additional service. In Germany, the fee regulations for architects and engineers (HOAI) make the clarification of the client’s requirements, the Grundlagenermittlung, the very first work phase, before any design phase starts. That sequencing means the design cannot be treated as complete until it is tested against a brief that the client has formally approved.
Example from practice: Seattle Central Library. When the City of Seattle commissioned a new central library in the late 1990s under its “Libraries for All” bond program, the formal brief described a conventional list of spaces. The architects, Rem Koolhaas and Joshua Prince-Ramus of OMA, together with local partners LMN Architects, did not simply accept the list. They re-analysed it, grouping the library’s activities into clusters, separating stable functions from flexible ones, and rethinking how books, staff, meeting rooms and the public would be organised in a continuous “book spiral” and a large central “mixing chamber”. The library opened in 2004. The project is an illustration of the dialogue between brief and design: the brief was a starting point, but the design team’s analysis of it generated the building’s distinctive form.
Who writes the project brief?
In principle, the brief belongs to the client, because only the client can decide what the project is for. In practice, it is rarely written by the client alone. At least five types of author appear in real projects.
The client or end-user organisation. Small clients, such as a family building a house or a school wanting an extension, often write their own brief, sometimes with help from the architect. The advantage is ownership; the risk is that important issues, such as accessibility, maintenance or planning constraints, may be overlooked.
An in-house client team. Large institutions, such as universities, hospitals and government departments, normally have estates or facilities departments that write the brief after consulting the users. In the United States, the General Services Administration (GSA), which procures federal buildings, issues a Program of Requirements for each project, supported by its Facilities Standards (P100).
An independent briefing consultant. In France, a professional programmiste is commonly commissioned to write the program. French public procurement practice, shaped by the 1985 loi MOP on public project ownership, requires the public client (maître d’ouvrage) to define the program and the overall budget envelope before an architect is appointed. This separates the author of the question from the author of the answer.
A project manager or cost consultant. On large UK and international projects, the client’s project manager frequently compiles the brief and the budget together, because the two have to be consistent.
The architect. In many cases the architect assists the client in refining the brief, particularly in the early stages. Under UK and US appointment forms, briefing support can be included in the architect’s services. The danger is conflict of interest: if the architect writes the brief, the client may not realise that the problem has been framed to suit a preferred solution.
Example from practice: the 9/11 Memorial competition. After the destruction of the World Trade Center in 2001, the Lower Manhattan Development Corporation (LMDC) organised an international design competition for the memorial. The brief was not written by an architect. It was the product of a long process of consultation with victims’ families, residents, civic groups and public officials. It included a mission statement and a program that specified, among other things, that the footprints of the Twin Towers should be recognised and that the names of the victims should be included. More than 5,000 entries from dozens of countries were submitted, and in January 2004 Michael Arad’s design, Reflecting Absence, was selected, later developed with landscape architect Peter Walker. The example shows that a brief can be a collective, public and highly emotional document, written by a client body on behalf of many stakeholders. The competition guidelines, including the Memorial Mission Statement and Program, are available through the National 9/11 Memorial & Museum collection (New York, USA): collection.911memorial.org/lmdc_competition.
For whom is it written?
A brief is addressed to several audiences at once, and good briefs are written with each of them in mind.
The design team. The primary audience is the architect and the engineers, landscape architects and other consultants who will respond to it. They need to understand the objectives, the scale of the project and the freedom they have.
The client’s decision-makers. The brief is also a way for the client’s own board, committee or sponsor to agree what it wants. Many briefs fail because different people inside the client organisation hold unspoken and incompatible expectations. Writing the brief forces those differences into the open.
Funders, regulators and approval bodies. Banks, grant-giving bodies, planning authorities and ministries often require a brief to justify funding or permission. In European Union-funded or publicly procured projects, the brief is a basis for demonstrating value for money and compliance with procurement rules.
Competition entrants and bidders. When the architect is chosen through a competition or tender, the brief is the document that every candidate reads. Under the EU public procurement framework, Directive 2014/24/EU covers “design contests”, and the competition brief must give all participants the same information so that selection is fair.
The contractor. Under design-and-build procurement, the brief, together with the client’s requirements, forms the starting point of the contractor’s own design. In the United States, design-build teams respond to a Request for Proposals that includes “criteria documents”.
Users and the public. In the long run, a brief is also an unwritten promise to the people who will use the building. For public buildings, it is increasingly drafted with public consultation so that residents recognise their own needs in the result.
Example from practice: Helsinki Central Library Oodi. The City of Helsinki ran an open international architecture competition for a new central library in 2012, which was won by ALA Architects. The brief, developed over several years, drew on extensive public consultation about what residents wanted from a twenty-first-century library: not just books, but workshops, studios, a cinema, meeting rooms and a place to be together. The library opened in December 2018 and has been reported as one of the most visited public buildings in Finland. Here the brief was written for the competitors, but its real audience was the city’s residents, and the result reflects this.
What are the components of a project brief?
The contents of briefs vary with project size and country, but a comprehensive brief normally covers the following elements.
1. Background and context. Why is the project being undertaken? The brief should describe the client organisation, the problem or opportunity driving the project and the strategic case for building.
2. Vision and objectives. The project’s purpose in a few sentences, together with measurable objectives. A good vision statement is concrete enough to guide a decision but not so concrete that it dictates the answer.
3. Stakeholders and decision-making. Who is involved, who decides, and how decisions will be made and recorded. This section often prevents later disputes.
4. Site and context information. Location, ownership, boundaries, access, surveys, services, ground conditions, heritage designations and planning constraints.
5. Functional requirements and space program. The heart of most briefs. This lists the activities to be accommodated, the spaces needed, their sizes, their adjacencies, and the number and type of users. It is often presented as an accommodation schedule with room names and areas.
6. Quality and performance requirements. The standard of finishes, structure, durability, acoustic and thermal comfort, accessibility, sustainability targets and any certification being sought, such as BREEAM, LEED or Passivhaus.
7. Budget and cost plan. The funds available, what they must cover, and the allowance for contingencies. A brief without a realistic budget is, in effect, a wish list.
8. Program and milestones. Key dates, such as funding deadlines, opening dates, planning submissions and the construction period.
9. Constraints, risks and assumptions. Legal, technical, financial and political constraints, plus the assumptions on which the brief has been written.
10. Operation and lifecycle. How the building will be run, maintained, adapted and eventually decommissioned. Increasingly, clients ask for whole-life cost thinking and flexibility for future change.
11. Procurement and team requirements. How the team will be selected, what services are expected, and what deliverables are required at each stage.
12. Success criteria. How the client will judge whether the project has succeeded, ideally including post-occupancy evaluation.
Example from practice: the Beijing National Stadium. For the 2008 Olympic Games, Beijing ran an international competition in 2002–2003 for its main stadium. The brief set out the capacity (about 91,000 seats at the Games stage, with some of them temporary), the athletics and football functions, the legacy use after the Games, and a retractable roof. Herzog & de Meuron, with the artist Ai Weiwei and the China Architecture Design & Research Group, won with the “Bird’s Nest” design. In 2004, as the project was reviewed for cost and structural complexity, the retractable roof was dropped from the scheme. The example shows how the components of a brief interact: a functional requirement (the roof) came into conflict with the budget and the program, and the brief had to be revised.
What is its importance?
The importance of the brief can be summarised in five points.
It aligns expectations. The most common source of project disputes is the gap between what the client thought it had asked for and what the design team understood. A written, agreed brief narrows that gap.
It controls cost and time. Changes in the brief after design has begun are among the largest causes of cost overruns and delays, because every change cascades through drawings, specifications and contracts. A stable brief is the first form of cost control.
It provides a basis for judgement. Without a brief, there is no objective way to choose between competing designs in a competition, or to assess whether the completed project was successful.
It focuses creativity. Contrary to a common belief, a good brief does not restrict architects; it gives them a precise question to answer creatively.
It protects the public interest. For publicly funded projects, a brief shows that the money is being spent for defined public benefits.
Two famous cases show the cost of getting the brief wrong.
Example from practice: the Sydney Opera House. In 1955 the New South Wales government launched an international competition for an opera house on Bennelong Point. Jørn Utzon’s winning scheme was chosen in 1957 from 233 entries. The competition brief, however, called for a large hall for both opera and concerts and a smaller hall for drama, and it was revised after the competition, partly to separate the opera and concert functions into different halls, which affected the geometry Utzon had designed. Work started early, before the structural design was resolved, and political disagreement over cost and changes led to Utzon’s resignation in 1966. The building was completed in 1973 at a cost of about A$102 million, against an early estimate of about A$7 million. The case is often cited as proof that an unsettled brief, combined with premature construction, can be extremely expensive, even when the design itself is a masterpiece.
Example from practice: the Scottish Parliament building at Holyrood. The building, designed by Enric Miralles and EMBT with RMJM, was opened in 2004. Early estimates ranged from about £10 million to £40 million; the final cost was approximately £414 million. The public inquiry led by Lord Fraser, reporting in 2004, identified weaknesses in how the project was defined and managed in its early stages, including an evolving brief, unrealistic early cost estimates and unclear lines of responsibility. The lesson is that a brief must be accompanied by a credible budget and a clear governance structure.
Does the brief differ in its written components depending on context and country?
Yes. The underlying purpose is universal, but the written form, the level of detail, the legal status and the author vary with legal systems, procurement traditions, professional culture and the role of the state. Some of the main differences follow.
Legal status. In some countries the brief is a quasi-legal document. French public projects require a formal program approved before design begins, and the architect’s mission is defined by reference to it. In Germany, competition briefs follow established rules, and architects’ fees and services are structured by the fee scale for architects and engineers (HOAI). In the UK and the US, the brief is more often a contractual or project-management document, adopted through the owner–architect agreement (for example the AIA B101 form in the US).
Level of detail. Briefs in North America tend to emphasise a detailed space program with areas, adjacencies and equipment lists, often with a separate set of owner’s project requirements for building performance, as set out in commissioning guidance such as ASHRAE Guideline 0. In the UK, briefs often start as short strategic documents and are developed over successive stages. In Japan and China, the early planning documents may be more closely tied to government approval processes, with the brief set at an institutional level and refined in a basic design phase.
Procurement route. Where architects are selected through competition, as is common in Germany, Finland, Switzerland, France and across the Nordic countries, the brief is written primarily as a competition document, and it must be complete enough to enable comparison between entries. Where design-and-build is common, as in much of the US and in large Asian infrastructure and commercial projects, the brief is written as a performance specification or a set of employer’s requirements that a contractor-led team will interpret.
Sustainability and regulation. European briefs increasingly cite the EU Energy Performance of Buildings Directive and national targets for nearly zero-energy buildings. US briefs may cite LEED, ASHRAE standards and local codes. Asian briefs may refer to national green building labels such as Singapore’s Green Mark, Japan’s CASBEE or China’s Three Star system.
Social and cultural content. Briefs reflect local values. A Nordic library brief may stress democratic access and informality; a Gulf cultural project brief may emphasise international prestige; a Japanese public building brief may prioritise earthquake resilience and efficient use of constrained urban land; and a Chinese urban masterplan brief may carry strong requirements regarding scale, symbolism and phasing.
Example from practice: France’s loi MOP in action. When the Centre Pompidou competition was launched in the early 1970s, the French state defined a program for a major cultural centre combining a modern art museum, a public library, a music research institute and an information centre. This program, prepared by the client before any architects were involved, attracted 681 entries from many countries. The winners, Renzo Piano, Richard Rogers and their team, turned the program’s call for flexibility and public openness into the building’s exposed structure and services. The French system, later formalised and reinforced in the 1985 MOP law, shows the strength of a state-written program as the foundation of public architecture.
Example from practice: Cool Abu Dhabi (United Arab Emirates). In February 2020 the Department of Municipalities and Transport (DMT), the Abu Dhabi government body responsible for urban planning and transport, launched “Cool Abu Dhabi”, an open international ideas competition built around a single question: how can public space remain comfortable in an extreme climate, given the urban heat island effect? The brief is a compact public-sector example of the form. It opens with the client’s mandate and background, states the challenge in measurable terms (outdoor thermal comfort expressed through the Universal Thermal Climate Index, with a focus on the shoulder months of May and October), and defines a prototypical site: a small plaza surrounded by a surface car park and 15-storey buildings, with the buildings and the parking provision left unchanged. It then sets five success criteria (visionary, anticipatory, replicable, robust and local), names the jury, and closes with the schedule, the prize fund (US$100,000, in up to ten awards), the submission requirements and the terms and conditions. More than 300 entries from 67 countries were received.
What the brief leaves out is as instructive as what it contains. There is no budget and no accommodation schedule, because the client was seeking ideas rather than a building, and the site is deliberately hypothetical so that the solutions can be replicated across the city. The terms also state that the DMT is not committed to build any entry, while reserving the right to base future designs on components of the proposals, and the winners were offered a chance to present to policy-makers. The brief is therefore an instrument of policy as much as a design document, which is typical of state-led briefing in the Gulf, where climate resilience and sustainability now stand alongside prestige. The original materials are available from the competition website (Abu Dhabi, UAE) at coolabudhabi.com, and the full competition brief can be read as a PDF at architexturez.net.
Examples from EU, USA, Asian and UAE projects
This final section collects project examples by region, with a short note on what each one teaches about briefing.
European Union examples
Berlin Brandenburg Airport (Germany). The new airport was planned to open in 2011 and finally opened in October 2020. Its delays and cost increases, with total costs reported at several times the early estimates, have been attributed to many causes: complex governance, inadequate planning and, importantly, repeated changes to requirements, such as enlargement of the terminal and problems with the fire protection and smoke extraction systems. It is a clear example of how a brief that continues to change during construction undermines a project.
Elbphilharmonie, Hamburg (Germany). Designed by Herzog & de Meuron, the concert hall opened in 2017 after years of delay. The public share of the cost rose from the €77 million originally planned to roughly €789 million. The project began with an ambitious but incompletely developed brief and an early contract, and the later changes led to long disputes between the city and the contractor. It is now a celebrated building, but its history is a warning about starting construction before the brief and the design are mature.
Helsinki Central Library Oodi (Finland). As discussed above, the brief was formed through years of public dialogue, and it is a positive example of participatory briefing in the Nordic tradition.
Centre Pompidou (France). A state-written program that gave a young team the freedom to reinvent the museum.
United States examples
The 9/11 Memorial (New York). A consultative, public brief written by a development corporation on behalf of many stakeholders, with a mission statement at its core.
Seattle Central Library. A bond-funded public library where the architects re-interpreted the program to generate new organisation of the building.
GSA federal buildings. The GSA’s Design Excellence Program connects each federal project’s program of requirements to a peer-reviewed process for selecting architects, aiming at high design quality in courthouses and federal offices. The brief in these cases is a formal document tied to national standards (P100), published and updated by the agency.
Yale and other university campuses. Universities in the US commonly commission a programming study from a specialist consultant before selecting the architect, and the resulting program document becomes part of the architect’s agreement. This model is routine across higher education, healthcare and school building in North America.
Asian examples
Japan National Stadium (Tokyo). The first competition in 2012 was won by Zaha Hadid Architects. In 2015, the Japanese government cancelled the design because estimated costs had risen sharply, to roughly ¥250 billion. A new competition followed in late 2015 with a revised brief that set a much stricter cost ceiling, reported at about ¥155 billion, and required a combined design-and-build team. The winning team, led by the contractor Taisei Corporation with Azusa Sekkei and Kengo Kuma and Associates, delivered the stadium for the Games, which were postponed to 2021. This example shows how a brief can be rewritten to bring cost and program under control, and how the budget became the dominant element of the second brief.
Beijing National Stadium (China). Discussed above, the brief had to be revised when cost and structure collided with the original roof requirement.
Gardens by the Bay (Singapore). In 2005–2006, Singapore’s National Parks Board ran an international competition for the gardens at Marina Bay as part of the transformation of the city’s waterfront. The brief called for a world-class horticultural destination with a strong sustainability agenda. The winning teams included Grant Associates and Wilkinson Eyre, and the project opened in 2012, with its Supertrees and conservatories. It illustrates a state agency’s ability to define a long-term vision in a brief and then execute it with considerable consistency.
Dongdaemun Design Plaza (Seoul, South Korea). Launched as a competition in 2007 on the site of the former Dongdaemun Stadium, the project was designed by Zaha Hadid Architects and opened in 2014. The City of Seoul reframed the project’s purpose during its development, in connection with political leadership changes and debates over preserving archaeological remains found on site. The case is a reminder that in rapidly changing urban contexts, the brief is shaped by politics as much as by function.
United Arab Emirates (Gulf) example
Cool Abu Dhabi (Abu Dhabi). A government-issued urban design brief that focuses a global audience on one public problem, outdoor thermal comfort, and sets clear criteria and a replicable test site instead of a budget and a space schedule. It shows how a municipal authority can use a short, criteria-led brief to gather ideas for policy. See the full discussion in section 7.
Putting it together: practical principles for a good brief
The examples above point toward a handful of principles that apply in any country.
Write the problem, not the solution. Maggie’s Centres succeeded because the brief expressed feelings and needs, not shapes.
Involve the people who will use the building. Oodi and the 9/11 Memorial show that consultation produces briefs with public legitimacy.
Tie the brief to a realistic budget and governance. Holyrood and the Japan National Stadium show what happens when ambitions and money diverge.
Freeze the brief before building. The Sydney Opera House, Berlin Brandenburg Airport and the Elbphilharmonie illustrate the price of building while the question is still changing.
Allow the brief to evolve through dialogue. The Seattle Central Library shows the other side: the best architects will test and sharpen the brief, and clients should welcome this in the early stages, as long as changes are agreed and documented.
Fit the format to the context. A French program, a US program of requirements, a German Grundlagenermittlung and a Chinese design task book differ in form, but each should state who the client is, what is needed, what it will cost, and how success will be judged.
Conclusion
The project brief is both a practical tool and a statement of intent. It defines the question to which architecture gives an answer. It is written by the client, often with help from consultants and architects; it is read by designers, decision-makers, funders, regulators, contractors and, ultimately, the public. Its components range from the vision and the space program to the budget, the timetable and the criteria of success. It matters because it aligns expectations, controls cost and time, and gives creative work a purpose.
Its form changes from country to country, shaped by legal systems and procurement traditions: the state-authored program in France, the competition Auslobung in Germany, the staged client brief in the United Kingdom, the detailed program and owner’s project requirements in the United States, the government-linked design task book in China, and the criteria-led ideas brief issued by Abu Dhabi’s municipal authority. Yet the same lessons recur across Sydney, Edinburgh, Berlin, Hamburg, Tokyo, Beijing, New York and Abu Dhabi. Where the brief was clear, shared and stable, projects tended to succeed; where it was vague, contested or constantly rewritten, they paid for it in money, time and trust. In architecture, the quality of the answer depends heavily on the quality of the question, and the project brief is where that question is written down.
Where to read the original briefs
Three of the briefs discussed above can be read at their source:
Maggie’s Centres architectural brief. Maggie’s (Maggie Keswick Jencks Cancer Caring Trust), Edinburgh, Scotland, UK. maggies.org/about-us/publications
World Trade Center Site Memorial Competition guidelines. Lower Manhattan Development Corporation, New York, USA. collection.911memorial.org/lmdc_competition
Cool Abu Dhabi competition brief. Department of Municipalities and Transport, Abu Dhabi, United Arab Emirates. coolabudhabi.com
Note on sources and figures: the examples are drawn from widely documented public projects. Numbers such as costs, dates and entry counts are approximate and are given to illustrate the argument. Links were checked at the time of writing; please check figures and links against primary sources before using them in academic or professional work.