Annual Planning for Multiple Teams: An 8-Week Roadmap
8 min read ยท 2026-10-14
Annual planning for a department or several teams means turning the company's priorities into one plan per team, then making those plans fit the people and budget you really have. The process has five steps. Leadership frames the priorities and limits. Each team drafts its plan. You compare what teams ask for with what is available. You settle the dependencies between teams. Then you sign off and set a review rhythm.
This guide is for heads of department, operations leads, chiefs of staff and anyone who has to pull several team plans into one. The hard part is not writing goals. It is the moment when the team plans together ask for more people, money and time than exist, and someone has to decide what gets cut. The roadmap below plans for that moment from day one.
The roadmap at a glance
Goal: A signed-off plan where every team's work links to a company priority, fits its capacity and budget, and has its cross-team dependencies agreed. Duration: 8 weeks
Frame Company Priorities and Planning Limits (Weeks 1-2)
Give every team the same starting point before anyone writes a plan.
- Rank the company priorities for the year in order, so teams know which one wins in a conflict.
- Set the planning envelope for each team: current headcount, approved hires and a budget ceiling.
- Write one planning template that every team must use, with the same fields and the same units.
- Publish the calendar: draft deadline, trade-off sessions and sign-off date.
- Name one person who owns the process and settles questions about the template.
Milestone: Every team lead has received a kickoff pack with ranked priorities, their envelope, the template and the deadlines.
Draft Team Plans (Weeks 3-4)
Each team turns the company priorities into its own plan and states what it needs.
- List the initiatives the team proposes, and link each one to a ranked company priority.
- Estimate the effort for each initiative in person weeks, not in vague sizes.
- Write down the run work the team must keep doing anyway, such as support, maintenance and reporting.
- List budget requests that go beyond the envelope, with what each one would unlock.
- Name every dependency on another team: what you need, from whom and by when.
Milestone: All team drafts are submitted in the shared template by the deadline, with effort, budget asks and dependencies filled in.
Trade Off Capacity and Budget (Weeks 5-6)
Add up demand, compare it with supply and decide what is funded.
- Roll up every team's effort and compare it with available capacity, team by team.
- Roll up budget requests and compare them with the total envelope.
- Sort all initiatives by the company priority they support, then draw the funded line.
- Apply the decision rules to everything near the line.
- Tell each team lead what moved above or below the line, and why.
Milestone: One consolidated view shows every initiative as funded or not funded, and each team's funded work fits its capacity.
Align Across Teams (Week 7)
Check that every promise one team relies on is also in the other team's plan.
- Build a dependency map that lists each request, the team asking and the team giving.
- For each dependency, confirm the giving team has funded capacity for it.
- Sequence shared work so the giving team delivers before the asking team needs it.
- Hold one joint session to settle the dependencies that are still open.
Milestone: Every dependency is either accepted with a date by the giving team, or the asking team's plan is changed to remove it.
Sign Off and Set the Operating Rhythm (Week 8)
Lock the plan and agree how it will be run and changed.
- Leadership approves the consolidated plan and the "not funded" list in one meeting.
- Publish each team plan and the dependency map in one shared place.
- Book a monthly portfolio review and a quarterly replanning session for the whole year.
- Write the change rule: who can add work, what must be removed to make room, and who approves.
Milestone: The plan is signed off, published, and all review dates and the change rule are shared with every team lead.
What Changes When You Plan for Several Teams
A single team can plan around its own goals. A department cannot. Once you have three or more teams, three problems appear that a personal or single team plan never meets.
That is why this process is built around a shared template, a capacity check and a dependency map. If you want to plan your own goals for the year rather than a department's, a 5-year career plan is a better fit.
- Competing claims on the same resources. Two teams want the same hire, the same budget or the same specialist.
- Hidden dependencies. Team A's plan quietly assumes Team B will build something that is not in Team B's plan.
- Different units. One team estimates in weeks, another in story points, a third in T-shirt sizes. You cannot add them up.
Who Does What
Keep the decision group small. Team leads propose, leadership decides. If everyone can veto, nothing gets cut.
- Leadership: ranks company priorities, sets envelopes, makes the final calls.
- Process owner: runs the calendar, owns the template, consolidates the drafts.
- Team leads: write team plans, estimate effort, declare dependencies.
- Finance: sets budget ceilings, checks requests against the envelope.
- People or HR: confirms headcount, open roles and realistic hiring dates.
How to Check Capacity Without a Complex Model
You do not need a planning tool to find out whether a team plan fits. You need one simple calculation per team, done the same way everywhere.
Here is an example. A team has 6 people. Take the working weeks each person really has in the year, after holidays and training. Say it is 44. That gives 264 person weeks. Then take off the run work the team listed in Phase 2. If support and maintenance use about a third of the time, around 175 person weeks are left for new initiatives. If the team's draft asks for 260, the plan does not fit, and no amount of motivation will close that gap.
Two rules make this work:
- Count new hires from their start date, not from January. A role approved for the year but filled in the summer gives half a year at most, and less while the person ramps up.
- Keep a buffer. Plan new work below the full remaining capacity, because urgent requests always arrive.
Decision Rules for When Plans Do Not Fit
In almost every department, the drafts ask for more than you have. Agree the rules before the trade-off sessions, so decisions feel fair and do not depend on who argues best.
The "not funded" list matters as much as the plan. It shows teams that their ideas were seen and judged, and it gives you a ready queue if capacity frees up during the year.
- Two initiatives compete for the same people: the one tied to the higher ranked company priority wins.
- An initiative cannot be fully staffed: fund it fully or move it to the "not funded" list, never fund it at half.
- Run work is squeezed by new projects: run work is protected unless leadership decides to stop it.
- A team asks for budget above its envelope: it must show what it drops if the request is refused.
- An initiative depends on a team with no room: it waits until the giving team has funded capacity.
Handling Dependencies Between Teams
Most cross-team delays come from dependencies that were never agreed, only assumed. Treat each dependency as a small contract.
A visual timeline makes this much easier to read than a spreadsheet. Our guide on how to make a roadmap shows how to lay out phases and milestones, and the roadmap vs project plan guide explains what belongs at plan level and what belongs in each team's project tracking.
- One line per dependency: asking team, giving team, what is needed, needed by.
- Accepted means funded: a dependency counts only if the giving team has put it inside its own funded work.
- Sequence on a timeline: place both sides on one shared view, so a delivery date after the need date stands out.
Timing Tip
Count back 8 weeks from the date your budget year opens, and add a little margin. That way the plan is signed off before money starts to be spent. If finance closes budgets earlier than that, move Phase 3 so the trade-off sessions end before their deadline.
Common mistakes to avoid
- Letting teams plan before priorities are ranked, so every team claims its work is the top priority.
- Accepting drafts in different formats, so the roll-up takes weeks and nobody trusts the totals.
- Funding initiatives at half capacity, so several things move slowly and none of them finish.
- Treating dependencies as notes, not commitments, so they surface as delays in the middle of the year.
- Skipping the change rule, so new requests get added all year without anything being removed.
Frequently asked questions
How long does annual planning take for a department?
This roadmap takes 8 weeks: two to frame priorities and limits, two for team drafts, two for capacity and budget trade-offs, one for cross-team alignment and one for sign-off. A department with only a few teams can sometimes go faster. A larger group can run the same steps with more time between them.
Should annual planning be top-down or bottom-up?
Both, in that order. Leadership sets the ranked priorities and the envelopes first. Teams then propose plans from the bottom up. The trade-off phase is where the two meet. Starting with drafts before priorities are set usually leads to plans that cannot be compared.
What should a team's annual plan include?
The initiatives it proposes, the company priority each one supports, the effort in person weeks, the run work it must keep doing, any budget asks above its envelope and its dependencies on other teams. Using the same template for every team is what makes the roll-up possible.
What do you do when team plans exceed capacity?
Apply decision rules agreed in advance. Rank initiatives by company priority, protect run work, fund initiatives fully or not at all, and move the rest to a written "not funded" list. Revisit that list at each quarterly replanning session.
What is the difference between an annual plan and a roadmap?
The annual plan decides what is funded and who does it. A roadmap shows how that work is sequenced over time, with phases, milestones and dependencies on a timeline. Many departments turn the signed-off plan into a visual roadmap so every team can follow progress during the year.