Many examples on a resume read more strongly when they show what came of the work, not just the activity. "Managed the reporting process" describes a task; adding what it led to, faster reporting, fewer errors, better-informed decisions, turns it into evidence. This article covers finding honest measures for your work, and the evidence that matters when no number exists.
Numbers help where they are accurate
A genuine metric is not always easy to find. Plenty of public service work does not produce a tidy figure, and it can take real thought to work out how to measure what you did. Where an accurate number exists, it is worth the effort: improving the efficiency of a process by a stated percentage is a concrete, checkable statement of impact.
But impact does not require a number, and a clear non-numeric contribution is not a weaker one. A policy you helped shape, a process you redesigned, a system you introduced, advice that informed a decision: these are real, describable impacts. The question is not "is there a number here" but "did something change because of my work, and can I describe that change clearly".
Where public-sector evidence lives
If you are stuck, start from how your work is assessed. What does your manager look at? What would show your team had a good year? Common forms in public-sector work:
- Timeliness: processing times, response times, turnaround on advice, delivery against deadlines.
- Volume and coverage: caseloads, applications processed, reports produced, stakeholders or regions covered.
- Accuracy and quality: error rates, audit findings, rework reduced, standards met.
- Service: satisfaction results, complaints resolved, accessibility improved, backlogs managed.
- Risk, compliance and governance: risks identified and reduced, compliance rates, assurance strengthened.
- Efficiency and cost: time saved, steps removed, the same work done with fewer resources.
- Advice and influence: briefs and submissions prepared, consultations completed and their scale, the decisions or changes your analysis supported.
- People: staff supported, trained or developed; survey results for a team you led.
For project work, add budget, team size, stakeholder breadth and delivery against timeframe. For analytical work, the systems implemented, datasets consolidated, reporting made possible.
Context can matter as much as the figure. A result achieved after a long period without progress, or under unusual constraints, is a different story from the same number in easy conditions, and a brief note of that context is worth including where true.
Intermediate contributions count too. If you moved on before the final outcome landed, or the outcome belonged to many people, the parts that were yours are still evidence: the backlog assessed, the requirements settled, the pilot delivered, the tool built. Describe them as what they are: "contributed to", "provided analysis for", "developed the tool used to". Claiming the whole outcome because your work formed part of it is the thing to avoid.
Keeping figures honest and explainable
Never invent or inflate a figure, and do not force one where none exists. Anything on a resume can be asked about, and a figure you cannot explain, where it came from, how it was measured, what your part was, does more damage than none. A defensible estimate presented as an estimate is fine. Surprising claims tend to draw sharper questions, so every figure should be one you would be comfortable walking a panel through.
Where no measurable change exists, scale still does: team size, caseload, complexity, the seniority of those your work supported, the accuracy the task demanded. That material belongs in the role overview described in the experience-section article.