Annual Operating Plan: 12-Week Process, Template and Example
8 min read ยท 2026-10-25
An annual operating plan (AOP) is the one-year plan that turns company strategy into specific targets, initiatives, headcount and budget for each team, with owners and quarterly milestones. Most companies build it in the last three or four months of the fiscal year so it is approved before the new year starts.
The hard part is not the template. It is the process: getting leadership to set targets early, getting departments to submit plans that add up, closing the gap between what teams ask for and what the business can fund, and keeping the plan alive after the board approves it. The roadmap below covers that 12-week build, then shows what the finished plan should contain and how to run it through the year.
The roadmap at a glance
Goal: A board-approved annual operating plan, with targets, initiatives, headcount and budget for every department, is cascaded to all teams before the fiscal year starts. Duration: 12 weeks
Kickoff and planning calendar (Weeks 1-2)
Set the rules, the dates and the templates before anyone starts planning.
- Agree on the planning calendar with the CEO and CFO, working back from the board meeting date.
- Name a planning lead (often FP&A or the chief of staff) and one planning owner in each department.
- Send a planning pack: last year's results, the strategic priorities, the department template and the submission deadlines.
- Hold a 60-minute kickoff with department heads to walk through the calendar and the template.
Milestone: Calendar, templates and planning owners confirmed, and the kickoff held with every department head.
Review last year and set top-down targets (Weeks 2-4)
Agree on where the company stands and what it must achieve next year.
- Review this year's results against plan: revenue, margin, cash, headcount and the status of each major initiative.
- Build a baseline forecast for next year if nothing changes.
- Have the executive team set three to five company goals and the top-line targets, such as revenue, operating margin and cash.
- Translate company targets into guidance for each department, such as a cost envelope or a pipeline target.
Milestone: Company goals and top-line targets approved by the executive team and shared with department heads.
Department plans and bottom-up budgets (Weeks 4-7)
Get each team's plan for how it will hit its share of the targets.
- Each department fills the template: goals, key initiatives, KPIs with targets by quarter, headcount and non-headcount costs.
- Ask every initiative to state its owner, start and end quarter, cost and expected result.
- Flag cross-team dependencies, such as a sales target that needs a product release in Q2.
- Hold a working session between finance and each department to check assumptions before submission.
Milestone: Every department submits a complete plan on the template by the deadline.
Consolidation and gap closing (Weeks 7-9)
Make the plans add up to the targets and fit the budget.
- Consolidate all submissions into one model and compare against the top-down targets.
- Rank the initiatives across departments by impact on company goals and by cost.
- Run trade-off sessions with the executive team to cut, delay or fund initiatives until the plan balances.
- Test a downside scenario and decide which spend is triggered only if targets are met.
Milestone: A balanced draft plan, with the gap to target closed or explained, signed off by the CEO and CFO.
Board review and approval (Weeks 10-11)
Get formal approval from the board or the owners.
- Prepare the board deck: goals, targets, key initiatives, headcount, P&L, cash and main risks.
- Pre-brief the board chair or key directors one week before the meeting.
- Present the plan, record the questions and agree on any changes.
- Update the model with the final changes and lock version 1.0.
Milestone: The annual operating plan approved by the board and locked as the baseline for the year.
Cascade and launch (Week 12)
Make sure every team knows its targets and how progress will be tracked.
- Share each department's final targets, budget and headcount with its leader.
- Load budgets into the finance system and KPIs into the reporting dashboard.
- Present the plan at an all-hands with the three to five company goals.
- Set the calendar for monthly reporting and quarterly business reviews.
Milestone: Every department has its approved targets and budget, and the first quarterly review is on the calendar.
What an annual operating plan contains
A good AOP fits in one model and one deck. The model holds the numbers. The deck tells leadership and the board why the numbers make sense.
Keep every initiative on a single line with an owner, timing, cost and expected result. If an initiative cannot be described that way, it is not ready to be funded.
- Company goals: three to five, each tied to the strategy.
- Financial targets: revenue, gross margin, operating expenses, operating margin and cash, by quarter.
- Department plans: goals, KPIs with quarterly targets and key initiatives for each team.
- Headcount plan: new roles by team and by quarter, with start dates.
- Budget: headcount and non-headcount costs by department, plus capital spending if relevant.
- Risks and assumptions: the main ones, with an owner and a fallback for each.
- Operating cadence: how progress is reported monthly and reviewed quarterly.
Annual operating plan vs strategic plan vs budget
People often mix these up. The strategic plan looks three to five years ahead and sets direction: which markets, which products, what the company wants to become. The annual operating plan takes the next 12 months of that strategy and makes it concrete, with targets, initiatives, owners and money. The budget is the financial part of the AOP: what each team can spend.
A budget without the rest of the AOP tells teams how much they can spend but not what they should achieve with it. An AOP without a link to strategy becomes a list of projects that do not add up to anything. You need all three, in that order.
Example: an AOP for a 300-person software company
Here is how one line per department could look for a business-to-business software company with a fiscal year that matches the calendar year.
Each line follows the same pattern: goal, initiative, owner and the quarter it lands. That makes the quarterly review fast, because you only discuss the lines that are off track.
- Company goals: grow annual recurring revenue, reach a positive operating margin in Q4, and launch in one new region.
- Sales (owner: CRO): add a mid-market team in Q1, pipeline targets by quarter, new region live in Q3.
- Marketing (owner: CMO): launch the partner referral program in Q2, cost per qualified lead target by quarter.
- Product and engineering (owner: CTO): ship the enterprise permissions release in Q2, which sales needs for the upmarket push.
- Customer success (owner: VP Customer Success): reduce churn in the smallest accounts with a new onboarding program in Q1.
- Finance and people (owners: CFO, CHRO): hiring plan of new roles phased by quarter, with Q3 and Q4 roles released only if Q2 revenue is on target.
Who owns what
The AOP process stalls when everyone thinks finance owns it. Finance runs the process and the model, but each leader owns their plan and their numbers.
Write these roles in the planning pack so nobody is surprised in week seven.
- CEO: sets company goals, makes the final trade-offs, presents to the board.
- CFO or head of FP&A: owns the calendar, the template, the model and consolidation.
- Department heads: own their goals, initiatives, KPIs, headcount and budget submissions.
- Planning owners in each department: gather inputs and fill the template on time.
- Chief of staff or PMO lead: tracks dependencies between departments and runs the quarterly reviews.
- Board: challenges and approves the plan.
How to present it to the board
Open with one slide that answers three questions: what we will achieve, what it will cost, and what could go wrong. Put the company goals, the top-line targets by quarter, the headcount change and the top three risks on that slide. Everything else goes in the appendix.
Then show the bridge from this year to next year: where the growth comes from and where the cost increases go. Boards often ask what happens if revenue comes in lower than planned, so show the downside scenario and the spending you would hold back. Leave out the line-by-line department detail unless someone asks for it.
How to keep the plan alive during the year
An AOP that is approved in December and opened again next November has not done its job. Set a monthly report with actuals against plan for the financial targets and the main KPIs, and a quarterly business review where each leader covers their lines that are off track.
Many companies also reforecast each quarter. Keep the approved AOP as the fixed baseline, and track the latest forecast next to it. That way you can see both whether the company will hit the plan and why it changed. When an initiative is cut or delayed, record the decision and its owner in a change log so the next planning cycle learns from it.
How to adapt it
A startup with under 50 people can run a lighter version in four to six weeks: company goals, a hiring plan, a simple budget and a list of initiatives with owners. The founders can set targets and approve trade-offs in one or two working sessions.
A large or multi-entity company needs more time and more layers: business unit plans, regional plans and a central consolidation. Start earlier, add a mid-point review of draft submissions, and agree on shared assumptions such as exchange rates, salary increases and inflation before departments start, so their numbers can be compared.
Common mistakes to avoid
- Letting departments plan before targets are set leads to plans that cannot be funded, so share top-down targets and cost guidance before submissions open.
- Treating the AOP as a finance exercise leaves leaders without ownership, so make each department head present and defend their own plan.
- Listing initiatives without owners or costs makes trade-offs impossible, so require owner, timing, cost and expected result for every line.
- Ignoring dependencies between teams causes missed targets in the middle of the year, so map the key ones during submissions and track them quarterly.
- Approving the plan and filing it away makes it useless by Q2, so schedule monthly reporting and quarterly reviews before the year starts.
- Starting the process too late forces rushed cuts, so work back from the board meeting date and start at least three months before year end.
Frequently asked questions
What is the purpose of an annual operating plan?
It turns the company strategy into a one-year plan that every team can act on. It sets targets, assigns owners, allocates headcount and budget, and gives leadership a baseline to track progress against during the year.
When should you start the annual operating plan process?
Many companies start about three months before the fiscal year ends, working back from the board meeting where the plan will be approved. Larger companies with many business units often start earlier. Starting too late usually leads to rushed cuts and plans that do not add up.
Who is responsible for the annual operating plan?
Finance, often FP&A, usually runs the process and owns the model. The CEO sets company goals and makes final trade-offs. Each department head owns their own targets, initiatives and budget.
What is the difference between an AOP and a forecast?
The AOP is the approved plan and stays fixed as the baseline for the year. A forecast is the latest estimate of where the year will land and is updated regularly, often monthly or quarterly. Comparing the two shows where the business is ahead or behind plan.
How detailed should an annual operating plan be?
Detailed enough to assign owners and budgets, but not a project plan. Financial targets and KPIs are usually set by quarter, and each initiative gets one line with owner, timing, cost and expected result. The detailed tasks belong in each team's own project plans.