Annual Operating Plan (AOP)
What is Annual Operating Plan (AOP)?
An annual operating plan (AOP) is a company's plan for the coming fiscal year, setting targets for revenue, costs, headcount and key initiatives, and the budgets each team will work within.
Updated November 2026 · 5 min read
The annual operating plan, often called the AOP, is the plan a company commits to for the next fiscal year. It translates strategy into specific targets and budgets: how much revenue the company expects, how much each department can spend, how many people it will hire and which initiatives will be funded. Once approved by leadership and the board, it becomes the baseline against which performance is measured throughout the year.
For technology organizations, the AOP sets the IT budget, the headcount plan and the list of funded projects for the year. The process of building it involves negotiation between IT, finance and the business over priorities and funding. For IT financial management, preparing a credible AOP submission, and then managing against it, is one of the most important responsibilities of IT finance.
Definition of Annual Operating Plan
An annual operating plan is a detailed plan for a single fiscal year that sets financial and operational targets for the whole organization and each of its units. It typically includes revenue and margin targets, an operating budget, a capital budget, a headcount plan and a list of major initiatives with their funding.
The AOP connects the company's longer-term strategic plan, which usually covers three to five years, with the work of the coming year. It is usually built during the final months of the previous fiscal year and approved before the new year begins.
What the AOP Contains
The financial section sets targets and budgets by department, cost center and major cost category. For IT, this covers labor, contractors, software, cloud, hardware, telecom and outsourced services, split between operating and capital spending.
The operational section sets goals and measures, such as service levels, project milestones and key results. It also lists the initiatives the company has chosen to fund, with owners and expected outcomes.
The headcount plan sets how many people each team can hire and when, which often drives most of the cost in the plan.
AOP vs Budget and Forecast
The terms are often used interchangeably, but the AOP is broader than the budget. The budget is the financial part of the plan, while the AOP also includes targets, initiatives and headcount.
The AOP is fixed once approved, while forecasts are updated during the year to show the expected outcome. Comparing the rolling forecast with the AOP shows whether the organization is on track.
Some companies reforecast formally at mid-year, but the original AOP usually remains the reference for measuring performance.
Importance of the AOP in IT Financial Management
The AOP determines how much IT can spend, on what, and with how many people for the year. It also sets the expectations against which IT will be judged.
How well IT prepares for the AOP process affects the funding it receives. Technology requests are often large and hard for other executives to evaluate, so the quality of the supporting information matters as much as the amounts requested.
A credible submission, grounded in clear cost data and linked to business outcomes, is more likely to be funded than one built on last year's figures plus an increase.
Making the Case for Funding
During the AOP process, IT competes with other functions for limited funds. A submission that shows the cost of running existing services, the drivers of growth and the value of proposed initiatives is easier to defend than a single total.
Separating spending into run, grow and transform categories helps leaders see how much is needed to keep the lights on and how much supports new priorities.
Linking costs to services and business units also helps business leaders understand what they are paying for and what would change if funding were cut.
Managing Against the Plan
Once approved, the AOP becomes the baseline for monthly reporting. IT finance compares actual spending and forecasts with the plan, explains variances and flags risks.
Because technology conditions change during the year, the AOP rarely matches reality exactly. Clear processes for reallocating funds between projects and categories keep the plan useful.
Tracking performance against the AOP also builds credibility for the next year's submission, since leaders can see how accurately IT planned and how well it delivered.
How to Build an IT AOP Submission
Building an IT AOP submission involves establishing the cost baseline, adding known changes and growth, and proposing new initiatives.
The work usually begins two to four months before the fiscal year starts. Finance typically issues guidance on growth assumptions, cost targets and timelines, and IT builds its submission within that guidance.
Establishing the Baseline
Start with the current run rate of spending, adjusted for known changes such as contract renewals, price increases, completed projects and depreciation of recent capital purchases.
Use driver-based planning to project costs that change with business volumes, such as headcount-driven licenses and usage-driven cloud costs.
Identify savings already planned, such as contracts ending or applications being retired, so that the baseline reflects them.
Proposing Initiatives and Finalizing
New initiatives should be presented with their costs, benefits, timing and risks, and prioritized so leadership can decide what to fund if the total exceeds what is available.
The submission typically goes through several rounds of review and adjustment as finance balances requests across the company. Keeping the underlying model flexible makes it easier to respond to requests for scenarios or cuts.
Once approved, the plan is loaded into financial systems by cost center and month, ready for tracking.
Examples of the AOP in IT Financial Management
The examples below show the AOP process for IT.
Both use illustrative figures.
In each, clear data about costs and drivers improved the outcome of the planning process and made trade-offs easier to discuss.
A Driver-Based Submission
An IT organization builds its AOP submission from a current run rate of $48 million. It adds $2.4 million for 5% vendor price increases, $1.6 million for licenses tied to planned company hiring and $1 million for cloud growth, and subtracts $1.5 million for retired applications, giving a baseline of $51.5 million.
It then proposes $6 million of new initiatives, ranked by value. Leadership funds $3.5 million of them, for an approved budget of $55 million. Because the baseline was built from visible drivers and known changes, the discussion focused on which initiatives to fund rather than on whether the baseline was reasonable.
Responding to a Cut
Finance asks all departments to reduce their submissions by 5%. Because IT's plan is built from services and drivers, it can show what a 5% cut would mean: delaying a laptop refresh, reducing support hours and postponing one initiative.
Leadership agrees to the refresh delay and the postponement but protects support hours, a decision made with a clear view of the trade-offs.
Conclusion
The annual operating plan is a company's plan for the coming fiscal year, setting targets, budgets, headcount and funded initiatives. It is approved before the year begins and serves as the baseline for measuring performance.
In IT financial management, the AOP sets IT's budget and expectations for the year. Building a submission from a clear baseline and drivers, presenting initiatives with costs and benefits, and managing against the plan with regular forecasts help IT secure the funding it needs and use it well.
Related terms
Operating Budget
An operating budget is a plan for the revenue and day-to-day expenses an organization expects over a period, usually a year. It covers recurring costs such as salaries, rent, subscriptions and services.
Capital Budget
A capital budget is an organization's plan for investments in long-term assets over a period, such as hardware, facilities and capitalized software. It sets how much will be spent and on which projects.
Rolling Forecast
A rolling forecast is a financial forecast that is updated at regular intervals, usually monthly or quarterly, and always extends a fixed period ahead, such as the next 12 or 18 months.
Run, Grow, Transform
Run, Grow, Transform is a model that classifies technology spending by purpose: running, growing or transforming the business. It shows how much of a budget maintains versus changes the business.