# Architecture Portfolio: What Goes In and What Gets Left Out An architecture portfolio is a curated presentation of your design work. Its job is to show a reviewer — a studio principal, a university admissions panel, an internship coordinator — that you can think architecturally and carry a project from idea to resolved design. It is not a dump of every drawing you have ever made. ## What an architecture portfolio contains The strongest portfolios are built around a small number of complete projects, usually three to six, depending on your stage: - **Project narrative.** What was the brief, the site, the constraints? - **Process.** Concept diagrams, sketches, iterations — reviewers want to see how you think, not just how you render. - **Resolution.** Plans, sections, elevations, details and visualizations that show the design is resolved. - **Outcome.** Model photos, built work (if any) and what the project achieved. Every image should earn its place. If a drawing does not add information, it is decoration, and decoration reads as filler. ## What gets left out - More than one or two projects shown shallowly - Page after page of unlabelled renders - Unclear drawings with no plan/section labels - Sketchbook pages included "for personality" without context - Anything you cannot explain in an interview ## How reviewers read portfolios Reviewers scan quickly, then slow down on the projects that interest them. That means the first project matters disproportionately, and every project needs a readable entry point: a strong lead image, a clear title, and a one- or two-line summary of the idea. They are not looking for maximum density. They are looking for **judgment**: what you chose to show, in what order, and what you decided mattered. ## The core structure that works 1. **Cover** — name, portfolio title, contact. 2. **About / intro** — two or three sentences, not an autobiography. 3. **Selected projects** — each with narrative, process and resolution. 4. **Skills / software / other work** — brief, at the end. Keep the intro short. The projects are the portfolio. ## Common beginner mistakes - Leading with the weakest project - Including unfinished work without saying it is unfinished - No plan or section on any page - Ten projects at one page each instead of four projects done properly Read about the [full build process](/architecture/how-to-make-an-architecture-portfolio/), see what strong portfolios look like in the [examples guide](/architecture/architecture-portfolio-examples/), and check the [layout guidance](/architecture/architecture-portfolio-layout/) before you start arranging pages. ## Getting your portfolio seen Once the portfolio itself is strong, the format matters: a [PDF for applications](/architecture/architecture-portfolio-pdf/) and a [website for sharing](/architecture/architecture-portfolio-website/). If you are applying for work, read the [job-application guide](/architecture/architecture-portfolio-for-jobs/) first. Want portfolio tools for architecture? [Join the Architecture beta](/architecture/#beta).