Brag document template for financial analysts

What this role is measured on

Forecast accuracy is the foundation of everything else in this role, because it is the thing that determines whether anyone believes your next number. An analyst whose forecasts land close to actuals is trusted when they say something surprising; one whose forecasts are consistently off is discounted even when they are right. Tracking your own accuracy over time, and reporting it honestly including the misses, is the single most credible thing you can put in a review.

Decision influence is the value axis. A model that sat in a folder produced nothing. A model that changed an investment decision, killed a proposal, or resized a budget produced a specific outcome, and that outcome is what to report.

Close and reporting reliability is the operational floor. Hitting the close calendar, producing accurate reporting, and doing it without a scramble is unglamorous and is the precondition for being trusted with anything more interesting.

Cost and margin work is where analysts most directly move the business. Finding the line item that was quietly growing, or the pricing assumption that no longer held, is high-value work that only someone in this seat is positioned to notice.

Model quality is the fourth axis: something you built that other people now run themselves is a durable asset rather than a one-off answer.

Wins that read well for this role

• "Held forecast variance within across , including ."
• "Analysis of surfaced , which changed the decision on ."
• "Identified growing at against plan, and the intervention recovered ."
• "Closed reporting cycles on the calendar with restatements."
• "Built now run independently by , replacing a request that used to come to me ."

Common undersell

Analysts undersell accuracy because tracking your own misses feels like documenting failure. It is the opposite: an analyst who can show their forecast error narrowing over time is demonstrating the core competence of the role, and one who never mentions accuracy invites the assumption that it was not good.

The second undersell is the scenario that did not happen. Modeling a downside case that persuaded the business to hold back, followed by the downside not materializing, looks in hindsight like unnecessary caution and was in fact the analysis working.

The third is automation of the routine. Every recurring report you automated is permanent recovered capacity, and it disappears into the general sense that reporting simply happens.