A STAR story for the requirement your CV lacks

You have read the posting, and one requirement stops you. It's on their must-have list and it is nowhere on your CV. From here there seem to be three moves, all bad: skip it and hope nobody notices, stretch something you did until it looks like the thing they asked for, or close the tab.

This guide assumes you have already decided the role is worth applying for — if you meet almost none of the must-haves, the CV tailoring mistakes guide makes the case for spending the effort elsewhere, and it is right. This is about the requirement you can honestly speak to and have not yet written down. The output is a STAR story — the shape itself is covered in how to write a STAR story from your own experience — and the work here is everything that has to happen before you can honestly write one.

Is the gap real? Sort it before you write anything

A requirement your CV doesn't cover is one of three different things, and only the sorting tells you which:

| What is actually true | The test | What it yields | |---|---|---| | You did it and never wrote it down. The CV records your job; the requirement asks about a practice. | Was there a moment when this outcome depended on you? | A story. This is the gap that isn't one. | | You did something adjacent. Same verb, but a different object, scale or setting. | Can you name the difference in one clause? | A story that carries the difference in it. | | You haven't done it. No moment, and no close cousin. | Neither question has an answer. | Nothing. No story exists to write. |

Run the sort honestly, because the whole method rests on it. The second and third rows look similar from the inside — both start with "not exactly" — and the pressure of an application pushes everything toward the second. The one-clause test is what keeps them apart: an adjacent case has a nameable difference. "Not yet" is not a difference.

We'll carry one specimen through all three. The posting is for a customer success manager at a software company, and three of its must-haves are missing from the candidate's CV: runs renewal negotiations with existing customers, onboards new customers onto the product, and has managed a small team. The candidate is an account coordinator at a logistics firm. Their CV is honest and says none of these things — the question is whether their history does.

The branch that yields nothing, said plainly

Take the third requirement first. The candidate has never managed anyone. They have covered for a manager, trained a new starter, and been the person colleagues ask — all real, and none of it is managing a team.

This branch produces no story, and the honest thing is to leave it empty. The tempting alternatives all have the same shape: take the covering, the training, the informal seniority, and write them up in the vocabulary of management until a reader can't tell the difference. That is not a STAR story about managing a team. It is a story about something else, wearing the requirement's clothes — and it fails the first time anyone asks a specific question about it, which is a worse outcome than the gap it was hiding.

What you can honestly do is small and worth doing:

• Leave the requirement uncovered. The gap stays where it is, visible to you and — if you choose to name it — to them. That is the position the tailoring-mistakes guide already told you to apply from. Nothing here changes it.
• File the real story under its real name. "Trained a new starter through their first month" is evidence of coaching or onboarding a colleague. If a different posting asks for that, you have a story ready. It just isn't this one.
• Do not write the aspirational version. "Keen to move into people management" is a fact about the future, and a STAR story is a record of the past. There is no honest Result to write for something that hasn't happened.

Say it to yourself out loud: I have not done this. It costs less than it feels like it will, because you already decided the role was worth applying for with the gap in view. The rest of this guide is for the two requirements where the sentence isn't true.

Branch one: you did it and never wrote it down

Most gaps in a CV are recording failures, not experience failures. A CV is organised around jobs, titles and headline achievements; a requirement is usually a practice — something that had to be done by someone, that may never have been your job, and that no bullet was ever written for. The practice happened in the weeks the CV summarises as "coordinated accounts for regional clients."

The question that surfaces it. Don't ask "have I done renewal negotiations?" — your CV already answered no, and asking again gets the same answer. Rewrite the requirement as the outcome it protects, then ask: when did that outcome last depend on me? For renewal negotiations the outcome is a customer who was going to leave, or pay less, stayed on acceptable terms. Now the question has somewhere to look.

Look in the places a CV never records:

• The weeks you covered for someone — a leave, a departure, a role left empty.
• The task nobody owned that landed on you because you were nearest.
• The thing you did for another team, which your own manager never wrote down.
• The crisis fortnight that got absorbed into an ordinary year.
• The part of a project you did that sat outside its official title.

The specimen, surfaced. The account manager for the candidate's largest client was on leave when the client's contract came up. The client's procurement lead opened with a demand for a lower rate and a threat to tender the work. The candidate — a coordinator, not a manager — held the conversation, pulled the service history to show missed-delivery rates had fallen since the last renewal, offered a longer term instead of a lower rate, and kept the account at the same price. The account manager came back to a signed renewal.

None of that is on the CV. What is on the CV is this:

• The CV line: "Coordinated accounts for regional clients, including contract administration."

And this is the story it was hiding:

• Situation. The renewal for our largest regional client fell due while the account manager was on extended leave; procurement opened by asking for a lower rate and raising the possibility of tendering the work.
• Task. Keep the account, on terms the business could stand behind, without waiting for the account manager's return.
• Action. Pulled the service history for the previous contract period and showed that missed deliveries had fallen since the last renewal; declined the rate reduction and offered a longer term at the existing price instead; agreed the terms with our operations director before putting them to the client.
• Result. The client renewed at the existing rate for a longer term. My manager returned to a signed contract.

