Writing Samples for Architects: What to Include

Writing samples for architects show how design thinking turns into clear work. They can help clients, hiring teams, or design partners see communication skills, process, and tone. Good samples also make it easier to understand scope, project goals, and the way decisions get explained. This article covers what to include in an architectural writing portfolio.

Each section below focuses on a different type of writing sample. It also explains what to add, how to format it, and what details to keep consistent. The goal is a set of samples that feels organized and easy to review.

One architecture SEO agency may also support how services are presented, so samples match the way discovery happens online. For example, an architecture SEO agency can help align portfolio pages with search intent. Learn more about architecture SEO services from an architecture SEO agency.

What “writing samples” means for architects

Common use cases

Writing samples for architects can support several goals. Many architects share them during client onboarding, sales calls, job interviews, or proposal reviews. Others use them to support marketing pages, press, or speaking topics.

Writing can also help internal teams. Clear scope notes and design summaries reduce confusion across architects, consultants, and contractors. These documents show how well project knowledge gets carried forward.

What reviewers look for

People reviewing samples usually look for clarity, structure, and accuracy. They often want to see how ideas are explained without missing key facts. They also want to understand decision making, not just outcomes.

• Plain language that stays readable for non-designers
• Project context such as site, constraints, and goals
• Design intent explained in words, not only in drawings
• Process showing how options get evaluated
• Ownership indicating what was written by the architect

Core writing samples to include in an architectural portfolio

Project narratives (design intent and goals)

Project narratives are usually the foundation of an architect’s writing portfolio. A strong narrative explains the project’s purpose, constraints, and design intent. It should connect the client’s needs to design choices.

Include a short project overview and a longer narrative section. The narrative can cover concept development, massing decisions, and how the plan supports program needs. If the project is a renovation, include existing conditions and how the approach adapted.

• Project type (residential, workplace, mixed-use, hospitality)
• Scope summary (new build, addition, renovation)
• Constraints (site limits, historic requirements, budget range)
• Design intent (how form and layout support goals)
• Outcome (what was delivered and why it matched the brief)

Case study summaries (short and scannable)

Case study summaries help reviewers skim quickly. These samples typically work well on a portfolio page, in an email, or in a PDF. Keep the text organized with clear headings and short paragraphs.

A case study summary often includes the problem, approach, and results. It can also include a short section on collaboration, such as coordination with structural engineers, landscape teams, or interior designers.

Client-ready scope explanations

Scope explanations show how an architect communicates what is included and what is not. This type of writing often supports proposals and project onboarding. It can reduce change orders by setting expectations early.

Include one scope sample that is formatted for clients. It can be based on a real proposal, but remove pricing details if needed. The focus should be on deliverables, timelines, and responsibilities.

• Services included (schematic design, design development, drawings)
• Services not included (if applicable)
• Assumptions used during planning
• Review cadence (meetings, feedback rounds)
• Decision points where approvals happen

Design rationales for specific decisions

Design rationales go deeper than a general narrative. They focus on one or two design decisions and explain why those choices were made. Examples include façade systems, daylighting approaches, circulation changes, or material selection.

Include enough context so the rationale makes sense. Mention the problem, the options considered, and the reasoning behind the final choice. This can show analysis skills even when drawings are limited.

Writing samples for hiring, interviews, and proposals

Cover letters and proposal introductions

Architect cover letters show tone and clarity. They also show how well project experience gets connected to the role or client need. Keep the writing specific and grounded in past work.

Include one sample for an employment context and one for a proposal context if possible. The language should stay consistent with the architect’s brand voice.

Writing that explains process steps

Many roles need clear writing about process. Include a sample that outlines design stages and typical deliverables. It can also describe how feedback is collected and how changes get documented.

Process writing can also show experience with coordination. Examples include how consultant inputs get integrated or how risk areas get tracked during design development.

• Stage-by-stage outline (concept, schematic, design development, construction documents)
• Review and revision workflow (who reviews what and when)
• Change management (how updates are recorded)
• Coordination notes (team roles and handoffs)

Editorial-style excerpts from real work

