Free template · People / Finance / Legal
Performance review template for a controller
A ready-to-use, section-by-section template with the competencies that matter for a controller, role-specific example phrases, and a guard against the stock filler that makes most reviews read as generic. Copy the structure, fill in your evidence, or skip the writing entirely with Crestento.
The template
Four sections, in this order. Length should match the evidence you have — a thin section is honest; an invented paragraph is not.
Summary
One or two paragraphs setting the context: what was expected of controller this period, and your overall verdict. Lead with the headline.
Example phrasing
“Compressed monthly close from day 8 to day 4 across the year, led the year-end audit to a clean opinion with zero material findings, implemented the revenue-recognition policy aligned to ASC 606, and developed two staff accountants into senior accountants.”
Strengths
The behaviours and outcomes that made the work happen. Anchor in evidence: close cycle time (and trend), audit-opinion outcome and material-finding count, internal-control deficiencies (significant + material).
- Evidence for: GAAP / IFRS technical accounting.
- Evidence for: month-end and year-end close ownership.
- Evidence for: external audit leadership.
- Evidence for: financial reporting (internal and external).
Areas for Growth
Forward-looking development edges. Frame as opportunities, not deficiencies. Specific behaviours to develop, not generic controller criticism.
- One pattern observed across the period.
- One specific behaviour to develop.
- One concrete next step.
Goals for the Next Period
Two or three concrete goals. Each should name a specific behaviour change, a measurable target, and a deadline. Avoid vague aspirations.
Competencies to evaluate
The 7 competencies a strong controller review structures around, in priority order. Use these as the spine of the Strengths and Areas for Growth sections.
- GAAP / IFRS technical accounting
- month-end and year-end close ownership
- external audit leadership
- financial reporting (internal and external)
- internal controls design (SOX-ready or scaled)
- team leadership and development of accountants
- ERP and accounting-system administration
Before you write
Controllers own the accuracy and timeliness of the company's financials and the audit relationship that validates them. The work is technical (technical-accounting interpretation, internal controls, audit response) AND managerial (team development, cross-functional partnership with FP&A and ops). Strong controllers shorten close cycles without sacrificing quality. Weak controllers either run slow accurate close cycles or fast inaccurate ones.
Evidence to gather
Strong reviews for a controller cite evidence of these shapes. Only use a specific value (a percentage, a count, a dollar amount) if you actually have it — don’t invent a number to sound concrete.
- close cycle time (and trend)
- audit-opinion outcome and material-finding count
- internal-control deficiencies (significant + material)
- team retention and promotion pipeline
- financial-reporting deadlines met
- technical-accounting positions documented
Where to find the evidence
Work products a controller produces. Reference these by name in the review when they’re relevant — it signals you know the work.
- monthly / quarterly close package
- audit-response binder and PBC schedules
- internal-control documentation
- technical-accounting memos
- team development plans
- financial-reporting templates
- ERP configuration and process documentation
Phrasing that lands vs phrasing that doesn’t
Strong — specific, evidenced, role-appropriate
“Compressed monthly close from day 8 to day 4 across the year, led the year-end audit to a clean opinion with zero material findings, implemented the revenue-recognition policy aligned to ASC 606, and developed two staff accountants into senior accountants.”
Weak — vague, unevidenced, generic
“Strong controller.”
Phrases to never use
Stock filler that AI-written controller reviews slip into. Managers spot it instantly. Rewrite to name a specific behaviour instead.
- “strong controller”
- “trusted financial leader”
- “drives close cycle”
- “passionate about accuracy”
- “exceptional GAAP knowledge”
- “consistent audit performance”
- “raises the financial bar”
Don’t invent these specifics
The details an AI tends to fabricate for controllerreviews. If you don’t have the specific number, name, or date in your notes, leave it out — generic-but-honest beats specific-but- invented every time.
- specific close-cycle compression numbers not in input
- named audit firms or outcomes not mentioned
- specific technical-accounting positions (ASC 606, etc.) not in input
- particular internal-control improvements not provided
- named team members developed when not in input
- specific ERP implementations not mentioned
Skip the template, generate the review
Drop your bullet points into Crestento and it produces the polished draft using this exact template structure, tuned for a controller. Two reviews free, no card.
Try Crestento free