Turning Duties Into Achievements: CV Bullets With Numbers

The single highest-return hour you can spend on your CV is rewriting your bullets from duties into achievements. Same career, same jobs, same truth — a completely different document. A duty tells a recruiter what your contract said. An achievement tells them what was different because you were there.

This guide gives you the rewrite formula, then a bank of before/after pairs from the roles Saudi job seekers actually hold — government administration, teaching, customer support, accounting, HR, projects, retail, logistics — not US marketing examples about “scaling growth funnels.” It ends with the hardest case: how to quantify honestly when your work genuinely has no metrics attached to it.

Quick answer

• A duty starts with “responsible for”. An achievement starts with a result.
• A number without a baseline is noise. “Improved by 30%” means nothing; “from 40 to 28 over 6 months” means something.
• You do not need company KPIs to have numbers. Volume, frequency, people, scope, time, and error rate exist in every job.
• Three to five achievement bullets for your current role, fewer as roles get older.
• Never write a figure you cannot defend in an interview. Approximate honestly instead of inventing precisely.

If you are building the CV from scratch, start with the complete Saudi CV guide, then come back here for the bullets — this is the part that decides whether a reader keeps going.

What actually separates a duty from an achievement?

A duty describes the boundaries of a job. An achievement describes a change inside those boundaries. The test is one question: if I had never held this job, what would be measurably different? If the answer is “nothing, someone else would have done the same tasks,” you have written a duty.

Weak: “Responsible for handling employee files and following up on requests.”

Strong: “Cleared a 400-file records backlog in 11 weeks and moved leave requests from paper to a shared tracker, cutting the average approval wait from 9 days to 2.”

Both sentences are true of the same person. The second one just answers the question the first one avoids.

The formula: result → method → scope

Write every bullet in that order, because a recruiter scanning at speed reads the first four words of each line and nothing else.

1. Result — what changed, with the before and after.
2. Method — what you specifically did to cause it.
3. Scope — the size that makes the number credible: how many branches, people, files, riyals, months.

Layer	Weak version	Strong version
Result	”Improved reporting"	"Cut monthly close from 12 days to 7”
Method	”Used Excel"	"By rebuilding the reconciliation sheet and pre-loading recurring entries”
Scope	(missing)	“Across 3 subsidiaries and 4 bank accounts”

Assembled: “Cut the monthly close from 12 days to 7 by rebuilding the reconciliation sheet across 3 subsidiaries and 4 bank accounts.” Nineteen words, fully verifiable, and impossible to write unless you actually did the work.

The six number types hiding in any job

Most people think they have no numbers because they are looking for revenue. Look for these instead.

• Volume — how many things passed through you. Files, tickets, students, invoices, shipments, candidates, site visits.
• Frequency — how often. Daily, per week, per closing cycle, per semester.
• People — team size, trainees, stakeholders, departments coordinated, external vendors.
• Scope — branches, cities, systems, contract value, budget under your control.
• Time — how long something used to take versus now, or how far ahead of a deadline you delivered.
• Quality — errors, returns, reopened tickets, audit findings, complaints, rework.

Any one of these turns a duty into a fact. Two of them together make it convincing.

The bank: before and after, by role

Government and administrative work

Weak: “Handling correspondence and archiving official documents.”

Strong: “Reorganised an archive of roughly 6,000 documents into a searchable index, cutting retrieval time from around 20 minutes to under 2.”

Weak: “Following up on transactions with other departments.”

Strong: “Ran the weekly follow-up cycle on 60–80 open transactions across 5 departments and reduced items sitting past 30 days from 22 to 4.”

Teaching and training

Weak: “Teaching mathematics to middle-school students.”

Strong: “Taught 5 sections, roughly 150 students per term, and built a weekly diagnostic quiz that lifted the class average in the weakest section from 61 to 74 over one semester.”

Weak: “Preparing lesson plans and participating in school activities.”

