Writing accomplishment bullets when your job had no numbers

The instruction to quantify your achievements assumes a job that generates numbers. Plenty do not. A school administrator, a social worker, a compliance officer, a librarian, a nurse, a technician — these roles produce outcomes that are real and often difficult to reduce to a percentage without inventing one.

Inventing one is worse than having none. An interviewer who asks where the figure came from and receives a vague answer has learned something about you that no bullet can undo. There are three other forms of evidence, and used properly they are as persuasive as a number. When describing results, here is a useful distinction: producing the right outcome is not the same as completing a task faster.

Evidence one: scale

You may not have improved a metric, but you operated at a size, and size is verifiable and immediately meaningful to a reader. For occupational outlook and pay data, consult the U.S. Bureau of Labor Statistics.

• "Handled the records for a 340-bed facility."
• "Sole administrator for a department of 26 across three sites."
• "Managed a caseload of 40 to 55 active clients."
• "Processed roughly 200 supplier invoices a week."

None of these claims an improvement. All of them tell the reader what you can be trusted with, which is usually what they are actually trying to work out.

Evidence two: difficulty

Some work is notable because of the conditions rather than the result. Name the condition.

• "Kept the rota covered through an eight-month period with two of six posts vacant."
• "Ran the year-end close during the finance system migration, in parallel on both systems."
• "Took over the contract three weeks before the renewal deadline, after the previous manager left."

A reader who has done similar work recognises these instantly. Difficulty evidence is especially strong in interviews, because it invites exactly the follow-up question you want.

Evidence three: firsts and durability

Did something not exist before you, and does it still exist? That is an outcome, and often a more meaningful one than a percentage.

• "Wrote the department's first documented onboarding process; still in use."
• "Set up the incident log the team now uses for its quarterly review."
• "Introduced the pre-visit checklist that was later adopted by the other two sites."

The adoption clause in the last one is doing a lot of work: something spreading beyond its origin is external validation without a number.

Finding numbers you did not know you had

Before giving up on figures, check the ones that exist as facts about your work rather than as performance measures. Team size. Budget, or the value of what passed through your hands. Volume per day, week or month. Number of sites, systems, clients, suppliers, or stakeholders. Duration of a project. Number of people trained. Frequency of a cycle you owned.

Approximations are fine and honest if flagged: "roughly 60 a week", "around 25 staff". A hedged real number beats an invented precise one. What you must not do is quantify an improvement you did not measure — "increased efficiency by 30%" invented in a coffee shop is a fabrication that will be tested.

The shape of a good bullet

Verb, object, scale or condition, outcome. Not every bullet needs all four, but the ones that land usually have three.

• Flat: "Responsible for training new staff."
• Better: "Trained new starters."
• Good: "Trained 30 new starters over two years, and wrote the induction pack they worked from."
• Good: "Trained new starters through a period when turnover ran near 40%, and cut the time to independent working from six weeks to three."

The last two use different evidence types. Both work. Neither invents anything.

Two failure modes

The duty list

Describing what the job involved rather than what you did with it. "Duties included answering the telephone, filing, and diary management" tells a reader the title, which they already had. Every one of those duties can carry evidence: whose diary, how many, what happened when it went wrong.

The credit problem

Taking sole credit for team work is detected easily and damages you badly at reference stage. The fix is to name your part precisely, which is more impressive than vagueness: "one of four leads on the migration, responsible for the supplier data" is a stronger sentence than "led the migration" if you did not lead the migration.

A recovery exercise

If you are staring at a role and cannot find anything, answer these in plain sentences and then compress:

• What broke while I was there, and what did I do about it?
• What did I do that nobody asked me to do?
• What would have gone wrong if I had been away for a month?
• What did someone thank me for, and what specifically for?
• What did I build, write, or set up that is still being used?
• What did I learn to do there that I could not do before?

The answers are almost never nothing. They are usually just uncollected, because the job did not have a reporting line that captured them.