Architecture case study page template: how to structure a project page that gets read

Most architecture firm project pages are a photo gallery with a paragraph underneath, and most visitors leave after the third image without learning what the firm actually did. A case study page should work for three readers at once: a prospective client skimming on a phone, an editor checking whether the project is worth a feature, and a search engine deciding what the page is about. This article is a template for that page: the section order, a project facts table, what to write for each block, SEO basics, how to handle unbuilt work, and a word-count guide so the page is neither thin nor exhausting.

Key takeaways

• Put the strongest image or a short film first, then a one-paragraph summary a reader can finish in fifteen seconds.
• A project facts table answers the questions a client and an editor both ask: where, how big, what type, who did what, when.
• Structure the narrative as challenge, approach, outcome; it reads faster than a chronological account and makes your contribution clear.
• Every photo needs a caption, a photographer credit and alt text; drawings need a title and a north arrow or scale note.
• Unbuilt projects belong on the site, labeled as concept work, with renderings presented as design intent rather than as a record.
• Aim for 600 to 1,200 words of text per built project page; the gallery carries the rest.

The section order

A case study page is a sales document that has to look like a portfolio piece. The order below moves from the fastest-to-consume element to the slowest, so a reader who leaves at any point has still taken away something true about the project.

1. Hero image or short film
2. One-paragraph summary
3. Project facts table
4. Challenge, approach, outcome
5. Drawings
6. Photo gallery with captions and credits
7. Team and collaborators
8. Press and awards
9. Related projects
10. Call to action

Not every project needs every block. A small residential renovation might skip press and awards; a competition entry might skip the photo gallery. Keep the order even when you drop blocks, so your pages feel consistent.

Hero image or short film

The hero is the one asset you would choose if the page could show only one. For a built project it is usually the exterior or primary interior from the photographer's set, at full width, with people in it if you have them. Avoid a slideshow at the top; a rotating hero makes the reader wait for the image they wanted.

A short film is a strong alternative when the project has a sequence worth showing, such as an approach, an entry and a reveal. Keep it under 30 seconds, muted, with a poster image that loads first so the page feels fast while the video arrives; website hero video for architecture firms covers file size, codec and poster-as-LCP. If you don't have footage, a 30-second film generated from six project images, such as those Arch2Video produces, can serve as the hero for a built project, with a caption noting that the motion is AI-generated from the project photography; review it against your drawings before it goes live.

One-paragraph summary

Immediately under the hero, write 60 to 100 words that say what the project is, where it is, who it is for and what the firm did. Lead with the building type and the problem, not with the firm's name. "A 4,200-square-foot addition that turns a 1920s bungalow toward its rear garden for a family of five" tells a reader more than "We were delighted to work with the clients on this transformative project." This paragraph is what a prospective client reads, what an editor copies into a pitch note, and the text a search engine most likely uses to describe the page.

Project facts table

A facts table sits right after the summary and answers the questions people scroll to find. It should be scannable in five seconds.

Use the same fields on every page, in the same order, even when some are blank. Consistent tables let a visitor compare projects, and they make it easy to add structured data later.

Challenge, approach, outcome

This is the narrative, and three short headed sections work better than one long essay.

Challenge states the site, program and constraints in 80 to 150 words. Be specific: a steep lot, a historic district review, a budget that ruled out a basement, a client who works nights and needs darkness at noon. Constraints are what make the design read as a decision rather than a preference.

Approach explains what you did and why, in 150 to 300 words. Describe two or three moves, not twelve. Name the materials and the reasons for them. If a consultant solved a key problem, say so here; it reads as confidence, not weakness.

Outcome closes in 80 to 150 words with what the project does now: how the client uses it, what changed for the neighborhood or the business, measured results where you have them (energy use, occupancy, a tenant signed). A quote from the client belongs here if you have written permission to use it; if you don't, describe the result without one.

Write in plain language; the reader may be a developer or a homeowner, and the vocabulary of a design review does not persuade them.

Drawings and photo gallery

Drawings separate a case study from a photo gallery. Include a site plan, the key floor plans and one section or diagram that explains the main idea. Simplify for the web: strip dimensions and notes, use a consistent line weight and a single accent color, add a scale note and a north arrow where they apply, and give each drawing a title. Never publish anything with a consultant's stamp or a client's address on it.