Strong: “Designed a 12-week remedial plan for 18 students below the pass line, of whom 15 passed the end-of-term exam, and trained 4 colleagues to run the same plan.”

Customer service and support

Weak: “Responding to customer inquiries by phone and email.”

Strong: “Handled 60–75 tickets a day on the retail line and cut reopened tickets from about 1 in 5 to 1 in 12 by writing a 9-case answer bank the whole team adopted.”

Weak: “Escalating complex issues to the relevant department.”

Strong: “Built the escalation matrix for a 14-person team, replacing informal WhatsApp routing and reducing average resolution time on complex cases from 4 days to under 2.”

Accounting and finance

Weak: “Preparing financial reports and reviewing accounting entries.”

Strong: “Closed the books monthly for a 3-entity group and reduced audit adjustments from 11 in the first year to 3 in the second by tightening the accrual checklist.”

Weak: “Following up on receivables.”

Strong: “Cut receivables over 90 days from roughly SAR 2.1M to SAR 700K in 8 months by introducing a tiered follow-up schedule and a weekly aging review with sales.”

HR and recruitment

Weak: “Posting jobs and screening CVs.”

Strong: “Screened around 1,200 applications for 40 openings in one year and shortened average time-to-offer from 46 days to 29 by moving first screening to a structured 15-minute call.”

Weak: “Handling employee onboarding procedures.”

Strong: “Rebuilt onboarding into a 5-day checklist covering GOSI registration, Qiwa contract issuance, and system access, taking new-hire first-week complaints from routine to near zero across 60 hires.”

Projects and engineering

Weak: “Supervising project execution and following up with contractors.”

Strong: “Supervised 3 fit-out packages worth about SAR 18M combined and delivered 2 of them 3 weeks ahead of schedule by resequencing MEP works against the finishing crew.”

Weak: “Preparing periodic reports for management.”

Strong: “Replaced a 20-page manual monthly report with a live Primavera-linked dashboard, freeing roughly 3 working days a month for the planning team.”

Retail and sales

Weak: “Selling products and meeting monthly targets.”

Strong: “Grew branch monthly sales from around SAR 380K to SAR 510K over two quarters by rebuilding the display plan around the 12 fastest-moving SKUs.”

Weak: “Training new employees at the branch.”

Strong: “Trained 9 new sales staff over 18 months, 7 of whom hit target within their first two months, using a 3-shift shadowing routine I wrote.”

Logistics and warehouse

Weak: “Receiving shipments and organising the warehouse.”

Strong: “Managed inbound of about 90 pallets a week and cut stock-count discrepancies from 6% of SKUs to under 1.5% by introducing bin-level labelling.”

Weak: “Coordinating with transport companies.”

Strong: “Consolidated deliveries across 3 carriers into 2 fixed weekly runs, reducing per-shipment cost by roughly a fifth on the Riyadh–Dammam lane.”

What if your job genuinely has no numbers?

Some work resists measurement: policy drafting, legal review, executive support, research, coordination. You still have four moves.

1. Count the inputs, not the outcomes. You may not own a KPI, but you know how many contracts you reviewed, how many committee meetings you prepared, how many policies you drafted. “Reviewed roughly 25 supplier contracts a month” is a real, defensible fact.

2. Name the thing that did not exist before you. A template, a checklist, a tracker, a training session, a filing convention. Creation is quantifiable by adoption: who uses it now, how many people, how often.

3. Use time and delay. Almost every administrative process has a “how long does this usually take” answer. If you shortened it, that is your number. If you did not shorten it but you protected it — “kept all 40 board packs delivered at least 3 days before each meeting for two years” — reliability is a result too.

4. Use scale and stakes. If nothing moved, describe what you were trusted with. “Sole coordinator for a committee of 12 department heads” or “handled the correspondence of a 300-employee directorate” tells a reader something real without a fake percentage.

Weak: “Assisting the manager with daily tasks and organising the schedule.”

Strong: “Ran the calendar and correspondence for a director overseeing 4 departments, prepared the material for roughly 40 committee meetings a year, and built the tracker that kept 100+ open action items visible with owners and due dates.”

