How to Analyze Team Workload: A Capacity Worksheet and Worked Example

To analyze team workload, estimate the work due during a defined period, calculate the time available to complete it, and check whether the people with that time have the required skills. Compare demand and capacity by person and task before looking at the team total. Then change the assignment, scope, or deadline where the plan does not fit.

The worksheet below uses hours for a single week. It is a planning aid, not a productivity score or a measure of employee wellbeing.

Separate demand, capacity, and observed activity

Demand is the estimated effort needed for the work included in your plan. Capacity is the time available for that work after other commitments. Observed activity records something that already happened, such as application use or time entered against a task.

These inputs are related, but they are not interchangeable. Thirty hours in business applications does not establish that someone has ten hours available next week. Nor does a task estimate establish how long the task actually took.

Start by agreeing on the period and the work included. For example: “Can our four-person operations team complete next week's assigned project tasks while maintaining its existing service commitments?”

A useful starting point is to inventory the less visible parts of the week. Atlassian's capacity-planning exercise asks contributors to account for regular and informal activities, then discuss availability together. Capacity-planning playbook

Calculate available time without counting work twice

Use this definition consistently:

Net task capacity = scheduled working hours − planned absence − fixed commitments − contingency allowance.

Scheduled working hours should already exclude nonworking breaks. Fixed commitments cover time outside the task list: meetings, routine service coverage, administration, or another project. Contingency is an explicit allowance for uncertain work, based on what the team expects rather than an assumed universal percentage.

Choose one place for each item. If routine requests are included in fixed commitments, do not add the same requests to task demand. If a task estimate already includes its review, do not subtract that review again as a fixed commitment.

Treat the allowance the same way. As unexpected work becomes known, allocate it against the allowance or replace the allowance with identified work. Do not keep the full allowance and add the same work again.

Ask each contributor to review their row. A shared calendar can identify absence and meetings; it cannot reliably supply every commitment or estimate.

Estimate the work due in the period

For each task, record the output, owner, deadline, estimated remaining effort, required skill, and dependency. Include preparation, review, and correction needed to finish. Use remaining effort for work already underway, not its original total estimate.

A two-hour task waiting three days for information needs two hours of effort, but its dependency can still threaten the deadline. Keep effort and elapsed waiting time in separate fields.

Use the people doing the work to challenge estimates. Where uncertainty is substantial, record a range and calculate both ends. A plan that fits only the most optimistic estimate needs a different discussion from one that fits throughout the range.

Equal task counts are not a useful shortcut here: five short checks and five complex investigations can represent very different demand.

Worked example: the total fits, but the assignments do not

The following team and figures are fictional. All assigned tasks are due by Friday. Fixed commitments exclude the listed task demand, and task estimates include the necessary review. This team has chosen four contingency hours per person for this example; that is not a recommended default.

All figures are hours for the same week. Balance means net capacity minus demand: a negative value is a planning shortfall.

For Ana, capacity is 40 − 0 − 10 − 4 = 26 hours. Her 32 hours of assigned work exceed that by six hours.

The team has 90 hours of capacity against 86 hours of demand. That apparent four-hour margin does not resolve Ana's six-hour shortfall or Cara's four-hour shortfall.

Now examine the tasks and skills:

• Ana's demand consists of 28 hours of specialist validation and four hours of general preparation. Only Ana can perform the validation this week.
• Ben can take the four preparation hours, bringing his demand from 16 to 20 hours. Ana still has 28 hours against 26 available.
• Cara can transfer four hours of document preparation to Dev. Her demand falls to 20; Dev's rises to 18. Dev cannot take Ana's specialist validation.

Moving those tasks leaves demand at 86 hours. The assignments have improved, but Ana still has a two-hour shortfall despite Dev having six unassigned hours.

Suppose the team agrees to move a two-hour validation item to next week and records the revised deadline with the person expecting it. The new demands are 26, 20, 20, and 18 hours, totaling 84. The plan now fits the stated capacity, with six hours unassigned at Dev.

The deferred item remains in next week's plan. Before accepting these transfers, check access, availability before the deadline, and any added handoff effort. If a transfer creates extra review or briefing time, update both people's estimates before declaring that it fits.

Turn the worksheet into a decision

A negative balance identifies a conflict in the plan. Discuss whether to change priority, divide a task, transfer suitable work, adjust scope, or renegotiate timing. Do not silently solve the calculation by assuming longer working hours.

A positive balance is not proof of spare capacity. It may reflect missing work, a skill mismatch, or availability that occurs after a deadline. Check the daily sequence when timing matters; weekly totals cannot establish that Tuesday's work fits before Tuesday afternoon.

Do not turn either result into a judgment about effort, performance, or burnout. This worksheet compares planning inputs. Those broader questions require different evidence and a conversation with the people involved.

Copy these columns into a spreadsheet

Use two tabs so task details remain traceable to the capacity totals.

People: period start, period end, person, scheduled hours, absence hours, fixed-commitment hours, contingency hours, net capacity, assigned demand, balance, notes.

Tasks: task ID, output, owner, due date, remaining-effort estimate, estimate range, required skill, dependency, status, decision, revised deadline.

Sum task estimates by owner to populate assigned demand. Check that every in-scope task has an owner and that shared tasks allocate each contributor's effort separately. Do not assign the entire shared-task estimate to every participant.

Revisit the assumptions after the week

Record completed work, remaining work, changed commitments, and unexpected requests. Discuss where estimates differed from experience before changing the next plan. Within its own framework, the Scrum Guide likewise connects forecasting confidence with knowledge of past performance, upcoming capacity, and what completion requires. Scrum Guide: planning

Keep the original plan alongside the revision. That lets the team distinguish an underestimated task from a new request or changed deadline. For the next period, update the assumptions that proved wrong and repeat the calculation with the people responsible for the work.