💡 Most architects know how to design. Far fewer know how to write about their work. This guide covers how to write architecture project descriptions that communicate your thinking and get you shortlisted.
The render gets the attention. The description gets you the interview.
Most architecture portfolios look good. The ones that lead to opportunities are the ones where the writing matches the quality of the work where the project description is as considered as the section drawing beside it.
This guide covers a simple, repeatable structure for writing project descriptions that communicate your thinking, your process, and your value.
Why project descriptions matter more than architects realise Hiring managers read them as a proxy for communication skills Clients use them to decide if you understood the brief Search engines index them good descriptions make your work findable
The three-part structure that works every time Brief: what was the challenge? (1–2 sentences) Concept: what was your response and process? (2–3 sentences show thinking, not just outcome) Outcome: what was delivered, and what did it achieve? (1–2 sentences)
Common mistakes and how to fix them Passive voice: "the building was designed to..." → "we designed the building to..." Describing what you see in the image instead of what's behind it Overloading with technical jargon precision is different from complexity Writing in third person when first person is more credible and engaging
Using Orbi AI to write better descriptions How to prompt Orbi: provide the brief, your concept notes, the outcome Using it to tighten, not replace your thinking is still the source material The difference between AI-generated and AI-assisted in a portfolio context
Try Orbi AI on your next project description. Available on the Planbase Standard plan start free at planbase.app.
