Department Annual Plan Template: Sections and Example

Every year, department heads are asked to submit their plans for the coming year. And every year, the plans arrive in different formats, at different levels of detail, with little visible link to the organisation’s strategy.
A shared department annual plan template solves most of that. It gives every department the same structure, forces the link to strategy, and makes plans easy to compare, approve and track. This guide walks through the eight sections we recommend, shows a filled example for an IT department, and explains how to review the plan each quarter so it does not end up in a drawer.
What Is a Department Annual Plan?
A department annual plan sets out what one department will achieve over a single fiscal year, how it will do it, with what resources, and who is responsible. It sits between the organisation’s strategy and the department’s day-to-day work.
As Asana’s annual planning guide puts it, strategic planning sets a long-term roadmap for three to five years, while annual planning focuses on goals for a single fiscal year. The department plan is one slice of that larger picture.
How It Connects to Other Plans
Strategic plan: three to five years, organisation-wide direction.
Organisation annual plan: this year’s priorities for the whole organisation.
Department annual plan: this department’s share of those priorities.
Operational plans and budgets: detailed activities, tasks and costs.
If your organisation does not yet have a clear strategy to cascade from, start with our practical guide for strategy formulation.
Department Annual Plan Template: The 8 Sections
Keep the main document short, ideally a few pages, and move detail into appendices.
1. Department Overview and Mandate
The department’s purpose in one or two sentences.
Main services or outputs and who they serve.
Team size and structure.
2. Review of Last Year
Objectives achieved and missed, with short reasons.
Initiatives carried over into the new year.
Key lessons on delivery, resources and dependencies.
3. Annual Objectives Linked to Strategy
A small number of objectives for the year.
For each one, the strategic objective it supports.
If an objective cannot be linked to any strategic goal, question whether it belongs in the plan.
4. KPIs and Targets
One to three KPIs per objective.
Baseline, target and measurement frequency for each.
Data source and owner.
5. Initiatives and Projects
The initiatives that will deliver each objective.
Scope, expected outputs, start and end dates.
6. Resources and Budget
People, technology and budget needed for each initiative.
Link to the operating budget submission. Wikipedia’s article on operational planning notes that operational plans form the basis of the annual operating budget, so the two should be built together, not separately.
7. Owners and Quarterly Timeline
One owner per objective and initiative.
Key milestones spread across the four quarters.
8. Risks and Dependencies
Main risks to delivery and how they will be handled.
Dependencies on other departments, suppliers or approvals.
Filled Example: An IT Department
The example below is illustrative. It shows how the sections fit together, not recommended targets.
Overview
Mandate: provide reliable systems and digital services for all departments.
Team: infrastructure, applications and service desk units.
Last Year in Brief
Data centre migration completed.
Service desk response target missed because of staff shortages in the second half.
Two application upgrades carried over.
Objectives, KPIs and Initiatives
Objective 1: Improve internal service quality (supports the strategic goal of operational efficiency).
KPI: share of service desk tickets resolved within the agreed time, measured monthly.
Initiatives: self-service portal for common requests; knowledge base for the service desk.
Objective 2: Strengthen cybersecurity (supports the strategic goal of resilience).
KPI: share of critical patches applied within the agreed window, measured monthly.
Initiatives: patch management automation; awareness training for all staff.
Objective 3: Deliver carried-over upgrades (supports digital transformation).
KPI: upgrade milestones completed on schedule, measured quarterly.
Resources, Owners and Timeline
Budget lines for the portal licence, security tooling and contractor support.
Owners: head of service desk (Objective 1), information security lead (Objective 2), applications manager (Objective 3).
Q1 portal design, Q2 launch, Q3 upgrades, Q4 review.
Risks
Delays in procurement approvals.
Dependence on business departments for user testing.
This is how a department annual plan template turns a list of wishes into a plan that can be tracked.
How to Fill in the Template Step by Step
Start from the organisation’s priorities. Get the approved annual priorities before drafting.
Review last year honestly. Use actual KPI results, not impressions.
Draft objectives with your team. People who helped write the plan are more committed to delivering it.
Define KPIs and targets. Base targets on historical data.
Cost the initiatives. Agree the numbers with finance before submission.
Assign owners and milestones. One name per line, not a team.
Submit, discuss and finalise. Expect at least one round of feedback from leadership.
Share the final plan with the whole team. Asana’s guide stresses making the annual plan “everyone’s plan”, so each person can see where their work fits.
How to Run Quarterly Reviews
A plan without reviews is forgotten by the second quarter. Keep the routine simple:
Quarterly progress report: status of each objective and initiative, with colours agreed in advance.
Review meeting: discuss only items that are behind, and leave with decisions.
Mid-year adjustment: update targets or initiatives if priorities change, and record why.
Year-end report: summarise results and feed them into next year’s plan and the organisation’s annual report.
Tips and Common Mistakes
Tips
Use the same department annual plan template across all departments, so leadership can compare plans quickly.
Keep objectives few and specific.
Build in some capacity for unplanned work.
Translate the plan into detailed operational plans for each unit.
Mistakes to Avoid
Copying last year’s plan and changing the dates.
Objectives without KPIs, or KPIs without targets.
No link to the budget, so approved initiatives have no funding.
Shared ownership, which usually means no ownership.
No reviews until year-end.
Conclusion
A good department annual plan template gives every department the same eight building blocks: mandate, last year’s review, objectives linked to strategy, KPIs and targets, initiatives, resources, owners and timeline, and risks. Fill it in with your team, connect it to the budget, and review it every quarter. That is what turns an annual plan from a compliance exercise into a tool that actually guides the year.
Plan Your Next Year with Empower
Want every department plan to line up with your strategy and budget? Empower’s Strategic Management consultants help you design the planning framework, templates and quarterly review routine, and support departments through their first cycle.
Learn more on the Empower homepage, or contact our team to discuss your planning calendar.
FAQs
What should a department annual plan include?
It should include the department’s mandate, a review of last year, annual objectives linked to strategy, KPIs and targets, initiatives, resources and budget, owners and timeline, and key risks.
Who prepares the department annual plan?
The department head leads it with input from the team, using the organisation’s priorities as a starting point. The strategy or planning office usually provides the template and reviews the drafts.
When should departments start their annual plans?
Annual planning usually takes place near the end of the fiscal year. Starting three to four months before the new year leaves time to review results, cost initiatives and get approvals.
How is a department annual plan different from an operational plan?
The annual plan sets the department’s objectives, KPIs and main initiatives for the year. The operational plan breaks those down into detailed activities, tasks and schedules.