The Core Principle

An architecture project description should explain what the project is, why it matters, what constraints shaped it and how the design responds. Strong submissions reduce ambiguity: the jury should be able to understand the project, its authorship, its status and the value of the design without reconstructing the story from scattered information.

A Practical Framework

1. Start with the project in plain language
2. Explain the challenge
3. Describe the design response
4. Add measurable facts
5. End with significance

Start with the project in plain language

Treat this as an editorial decision, not a decorative one. Every element should help a reviewer understand the project faster and compare it fairly within the selected category. Use facts, drawings, photographs and concise text as evidence rather than relying on unsupported claims.

Explain the challenge

Treat this as an editorial decision, not a decorative one. Every element should help a reviewer understand the project faster and compare it fairly within the selected category. Use facts, drawings, photographs and concise text as evidence rather than relying on unsupported claims.

Describe the design response

Treat this as an editorial decision, not a decorative one. Every element should help a reviewer understand the project faster and compare it fairly within the selected category. Use facts, drawings, photographs and concise text as evidence rather than relying on unsupported claims.

Common Mistakes to Avoid

• Writing a chronological diary of the design process
• Opening with vague adjectives
• Repeating information visible in drawings
• Omitting location, status, area or programme

How This Supports SEO and AI Discovery

Use one clear page purpose, descriptive headings, factual project terminology and links to stable entities such as the project, studio, person, category and location. This makes the page easier for search engines and generative systems to interpret without keyword stuffing.