The gallery comes after the drawings so the reader understands the plan before touring it. Eight to fifteen images is a comfortable range for a built project. Order them as a visit: approach, entry, main spaces, secondary spaces, details, and one closing exterior or dusk shot.

Each image gets three pieces of text. A caption of one sentence that says what the viewer is looking at and, where useful, why it matters ("The kitchen's north clerestory borrows light from the garden without facing the neighbor"). A photographer credit in a consistent format. And alt text, the hidden description screen readers and search engines use; write what is in the frame, factually, in one sentence, without repeating the caption word for word.

Confirm you have the rights to use the photographs on your website, and check whether the license covers video and social reuse, because the hero film and the Instagram post that follow often rely on the same images; architectural photo licensing for video explains what to ask for. If you are commissioning a shoot for the page, an architectural photography shot list will get you the set this template needs.

Team, press, related projects and the call to action

List the project team by name and role, including people who have since left the firm. List every collaborator by firm name with a link; the structural engineer, landscape architect, lighting designer and contractor are also marketing channels, because when they share your page it reaches their clients.

Press and awards go in a short list with the publication or award name, the year and a link. If the project has not yet been published, this is the block you'll fill in after you pitch it; how to get your architecture project published covers submission specs and exclusivity, and a complete case study page is the first thing an editor will look at.

Three related projects, chosen by type or location rather than by date, keep a reader inside your work. Then close with one call to action that matches the project: "Planning a renovation? Start with a conversation," linking to a contact page, or a PDF project sheet for a developer to forward. One sentence, one link, not buried below a footer.

SEO basics for a project page

Search engines reward pages that say clearly what they are, so most of the work here is already done by the template above. Four items are worth doing deliberately.

Title tag. Project name, type and location, under about 60 characters: "Hillside Addition | Residential Renovation in Oakland, CA." Avoid leading with the firm name on every page; the firm name can sit at the end.

Meta description. One sentence of 120 to 160 characters, often a trimmed version of your summary paragraph, with the building type and location early.

Image alt text and file names. Descriptive alt text on every image, and file names that say what the image is rather than a camera's default string.

Structured data in principle. Structured data is machine-readable markup that tells a search engine what an element on the page is: an image, a video, an organization. For a project page the relevant idea is marking the hero video as a video, with its title, description, thumbnail and upload date, so that search engines can show it as a video result; Google's documentation on video structured data lists the fields as of October 2026. Many website platforms add it automatically, so ask your web developer before assuming you need to do anything.

What to write for unbuilt projects

Unbuilt and in-progress work belongs on the site; it shows range, and it is often the work a prospective client most wants to see because it resembles what they are about to commission. Three rules keep it honest.

Label the status plainly in the facts table and in the hero caption: concept, competition entry, in design, under construction. Present renderings as design intent, with a line that says so. Use the challenge, approach, outcome structure but replace the outcome with what the design is meant to achieve and where the project stands.

A film generated from renderings is a legitimate way to show an unbuilt scheme, but it should be captioned as a concept study made from design renderings, and nothing on the page should imply the building exists; AI rendering disclosure for architects has caption wording you can copy. Keep unbuilt pages in the same template as built ones; a separate, lesser format signals that you think less of the work.

Word-count guide

Treat these as targets, not rules. A built civic project can run long; a small interiors job should not.

A page under about 400 words reads as a gallery; a page over about 1,500 words usually means the approach section has turned into a design statement, which belongs in a journal post that links back to the project page.

Frequently asked questions

Should the project page be a single scrolling page or several tabs?

A single page. Tabs hide content from both readers and search engines, and a phone user will not tap through them. Use anchor links at the top if the page is long, but keep every block on one URL.

How many photos is too many?

More than fifteen for most built projects; beyond that the gallery stops telling a story and starts repeating itself. Keep the full set in your press kit for editors who ask, and choose the fifteen that follow the approach-to-detail order on the page.

Do I need the client's permission to publish the project?

Check your agreement. Many owner-architect contracts grant the architect the right to publish the work, often subject to the client's reasonable approval and with their name and address withheld. If the agreement is silent, ask in writing before the page goes live, and respect a request to leave out the address or photos of private rooms.

Where does video belong if not in the hero?

If the hero is a photograph, place a short film after the drawings and before the gallery, where the reader already understands the plan and is ready to move through the spaces. Caption it like any other asset, including the source of the footage and whether any motion is AI-generated.