A creative director opens your portfolio, reads three projects, and decides in about four minutes that you can do the work. Your CV is still sitting unread in the same email. That sequence is real in a handful of fields, and it does not remove the need for a CV. It changes what the CV is for, and it moves the hardest question onto a different page: who actually did the work you are showing.
The fields where the work decides, and the ones where it only helps
The useful test is not whether a job is creative. It is whether the output can be inspected by someone who does not work at the company that paid for it.
Graphic and editorial work passes that test. So do UX and UI, motion, photography, illustration, front-end engineering, copywriting and architecture. Data roles are moving into the same category as public notebooks and dashboards become normal, though the artefact there is usually a method rather than a finished object.
Now the other side. In product management, marketing strategy, operations, sales, teaching and most back-end engineering, there is no inspectable artefact. What people call a portfolio in those roles is a set of case studies, and a case study is a claim about work, not the work. A reviewer reading it is doing exactly what they do when they read a CV, only slower. If your portfolio is mostly prose about outcomes, it is supporting evidence and your CV is still the deciding document.
One honest complication: even in the fields that pass the test, the portfolio decides whether you get a conversation. It rarely decides whether you get an offer. Between those two moments the CV does a lot of quiet work.
What the CV is still for, and how short it can safely get
Three jobs, and none of them is persuasion.
It gets you into the system. Applicant tracking software parses a document. It does not open a link, render a case study or watch a showreel. If your experience is not in a parseable file, the system holds no record of you at all.
It establishes the facts that the work cannot carry: dates, job titles, employment type, seniority, whether you were staff or freelance, whether you can legally start in six weeks. Reviewers use these to place you on a salary band and a level. A stunning portfolio with no dates attached reads as a talented unknown, and unknowns get offered the bottom of the range.
And it is the artefact that travels. The recruiter who likes you forwards something internally. That something is your CV. It gets read by a finance lead, a department head and an HR partner who will never open your site. Your CV is the version of you those people hold.
In a portfolio-led field, a two-page CV is usually a page of padding. One page, dense with facts the work cannot show, beats two pages of restated project descriptions.
What a portfolio physically cannot show
This is where most creative CVs waste their space. They describe the work, which is visible, and skip the context, which is not. Six things belong here and nowhere else.
Scale. A poster is a poster whether it ran in one cafe or across a national transport network. Print run, audience, monthly users, number of screens, budget, how many markets it shipped in.
Team size and shape. A solo project and a fourteen-person project look identical on screen. Say which it was, and say who you reported to.
Your actual role. The single most valuable line on a creative CV. Art direction, or execution to someone else's direction? Did you set the type system or apply it?
The constraints. Brand guidelines you could not break, a legacy codebase, a regulator, an eight-hundred-euro budget, a four-week turnaround. Constraints are the difference between pretty work and good judgement, and only you can report them.
The brief. What the client actually asked for. Reviewers want to know whether you solved the stated problem or a more interesting one you invented.
What happened after launch. Did it ship. Did it stay shipped. Did the rebrand survive the next management change. A portfolio is frozen at the moment of delivery; the CV is the only place the aftermath appears.
A line that does all of this at once: rebrand for a regional bank, team of fourteen, owned the type system and the motion spec, nine months, rolled out across two hundred and twenty branches, still in use.
The attribution problem
Everything above assumes the reader believes you. In portfolio-led fields that assumption is fragile, because the work is nearly always collective and the document is written in the first person.
What you can honestly claim
The reviewer is not asking whether you touched the project. They are asking a sharper question: what would be missing from this if you had not been there?
Answer that, and the claim writes itself. You can claim decisions you made, problems you solved, parts you produced and things you argued for that ended up in the final work. You cannot claim the project. Nobody claims the project.
Credit the team without deleting yourself
The formulation experienced reviewers trust is boring and specific: I did the X, the team did the Y. "I led the identity and the packaging system; the campaign photography was shot by our in-house team." Two sentences, no ambiguity, and it reads as confidence rather than modesty.
The opposite failure is real and more common than inflation. Some candidates credit so generously that their own contribution vanishes. A CV written entirely in "we" reads as either junior or evasive, and a reviewer under time pressure will not dig for your part. Use "we" for the context and "I" for your contribution, in the same paragraph.
On the CV, credit roles rather than names. Collaborator names belong on the portfolio page, where there is room and where the courtesy is visible to the people being credited.
Agency work, client brands and ghost work
Work made inside an agency belongs to the client, and the reviewer knows this. What damages you is not the arrangement, it is the vagueness. Name the agency as your employer, name the client or describe them generically if you must, and state your role. "At a fifty-person independent studio, for a national grocery chain, as the designer on packaging."
Never let the layout imply you were in-house at a brand you served through an agency. That inference is easy to create by accident and it is the first thing a reference check corrects.
White-label and ghost work is harder. If the arrangement forbids naming yourself, describe the category of work and the scope, and treat the client as unnamed rather than absent.
Work covered by an NDA
An NDA restricts what you can publish. It rarely restricts your employment record. You can say that you spent eighteen months at a company doing a named job. What you cannot do is show the deliverable.
Three moves work. Describe the problem and the constraint without the artefact, which is often more interesting anyway. Show process material instead of the outcome, since sketches, flows, tests and rejected directions tell a reviewer more about your thinking than a finished screen does. Or ask for written permission, which gets granted more often than candidates expect, particularly once the product has launched.
Why inflation is the one unrecoverable error
These fields are small. Art directors move between studios, UX leads sit on the same panels, photographers share assistants. Attribution inflation does not get caught by a system. It gets caught by one phone call to someone who was in the room, and it ends the candidacy on the spot, along with the next three.
The workable rule: claim only what you can defend in a twenty-minute conversation with a person who was there. If a line makes you slightly uneasy, it is already too strong.
Where to start
Take your last five projects. For each one write a single line carrying the scale, the team size, your specific role, the main constraint and what happened after launch. That is your CV. The images already exist elsewhere, and a tool like Postulit can pull your employment dates and titles out of LinkedIn so you are not retyping the boring half.
Then reread every first-person verb and ask who else was in that room. The portfolio proves you can do the work. The CV proves you can be hired to do it inside a company, alongside the people who did the rest of it.