Portfolio Review Examples

Sarah, an M.Arch graduate with strong residential studio work, was getting zero callbacks from boutique residential firms. The review caught three problems: a soft cover image, inconsistent line weights across her plans, and the fact that her two strongest projects were buried at pages 28 and 32 of a 47-page deck. After a single weekend of edits she was at 91/100 and had three first-round interviews lined up.

• Promoted Project 05 (Marin Residence) to lead, strongest single drawing
• Cut 12 weakest pages, dropped book to 35 pages
• Rebuilt cover with the signature wall section at 1:50
• Standardized line weights across all plans (cut/edge/surface/reference)

James was applying to top-tier public-sector firms (BIG, Snøhetta, Henning Larsen) but his portfolio read like a private-residential book, small in scale, light on context. The review flagged that his renderings were aesthetically polished but missing site, scale, and program. He rebuilt three project spreads and added two large-scale site diagrams; the portfolio tested 88/100 against the firms he was targeting.

• Added program-and-context diagrams to the lead project
• Replaced eye-level renderings with aerial site shots
• Quantified program (m²/users/connections) under each title
• Reordered projects from largest scale to smallest

Emma was applying to MIT, GSAPP, and the Berlage. Her starting score was 38/100, concept narrative was strong but technical drawings were "applicant-tier, not admit-tier" according to the rubric. Two weekends of edits later she scored 94/100 and was admitted to all three programs.

• Drew three new wall sections at 1:20 (cut/material specificity)
• Tightened typography, single heading + body pair across 47 pages
• Added measurable concept statement (one sentence per project)
• Built a process spread for the lead project (sketches → final)

Liam, eleven years post-license, was moving from a 200-person corporate firm to a partner-track role at a 30-person studio. His portfolio was dense, polished, but anonymous, every project read as "team work" with no clear ownership. The review called this out and Liam rebuilt the role-attribution layer across his entire book.

• Added explicit "My role" line to every project (with team scale)
• Pulled three management-led projects to the front
• Removed twelve renderings produced by visualization studios
• Added a single page summarizing built area + budget by year

Aisha was applying for landscape positions at SWA and Field Operations. Her plant palettes and seasonal diagrams were beautiful but isolated from the design intent. The review recommended threading climate, hydrology, and ecology data through every project as supporting layers.

• Added climate/hydrology overlays to every site plan
• Built one signature seasonal-change diagram per project
• Replaced generic plant palette with project-specific lists
• Cut three weakest projects, kept five strongest at full bleed

Diego was a first-time master-plan applicant. His urban-design book was strong on rendering but weak on phasing and economic feasibility. The review pushed him to add a phasing diagram, a stakeholder map, and a one-page financial sketch to each master-plan entry. Result: 89/100 and an offer from Sasaki Associates.

• Added 4-phase build-out diagram to each master plan
• Built a stakeholder map for the lead project
• Included a one-page back-of-envelope financial summary
• Re-rendered the lead bird-eye in cooler, more analytical tones