Example Achievement Log for a Operations Manager

This Operations Manager has tracked a year of scheduling chaos, vendor negotiations, and a major system migration alongside the daily firefighting. The log shows how concrete numbers and named wins survive memory better than vague 'process improvements' do.

A year in the life of a Operations Manager's log

Jan - task: Took over the warehouse staff schedule after Marcus left mid-shift. First two weeks were hand-written rosters and angry texts from night shift. Switched to Deputy by end of month, cut call-outs from 18% to 11%.
Jan - feedback: Saul from the warehouse floor told me: 'People actually know when they're working now.' Said it at the coffee machine, but it stuck.
Mar - achievement: Renegotiated Grainger industrial supply contract. Cut unit costs by 12%, saved £8400 over the year. Kept same 2-day delivery window they had before.
Apr - task: Started audit prep for the ISO 9001 recertification. Built a compliance tracker in Excel, assigned responsibilities to team leads, scheduled audit for October.
May - achievement: Led the move from the old inventory system (Navision, horrific) to Cin7. Three weeks of parallel running, wrote the staff guide, hit zero order gaps on day one of cutover.
Jun - feedback: Janet, our Finance Director, said during the handover meeting: 'You actually gave us training that made sense. Most people hand over a 200-page manual and run.' Mentioned it in the June all-hands.
Jul - task: Hiring freeze lifted. Recruited two new warehouse supervisors and an office coordinator. Took longer than planned, but both supervisors had logistics experience, not internal promotion gambles.
Sep - achievement: Resolved a supplier payment dispute with Legrand that had been sitting since April. Their invoice was duplicated in our system. Recovered £2860 and improved the three-way match process so it won't happen again.
Sep - task: Final weeks of ISO audit prep. Site walkthrough revealed outdated signage and one unlabeled chemical. Fixed both, updated procedures. Audit is now 11 days away.
Nov - achievement: Passed ISO 9001 recertification with zero non-conformances. Auditor signed off in one day.
Dec - task: Year-end inventory count took two days instead of our usual three. New system and trained count team paid off. Variance came in at 0.8%, down from 1.4% last year.

What makes a strong entry

What most people write: Improved scheduling process and reduced absences.

What went in the log: Took over the warehouse staff schedule after Marcus left mid-shift. First two weeks were hand-written rosters and angry texts from night shift. Switched to Deputy by end of month, cut call-outs from 18% to 11%.

The strong version names the predecessor, shows the failure state (hand-written, reactive), names the tool (Deputy), and gives the before/after number (18% to 11%). Without these details, the reviewer has no way to distinguish this from someone who tweaked a spreadsheet.

What most people write: Led system migration and trained the team.

What went in the log: Led the move from the old inventory system (Navision, horrific) to Cin7. Three weeks of parallel running, wrote the staff guide, hit zero order gaps on day one of cutover.

The strong version names the systems (Navision to Cin7), specifies the method (parallel running), shows the work (wrote the guide), and gives the outcome metric (zero gaps on day one). A vague entry would not let your reviewer explain why this matters in a promotion conversation.

How this becomes your review in November

This year I've owned both the planned change and the operational baseline. The Navision to Cin7 migration was the biggest move: three weeks of parallel running, a guide I wrote from scratch, and we hit zero order gaps on day one of cutover. Alongside that, the ongoing work kept going: renegotiated Grainger and cut costs by 12%, passed ISO 9001 recertification with zero non-conformances, and fixed the scheduling chaos that Marcus left by switching to Deputy, which cut call-outs from 18% to 11%. By December the year-end count was done in two days instead of three, and variance dropped to 0.8%.

Starting your own log

Don't try to reconstruct a year you have already had. Start from today, one line whenever something happens, and let it build. The Perform Review Achievement Log does this for you and can capture wins straight from Slack, and how to start an achievement log covers the wider playbook.

Example Logs for Related Roles

Ready to start your own? Start your Achievement Log free, see how the Perform Review Achievement Log works, or browse performance review phrases for Operations Manager.