Slide Deck for Architecture Firms

Architecture firms present constantly — to clients at every phase of design, to planning commissions and zoning boards, to procurement officers reviewing RFQ submissions, and to juries evaluating competition entries. Each audience has different goals, different authority, and different fluency with architectural drawings. A single generic presentation template won't serve all of these contexts. This guide covers the structures that work for each major presentation format in architectural practice, and how to adapt your visual approach accordingly.

Design Phase Presentations

The design process moves through schematic design, design development, and construction documents. Each phase has a corresponding presentation with different content expectations and different levels of design development. Conflating them — showing too much resolution at SD or too little at DD — creates problems with clients and with project scope.

Schematic Design (SD) Presentation

The SD presentation establishes the design direction. At this phase, you're seeking conceptual approval, not authorization of specific materials or assemblies. Structure:

1. Project goals — what success looks like for this project, derived from your programming and discovery work with the client
2. Site analysis — existing conditions, zoning constraints, context, views, solar orientation
3. Concept exploration — three to five concept diagrams showing the organizational ideas you explored (parti diagrams, not floor plans)
4. Three scheme options — for each: ground floor plan, key upper floor plan, exterior perspective or massing study, area tabulation compared to program
5. Recommended scheme — your recommendation with rationale connected to project goals
6. Feedback request — specific questions you need the client to answer to advance the design

Keep SD renderings at a level of resolution that matches the certainty of the design. Watercolor-style renderings, hand sketches, and massing models are appropriate; photorealistic Enscape renders of unresolved interiors are not.

Design Development (DD) Presentation

At DD, the design is selected and you're developing it to a level that allows coordination with engineers and pricing by contractors. The presentation should show:

• Developed floor plans with room names, gross areas, and key dimensions
• Building elevations (all four if the client relationship expects it)
• Key building sections showing ceiling heights, structural bays, and floor-to-floor relationships
• Exterior material palette — actual material samples or high-resolution manufacturer photographs, organized by building assembly (base, middle, top, or by material type)
• Building systems narrative — structural system, mechanical system approach, plumbing strategy, electrical concept
• Updated area calculations — compare to program; flag any scope changes
• Updated project schedule and budget estimate (if a cost consultant is engaged)

Construction Documents (CD) Presentation

Most firms do a project status presentation as CDs are being issued to allow for permit review. This deck is less about design and more about project management:

• CD progress status by discipline (percentage complete per the production schedule)
• Open RFI or coordination issues requiring client input
• Value engineering log — items flagged, owner decisions required, design impact of each option
• Permit submission status, jurisdiction, expected review timeline
• Pre-bid or bidding schedule

Public Hearing Presentations

Planning commission, zoning board of appeals, design review board, and historic preservation commission presentations each have specific conventions. Know the format of your jurisdiction: some require a specific order of information; some limit presentation time strictly.

Standard structure for a planning commission presentation:

1. Project description — address, parcel size, existing use, proposed use, summary of what you're asking the board to approve
2. Zoning conformance — how the project meets each standard: setbacks, height, FAR, lot coverage, parking count, landscaping percentage. Show a simple table comparing "Required" vs. "Provided" for each standard.
3. Design quality narrative — materiality, scale relationship to adjacent buildings, pedestrian experience, streetscape contribution. Use annotated elevations and street-level perspectives.
4. Community benefit statement — jobs, housing units (if residential), tax base, open space, transportation improvements
5. Response to staff comments — address each condition or comment in the staff report directly. Board members read the staff report; a presentation that ignores it looks unprepared.

Keep all plan graphics at a scale that reads on the projection screen. Avoid showing permit drawings at full sheet — export detail areas at readable scale and annotate.

Firm Capability and RFQ/RFP Presentations

Public-sector procurement presentations and private developer RFPs require a different structure than design presentations. The audience is evaluating your firm's qualifications and your understanding of their project, not approving a design.

Standard RFQ/RFP structure:

1. Firm overview — year founded, number of staff, office locations, ownership structure (if relevant — DBE/WBE/MBE status for public work)
2. Relevant project portfolio — three to five case studies. For each: project name and client, location, construction cost, schedule (duration of design, construction), your firm's specific role (prime vs. subconsultant; which team members led it), and one measured outcome (delivered on time, under budget, LEED Gold achieved, award won)
3. Key team members — project manager and principal in charge with project assignments, not just bios. Show which portfolio projects each person led.
4. Project understanding and approach — demonstrate that you read the RFP. Address the specific challenges or opportunities the owner identified. Do not paste in generic boilerplate.
5. Fee proposal — some RFPs ask for fees; some don't. If included, present as a clear table: phase, deliverables, hours, rate, total. Separate lump sum from hourly-not-to-exceed.
6. References — three project-specific references with contact information

What loses RFQ evaluations:

• Generic capability statements that don't reference the specific project or owner type
• Portfolio case studies that show beautiful photos without project data (budget, scale, outcome)
• Team bios that list credentials without connecting the person to this project
• Fee proposals with unexplained lump sums

Design Competition Submissions

Competition submissions are evaluated by juries with limited time and often no opportunity for the firm to speak to the work. Your boards must communicate without you in the room.

Design your hierarchy in three tiers: the primary concept image that communicates the big idea from across the room, the supporting diagrams and plans that explain how the concept works, and the supplemental text and specifications that confirm the technical viability.

For the written portions: competition boards are not the place for architectural prose. Write declarative sentences. State your concept, state your reasoning, state the outcomes. Reviewers are reading many entries; they reward clarity.

Rendering Standards by Phase

Match rendering resolution to project phase and use these as guidelines:

• Schematic design: massing models, concept diagrams, site plan sketches, watercolor or charcoal-style perspectives. Conveys the idea without overstating the certainty.
• Design development: Revit/BIM-based elevations and sections, Enscape or Lumion mid-quality renders, material palette photographs. Conveys the resolved design direction.
• Public hearings: high-quality exterior perspectives from street level, color-rendered site plan, section through the street showing context. Conveys the community experience of the building.
• RFQ/RFP: portfolio project photographs, key plan graphics at high resolution, team headshots (professional, consistent backgrounds).

Owner-Architect Agreement Scope Presentations

When negotiating the owner-architect agreement, a scope presentation helps the client understand what they're paying for. Many disputes about scope originate from clients who didn't understand what each phase entails. Cover: what deliverables you produce in each phase, what decisions the owner must make to allow you to proceed, what your reimbursable expense assumptions are, and what services are explicitly excluded (furniture selection, equipment, permit fees, cost estimating beyond narrative estimates).

Getting Started

Slide-deck.io architecture firm templates are built around the phase-specific structures described here. Each template is sized for a 16:9 widescreen presentation and includes slide types for site analysis diagrams, floor plan layouts with labels, material palette grids, team member cards, and case study formats. Start from the template that matches your presentation context, replace the placeholder content with your project material, and focus your time on the design narrative rather than the slide layout.