How to structure an architecture portfolio for a job application
- Emerging Architects
Updated 23 October 2026. Written by the architects at blng studio, for architecture students, graduates and early-career architects.
What "structure" means in a portfolio
When people ask how to structure an architecture portfolio, they usually mean the order of the projects. That's part of it, but a portfolio has structure at three levels:
- The sequence of the whole document: what comes first, what comes last and how much space each part gets.
- The structure inside each project: the order in which you tell one project's story.
- The navigation: how a reader knows where they are and finds what they're looking for.
Get all three right and the portfolio reads as one document, not a folder of exports. Our article on architecture portfolio tips covers what a reviewer looks at in the first minute, how to choose projects and how to send the file. This one is about the skeleton underneath.
How to structure an architecture portfolio, front to back
Here's the structure we'd start from for a portfolio sent with a job application. It's a starting point, not a rule. Tailor it to the practice and the role.
The front: cover and contents
Keep the front short. The cover says who you are and how to reach you. The contents page lists your projects, each with its name, type, date and whether it was academic, a competition or office work. We cover both in more detail in the opening pages.
The contents page does a structural job too: it's the map of everything that follows. If your projects don't fit neatly on one contents page, that's often a sign there are too many of them.
The middle: your projects
The projects are the portfolio. A few principles for the order:
- Strongest and most relevant first. The first project after the contents page is your lead. Strongest means the project that best shows how you think and what you can produce. Relevant means relevant to the practice you're sending it to.
- Not chronological. A reviewer doesn't need your work in the order you did it. Put dates on the contents page and in each project's header, and order the projects by strength instead.
- Vary the second and third. If your lead is a large cultural building, a smaller housing project or a technical study next shows range.
- Place office work deliberately. If you have office experience, put it where it's most relevant to the role, often second, sometimes first. We cover how this changes between Part 1 and Part 2 in Part 1 vs Part 2 portfolios.
- End on something good. The last project is the one a reviewer may remember. Don't let it be the weakest one by default.
The back: other work and contact
The back of the portfolio is for work that supports the projects without needing a full project section:
- Other work: sketches, models, competitions, workshops, short studies or making. One or two pages, grouped, with a short caption each.
- Contact: your name, email and, if you have one, a link to an online portfolio, repeated from the cover. A reviewer who reaches the end and wants to call you shouldn't have to scroll back.
- CV: we'd send it as a separate document with the application, so it can be read on its own. If the practice asks for one combined PDF, put the CV at the very back.
How to structure each project
Once the sequence is set, give every project the same internal order. A reviewer who has read your first project then knows how to read the rest, and can jump to the part they care about.
- Opener. One strong image or drawing and a header: project name, type, date, academic or office, group or individual, and your role in one line.
- Site and brief. Where it is, what was asked, and the constraint that mattered. A site plan and two or three sentences.
- Idea. The question you were answering and your response, in a diagram and a sentence or two.
- Development. How the idea was tested: sketches, models, options. Keep it selective; a reviewer wants to see judgement, not everything you tried.
- Resolution. The drawings that show the project as a building: plans, sections, elevations, and the key view.
- Detail and role. A detail, a construction study or a close-up that shows you can resolve things, and a clear note of what you did, especially on group and office work.
Shorter projects drop steps 2 and 4. A one- or two-page project can be an opener plus a resolution. The order inside stays the same, so it still reads as part of the same document.
The header is part of the structure. Use the same header position and format on every project opener, so a reviewer flicking through can see where each project starts.
Pacing: how much space each part gets
Structure is also about weight. A common problem is giving every project the same number of pages, so the lead project gets no more attention than the fourth.
- Give the lead project the most pages. It's the one most likely to be read in full.
- Shorten as you go. Later projects can be shorter, as long as each still has an opener and a resolution.
- Keep the front and back light. If the cover, contents and back matter take as much space as a project, they're doing too much.
We don't give a page count here: it depends on the practice, the role and whether you're sending a sample or a full portfolio. Our tips article covers how many pages to send and the difference between a sample and a full portfolio.
Navigation: helping a reader find their way
A portfolio is often read on a screen, out of order. A few structural devices help:
- Page numbers that match the contents page.
- A consistent header or footer with the project name, so a reader who lands mid-project knows where they are.
- A clear start to each project: a new spread, a project number or a change of layout. Avoid full divider pages with nothing on them; they take space without telling the reader anything.
- Links in the PDF, if you add them, from the contents page to each project.
How to restructure the portfolio you have
If your portfolio has grown project by project, restructuring it can feel like starting again. It doesn't have to be. Try a contact sheet:
- Export every page as a small image and lay them out on one screen or print them on one sheet.
- Mark each project's opener and resolution pages. If you can't find them, that project needs them.
- Rank the projects by strength and relevance to the practice you're applying to.
- Rearrange the thumbnails into the new sequence: front, projects in rank order, back.
- Cut pages from projects that are longer than their rank deserves.
- Check the internal order of each project against the six steps above.
- Rebuild the contents page last, from the new order.
Then do the same for the sample you'll send with applications. A sample uses the same skeleton, just shorter: a cover, your lead project, perhaps one more, and your contact details. If the full portfolio is well structured, the sample is mostly a matter of choosing which pages to keep, not rebuilding it.
Looking at the whole portfolio at once makes structural problems obvious: a weak project in second place, a lead project buried in the middle, or three projects that open in three different ways.
Common structure problems we see
- Chronological order, so the strongest work is at the back.
- Every project the same length, regardless of its strength.
- Projects that start mid-story, with no opener, so a reviewer can't tell where one ends and the next begins.
- The role note missing from group and office projects, or hidden at the end.
- A long front: a statement, a CV page and a skills page before the first project.
- Other work scattered between projects instead of grouped at the back.
- A different layout for every project, so the portfolio reads as a set of separate documents rather than one.
Most of these are quick to fix once you can see the whole sequence. The content usually stays; only the order and the weight change.
Frequently asked questions
What order should an architecture portfolio be in?
Cover and contents first, then your projects, strongest and most relevant to the practice first, then a few pages of other work and your contact details. Order projects by strength, not by date.
What should an architecture portfolio include?
For a job application: a cover, a contents page, a few of your strongest projects and your contact details. There's no set number of projects. Each project should show the idea, the resolved drawings and your role. Our tips article covers choosing the projects.
Should I put office work first?
Put it where it's most relevant to the role. If you're applying for a job like the one you did in practice, office work can lead. Make your role on it clear, and check what you're allowed to share.
Should my CV go in my portfolio?
We'd send it as a separate document, unless the practice asks for a single file. If it goes in, put it at the back.
Should every project follow the same structure?
Yes, in the same order, though not at the same length. A shared order inside each project makes the portfolio easier to read and compare.
Working on your portfolio?
If you're applying for jobs, the Portfolio Review Sprint is a 30-minute video call with Ariadna López Bieling, Principal of blng studio. You share your screen, she goes through the portfolio you already have with you, and you come away knowing what to change first. £69 incl. VAT, paid when you book. It's feedback on your portfolio, not a guarantee of a job or an interview.
Before you book, the free portfolio self-check gives you 16 yes/no questions to run through on one page.
See the Portfolio Review Sprint → Get the free portfolio self-check →