Some architects also include editorial writing samples. These can be short essays, project reflections, or publication-ready blurbs. Editorial samples are helpful because they show a stronger point of view in plain language.

When using editorial writing, keep facts accurate and avoid vague claims. Focus on what was learned from the project, how the approach evolved, and what the final design supports.

If brand voice matters for marketing and portfolio consistency, review guidance on architect brand voice. This helps keep writing style consistent across proposal text, case studies, and outreach.

Marketing and online portfolio writing samples

Website portfolio page copy

Website writing is often where clients first notice communication quality. Include at least one portfolio page sample written in a clear, helpful structure. The text should explain the project without assuming the reader can interpret every drawing detail.

Use headings, short paragraphs, and focused details. Include a short summary and a longer narrative section. If images are not included, describe what the reader would see in the visuals.

Service page sections (what the practice does)

Service page writing should match the architect’s actual offerings. Include sample sections that explain services by project stage or by client need. For example, there may be sections for concept design, construction documentation, or permitting support.

A good service writing sample also clarifies how projects start. It can explain intake steps, typical timelines, and how early decisions get made.

Architect blog posts or project explainers

Blog posts show writing depth and topic knowledge. Include one project explainer or one educational post. The best topics usually connect design decisions to real constraints such as zoning, accessibility, or site planning.

Keep the writing structured. Use headings and lists. Avoid very long paragraphs. Also ensure the post stays specific to architecture, not generic marketing.

Email outreach samples

Email writing samples can show how an architect starts conversations. Include a short outreach email and a follow-up email. The content should be respectful, concise, and tied to the reason for reaching out.

Include a version that offers a next step, such as a discovery call or a project fit discussion. If an email includes attachments, explain what they include.

For support on writing that matches an architectural tone, see architect email copywriting. It can help keep outreach clear and aligned with typical client questions.

Technical writing samples architects can include

Permit-ready summaries and submittal notes

Technical writing can be part of a strong portfolio. Permit-ready summaries show how complex information gets organized. Submittal notes can also show how drawing sets get coordinated and checked.

These samples can be simplified for a portfolio. Remove sensitive addresses and owner details. Keep the structure and include clear headings for scope, drawings, and compliance topics.

• Submittal description (what is being submitted and why)
• Code or compliance topics discussed at a high level
• Assumptions used during design documentation
• Drawings included in the package

Program briefs and requirements documentation

Program briefs show how needs get turned into design inputs. Include a sample that summarizes requirements such as spaces, relationships, adjacency needs, and functional goals. This writing can be useful in interviews because it shows early-stage thinking.

A program brief can also describe stakeholder goals and priorities. If the brief comes from a workshop, include the outcomes and how decisions were recorded.

Meeting notes and design decision logs

Meeting notes and decision logs are often overlooked. They can be excellent writing samples because they show accuracy and accountability. A good decision log tracks what was discussed, what was decided, and what next steps follow.

To protect privacy, remove names and contact info. Keep the structure of decisions and next actions. These documents can also show how the architect communicates with consultants.

Brand voice and consistency across samples

Define a simple writing style guide

Writing samples should feel consistent even when they cover different project types. A simple style guide can help. It can cover tone, how headings are used, and how abbreviations are handled.

Consistency matters in portfolio PDFs and online pages. It also helps in proposals where multiple writers may contribute.

• Tone: clear, calm, and factual
• Headings: short and specific
• Paragraph length: short, easy to scan
• Terminology: consistent terms for spaces and systems
• Privacy: remove sensitive details

Match the same level of detail across projects

Some samples may be short, but they should not leave out key context. Include the same basic elements for each project narrative. For example, each case study can include goals, constraints, and design intent.

If one sample is a deep technical explanation, add a brief summary first. This helps reviewers know what the document covers before reading details.

For editorial planning that supports consistent publishing, see architect editorial calendar. A planned schedule can make it easier to gather writing samples over time.

How to format and present writing samples

Use a portfolio layout that supports scanning

Formatting affects how samples are reviewed. Use clear headings and keep paragraphs short. Also include page breaks or spacing so text does not look crowded.

