Free template · Operations
Performance review template for an operations manager
A ready-to-use, section-by-section template with the competencies that matter for an operations manager, 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 operations manager this period, and your overall verdict. Lead with the headline.
Example phrasing
“Reduced average order-fulfilment time from 4.2 days to 2.8 days through a documented workflow redesign, held operating costs flat through a 22% volume growth period, and developed two team leads into supervisor roles.”
Strengths
The behaviours and outcomes that made the work happen. Anchor in evidence: cycle time / lead time on core operations, cost per unit / operational cost ratio, SLA adherence rate.
- Evidence for: process design and operational efficiency.
- Evidence for: vendor and supplier management.
- Evidence for: team leadership and people development.
- Evidence for: cost control and budget management.
Areas for Growth
Forward-looking development edges. Frame as opportunities, not deficiencies. Specific behaviours to develop, not generic operations manager 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 operations manager review structures around, in priority order. Use these as the spine of the Strengths and Areas for Growth sections.
- process design and operational efficiency
- vendor and supplier management
- team leadership and people development
- cost control and budget management
- compliance, safety, and risk
- cross-functional partnership (finance, sales, customer-facing teams)
- KPI dashboards and operational reporting
Before you write
Operations managers are evaluated on three things at once: the run-rate of the business (everything that has to happen every week), the improvements they ship on top of that (process redesigns, cost reductions, capability builds), and the team they develop. Strong ops managers make the business cheaper and more predictable over time. Weak ops managers fight fires and never build the systems that prevent fires.
Evidence to gather
Strong reviews for an operations manager 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.
- cycle time / lead time on core operations
- cost per unit / operational cost ratio
- SLA adherence rate
- team retention and promotion pipeline
- vendor performance metrics (on-time, in-spec)
- compliance / safety incident rate
- capacity utilisation
Where to find the evidence
Work products an operations manager produces. Reference these by name in the review when they’re relevant — it signals you know the work.
- process / workflow documentation (SOPs)
- weekly operational KPI dashboard
- vendor scorecards and contract reviews
- budget actuals vs plan reporting
- team development plans
- process-improvement project briefs
- safety / compliance audit responses
Phrasing that lands vs phrasing that doesn’t
Strong — specific, evidenced, role-appropriate
“Reduced average order-fulfilment time from 4.2 days to 2.8 days through a documented workflow redesign, held operating costs flat through a 22% volume growth period, and developed two team leads into supervisor roles.”
Weak — vague, unevidenced, generic
“Strong operations leader.”
Phrases to never use
Stock filler that AI-written operations manager reviews slip into. Managers spot it instantly. Rewrite to name a specific behaviour instead.
- “strong operations leader”
- “drives operational excellence”
- “consistent and reliable”
- “trusted partner to the team”
- “passionate about operations”
- “consistently delivers results”
- “wears many hats”
Don’t invent these specifics
The details an AI tends to fabricate for operations managerreviews. 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 cycle-time or cost-reduction percentages not in input
- named process improvements or projects the manager didn't write
- particular methodology adoption claims (Lean, Six Sigma) not mentioned
- specific vendor or supplier names not in input
- named direct reports the manager didn't reference
- exact budget figures 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 an operations manager. Two reviews free, no card.
Try Crestento free