What Is the Difference Between Top-Down and Bottom-Up Capacity Planning?

Top-down and bottom-up capacity planning are two ways to estimate and manage resource demand in Project Insight.

Top-down planning starts with a high-level estimate of how much time a person, role, or team will spend on a project. Bottom-up planning calculates capacity from the detailed tasks, durations, work hours, and assignments in the project plan.

Use this article to decide which planning method fits your project, especially when you are forecasting future work, planning before all tasks are known, or comparing high-level demand against detailed task assignments.

When to Use It

Use this guidance when:

• You are setting up resource and capacity planning for the first time
• A project does not have a full work breakdown structure yet
• You need to forecast resource demand before tasks are fully planned
• You want to reserve time for a person, role, or department
• You need detailed task-level capacity calculations
• You are planning day-to-day operations work alongside project work
• You need to compare planned resource demand against actual task assignments

What Is Top-Down Capacity Planning?

Top-down capacity planning starts with a high-level estimate of how much resource time a project will need.

Instead of building every task first, you estimate the amount of time a person, role, team, or department will spend on the project during a time period.

For example:

• A business analyst will spend 10 hours per week on a planning project.
• A developer will spend 50% of their time on an upcoming initiative.
• A support team member will spend 20 hours per week on day-to-day operations work.
• A resource type, such as Project Manager or Designer, is needed for a future project before a named person is assigned.

Top-down planning is useful when you know the expected resource demand but do not yet know every task required to complete the work.

What Is Bottom-Up Capacity Planning?

Bottom-up capacity planning calculates capacity from the details in the project task list.

In Project Insight, this can include:

• Task duration
• Task start and end dates
• Work hours
• Assigned resources
• Resource type
• Work schedules
• PTO
• Task dependencies
• Project schedules

This method works best when the project has a defined work breakdown structure and the team is ready to plan or manage work at the task level.

For example, if a task is scheduled for 5 days and has 10 hours of work assigned to a specific resource, Project Insight can use that task-level data to help calculate the resource’s workload during that time period.

Top-Down vs. Bottom-Up Capacity Planning

Top-down planning answers the question:

How much capacity do we expect this project, role, or team to need?

Bottom-up planning answers the question:

How much capacity is required based on the actual task plan?

Use top-down planning when the work is still early, high-level, or recurring.

Use bottom-up planning when the tasks, dates, work hours, and assignments are defined.

When Should You Use Top-Down Planning?

Use top-down planning when you need to forecast capacity before the full project plan exists.

Top-down planning is helpful when:

• A project is in intake or planning
• You are deciding whether the organization can take on new work
• Named resources have not been assigned yet
• The work is being planned by role, department, or resource type
• You need to reserve capacity for future demand
• The work is ongoing and does not need detailed task tracking
• You are accounting for day-to-day operations work

Top-down planning helps PMO leaders and executives see demand earlier, before the project is fully scheduled.

When Should You Use Bottom-Up Planning?

Use bottom-up planning when the project has enough detail to calculate resource demand from tasks.

Bottom-up planning is helpful when:

• Tasks are defined
• Dates and dependencies are known
• Work hours have been estimated
• Resources are assigned to tasks
• Project managers need to manage workload at the task level
• Teams need to adjust specific assignments or schedules
• Resource allocation reports should reflect detailed project execution

Bottom-up planning gives project managers a more precise view of how task assignments affect capacity.

Can You Use Both Methods?

Yes. Many teams use both methods at different stages of planning.

A common approach is:

1. Use top-down planning during intake or early forecasting.
2. Estimate resource demand by role, department, or placeholder resource.
3. Review whether the organization has enough capacity to approve or schedule the work.
4. Build the detailed project plan when the work is approved.
5. Use bottom-up planning from tasks, dates, work hours, and assignments.
6. Compare the detailed plan against the original high-level estimate.

This lets teams start with a forecast, then replace or refine that forecast as the project becomes more detailed.

How Does This Help With Future Project Planning?

Top-down planning helps teams understand future demand before they commit to a project.

For example, a planning-stage project may not have every task built yet, but leadership still needs to know whether the team can support it. Top-down planning can reserve expected capacity by role, department, or placeholder resource.

Once the project is approved and the task plan is built, bottom-up planning can provide a more detailed view of the actual workload.

This helps teams avoid approving new projects without understanding the resource impact.

How Does This Help With Day-to-Day Operations Work?

Day-to-day operations work often works better with top-down planning.

For example, if someone spends 20 hours per week on help desk support, maintenance, or recurring internal operations, that work may not need a detailed task list. Instead, the expected time can be represented at a higher level so it appears in capacity planning.

This keeps operational work visible in resource reports instead of simply reducing a person’s capacity without showing what they are doing.

How Does This Affect Resource Allocation Reports?

Resource allocation reports are more useful when the planning method matches the maturity of the work.

Use top-down data when the project is still being forecasted or when work does not need detailed task planning.

Use bottom-up task data when the project plan is detailed enough to show actual assignments, work hours, and schedule impact.

Project Insight can support both high-level forecasts and detailed task planning, which helps teams understand current assignments and future demand.

Best Practices

• Use top-down planning early, before the full task plan exists.
• Use bottom-up planning once tasks, dates, work hours, and assignments are defined.
• Use placeholder resources when planning by role or department before named people are assigned.
• Include day-to-day operations work so resource availability is realistic.
• Review top-down estimates after the detailed project plan is created.
• Avoid treating early top-down estimates as final commitments.
• Keep work estimates current so capacity reports reflect real workload.
• Use planning-stage projects to understand future demand before approving new work.

Common Mistakes to Avoid

• Waiting for a full task plan before forecasting capacity.
• Using only bottom-up planning when the project is still in intake.
• Using only top-down planning after detailed task assignments exist.
• Ignoring day-to-day operations work when reviewing availability.
• Treating 100% capacity as if every hour is available for project work.
• Forgetting to replace placeholder or top-down estimates with detailed task planning when the project becomes active.
• Approving future work without checking the resource impact.

Need More Help?

If you are not sure whether to use top-down or bottom-up capacity planning, contact your Project Insight administrator or Customer Success representative. You can also get more help at projectinsight.com/support.