A freelance CV usually fails for a reason that has nothing to do with the writing. The format is the problem. A standard experience block holds one employer, one title and one date range, and six years of client work does not arrive in that shape.
So most freelancers do the obvious thing and list everything. Forty entries, most of them two or three months long, stacked in reverse chronological order. What a recruiter sees in the first pass is not a career. It is somebody who kept losing jobs.
Why a long client list reads as instability
Nobody opens your CV already knowing you are self-employed. They open it and pattern-match on shape before they read a single bullet. Short block, short block, short block, and the shape has already said "churn" before the content gets a chance to say anything else.
The same six years, presented as one continuous practice, reads as a stable run with unusual variety. The work is identical. The shape is what changed.
That is worth sitting with, because it tells you where the effort belongs. The fix is not sharper bullet points inside forty blocks. The fix is to stop having forty blocks.
One heading for your practice, with the work nested underneath
The pattern that solves this is an umbrella entry. You create a single experience block for your own practice, give it a continuous date range, and put selected client engagements under it as projects rather than as jobs.
The heading line does three jobs at once: it names the entity, states what you do, and fixes the dates. Something like "Independent Front-End Developer, self-employed, March 2019 to present". Under it, two lines of positioning that tell a reader what kind of work you take and who buys it. Then a short block labelled "Selected engagements" with four to six nested items.
On naming, you have two choices and they say different things.
- Your own name, or no entity at all, just "Freelance Copywriter". A recruiter reads: one person, available, no complications. This is the right default if you are applying for a salaried role.
- A registered business name, "Okafor Studio Ltd". A recruiter reads: possibly a small agency, possibly a founder, possibly someone with a company they may want to keep running. That last inference is the one that quietly costs you interviews.
If you trade under a business name and you want a salaried job, make the solo part explicit in the positioning line. One clause does it: "sole practitioner, no employees". Otherwise a hiring manager spends the whole screen wondering whether you are going to disappear back into your own company after eight months.
What this does inside an ATS
Parsers hunt for employer, title and date triplets. Give them forty and several things go wrong. Overlapping date ranges break the chronology logic, since you almost certainly ran two clients at the same time in most months. Some parsers compute total experience by summing date ranges, which either double counts your overlaps or truncates them. Very short entries get dropped as noise or merged into the one above.
One umbrella entry gives the parser one clean triplet with a six-year span and no overlaps. The engagements become body text attached to it, which is exactly what they are. If you are rebuilding a CV from your LinkedIn profile, a tool like Postulit will import the experience section for you, but the grouping decision is yours. No importer can guess that these eleven entries are one practice.
Dates are the part recruiters actually check
Put a continuous range on the umbrella heading and stop there. Your practice existed from the month you registered it to today, and that is true even in the months you had no billable work. Between-contract troughs are ordinary business, not employment gaps, and you are under no obligation to publish your invoicing calendar.
My opinion, and not everyone agrees: leave month-level dates off the individual engagements entirely. Year is enough context, and precise per-project dates invite someone to reconstruct your quiet periods and ask about them. You would not list the weeks you spent on a specific internal project at a salaried job either.
If you had a genuine break, a sabbatical, caring responsibilities, illness, treat it the way an employed candidate would. Name it in one line if it is long enough to be visible, then move on.
Choose four to six engagements, not forty
Selection is the part most people skip, and it is the part that does the work. You are not building an archive. You are picking evidence for one specific job.
Choose by relevance to the target role, not by how big the client was or how much you enjoyed it. If the role is a fintech product team, the credit union rebuild goes in and the restaurant menu redesign stays out, even if the restaurant project was better work. Rotate the selection per application. This takes about ten minutes once the full list lives in a separate document.
Then account for the volume you left out, in one line, right under the selected items. "Thirty-plus engagements delivered since 2019 across fintech, logistics and public sector clients; six shown." That line does something important: it tells the reader the short list is a choice, not everything you have.
Listing every client is not thoroughness. It is refusing to decide, and the reader ends up doing your editing for you.
Outcomes when the client is under NDA
Confidentiality kills the client name, not the result. Describe the client by shape instead: "a mid-size insurance group", "a Series B logistics platform", "a national retailer". A reader gets everything useful from that, and you have not breached anything.
For the outcome itself, work down this order:
- The business result you can prove. "Cut checkout abandonment by a third over two quarters."
- Scale and constraint, if the result is off limits. "Rebuilt a 400-page product catalogue in eleven weeks, solo." That is a real, checkable statement about the work.
- Problem and method, if nothing else is available. What was broken, what you did, what shipped. A named deliverable beats a vague claim about impact every time.
What you must not do is invent a percentage because the real number is confidential. Made-up metrics fall apart in the first interview, and they tend to fall apart in front of the one person in the room who has done your job.
Rates, logos, and the question to answer before it is asked
Three quick calls, and the first two are firm.
Rates do not belong on a CV. A day rate anchors a salary conversation before you are in the room, and a daily figure held up against an annual salary always looks wrong in one direction or the other. It is also information you give away for free with nothing in return. Save it for the conversation where it is negotiable.
Client logos do not belong there either. They bloat the file, they carry no parseable text, and a grid of logos reads as marketing rather than as a record of work. Your portfolio site is the right home for them. Names in plain text are fine where the client permits it.
The question, though, is the one that matters. If you are applying for a salaried role after years of independence, the hiring manager is already wondering why. Answer it in your summary, in one sentence, and make the reason forward-looking rather than an escape. "After six years running my own practice, I want to own a single product across multiple release cycles instead of handing work over at the end of every engagement." Compare that with "freelance work has slowed down", which is honest and lands badly. Both may be true. Only one belongs on the page.
The freelancer's problem is not that their work is unimpressive. It is that a CV was designed for a career shape they do not have, and the umbrella entry is how you fit one into the other. Open your CV, count your experience blocks, and if the number is above eight, you have a layout problem rather than a content problem. Collapse them into one practice, pick your six, and give the rest a single summarising line.