Example Achievement Log for a Advisory Associate

This log belongs to an Advisory Associate at a mid-size professional services firm who spends the year moving between client projects, building a regulatory compliance practice, and learning the firm's delivery model. The entries show a mix of client wins, internal process work, and the occasional false start that teaches something useful.

A year in the life of a Advisory Associate's log

Jan - task: Assigned to Hartwell Manufacturing compliance review under Michael Chen. Built baseline audit of their SOX controls across five process areas. No prior manufacturing experience, so spent first week reading their production and inventory systems.
Feb - achievement: Identified undocumented variance approval process in Hartwell's purchasing that created a 47% reject rate on control testing. Mapped the actual workflow, documented it, and got their operations manager to sign off on new sign-off matrix.
Feb - feedback: Michael Chen told me in our project debrief: 'You asked better questions than I did about why they were doing it that way instead of complaining it was wrong. That's the difference between advisory and audit.' Felt earned.
Apr - task: Took on support role for Brennan Foods transformation project while Hartwell work wound down. Their ERP was six months in and heavily over budget. Attended their weekly steering calls but was initially just taking notes.
May - achievement: Brennan's supply chain lead asked me to trace why accounts payable reconciliation was still 12 days behind SLA. Found their three-part approval workflow was routing to wrong cost centers. Rebuilt routing rules and cut the cycle to four days.
May - feedback: At Brennan's project closeout, their CFO Catherine Wu said in the all-hands call, 'This team figured out what we built wrong before it became a bigger problem.' Named me specifically in the email follow-up.
Jul - task: Started writing the firm's internal guidance on post-go-live ERP support models. Drew on both projects. First draft got feedback that it was too prescriptive for different company sizes, so I restructured it as decision trees.
Aug - achievement: Completed ERP support guidance document. Partner Rachel Okafor approved it for publication on the firm wiki. Three other associates have already cited it in new client proposals, so it's already generating reuse value.
Oct - task: Scoped a potential audit expansion with Hartwell for next year. Their CFO said their board was asking about control gaps we hadn't covered. Met with Michael three times trying to build the scope, but we couldn't find a clean engagement size.
Nov - achievement: Hartwell deal fell apart but Michael asked me to pitch it to Rachel as a custom advisory project instead of audit. We landed it as a six-week governance review at higher fee rate. First client I sourced and scoped myself.
Dec - feedback: Rachel told me in our year-end coffee: 'You're comfortable sitting in the ambiguity of a client problem longer than most people. You don't jump to the answer.' That's the feedback that sticks with you.

What makes a strong entry

What most people write: Improved accounts payable reconciliation process at Brennan Foods.

What went in the log: Brennan's supply chain lead asked me to trace why accounts payable reconciliation was still 12 days behind SLA. Found their three-part approval workflow was routing to wrong cost centers. Rebuilt routing rules and cut the cycle to four days.

The strong version names the person who asked, specifies the starting metric and root cause, and gives the endpoint number. Without these, the reviewer has no way to verify the claim or understand what you actually did.

What most people write: Wrote guidance document on ERP support models.

What went in the log: Completed ERP support guidance document. Partner Rachel Okafor approved it for publication on the firm wiki. Three other associates have already cited it in new client proposals, so it's already generating reuse value.

The strong version names the approver, identifies where it lives, and proves impact through a concrete downstream use. Six months later, the reviewer can check whether those proposals actually exist.

How this becomes your review in November

This year I delivered wins on two major client projects and built an asset the firm is already reusing. On the Hartwell Manufacturing and Brennan Foods engagements, I moved beyond documenting process gaps to actually tracing root cause and getting sign-off on fixes, which Michael Chen and Catherine Wu both noticed and said was the difference between checking boxes and advisory work. The ERP support guidance I wrote for the firm has already been cited in three new proposals, and Rachel approved it for the wiki because it uses decision trees instead of prescriptive rules. By October I had built enough client trust and project experience to scope the Hartwell governance engagement myself, moving it from a stalled audit deal into a custom advisory win at a higher rate.

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 Advisory Associate.