A well-written architecture description is the difference between a project that gets skimmed past and one that gets remembered, published, or shortlisted. It's the text that accompanies your images on your website, in an award submission, in a magazine feature, or on a competition board – and it does the work your photos can't do alone: explaining why the building looks and works the way it does.
And yet, many architects write it last, rushed, and without much thought to structure. That's a missed opportunity, because a strong description isn't just supporting text – it shapes how editors, jurors, and clients understand the work.
This guide breaks down how to write an architecture description for a completed or in-progress project, whether it's headed to your own portfolio, a publication, or an awards jury.
What Is an Architecture Description, and Why Does It Matter?
An architecture description is a written narrative that explains a project: its concept, its site, its materials, and the reasoning behind its design decisions. Unlike a press release, it isn't built around a news hook – it doesn't need a "why now." It exists to make the project legible to someone who can't walk through it.
Done well, an architecture description does three things at once:
- Translates design intent into language: Photos show what a space looks like; the description explains why it looks that way.
- Builds credibility with editors and jurors: A clear, well-argued narrative signals a firm that thinks as rigorously as it designs.
- Extends the life of the project: A strong description gets reused — in your portfolio, in submissions, in press pickups — long after the ribbon-cutting.
When You'll Need an Architecture Project Description
Architecture descriptions show up in more places than most firms plan for. Common occasions include:
- Portfolio and website entries: Every completed project on your site needs a description, and it's often the first substantial text a prospective client reads about your work.
- Award submissions: Juries read dozens or hundreds of entries; a sharp description is often what earns a project a second look.
- Publication submittals: Editors at trade and design publications typically request a description alongside photography before they'll consider covering a project.
- Competition boards and submissions: A concise, persuasive description often accompanies drawings and renderings in competition entries.
- Planning and permitting narratives: Some jurisdictions require a written design narrative as part of a planning or design-review submission.
Because the same project may need a 50-word version, a 300-word version, and a 1,000-word version for different audiences, it's worth writing one thorough master description you can trim down rather than starting from scratch each time.
The Anatomy of a Strong Architecture Description
1. The Opening Statement
Your first one or two sentences should establish what the project is and its defining idea. This isn't a headline, it's a compressed thesis that tells the reader what to look for as they continue.
2. Project Facts
Establish the essentials early: location, program, size, client, and completion date. Readers, especially editors and jurors, often look for these before reading further, so don't bury them deep in the narrative.
- Location: Austin, Texas
- Program: Cultural center with galleries, performance hall, and public plaza
- Size: 45,000 square feet
- Client: City of Austin Parks and Recreation Department
- Completion: 2026
3. The Concept / Design Narrative
This is the core of the description. Explain the central idea driving the design: the organizing move, the response to a constraint, or the design question the project answers. Avoid listing features; instead, connect them to a reasoned intent.
4. Site and Context
Describe how the project responds to its physical, cultural, or urban context — topography, climate, adjacent buildings, or neighborhood character. This section grounds the concept in a specific place rather than treating the building as if it could exist anywhere.
5. Materials and Construction
Name specific materials, structural systems, and construction methods, and explain why they were chosen — for performance, cost, craft, or narrative reasons. Precision here does more work than adjectives.
"A board-formed concrete base anchors the building to the slope, while a lighter, perforated aluminum screen wraps the upper volumes to filter southern light" tells a far richer story than "a mix of durable and elegant materials."
6. Spatial Experience
Walk the reader through the building the way a visitor would move through it — arrival, procession, key thresholds, and standout interior or exterior moments. This section is where the writing can slow down and become more sensory, since it's describing lived experience rather than design logic.
7. Performance and Sustainability (if relevant)
If the project includes notable sustainability strategies, certifications, or performance outcomes (passive cooling, daylighting, energy targets, material sourcing), include them here with specifics rather than general claims.
8. Project Credits
Close with a full credits list: architect of record, design team, structural and MEP engineers, landscape architect, contractor, and any other key collaborators. This is both a professional courtesy and, in the case of publications, often required for the piece to run.
Writing Tone: Analytical, Not Promotional
The best architecture descriptions read like reasoned arguments, not marketing copy. Aim for language that is:
- Precise: Use exact material names, dimensions, and construction terms rather than vague praise.
- Causal: Connect design decisions to the problems or conditions that produced them — "because," "in response to," "to allow" — rather than presenting choices as arbitrary.
- Restrained: Let the reasoning and the specificity carry the weight. If a sentence just praises the design without explaining it, cut it.
A useful test: if you can delete an adjective without losing any information, delete it.
How Long Should It Be?
Length depends entirely on where the description is going:
- Website/portfolio: 150–400 words is typical — enough to establish concept, context, and key facts without overwhelming the images.
- Award submissions: Follow the awarding body's word limit exactly; juries read too many entries to make exceptions.
- Publications: Editors often prefer 300–800 words and will edit for length, so lead with your strongest material first.
- Competition boards: Often the shortest version — 100–200 words — since it competes for attention with drawings on the same page.
Writing one comprehensive 800–1,000 word master version first, then cutting it down for each use case, is far easier than writing multiple versions from scratch.
Common Mistakes to Avoid
- Describing images instead of decisions. "The building features large windows and clean lines" describes what's already visible in the photos. Explain why those choices were made instead.
- Leading with praise instead of substance. Starting with "an award-winning, striking addition to the city" delays the actual information the reader wants.
- Omitting the site. A description that could apply to the same building dropped anywhere loses its strongest source of specificity.
- Skipping credits. An incomplete credits list can disqualify a submission or delay a publication from running the piece.
- Overusing adjectives. Words like "stunning," "iconic," "seamless," or "genuinely" weaken a description rather than strengthen it. Let the reasoning and the facts speak.