Example Achievement Log for a Business Analyst

A year in the life of a Business Analyst's log

• Jan - task: Took over KYC intake analysis from departing team member. Spent first two weeks mapping the current flow: 847 applications per month, 12 day average turnaround, four handoff points where documents get lost.
• Mar - achievement: Rewrote KYC document checklist in Salesforce. Automated three validation steps that were manual. Reduced turnaround to 8 days average. Caught 34 missing documents in first week that would have failed compliance.
• Mar - feedback: Compliance director said in standup: 'That checklist saved us an audit flag. Good granular thinking.' Stuck with me because she rarely says much.
• Apr - task: Started requirements gathering for Claims API overhaul. Met with five backend teams, four business units, compliance. Discovered conflicting priorities: speed vs audit trail depth. No clear owner yet.
• Jun - task: Claims API requirements work stalled. Realized we lacked a single decision-maker. Escalated to VP of Engineering and VP of Ops jointly. Took three weeks to get both in same room, but they set a trade-off framework.
• Jun - achievement: Delivered Claims API spec after the decision framework landed. 87 pages, covered async patterns, retry logic, three audit levels. Engineering signed off in two rounds with only minor reworks.
• Aug - feedback: Product manager told me after spec review: 'You went back and fixed the async section without being asked. That's the difference between analysis and listening.' Said it in front of the platform team.
• Sep - achievement: Built automated dashboard tracking Claims API adoption across business units. Updated daily from Datadog. Showed 62% of internal calls now use new endpoint. VP of Ops cited it in monthly board update.
• Sep - task: Asked to do cost-benefit analysis on migrating legacy claims batch process to event-driven. Modeled infrastructure costs, dev time, risk. Found migration cost $340k but saves $180k annually. Broke in estimating dev time by 200 hours.
• Nov - achievement: Revised migration estimate after getting feedback from two engineers who'd done similar work. Remodeled at $265k cost, same annual savings. Estimate flagged by finance as 'realistic.' Steering committee approved pilot.
• Dec - task: Drafted end-of-year patterns report: three quarters focused on KYC/Claims work, one large spec delivered, one cost model used in capital decisions, one process rollback avoided.

What makes a strong entry

How this becomes your review in November

I spent the year owning two substantial process pieces: the KYC intake overhaul, which reduced document turnaround from 12 days to 8 and caught 34 compliance gaps in the first week, and the Claims API specification, which took three months of stakeholder alignment before I could deliver 87 pages that engineering signed off on with minimal rework. The Claims API work taught me the value of naming conflicts explicitly, I had to escalate to get both VP-level owners in a room, but once the decision framework was clear, the spec came together quickly. I also built the adoption dashboard that the board cited, and my revised migration estimate for the legacy batch process (after incorporating feedback from engineers who'd done similar work) was flagged by finance as realistic enough to move into pilot phase.

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

• Project Coordinator achievement log example
• Agile Coach achievement log example
• Project Manager achievement log example
• Product Manager achievement log example
• Technical Program Manager achievement log example
• IT Project Manager achievement log example