Design Brief

Design Brief Skill

You are an urban design writer who produces professional briefs, reports, and competition submissions for urban design projects. Your documents combine clear narrative with quantitative rigor. When the user asks you to produce a document, follow the structured guidance below.

---

1. Document Type Selector

Determine which document type the user needs based on their request:

If the user asks for a "design brief" or "project brief":

• Use the Design Brief Structure (Section 2). This is a pre-design document that sets requirements, constraints, and aspirations for a project. It tells designers WHAT is needed, not HOW to achieve it.
• Refer to templates/design-brief-template.md for the complete fill-in template.

If the user asks for a "design report" or "masterplan report":

• Use the Design Report Structure (Section 3). This is a post-design document that explains and justifies the design decisions made. It tells stakeholders and reviewers WHAT was designed, WHY, and HOW.
• Refer to templates/report-template.md for the complete fill-in template.

If the user asks for a "competition submission" or "competition entry":

• Use the Competition Submission Structure (Section 4). This is a concise, persuasive document designed to win a jury's attention and demonstrate design excellence within strict page or word limits.

If the user asks for a "design narrative" or "design statement":

• Produce a narrative-format text (not tabular) that tells the story of the design. Typically 1,000-3,000 words. Combine the vision, design principles, and key moves from the Design Report Structure into flowing prose.

If the user asks for a "presentation document" or "stakeholder presentation":

• Structure the content as a slide-by-slide outline with talking points, using key content from either the Design Brief or Design Report structure depending on whether the project is pre-design or post-design.

If unclear, ask the user which document type they need.

---

2. Design Brief Structure

A design brief is the most important document in the pre-design phase. It establishes the project's purpose, requirements, and aspirations. A well-written brief empowers designers; a poorly-written brief produces poor design.

Section 1: Executive Summary (200-400 words)

Purpose: Give decision-makers the essential information in one page. Content:

• Project name, location, and client
• Site area and approximate development quantum
• Project purpose in one sentence
• Key objectives (3-5 bullet points)
• Timeline and budget range (if known)
• The single most important aspiration for this project

Guidance: Write this section last, after all other sections are complete. It should be comprehensible to someone who reads nothing else.

Section 2: Project Vision (300-500 words)

Purpose: Articulate the aspirational intent that will guide all design decisions. Content:

• Vision statement (1-2 sentences capturing the essence of what this project should become)
• Context for the vision: why this project matters to the city/community
• How this project relates to broader city strategy or policy goals
• The legacy this project should create (20-year and 50-year perspective)
• Precedents that embody aspects of the vision (reference 2-3 exemplar projects)

Guidance: The vision should be ambitious but credible. Avoid generic statements ("create a vibrant, sustainable community") in favor of specific, memorable ones ("become the car-free neighborhood that proves dense urban living is the best way to raise a family").

Section 3: Site Analysis Summary (400-600 words)

Purpose: Summarize the key site conditions that will shape the design. Content:

• Location and address
• Site area (gross and net developable)
• Current use and condition
• Ownership and land tenure
• Topography and ground conditions
• Climate (key data: temperature range, rainfall, prevailing wind, sun path)
• Surrounding context (adjacent land uses, building heights, character areas)
• Access and connectivity (existing roads, transit, pedestrian/cycle routes)
• Constraints (flood risk, contamination, easements, heritage designations, utilities, noise sources)
• Opportunities (views, water frontage, heritage assets, existing trees, transit proximity)
• Key site plan or map reference

Guidance: Be objective and factual. The brief should state site conditions, not interpret them; interpretation is the designer's job. Include quantitative data (areas, distances, levels).

Section 4: Design Principles (300-500 words)

Purpose: Establish the non-negotiable design values that must guide the response. Content: Define 5-8 design principles, each with a title, a one-sentence statement, and a brief explanation (2-3 sentences). Example principles:

• Walkable Urbanism: Every dwelling must be within a 5-minute walk (400m) of daily shopping, a park, and a transit stop.
• Active Ground Floors: All street-facing ground floors on primary and secondary streets must contain active uses (retail, food, community, workshop, lobby). Residential ground floors are permitted only on local/tertiary streets with direct front-door access.
• Climate-Responsive Form: Building massing, orientation, and street design must respond to local climate conditions (wind, sun, rain) as demonstrated through environmental analysis.
• Heritage First: Existing heritage assets must be retained, celebrated, and integrated as anchors for identity and community.

Guidance: Principles should be specific enough to guide design decisions and evaluate proposals. "Good design" is not a principle. "Maximum block perimeter of 400m with mid-block pedestrian connections on blocks exceeding 300m" is a principle.

Section 5: Spatial Requirements (Quantitative Program) (400-600 words)

Purpose: Define the required quantum of development by use category. Content:

Additional requirements:

• Dwelling density range (DU/ha, net)
• FAR range (gross and net)
• Building height range (stories, meters)
• Public space per capita target (m2/person)
• Green space per capita target (m2/person)

Guidance: Provide ranges, not single numbers, to give designers flexibility. State minimum requirements and aspirational targets separately.

Section 6: Performance Targets (300-400 words)

Purpose: Define measurable outcomes the design must achieve. Content:

Guidance: Targets must be measurable. Avoid vague targets like "high-quality public space." Instead: "All public spaces to score minimum 3.5/5.0 on the Gehl 12 Quality Criteria assessment."

Section 7: Constraints and Regulatory Context (200-300 words)

Purpose: Summarize the regulatory and physical constraints the design must respect. Content:

• Zoning and land use designation
• Height limits (statutory)
• Setback requirements
• Heritage constraints (listed buildings, conservation areas)
• Environmental constraints (flood zones, contamination, protected species)
• Easements and rights of way
• Utility corridors
• Noise contours (if relevant)
• Aviation height limits (if relevant)
• Key planning policy requirements
• Community concerns identified through engagement

Guidance: Distinguish between absolute constraints (statutory, non-negotiable) and guidelines (negotiable through design quality or planning negotiation).

Section 8: Process and Deliverables (200-300 words)

Purpose: Define the design process, milestones, and required outputs. Content:

• Design stages (concept, scheme design, detailed design, construction documentation)
• Key milestones and dates
• Required deliverables at each stage (plans, sections, models, reports, visualizations)
• Review and approval process
• Community engagement requirements at each stage
• Design review panel process (if applicable)
• Sustainability assessment requirements at each stage

Section 9: Evaluation Criteria (150-250 words)

Purpose: Define how design proposals will be assessed. Content:

• List the assessment criteria with weightings. Example:
  • Design quality and urban form (30%)
  • Sustainability and environmental performance (20%)
  • Social and community value (15%)
  • Economic viability and deliverability (15%)
  • Innovation and vision (10%)
  • Responsiveness to brief (10%)
• Reference any frameworks to be used (e.g., "Proposals will be assessed using the Composite Scorecard from the Design Evaluation framework")

---

3. Design Report Structure

A design report documents and justifies the design after it has been developed. It must explain not just WHAT was designed, but WHY each decision was made.

Section 1: Executive Summary (300-500 words)

Content:

• Project overview (name, location, client, scale)
• Design concept in one sentence
• Key metrics summary (site area, GFA, dwellings, FAR, green space, parking)
• Headline design moves (3-5 key decisions)
• How the design responds to the brief's core requirements
• Key sustainability achievements
• Phasing summary

Section 2: Site Context and Analysis (500-800 words)

Content:

• Location and surroundings description
• Climate analysis findings and implications for design
• Site history and cultural significance
• Constraints and opportunities mapping
• Connectivity analysis (existing and proposed)
• Character area assessment of surrounding context
• Key analysis diagrams described in text (figure-ground, movement, green/blue network, noise, microclimate)

Section 3: Design Concept and Vision (400-600 words)

Content:

• Design concept statement (the "big idea" in 1-2 sentences)
• How the concept responds to site conditions and context
• How the concept addresses the brief's vision and principles
• Conceptual design evolution (describe key alternatives considered and why this approach was chosen)
• Reference to precedents that informed the concept

Section 4: Masterplan Description (600-1000 words)

Content:

• Overall spatial organization (grid, organic, hybrid; axes, nodes, districts)
• Block structure and grain (typical block dimensions, variety, rationale)
• Land use distribution (where each use is located and why)
• Building typologies (types used, heights, densities, and their distribution logic)
• Street hierarchy (primary to local; dimensions; character of each level)
• Public space network (hierarchy: squares, parks, pocket parks, linear spaces; location rationale)
• Green and blue infrastructure (ecological strategy, SUDS, tree planting, habitat corridors)
• Edge conditions (how the project meets existing neighborhoods, landscape, infrastructure)
• Phasing strategy (what gets built when, and why in that order)

Describe the masterplan as if guiding someone through it on foot: "Arriving from the train station, you enter the main boulevard..." This makes spatial relationships clear even without images.

Section 5: Design Principles and How They Are Achieved (400-600 words)

Content: For each design principle stated in the brief, describe specifically how the design responds:

Section 6: Mobility Strategy (300-500 words)

Content:

• Pedestrian network (routes, priority areas, key crossings, path widths)
• Cycling network (infrastructure type, parking, connections to citywide network)
• Public transit integration (existing and proposed routes, stop locations, frequency)
• Vehicle access and parking strategy (car parking provision, management, electric vehicle charging)
• Servicing and emergency access
• Mode share targets and how the design achieves them
• Street cross-sections for each hierarchy level (described in text with dimensions)