Architecture portfolio project order matters because a practice rarely studies every page with equal attention. Your strongest relevant evidence needs to appear early, with enough context to understand why it matters.
A good order does not simply follow chronology. It follows relevance, clarity and the role you are applying for.
Also watch: original video from this article
This video was already part of the article before the rewrite, so it stays with the guide rather than being replaced by the new media.
Listen: architecture portfolio bootcamp
Prefer audio? This portfolio bootcamp expands on project order, evidence and presentation choices.
You can also open the related Architecture Social podcast page.
Continue with related Architecture Social content
If you want to go deeper, these related Architecture Social episodes add more context without getting in the way of the main guide.
Related audio: sample versus full portfolio
This related episode helps you decide what belongs in the sample portfolio and what can wait for interview.
You can also open the related Architecture Social podcast page.
Choose the strongest opener
The first substantial project should prove something useful about the role. It might be your best academic project, strongest practice work, clearest technical evidence or most relevant sector experience.
- Does this project match the role?
- Can the reader understand the brief quickly?
- Is your role or contribution clear?
- Are the drawings and visuals readable?
- Does it make someone want to keep going?
Build a clear sequence
After the opener, use supporting projects to show range without losing focus. One project might prove design thinking, another technical ability, another communication or software confidence.
If two projects prove the same thing, choose the stronger one for the sample portfolio and keep the other for interview if needed.
Use captions to keep the pace
- Project type and brief.
- Academic, professional, individual or group work.
- Your contribution.
- Software or workflow where relevant.
- Why this page is included.
Sample portfolio versus interview portfolio
For most applications, the sample portfolio should be sharper than the full version. Use it to win the conversation, then keep deeper project evidence ready for interview.
That gives you more control. The first file is easy to open and relevant. The fuller version is there when the practice wants to dig into process, drawings, technical detail or design development.
Common mistakes
- Opening with the oldest project because it came first.
- Saving the strongest work until the end.
- Including too many similar pages.
- Letting page design hide the actual evidence.
- Not adapting the order for different role types.
Architecture Social view
Stephen’s recruiter view is that a portfolio should be generous to the reader. If the best evidence is buried, the portfolio is not doing enough work.
Next step
Reorder your first ten pages, then use the architecture portfolio guide, the CV and portfolio evidence guide, the sample portfolio guide and live architecture jobs.
Add a comment