How to Create a Team Capacity Plan in Linear
Most product teams plan based on what they want to ship, not what they can ship. The result is chronic overcommitment: every sprint ends with carryover, deadlines slip, and the PM loses credibility with stakeholders. Capacity planning fixes this by starting from how much work your team can actually absorb and working backward to what fits.
Linear's cycles, estimate fields, and workload views provide the raw data for capacity planning, but the tool does not prescribe a methodology. This guide shows you how to calculate team capacity, configure Linear to track it, and build a planning cadence that keeps your roadmap honest about what is achievable in any given period.
Step-by-step guide
Calculate your team's available capacity per cycle
Start with the number of engineers on your team and multiply by the cycle length in days. Then subtract known overhead: meetings (typically 15-20%), on-call rotations, PTO, and company-wide events. A five-person team on a two-week cycle has 50 person-days of raw capacity, but after overhead you might have 35-38 effective person-days.
- List every team member and their availability for the upcoming cycle (full-time, half-time, PTO days)
- Subtract recurring meeting hours converted to days (e.g., 8 hours/week of meetings = 1 day/week)
- Reserve 10-15% for unplanned work (bugs, support escalations, production issues)
Configure Linear's estimate field and scale
Go to your team's settings in Linear and enable estimates. Choose between linear (1-5 scale) and exponential (Fibonacci) estimation. For capacity planning, linear scales are easier to sum because a 3-point task is literally three times a 1-point task. Set up your scale so that one point equals roughly one person-day of work.
- Navigate to Team Settings > Estimates and enable the feature
- Choose 'Linear' scale for straightforward capacity math
- Document what each point value means in your team description (1 = half day, 2 = one day, etc.)
Set up cycles with consistent duration
Configure cycles in Linear with a fixed duration — one or two weeks is standard. Capacity planning requires consistency; if cycles vary in length, you cannot compare capacity across periods. Set the cycle to auto-advance so completed cycles close on schedule and incomplete issues automatically move forward.
- Go to Team Settings > Cycles and enable them
- Set a fixed duration (two weeks is the most common for capacity planning)
- Enable auto-archiving of completed cycles and auto-advance for incomplete issues
Use the workload view to visualize allocation
Switch to Linear's workload view during planning. This view shows each team member's assigned issues with their estimates, making overallocation visible at a glance. If one engineer has 12 points of work and your per-person capacity is 8, the imbalance is obvious. Rebalance before committing to the cycle.
- Navigate to the Cycles section and select the current or upcoming cycle
- Switch to the Workload view to see per-person allocation
- Look for team members whose total estimates exceed their available capacity
Fill the cycle to 80% of calculated capacity
Move issues from the backlog into the cycle until the total estimate reaches 80% of your calculated capacity. The 20% buffer absorbs estimation errors and unplanned work without requiring a cycle extension. If your team has 38 effective person-days and one point equals one person-day, plan for 30-31 points of work.
- Sort the backlog by priority and move top-priority issues into the cycle
- Track the running total of estimates against your 80% target
- Stop adding work when you hit the threshold — this is the discipline that makes capacity planning work
Track planned vs delivered each cycle to refine your model
At the end of each cycle, compare planned points to completed points. If you consistently complete 85% of planned work, your capacity model is slightly optimistic — reduce next cycle's target by 5%. If you complete 100% every cycle, you are underplanning and can increase. This feedback loop makes your capacity estimates more accurate over time.
- Record planned and completed estimates in a simple spreadsheet or Linear project description
- Calculate your planning accuracy ratio (completed / planned) each cycle
- Adjust the capacity target quarterly based on the trailing accuracy ratio
Common mistakes
Planning to 100% capacity with no buffer
A team planned to 100% capacity has zero room for the unexpected — and the unexpected always happens. Production incidents, urgent customer requests, and estimation misses all eat into capacity. Planning to 80% is not leaving slack, it is acknowledging reality.
Ignoring meeting overhead in capacity calculations
Engineers in growth-stage companies typically spend 15-25% of their time in meetings. A five-person team with 20% meeting load has four effective engineers, not five. If your capacity model does not subtract meetings, you are overcommitting by 20% every cycle.
Using capacity planning as a productivity pressure tool
The moment capacity numbers become targets that management pushes teams to 'improve,' engineers inflate estimates to avoid pressure. Capacity planning is about planning accuracy, not productivity optimization. Keep the data descriptive, not evaluative.
Tips
Use Linear's project progress indicators to show stakeholders how much capacity is allocated to their project vs. others — it makes prioritization tradeoffs visible.
Create a 'Capacity Reserve' issue in every cycle with points equal to your buffer — it makes the buffer visible in the workload view instead of invisible.
Run a quarterly capacity calibration where you compare estimates to actual time spent (using cycle time data) to improve estimation accuracy.
Factor in seasonal variations — capacity drops 20-30% during December holidays and summer vacation periods in many companies.
How Vantage helps
When Vantage generates tickets from your PRD, it consults your team's Linear cycle history to understand actual delivery capacity. Generated wave plans respect your team's throughput data so the suggested timeline is realistic rather than aspirational, helping PMs set stakeholder expectations that they can actually meet.