How to write resume achievements you can back up

Start with something you could show someone

Pick one piece of work you remember well. If a coworker had to pick up where you left off, what would you hand over? Maybe it’s a spreadsheet you revised, a booking form you tested, or an answer a support agent can send to a customer. Write down what it was, what you personally did, and how you knew the work was done. You now have the raw material for a resume bullet.

A responsibility tells the reader what came with the job. An achievement tells them what came of your work. “Tracked 20 open tasks” gives us a sense of the workload. To say the team missed fewer deadlines, you’d also need to know how often it missed them before and after.

In your notes, finish the sentence “I did ___, and afterward ___.” Jot down how you know. The short version goes on your resume. The rest comes in handy when an interviewer asks, “How did you measure that?”

Three resume achievement examples with numbers

The six examples below are fictional. For your own resume, use figures you can verify and share.

A weekly report

Before · Prepared weekly reports.

After · Redesigned the weekly report template, cutting average hands-on preparation time from 120 to 45 minutes.

The time log covers four weekly reports before the template change and four after. Each report covered the same work, and the log counted only the time spent preparing it. That’s an hour and a quarter back per report, on average. What the department did with the extra time is anyone’s guess.

A database cleanup

Before · Worked with the customer database.

After · Reviewed 240 records and removed 24 confirmed duplicates after the database owner approved the list.

The reviewer checked IDs and contact details using the agreed rules for spotting duplicates. You can count the removals by comparing the original file with the cleaned copy. Ten percent of the reviewed records were removed as duplicates. That fraction tells you how much of the list was cleaned up. To claim the database became 10% more accurate, you’d need to measure accuracy before and after.

A booking form for a class project

Before · Participated in a software project.

After · Built a form for booking consultations in a class prototype. After the fixes, the form passed all 20 test cases.

The student built the form. Classmates built the rest of the prototype. The test log gives the word all a precise meaning. It lists the 20 cases the form passed after the fixes. It can’t tell you how many people went on to use it.

Three resume accomplishments without numbers

If you didn’t track a number, ask what someone could use on Friday that didn’t exist on Monday. Sometimes the answer is a document with a very boring filename. Open it anyway.

Meeting minutes people could act on

Before · Helped the team with documents.

After · Recorded what the team agreed to do at each meeting and sent the minutes that same day.

Emily Carter, the fictional administrative assistant at Maplebridge Services, has the minutes and a timestamp in her Sent folder. That’s enough to claim a same-day turnaround. Whether everyone carried out those decisions on time is another story. See how this detail fits into Emily’s resume for a project coordinator role.

An account recovery guide

Before · Handled support documentation.

After · Wrote an account recovery guide, got it approved by a specialist, and published it in the support knowledge base.

The draft, the specialist’s sign-off, and the live guide each back up a verb in that bullet. If an interviewer asks whether ticket volume fell, “We didn’t track that” is a perfectly good answer. You can still explain which instructions needed the specialist’s review.

Your part in a team launch

Before · Launched the new help section.

After · Edited the answers for the new help section and checked the wording with a subject matter expert before the team published the page.

The developers built the page. A manager made the call to publish. Ask the editor what changed between the first draft and the approved answers, though, and you’ve got the right person.

Choose the bullet you’ll use

Read the job posting and pick a bullet that answers a question the hiring team might ask. If the job involves weekly reporting, the template shows you know how to save time on a recurring task. If you’d be writing support articles, the account recovery guide shows you can take a draft through technical review and get it published. The flashiest number on the page may have very little to do with the job.

Read the bullet aloud. Would you be comfortable answering these four questions in an interview?

• Which verb describes my own work?

• Can I explain what was measured, over what period, and for which part of the project?

• If there’s no measurement, what finished item or handoff shows the result?

• Could a teammate recognize both my part and theirs?

Keep the full account in your notes. If you use AI to shorten it, compare the final sentence with those notes, especially the verbs. “Edited” can become “led” in a keystroke. Promotions generally take longer.

When you’re ready to use the bullet in an application, build your resume with Mansap. For another way to organize your notes around the project, your actions, and the result, see MIT’s guide to writing about your skills.