Results-focused resume: turn responsibilities into evidence
- Author:
- TremplinCV editorial team
- Published:
- Updated:
- Review:
- Editorial review, with links to sources for external information.
A results-focused resume does not need a percentage on every line. It shows what you were responsible for, what you changed and how you can support those claims. This approach works for administrative, technical, sales and software roles alike.
The key steps
To turn a responsibility into evidence:
- start with the context;
- choose an action verb that accurately describes your role;
- specify the deliverable, volume or constraint;
- add a measurable result when you have one;
- check that the sentence remains accurate and easy to understand.
Evidence does not always need a number. A procedure you created, a certification you earned, a deadline you met or a team you coordinated can also make your contribution concrete.
A method based on four questions
For each important responsibility, answer four questions:
- What was the context? The department, client, product, volume or initial problem.
- What did you do? Your specific action, rather than the work of the entire team.
- What resources or constraints were involved? Tools, methods, deadlines, budgets or stakeholders.
- What changed? Results, quality, cost, time, reliability or the customer experience.
You do not need to include all four answers in every sentence. They help you find the relevant information before you shorten it.
An example for an administrative role
A responsibility such as "managing customer files" does not show the extent of your role. Look for the details:
Case administrator: tracked 80 requests per month, checked supporting documents and coordinated with sales teams through to completion.
If you improved the process:
Reorganised request tracking and reduced response time from 5 to 3 days using a shared tracker and follow-up rules.
Do not write "reduced" if you cannot verify the claim. You can keep a version without a number: "Reorganised request tracking and clarified follow-up rules with the sales team."
An example for a technical role
"Machine maintenance" becomes more informative when the equipment and your action are clear:
Planned preventive maintenance for 35 pieces of equipment, documented interventions in the maintenance management system and reported recurring faults to production.
If the result is known:
Analysed recurring faults on a packaging line and reduced stoppages caused by the same fault by 20%.
The result might concern availability, intervention time, safety or traceability. Choose the one that is relevant to the vacancy.
An example for a sales or finance role
"Managing a client portfolio" does not explain whether you developed, retained or simply administered those accounts. Specify your contribution:
Developed a portfolio of 40 small and medium-sized business accounts, increased revenue by 18% in 12 months and organised follow-ups in the CRM.
For an accounting role:
Prepared monthly closing for 4 companies, checked sensitive accounts and submitted management reporting within the agreed deadlines.
The sentence is credible because it distinguishes the actions you were responsible for. Do not claim a whole department's result as your own if you were not solely responsible.
What if you have no quantified results?
Use other forms of evidence:
- the number of people you supported;
- your geographic or functional scope;
- how often you performed an activity;
- a deadline or time limit;
- a tool you introduced or a procedure you documented;
- responsibility for handovers, checks or coordination.
You can also ask a former manager or colleague to help you recover a relevant indicator. Do not fill the gap with an approximate number.
How many achievements should you include?
Select evidence that matches the role you are applying for. Three or four strong achievements in your most recent position are more useful than a string of numbers without context. You can summarise older experience that demonstrates a relevant skill without repeating every detail.
Our guide to resume skills (in French) can help you make this selection. You can then tailor your resume to the vacancy (guide in French) to bring the most relevant evidence to the top.
Common mistakes
- confusing a team's task with your personal achievement;
- adding percentages you cannot explain;
- using words such as "optimised" or "led" without describing the action;
- quantifying an activity without explaining why it mattered;
- keeping the same achievements for every application.
Frequently asked questions
Does every line of a resume need a number?
No. A number helps when it provides useful context, but a clearly described responsibility can be enough. Prioritise precision over adding percentages.
How can you find numbers several years later?
Review your previous reports, targets or tracking tools, and ask a former colleague to remind you of the context. Use only information you are permitted to share.
Can a team achievement appear on your resume?
Yes. State the team's result and then your exact contribution: coordination, analysis, development, implementation or handover.