How to write an architecture project description, with a structure, lengths by channel and examples

You have the photographs, the drawings and the facts, and you need a paragraph that explains the project. What comes out is either a list of square footage and materials or a page of "dialogue between inside and outside" that nobody outside the studio understands. A good project description sits between the two: it tells a reader where the project is, what problem it solved, the one idea that shaped it and how it turned out. This guide gives a five-part structure, plain-language rules from editors, lengths for your website, Instagram and publications, a facts and credits block, and worked examples at four lengths.

Key takeaways

• Build every project description from five parts: context, brief, idea, materials and making, and outcome.
• Open with one plain sentence that says what the project is and where; it becomes your caption's first line, your summary and your page's opening.
• Editors ask for directness: Architectural Record tells submitters to avoid "flowery, inflated descriptions," and ArchDaily asks what "can't be seen on the drawings and photographs."
• Write the long version once, then cut it to each channel's length rather than writing a new text for every use.
• Finish with a facts block and full credits, and state the project's status plainly: built, under construction or concept.

How to write an architecture project description

To write an architecture project description, start with one sentence that says what the project is and where, then cover five parts in order: the context, the client's brief, the central design idea, the materials and how it was built, and the outcome. Use plain words a client would use, and explain what the photographs can't show. Write a 300- to 600-word version first, then cut it down for each channel, and end with project facts and credits.

The five-part structure

Each part answers one question a reader has. Leave a part out and the reader notices the gap, even if they couldn't name it.

Context. The site, the street, the climate, the existing building. "A 1920s bungalow on a narrow lot in a historic district" sets up every decision that follows.

Brief. The client's needs in their terms: a family that outgrew the house but wanted to stay in the neighborhood, a clinic that needed calmer waiting rooms. Name the constraint too: budget, zoning, a tight schedule.

Idea. One idea, stated simply. "We put the addition behind the house so the street sees the original bungalow" is an idea. Five ideas is a list.

Materials and making. The two or three materials that matter, and why: what they do for light, cost, maintenance or the neighborhood. Skip the full specification.

Outcome. What changed for the people who use it. Avoid invented claims and numbers you can't stand behind; describe what you know: the family now cooks and eats in one room, the garden is visible from the front door.

Plain language is what editors ask for

Publications are explicit about tone. As of October 2026, Architectural Record asks submitters to "clearly present your ideas in a short, direct narrative" and to "avoid flowery, inflated descriptions; the project will speak for itself" (Architectural Record). ArchDaily's guide asks you to "explain what makes your project unique" and to "tell us about what can't be seen on the drawings and photographs" (ArchDaily). Interior Design asks for "a brief description of the project, noting the client's program, your design solution, total square footage and the project cost" (Interior Design).

The same rules work for clients scrolling Instagram. Swap studio vocabulary for words a homeowner uses:

Read the text aloud. If a sentence would sound strange said to a client across a table, rewrite it.

Length by channel

Write the long version once, then cut. Each channel keeps different parts.

Instagram captions for architects has caption templates built on the same first line, the case study page template sets out the section order for the website version, and the award submission guide covers blind judging and word limits.

Worked examples: one project, four lengths

The project below is hypothetical, written only to show the method.

One line (caption first line, summary, page opening): "A rear addition that gives a 1920s bungalow in Austin a family kitchen without changing its face to the street."

About 50 words (Reel caption, LinkedIn opener, directory listing): "A family of four had outgrown their 1920s bungalow but loved the street. We added a single-story kitchen and family room behind the house, lower than the original roof, so the street still sees the bungalow. Brick to match the neighbors, oak inside, and a long window onto the garden."

About 150 words (website summary or Instagram caption body): "A family of four had outgrown their 1920s bungalow in a historic district in Austin, but they didn't want to leave the street. The brief was a kitchen big enough to cook and eat together, a place for homework, and a better connection to the garden.

We placed the addition behind the house and kept its roof below the original ridge, so from the sidewalk the bungalow looks the way it always has. Inside, a wide hallway with a window seat links the old rooms to the new kitchen and family room. The walls are brick, chosen to match the neighbors; everything you touch is oak. A long, low window frames the garden from the kitchen table.

The family now cooks, eats and does homework in one room, and the garden is in view from the front door."

Facts and credits (end of every version): "Project: Bungalow rear addition. Location: Austin, Texas. Type: Residential addition. Status: Completed 2026. Architect: [Studio]. Structural engineer: [Firm]. Builder: [Firm]. Photography: [Photographer]."

The 400-word version for a website or submission expands each part of the 150-word text with one more paragraph of detail: the zoning constraint, why brick, how the window seat is built, how the family uses the room.

Facts, credits and status

The facts block keeps every channel consistent and saves editors an email. Include the project name, the location (city or neighborhood only for private homes), the type, the size if you're comfortable publishing it, the completion year and the status. Then credit everyone: your team, consultants, the builder, interior and landscape designers, the photographer and the visualizer. How to get your project published has a full credits list and press kit.

Check with the client before naming them or the address; asking permission to post a client's home covers what to agree on.

Describing unbuilt and AI-assisted work honestly

Status words prevent the most common misunderstanding. "Completed," "under construction," "proposed" and "concept" mean different things to a reader, and a rendering described as if it were a photograph of a built house is a problem waiting to happen. Put the status in the facts block and, for unbuilt work, in the first or second sentence as well.

If the images or a video were made or animated with AI, say so in the description. Arch2Video, for example, turns six project images into a 30-second vertical film; the motion is an AI interpretation of your images, so a caption such as "AI-animated from our renderings; concept design, not yet built" keeps the description accurate. AI rendering disclosure wording has more lines you can adapt for built and unbuilt projects.

Mistakes to avoid

• Starting with philosophy instead of the project: the first sentence should say what and where.
• Listing every material: name the two or three that shaped the design.
• Using a different square footage, year or project name on each channel: copy from the facts block.
• Superlatives and claims you can't check: "groundbreaking," "award-worthy," invented energy savings.
• Leaving out the outcome: the reader wants to know whether it worked.
• Forgetting credits, especially the photographer, whose images are doing much of the work.

Frequently asked questions

How long should an architecture project description be?

It depends on where it goes. A strong one-sentence summary is the core. Around 150 to 400 words suits a website project page, 300 to 600 words with facts and credits suits most publication submissions, and an Instagram caption needs a sharp first line and a few short paragraphs. Award programs set their own limits, so follow each program's form exactly.

Should I write a project description in first person or third person?

Either works; pick one and keep it consistent. "We" sounds warmer and suits your website and Instagram, where a client is getting to know the studio. Many publications prefer third person, or rewrite submissions in their own voice, so a neutral third-person version is useful for press kits. Avoid mixing the two in the same text.

What should I write about a house when the clients want privacy?

Describe the project without identifying the family or the address. Use the city or neighborhood, describe the household in general terms ("a family of four") or not at all, leave out anything about security or valuables, and get the clients' approval of the text as well as the photos. The design story usually survives without personal details.

Can I use ChatGPT to write my architecture project description?

It's a useful editor but a poor author. Give it your own notes in the five-part structure and ask it to tighten the text or cut it to a length, then check every fact, because it can invent materials, dates or claims it has no way of knowing. Read the result aloud and remove any phrases that sound like no one at your studio would say them.