Example Achievement Log for a Project Coordinator

A year in the life of a Project Coordinator's log

• Jan - task: Took over Waypoint migration project from departing coordinator. Built fresh tracker in Excel with dependencies, resource allocation, and risk register. Ran first Friday standup with 14 attendees from facilities, IT, and operations.
• Mar - feedback: Marcus from IT said in the standup: 'This is the first time I've actually known what's blocking us.' Unblocked his team's database schema work same day.
• Mar - achievement: Waypoint migration hit March go-live on time despite February delay caused by vendor contract dispute I resolved. Zero critical incidents in first week. Three business units live, 89 user accounts migrated.
• Apr - task: Started managing Benefits Refresh project alongside Waypoint support. Stakeholder meetings ballooned to four separate calendars (HR, payroll, legal, comms). Built a single source-of-truth document to stop conflicting direction.
• Jun - task: Missed two tracker updates in a row due to competing urgent requests. Realized my spreadsheet approach was breaking under dual-project load. Moved both projects into Asana and set up automated weekly digest emails.
• Jun - achievement: Benefits Refresh stakeholder forum went from chaotic meetings with 30 minutes lost to scrolling email threads to 45 minutes focused discussion. HR director said scope creep had stopped for the first time.
• Aug - feedback: Sarah from legal told me in the corridor: 'You caught that contract language issue before it cost us six weeks.' That risk flag I'd added to Asana had actually mattered.
• Sep - achievement: Benefits Refresh UAT phase completed. 47 test cases run, 12 defects found and logged in the tracker by end-users themselves instead of me transcribing. Vendor fixed 8 before UAT close.
• Sep - task: Waypoint Phase 2 expansion started. Onboarded two more facilities (700 additional users). Inherited a non-existent communication plan so wrote one from scratch: 12 department kick-offs, FAQ document, helpdesk briefing.
• Nov - achievement: Benefits Refresh go-live landed on November 15. All payroll processes migrated. First pay run processed on new system without manual intervention. 4,200 employees enrolled in updated plans.
• Dec - feedback: Finance controller in the post-launch review: 'You forced us to make decisions early instead of letting them slide. That's exactly what we needed.' Three major dependencies locked six weeks before cutover.

What makes a strong entry

How this becomes your review in November

I coordinated two major platform migrations this year and delivered both on schedule. Waypoint migration went live in March with zero critical incidents and 89 users deployed; Benefits Refresh followed in November at 4,200 employees with the first pay run processed without manual workarounds. Early in the Waypoint project I recognized that scattered email threads were creating conflicting direction across four stakeholder groups, so I built a single source-of-truth document that the finance controller specifically credited for forcing early decisions rather than letting them slip. I also caught a contract language issue that would have cost six weeks in rework and set up automated Asana workflows that let end-users log their own UAT defects instead of bottlenecking through me.

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

• IT Project Manager achievement log example
• Project Manager achievement log example
• Product Manager achievement log example
• Delivery Manager achievement log example
• Program Manager achievement log example
• Business Analyst achievement log example