No percentage anywhere. Still a strong bullet, because it is specific.

Honesty rules you cannot break

Everything above collapses if a number cannot survive one follow-up question. Interviewers in Saudi hiring processes — especially in banking, government, and the large semi-government employers — will ask “how did you measure that?” and the answer has to come easily.

• Approximate openly. “Around 60 tickets a day” is stronger than “63.4 tickets a day” you invented for precision. Round numbers read as honest; suspicious decimals read as decoration.
• Know your base. Before you write a percentage, be able to say the two raw numbers behind it. If you cannot, write the raw numbers instead and skip the percentage.
• Separate your part from the team’s. “Part of the team that reduced X” is weak; “owned the vendor renegotiation inside a project that reduced X” is strong and still honest.
• Do not borrow the company’s number. Your employer’s annual growth is not your achievement unless you can trace a line from your work to it.
• Write it once, defend it forever. Assume every bullet becomes an interview question. If a line makes you nervous, rewrite it smaller and truer — see the common traps in CV mistakes that cost you interviews.

Where achievements sit on the page

Achievements go first, everywhere. Under each job title, add one short scope line if the role needs context — team size, sector, budget — then three to five result-first bullets. Never open a role with a paragraph of responsibilities and hide the results underneath; almost nobody reads that far.

For senior careers, lift your three strongest numbers into a “Selected Achievements” block right under the summary, so the best evidence sits on the first screen instead of page two. The summary line itself should carry one number — see CV summary examples for the pattern. And because the parser reads plain text linearly, keep all of this in one column with standard headings, as covered in how to write an ATS-friendly CV.

Recent graduates: your bullets come from co-op training, projects, volunteering, and student activities, and the same six number types apply. Writing a CV with no experience covers where to find them.

This rewrite is exactly what TrueSira is built around. You describe your work once into a Master Profile — plainly, in your own words — and the system helps turn each duty into a result-first bullet with the baseline attached, asking you for the numbers rather than inventing them. Then when you paste a job description, it reorders those achievements so the ones closest to the posting rise to the top, and you approve every line before it enters your CV. Get started free.

FAQ

How do I quantify achievements if my job has no numbers?

Every job has countable things even when nothing is formally measured. Count volume (how many files, tickets, students, shipments), frequency (per day, per closing cycle), people (team, trainees, stakeholders), scope (branches, systems, budget), time (how long it used to take), and quality (errors, complaints, rework). Pick two of those, state what changed, and you have a real achievement without a fabricated KPI.

What is the difference between a duty and an achievement?

A duty is what your job description said you should do. An achievement is what was different because you did it — a number that moved, a process that started existing, a problem that stopped recurring. The quickest test: if you had never held the job, what would be measurably different? Write that.

How many achievements should I list per role?

Three to five bullets for your current and most recent role, two to three for the role before it, and a single line for anything older than roughly eight years. Depth belongs to the roles closest to the job you are applying for. Older positions exist to show continuity, not to be sold again.

Can I use percentages I only estimated?

Only if you can explain in an interview how you arrived at the figure. Say the base you counted, use a round approximate number, and add “approximately” rather than manufacturing precision. If you cannot name the two raw numbers behind a percentage, drop the percentage and write the raw counts instead — they are more convincing anyway.

Should achievements go before or after responsibilities?

Achievements first, always. If a role needs context, give it in one short scope line under the job title — team size, sector, budget — then let every bullet below start with a result. Recruiters scan the first words of each line, so a bullet beginning with “Responsible for” spends its only chance on nothing.

What if the result came from a team, not just me?

Name your specific contribution inside the team result. “Part of the team that cut delivery time” is weak and slightly evasive; “owned the carrier renegotiation in a project that cut delivery time from 5 days to 3” is strong, honest, and gives the interviewer something concrete to ask about. Claiming a whole team’s outcome is the fastest way to lose credibility in the interview.