Turn responsibilities into CV evidence without inventing numbers

Pick the evidence the next role actually needs

Choose a real role description or a clear type of work you want to pursue. Identify one requirement for which you have a defensible example. “Explain complex information to non-specialists” needs different evidence from “maintain accurate monthly reports”, even if both occurred in the same job.

The National Careers Service recommends tailoring a CV to the opportunity and keeping it clear and concise. That is a useful starting principle, not evidence that one format or wording will work for every employer. ^[1]

Do not rewrite your entire career to resemble one advert. Choose relevant examples while keeping titles, dates, qualifications and scope accurate. Tailoring changes what you emphasise; it does not change what happened.

Make a private evidence note before writing the bullet

Ask: What was happening? What was I personally responsible for? What did I do? What result, deliverable or learning can I explain? Write rough notes first, without trying to make them sound impressive.

The STAR method is one established way to organise an example, and the National Careers Service describes its use in CVs as well as interviews. You do not need to reproduce all four labels in the final sentence. ^[2]

Use records you are permitted to consult, and keep confidential employer or customer material out of your personal notes. You are recovering your own contribution, not copying internal documents into a job application.

Compare a vague claim with a specific one

Consider this fictional starting point: “Responsible for customer reporting.” It establishes an area of work but not the task or your contribution.

A more specific fictional version is: “Prepared the monthly customer-service report, reconciled conflicting ticket categories and explained the remaining data gaps to the team lead.” There is no invented revenue impact or claim that all errors disappeared. A reader can see the kind of work involved and ask about it.

If you can also verify what changed, add that outcome: “Introduced a shared category guide used in the next monthly reporting cycle.” Only combine this with the earlier sentence if the same person actually did that work and the statement is accurate. The example is not a phrase to copy as your own experience.

Use numbers where they clarify something true

A number might describe scale, frequency, duration or a measured change. It does not have to be a dramatic business result. “Coordinated the weekly handover across three shifts” can explain scope if that is what you did.

Before using a percentage, check what was counted, the comparison period and whether the change can reasonably be attributed to your work. If several people or changes contributed, preserve that context. “Contributed to…” may be the accurate description; accuracy is not a weakness to edit away.

When you cannot verify a number, leave it out. Describe the observable output, the decision it supported or the responsibility you held. Do not disguise a guess as an estimate simply to make a bullet look stronger.

Keep shared credit and unfinished work visible

If you supported a project, name your part rather than claiming to have led the whole initiative. If a proposal was not adopted, do not present its projected benefit as an achieved result. An analysis, tested prototype or clarified problem can still be relevant evidence if described honestly.

Not every role gives you access to outcome measures. Not every useful contribution can be reduced to a business metric. The question is whether you can explain what you did and why it was relevant, not whether every line contains a number.

Recover evidence when your work is not measured neatly

Imagine a fictional office administrator who helped a team move to a new building. They did not own the budget and cannot claim to have saved money. Their contribution was collecting equipment requirements, checking the delivery list and recording unresolved setup issues for the facilities lead. Those facts can still demonstrate coordination and attention to detail.

A defensible bullet might be: “Coordinated equipment requirements and delivery checks for an office move, maintaining an issue list for the facilities lead.” If the person also verified that all named teams received their agreed equipment, they can consider adding that outcome. If they only expected this to happen, they should not describe it as completed. A relevant deliverable is preferable to a fictional impact claim.

Apply the same distinction to unfinished projects. “Developed a proposed handover checklist and tested it with two colleagues” describes completed work even if the wider rollout never happened. “Transformed the organisation's handovers” would not be supported by that evidence. The smaller statement may still answer an employer's question about how you approach a problem.

Build an evidence bank you can reuse

For each useful example, keep a short private note of the context, your role, actions, output, any verified outcome and the limits on what you can disclose. Add the type of requirement it could support, such as coordination, analysis or customer communication. This is your own working record, not a collection of copied employer files.

When tailoring an application, select an example because it addresses a real requirement. The same office-move experience might demonstrate coordination in one application and careful follow-up in another. You can emphasise a different aspect without changing the facts. Keep enough context to recognise the story behind the sentence when you are asked about it later.

Use a simple credibility check before keeping a bullet: could you explain the situation, distinguish your work from the team's work and support the stated outcome without revealing confidential information? If not, narrow the claim. Strong wording should be the final edit to a defensible example, not a substitute for one.

Test the sentence with follow-up questions

Read your new bullet and ask yourself: “What did that involve? Which part was mine? How do I know the result? What could I say without disclosing confidential information?” If you would struggle to answer, revise the claim before polishing the wording.

Your next move is to rewrite one responsibility using verified detail, then compare it with the requirement you chose. Remove any claim you cannot support and keep the useful context. Repeat only where it improves the reader’s understanding. A clearer CV cannot guarantee an interview, but it can represent your experience more faithfully.