In a PDF, each sample can include a title, a brief context line, and then the writing section. In a web portfolio, each sample can include a short excerpt plus a link to the full text if needed.

Include a one-paragraph summary for each sample

Each writing sample benefits from a short summary at the top. The summary can say what the document is, what project stage it came from, and what role the architect played in the writing.

This helps reviewers understand relevance quickly. It also helps when multiple samples come from different types of work.

Show authorship clearly

If other team members contributed, mention it. State what was written by the architect and what was edited or co-authored. This is especially important for proposals and technical documentation.

Clear authorship builds trust. It also helps avoid misrepresenting responsibilities.

Realistic examples of writing samples (with what to include)

Example: Residential project narrative

A residential narrative sample can include a short introduction, site constraints, and a design intent section. It can also include a short section on material direction and daylighting goals.

• Brief context: site conditions and client priorities
• Design concept: explain the chosen approach
• Decision rationale: one or two key choices
• Process: how options were evaluated
• Result: what was built and how it meets goals

Example: Workplace proposal scope explanation

A workplace scope sample can be written as a client-facing section. It should describe deliverables by stage and explain how feedback rounds work.

• Deliverables list: schematic, design development, and construction docs
• Coordination: who manages consultant input
• Review timeline: set expectations for meetings and revisions
• Assumptions: what the client provides or confirms

Example: Design decision log excerpt

A decision log excerpt can cover one meeting and its results. Keep the writing factual and use dates or stage labels if possible.

• Topic: circulation change or façade adjustment
• Options discussed: brief descriptions
• Decision: what was chosen
• Reasoning: project goals tied to the choice
• Next steps: who does what next

Common mistakes to avoid

Overly general summaries

Some samples sound generic and do not show real work. Avoid text that could apply to any project. Add specific context, named constraints, or clear decision points.

Missing the architect’s role

When authorship is unclear, reviewers may assume the architect had less involvement. Keep a clear note on what was written and what was developed.

Too much jargon without explanation

Technical language can be helpful, but it should be explained at least once. Use clear terms for building systems, materials, or compliance topics. Then add a short plain-language explanation.

Large blocks of text

Dense paragraphs reduce readability. Use headings and lists for key points. Keep sentences short and focused. This improves both human review and quick scanning.

How many writing samples to include

A practical starting set

A strong portfolio can start with a manageable set. Many architects begin with a few narratives, one proposal or scope sample, and one technical or process writing sample. Over time, additional blog posts or editorial blurbs can round out the portfolio.

Quality usually matters more than quantity. Each sample should show a distinct writing strength, such as clarity, structure, process explanation, or technical organization.

Keep samples grouped by purpose

Grouping makes it easier to find what matches the situation. For example, an “interviews” group can include cover letters, process outlines, and decision logs. A “client work” group can include project narratives and scope explanations. A “marketing” group can include email outreach, website copy, and project explainers.

Checklist: writing samples for architects to include

• Project narrative with design intent, constraints, and goals
• Case study summary that is scannable and organized
• Client-ready scope explanation with deliverables and assumptions
• Design rationale for a specific decision
• Proposal or cover letter sample with clear tone
• Process writing that shows stages and workflow
• Technical writing sample such as submittal notes or program brief
• Email outreach sample plus a follow-up note
• Editorial excerpt or project reflection (optional but helpful)
• Authorship notes stating what was written and what was edited

Next steps for building an architectural writing portfolio

Collect and label existing documents

Many samples already exist in proposals, meeting notes, and project reports. Gather these documents and label them by purpose and project stage. Then remove any sensitive details before using them in a portfolio.

Standardize context lines

Before publishing or sending samples, add a short context line to each one. The context line can include project type and stage. It can also note the key writing focus, such as scope clarity or decision rationale.

Refine for readability

After standardizing context, refine formatting and language. Break long paragraphs into shorter ones. Add headings where the sample shifts topics. Make lists where the sample includes multiple items or steps.

When writing samples for architects are organized by purpose, reviewers can find what they need quickly. A clear set of narratives, scope writing, and process explanations can support both client trust and hiring decisions. Over time, consistent brand voice and planned publishing can help the portfolio stay current.