Two tests before you keep it. Could the account manager, reading it, sign every line? And is the requirement's own verb — negotiate — actually performed in the Action, or only implied? Here it is performed: a demand was declined and a counter-offer was made. If the Action only contains "supported", "assisted" or "was involved in", the story is adjacent evidence, and belongs in the next section.

The story stays a story. Whether a line from it later earns a place on the CV is a tailoring decision — the pillar guide owns that — and this page does not teach it.

Branch two: presenting adjacent evidence as adjacent

If your whole history is in a different field, the reframing problem is bigger than one requirement and tailoring a CV for a career change is the guide for it. This section is about a single requirement in a role you otherwise fit.

Adjacent evidence is the same verb performed on a different object, at a different scale, or in a different setting. The candidate has onboarded — but sites, not customers; onto a tracking portal, not a software product; one at a time, not in a programme. The verb is real. The distance is also real, and the whole craft of this branch is keeping both on the page.

The dishonest version drops the distance:

• "Onboarded new customers onto the platform."

Every word is defensible in isolation and the sentence is still false, because the reader will picture a software customer-success onboarding and that is not what happened. This is the line between reframing and inflating that the tailoring-mistakes guide draws — a reframe changes the vocabulary, an inflation changes what happened — and the distance between your case and theirs is a fact. Deleting it changes what happened.

The honest version puts the distance inside the story, where it is part of the record rather than a caveat stapled to the end:

• Situation. Each new client site had to be set up on our delivery-tracking portal before its first collection — user accounts, address and cut-off data, and someone at the site who could read the dashboard.
• Task. Get each site live and self-sufficient by its first collection date, with no training visits available.
• Action. Wrote a one-page setup sheet the site contact could follow without me; ran a short call for each new site walking through the dashboard on their own data; followed up after the first week's deliveries to catch what they hadn't understood.
• Result. New sites went live on time, and support calls from newly onboarded sites dropped enough that the setup sheet became the standard for the team.

Notice where the distance lives. The Situation says client sites, tracking portal, first collection. A customer-success reader knows immediately that this is not their onboarding, and they also know that the parts that transfer — the self-serve material, the guided first session, the follow-up that catches confusion — are the parts they actually care about. The story argues for itself without pretending to be something else.

Three rules for this branch:

1. Name the object you actually acted on, in the Situation, in your own field's words. Don't translate "client sites" into "customers" — the translation is the inflation.
2. Let the transferable part be visible in the Action. That is where the reader finds the verb they wanted, and it needs no help.
3. Keep the scale honest in the Result. "Sites went live on time" is smaller than a customer-success programme and is exactly the right size for what happened.

Adjacent evidence presented as adjacent is stronger than it feels, because a reader who sees you mark the distance yourself stops looking for the places you've hidden it.

The one this guide doesn't cover: messy evidence

Branch one assumes that once you find the moment, it takes the STAR shape without a fight. Some evidence doesn't: the renewal that was really a year-long saga with three people involved and a partial outcome, the project where the thing you did is buried in a thing the team did. That is a different problem — you have the evidence and can't shape it — and turning a messy project into a STAR story is the guide for it. The boundary is simple: if you know the work happened and are stuck on the shape, go there; if you are not yet sure the evidence exists at all, you are still here.

What you have now, and what it is for

Run the sort on every uncovered requirement and the specimen ends up where it honestly should: one story surfaced from an unrecorded fortnight, one adjacent story that carries its own distance, and one requirement left open. That is a complete answer. Three stories would have been a worse one.

The two stories you wrote are not single-use. What happened is fixed, which is what makes a STAR story a reusable asset rather than a per-posting argument — the next posting that asks for negotiation or onboarding gets the same facts, with a different one leading. How to keep and re-aim them is reusing one STAR story across job applications.

Before you keep either story, check it against this:

• The requirement's own verb is performed in the Action, not implied around it.
• If the evidence is adjacent, the object, setting or scale you actually worked at is named in the Situation — in your field's words, not theirs.
• Someone who was there could sign every line.
• The Result is the size it really was.
• Any requirement that failed both tests is left open, and you have said so to yourself.

The hardest part of this guide is not the writing; it is the sort at the top, and the sort is slower by hand than it looks, because you have to re-read your own history looking for a practice rather than a job. HireReady24 runs the first half of it: it reads the posting's requirements against your CV, lists the ones it can't find evidence for, and asks you to answer one. From what you say, it drafts the story — from your words, nothing invented — and it is honest in the other direction too: if the posting describes the person it wants rather than listing anything a CV could be checked against, it says so and declines to score you at all. What it cannot do is the sort. It cannot tell an unrecorded fortnight from a requirement you have never met, because only you were there. When the honest answer is that you have not done it, skipping the requirement is the right answer, and the tool will let you give it.