The Portfolio Slot Rubric: Score, Rank, and Cut Each Piece
You will be able to score any work sample on five fixed dimensions, clear the legal gate first, rank your pieces, and cut to a defensible set.
Deciding what goes in your portfolio is a per-piece cut decision, and most advice never gives you one. It stops at "show your best, relevant work" and hands you a long list of things to include, then leaves the actual keep-or-cut call to instinct. This guide replaces instinct with a rubric you apply to one artifact at a time, so the decision is repeatable and defensible. It is for anyone assembling or trimming a portfolio: designers, writers, project managers, architects, and anyone whose work is judged by samples rather than words alone.
The method has two moves that public advice usually skips. First, a legal gate runs before you score anything, because a piece can top every quality axis and still be one you are not allowed to show. Second, scoring runs on five fixed dimensions, so two pieces can be compared on the same axes instead of on how you happen to feel about them today.
Why a rubric beats "show your best work"
A rubric beats "show your best work" because "best" is not the question a reviewer is asking. The reviewer's first concern is relevance, not quality, and the two often disagree. Your most beautiful piece can score top on polish and still be dismissed because it does not resemble the problems the hiring team is solving.
The reason is the time budget. During initial review, reviewers scan for signals rather than reading line by line, and they are doing it fast. Research shows a recruiter initially spends 6 to 8 seconds looking at a resume, and one eye-tracking study of hiring professionals measured an average of 7.4 seconds per resume. A portfolio buys more attention than a resume, but not unlimited attention: architecture reviewers report they can only afford to give 15 to 20 minutes to a full portfolio, and design managers at large companies describe going through hundreds of applications a week. Scarce attention forces a single-question triage on the first pass, and that question is relevance. A relevant B-plus beats an irrelevant A.
"Show your best work" also gives you no way to cut. If two pieces are both good, taste breaks the tie, and taste is exactly what fails you when you are close to your own work. A rubric breaks the tie on dimensions a reviewer actually uses, and it produces a number you can defend to yourself at 11pm when you are tempted to keep a piece for sentimental reasons.
A relevant B-plus beats an irrelevant A, because the reviewer only has time to register one signal.
The five dimensions, and what each proves
Score every piece that clears the legal gate on five dimensions. Each one maps to a question a reviewer asks, and each has a tell for when it lies to you.
- Relevance. Does this resemble the problems the target team solves? This is the first-pass filter, and it outranks everything. It lies when a piece is so polished you assume relevance will be forgiven. It will not be.
- Resume-beating proof. Does this piece show something words cannot? A portfolio exists because words without evidence carry very little weight compared to visual evidence. A piece that only restates a resume bullet adds no information and spends scarce scan-time. It lies when a piece feels substantial but, stripped of its screenshots, says exactly what one line of your resume already said.
- Attributable contribution. Can a reader see what you personally did? Reviewers look for a clear explanation of your role, and ambiguity around ownership creates friction. It lies when an impressive shipped product reads as sole authorship because you never drew the boundary.
- Legibility under time pressure. Can a stranger name the problem and your role in about ten seconds? Reviewers rarely read line by line. It lies when you know the context so well that you cannot see how opaque the piece is to someone seeing it cold.
- Recency and trajectory. Does the set show increasing scope, or the same move repeated for years? Portfolios showing increasing scope reveal trajectory, while the same work repeated may signal plateauing. It lies when a consistent style reads to you as a signature but reads to a reviewer as a plateau.
Score each dimension from 0 to 3. Relevance and attribution are gates within the score: a piece that scores 0 on either is a cut regardless of the total, because an irrelevant piece wastes the one signal you get, and an unattributable one becomes a reference-check liability.
What the reviewer's question is at each layer
- Legal gateAm I allowed to show this at all?
- RelevanceDoes this resemble the problem this team solves?
- Proof and attributionDoes it show something words cannot, and can I see what you did?
- Legibility and recencyCan a stranger read it in ten seconds, and does the set show growth?
kind: rule
title: Relevance and attribution are hard gates
A piece that scores zero on relevance or on attributable contribution is a cut no matter how high the other dimensions score. One wastes your single signal; the other detonates at the reference stage.
Questions job seekers ask
How many pieces should be in my portfolio?
It depends on field, not preference. Application and job portfolios trend to 3 to 6 aligned pieces per Wix, and architecture thesis portfolios run 3 to 7 with 5 typical per Syracuse. Creative and fine-art portfolios run higher: Montclair recommends 15 to 20 and Prospects cites 16 to 20, with under 10 showing too little diversity. Pick your field's range, then let the rubric decide which pieces fill it.
Can I put work from a previous employer in my portfolio without permission?
Generally no, not if a confidentiality clause or NDA covers it. Confidential or unreleased work cannot be displayed without written permission, and confidentiality can override portfolio rights outright. Never assume time has cleared an NDA, and never rely on a verbal yes. Your safe options are to request written approval, redact identifying details, recreate the work with fictional data, or keep it in a password-protected section shown only during interviews.
How do I show team projects without over-claiming?
Label your specific function on every piece, for example noting that you led visual design while a researcher ran interviews and a copywriter produced content. Weak portfolios present team outcomes without boundaries, and reviewers run contribution validation by asking prior collaborators to confirm your role. Honest attribution is risk reduction, since over-claiming is detected at the reference stage after you have already spent interview cycles.
What should I leave out of a portfolio?
Cut anything that dilutes the first impression or creates legal or attribution risk. That means filler added only to hit a number, high-craft work that does not resemble the target team's problems, stale pieces that repeat old work without growing scope, unattributable team outcomes presented as sole authorship, and any raw NDA-covered artifact such as proprietary metrics, methods, or user data on a public platform.
Should I redact confidential work or recreate it?
Recreate it where you can. A heavy redaction destroys the very signal a reviewer needs, so it scores poorly on legibility. Rebuilding the work with fictional data, or swapping real copy for lorem ipsum, shows the design if not the content and preserves the piece's score while still satisfying the legal gate. Reserve black-box redaction for cases where recreation is impractical, and always keep approvals in writing.