Free template · Operations
Performance review template for a business analyst
A ready-to-use, section-by-section template with the competencies that matter for a business analyst, 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 business analyst this period, and your overall verdict. Lead with the headline.
Example phrasing
“Led requirements for the order-to-cash redesign, mapped the as-is and to-be processes with the four functional leads, built the business case that secured the $180K project budget, and ran the change-management plan through cutover.”
Strengths
The behaviours and outcomes that made the work happen. Anchor in evidence: projects delivered (count and complexity), requirements stability (change requests post-baseline), stakeholder satisfaction signal.
- Evidence for: requirements gathering and elicitation.
- Evidence for: process mapping (as-is / to-be).
- Evidence for: stakeholder facilitation across functions.
- Evidence for: data analysis and reporting.
Areas for Growth
Forward-looking development edges. Frame as opportunities, not deficiencies. Specific behaviours to develop, not generic business analyst 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 business analyst review structures around, in priority order. Use these as the spine of the Strengths and Areas for Growth sections.
- requirements gathering and elicitation
- process mapping (as-is / to-be)
- stakeholder facilitation across functions
- data analysis and reporting
- business case development
- change-management support
- documentation rigor (BRD, FRD, user stories)
Before you write
Business analysts translate ambiguous business problems into work that can actually be delivered. The craft is in facilitating stakeholders into agreement on requirements, mapping processes accurately, and writing documentation that holds up during build and after launch. Strong BAs prevent the worst rework by getting the requirements right upfront. Weak BAs document what they're told and miss the structural issues.
Evidence to gather
Strong reviews for a business analyst 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.
- projects delivered (count and complexity)
- requirements stability (change requests post-baseline)
- stakeholder satisfaction signal
- business case adoption rate (proposals that became projects)
- post-launch defect rate attributable to missed requirements
Where to find the evidence
Work products a business analyst produces. Reference these by name in the review when they’re relevant — it signals you know the work.
- BRD (Business Requirements Document)
- FRD (Functional Requirements Document)
- process maps (as-is and to-be)
- user stories and acceptance criteria
- business case / ROI analysis
- stakeholder map and RACI
- change-management plan
Phrasing that lands vs phrasing that doesn’t
Strong — specific, evidenced, role-appropriate
“Led requirements for the order-to-cash redesign, mapped the as-is and to-be processes with the four functional leads, built the business case that secured the $180K project budget, and ran the change-management plan through cutover.”
Weak — vague, unevidenced, generic
“Helped the team understand the requirements.”
Phrases to never use
Stock filler that AI-written business analyst reviews slip into. Managers spot it instantly. Rewrite to name a specific behaviour instead.
- “strong analytical mindset”
- “great with stakeholders”
- “consistently delivers insights”
- “trusted partner to the business”
- “passionate about analysis”
- “drives clarity in complex situations”
- “bridge between business and tech”
Don’t invent these specifics
The details an AI tends to fabricate for business analystreviews. 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 project names or budgets not in input
- named functional leads or stakeholders not mentioned
- specific documentation deliverables (BRD, FRD) not referenced
- particular methodology adoption (Agile, BABOK) not in input
- specific change-management outcomes not provided
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 business analyst. Two reviews free, no card.
Try Crestento free