Template · Management
Team capacity planner by week
Compare each person's weekly available hours with planned hours by project, and flag over- and under-allocation.
Downloads are included in the $19.85 yearly membership. Sign in
XLSXCSVODSXMLNumbers| Team capacity by week | |||||||||||
| Example data — replace the blue input cells with your own. | |||||||||||
| TEAM UTILIZATION, 12 WEEKS | OVER-ALLOCATED PERSON-WEEKS | UNASSIGNED HOURS (AVAILABLE LESS ASSIGNED) | |||||||||
| 93% | 36 | 254 | |||||||||
| Settings | |||||||||||
| Under-allocated when utilization is below | 60% | Flags Under for a person-week below this share of available hours | |||||||||
| Assigned hours per person and week (from the Assignments tab) | |||||||||||
| Person | Role | Oct 2026 | Oct 2026 | Oct 2026 | Nov 2026 | Nov 2026 | Nov 2026 | Nov 2026 | Nov 2026 | Dec 2026 | Dec 2026 |
| Ana Example | Product owner | 26.0 | 26.0 | 26.0 | 24.0 | 26.0 | 26.0 | 26.0 | 26.0 | 24.0 | 24.0 |
| Ben Example | Engineer | 48.0 | 48.0 | 50.0 | 48.0 | 48.0 | 48.0 | 48.0 | 48.0 | 48.0 | 48.0 |
| Chidi Example | Engineer | 36.0 | 36.0 | 36.0 | 36.0 | 36.0 | 36.0 | 36.0 | 36.0 | 36.0 | 36.0 |
| Dana Example | Data analyst | 24.0 | 24.0 | 24.0 | 24.0 | 24.0 | 24.0 | 24.0 | 24.0 | 24.0 | 24.0 |
| Elif Example | QA engineer | 42.0 | 42.0 | 42.0 | 42.0 | 42.0 | 42.0 | 42.0 | 42.0 | 42.0 | 42.0 |
Showing the first 16 of 113 rows and 12 of 15 columns. Cells with formulas show the formula on hover.
| People and weekly capacity | |||||||||||
| Standard hours and leave for each person. Available hours are standard hours less leave, never below zero. | |||||||||||
| Plan start (week 1 begins on) | Oct 12, 2026 | Use a Monday; each week column is 7 days later | |||||||||
| Person | Leave and holiday hours (inputs) | ||||||||||
| Person | Role | Standard hours per week | Oct 12, 2026 | Oct 19, 2026 | Oct 26, 2026 | Nov 2, 2026 | Nov 9, 2026 | Nov 16, 2026 | Nov 23, 2026 | Nov 30, 2026 | Dec 7, 2026 |
| Ana Example | Product owner | 40.0 | 0.0 | 0.0 | 0.0 | 8.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| Ben Example | Engineer | 40.0 | 0.0 | 0.0 | 16.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| Chidi Example | Engineer | 40.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| Dana Example | Data analyst | 32.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 8.0 | 0.0 | 0.0 | 0.0 |
| Elif Example | QA engineer | 40.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| Farid Example | Designer | 32.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| Grace Example | Project manager | 40.0 | 0.0 | 4.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 |
| Hugo Example | Support lead | 37.5 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 0.0 | 8.0 | 0.0 | 0.0 |
Showing the first 16 of 32 rows and 12 of 28 columns. Cells with formulas show the formula on hover.
| Assignments by week | |||||||||||
| One row per project and person, with planned hours for each week. Spare rows stay blank. | |||||||||||
| Planned hours by week (blue cells are inputs; the role comes from the Capacity tab) | |||||||||||
| Project | Person | Role | Oct 12, 2026 | Oct 19, 2026 | Oct 26, 2026 | Nov 2, 2026 | Nov 9, 2026 | Nov 16, 2026 | Nov 23, 2026 | Nov 30, 2026 | Dec 7, 2026 |
| Example customer portal | Ana Example | Product owner | 8.0 | 8.0 | 8.0 | 6.0 | 8.0 | 8.0 | 8.0 | 8.0 | 6.0 |
| Example billing platform | Ana Example | Product owner | 14.0 | 14.0 | 14.0 | 14.0 | 14.0 | 14.0 | 14.0 | 14.0 | 14.0 |
| Example customer portal | Ben Example | Engineer | 20.0 | 20.0 | 20.0 | 20.0 | 20.0 | 20.0 | 20.0 | 20.0 | 20.0 |
| Example billing platform | Ben Example | Engineer | 24.0 | 24.0 | 26.0 | 24.0 | 24.0 | 24.0 | 24.0 | 24.0 | 24.0 |
| Example warehouse automation | Chidi Example | Engineer | 28.0 | 28.0 | 28.0 | 28.0 | 28.0 | 28.0 | 28.0 | 28.0 | 28.0 |
| Run the service | Chidi Example | Engineer | 4.0 | 4.0 | 4.0 | 4.0 | 4.0 | 4.0 | 4.0 | 4.0 | 4.0 |
| Example customer portal | Dana Example | Data analyst | 12.0 | 12.0 | 12.0 | 12.0 | 12.0 | 12.0 | 12.0 | 12.0 | 12.0 |
| Run the service | Dana Example | Data analyst | 6.0 | 6.0 | 6.0 | 6.0 | 6.0 | 6.0 | 6.0 | 6.0 | 6.0 |
| Example billing platform | Elif Example | QA engineer | 30.0 | 30.0 | 30.0 | 30.0 | 30.0 | 30.0 | 30.0 | 30.0 | 30.0 |
| Example customer portal | Elif Example | QA engineer | 12.0 | 12.0 | 12.0 | 12.0 | 12.0 | 12.0 | 12.0 | 12.0 | 12.0 |
| Example warehouse automation | Farid Example | Designer | 16.0 | 16.0 | 16.0 | 16.0 | 16.0 | 16.0 | 16.0 | 16.0 | 16.0 |
Showing the first 16 of 156 rows and 12 of 16 columns. Cells with formulas show the formula on hover.
| Team capacity planner by week |
| Notes: what this workbook does, how to use it and the method behind it. |
| What it does |
| Compares each person's weekly available hours with the hours assigned to them on each project, for twelve weeks. It flags people who are over-allocated or under-allocated and totals the hours by project. |
| How to use it |
| 1. On the Capacity tab, enter the plan start date (a Monday), each person's role and standard weekly hours, and any leave or holiday hours by week. |
| 2. On the Assignments tab, enter the project, the person and the planned hours for each week. The role fills in from the Capacity tab. |
| 3. On the Plan tab, read the team utilization, the number of over-allocated person-weeks and the unassigned hours at the top. |
| 4. Check each person's utilization and flag week by week; Over means above 100% and Under means below the threshold on the Plan tab. |
| 5. Use the hours-by-project block to see how the team's hours split across projects. |
| Formulas and method |
| Available hours = standard hours - leave hours, never below 0. |
| Assigned hours = SUMIF of the Assignments hours for that person and week. |
Showing the first 16 of 32 rows and 1 of 1 columns. Cells with formulas show the formula on hover.
What does this template do?
A team capacity planner shows whether the people on a team have the hours for the work planned for them. It is for team leads, project managers and resource planners who plan in weeks rather than months.
The Capacity tab holds standard weekly hours and leave for up to twenty-five people. It calculates the available hours for twelve weeks by subtracting leave. The Assignments tab holds planned hours by project, person and week. The Plan tab sums each person's hours for each week with SUMIF, divides them by the available hours to give utilization, and flags each person-week as Over above 100% or Under below a threshold you set.
The Plan tab also totals each week for the team and the hours by project. It reports team utilization, the number of over-allocated person-weeks and the unassigned hours. The example is a fictional team of eight people with twenty-two assignment rows over twelve weeks.
What’s inside
- Available hours by week: standard hours less leave and holidays
- Utilization for each person and week, with a flag of Over, Under or OK
- Team totals and team utilization for each of the twelve weeks
- Hours by project across the same twelve weeks
- Role filled in from the people list, with a check for names that do not match
Which tabs does the workbook have?
| Tab | What it holds |
|---|---|
| Plan | Team tiles, assigned hours, utilization and flags per person and week, team totals and hours by project. |
| Capacity | Plan start date, people and roles, standard hours, weekly leave and available hours. |
| Assignments | Planned hours by project, person and week; the role fills in from the Capacity tab. |
| Notes | Purpose, steps, formulas used, assumptions and limits. |
What formulas does this template use?
This template holds 1,982 formulas in 2,494 cells across 4 tabs, so 79% of its cells calculate. They use 9 distinct functions; the longest formula is 223 characters and 1,236 of them read from another tab.
| Function | Uses | What it does |
|---|---|---|
IF | 3,344 | one result when a test is true, another when false |
SUMIF | 372 | adds values meeting one condition |
MAX | 300 | largest value |
SUM | 289 | adds numbers |
IFERROR | 150 | swaps an error for a fallback value |
INDEX | 150 | value at a position in a range |
MATCH | 150 | position of a value in a range |
COUNTIF | 53 | counts cells meeting one condition |
ABS | 1 | absolute value |
Counted from the workbook itself. Only functions that Excel, LibreOffice Calc, Google Sheets and Apple Numbers evaluate the same way are used, so the formulas survive every download format.
How do you use it?
- On the Capacity tab, set the plan start date, which should be a Monday.
- Enter each person's role, standard weekly hours and leave for each week.
- On the Assignments tab, enter the project, the person and the planned hours for each week.
- On the Plan tab, read the team tiles, then the utilization and flag blocks for each person.
What is it good for?
- Checking whether a team can take on a new project next quarter
- Spotting weeks when one engineer is over-committed
- Planning around holidays and planned leave
- Showing how the team's hours split between projects and run work
Questions about this sheet
How is utilization calculated?
Assigned hours divided by available hours. It is left blank when a person has no available hours that week.
What happens when leave equals the standard hours?
Available hours fall to zero. Any hours assigned to that person in that week are flagged Over, because there are no available hours to fill.
Are the hours timesheet hours?
No. They are planned hours. The sheet does not model overtime, contractors or partial-week starts.
Why does the name check matter?
A name on the Assignments tab that does not match the Capacity tab exactly is left out of that person's totals, so the check reports it.