Back to all articlesManager routines

Run a Weekly Capacity Review Before Committing to More Work

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A manager sees four people on the team and a few blank calendar slots, then agrees to another deadline. By midweek, recurring support work, unfinished deliverables, and an absent reviewer have consumed the apparent space. The new commitment was made against headcount, not usable capacity.

Before accepting more work, run a weekly review that subtracts known absences, fixed obligations, existing commitments, and an explicit uncertainty allowance from scheduled working time. Then check whether the remaining time belongs to the people who can do the work, before the requested deadline. The result is a decision aid, not a precise measurement of human output.

The worksheet below makes those deductions visible and records what the manager actually agrees to: accept, defer, reduce scope, or renegotiate. It also leaves room to say that the estimate is too uncertain to support a promise.

1. Establish what the week already owes

Start with the coming week, not the team's theoretical maximum. Use scheduled working hours as the opening balance, adjusted for individual working arrangements. Subtract known leave and other absences before discussing projects.

Next, separate the work the team already owes into two categories:

  • Fixed obligations: recurring meetings, routine administration, scheduled support coverage, and other duties that consume time regardless of which new request arrives.
  • Committed work: the remaining effort needed this week for deliverables already promised, including preparation, review, revisions, and handoff.

Keep these categories mutually exclusive. If scheduled support coverage is counted as a fixed obligation, do not also enter the same hours as a committed support task. If a recurring meeting is cancelled, remove it rather than retaining it as an invisible cushion.

Estimate remaining work, not the original project size. A nearly finished deliverable can still need substantial review. Conversely, work that is waiting on another team may require little effort this week but still carry a deadline risk. Record that dependency separately rather than treating all waiting time as working time.

The opening question is simple: What must happen this week even if we accept nothing new? Ask each person to correct the answer before using the worksheet to promise anything.

2. Use a small set of honest capacity fields

A weekly team capacity planning worksheet needs enough detail to expose a bad commitment, but not so much that maintaining it becomes another project. Use these fields for each person:

  1. Scheduled working time.
  2. Known absences.
  3. Available time after absences.
  4. Fixed obligations.
  5. Remaining effort on existing commitments.
  6. Uncertainty allowance.
  7. Uncommitted planning room.
  8. Constraints, assumptions, and acceptance decisions.

The calculation is:

Available time = scheduled time − known absences
Uncommitted planning room = available time − fixed obligations
                            − committed work − uncertainty allowance

The uncertainty allowance protects space for plausible interruptions, rework, or estimation error. It is not a universal percentage or a target everyone must meet. Choose it using the conditions of the week: unfamiliar work, unresolved dependencies, and unpredictable requests deserve explicit discussion.

Do not charge the same uncertainty twice. If an estimate already includes a specific revision round, the allowance should cover other uncertainty, not that same round again. Where a major unknown could change the scope entirely, add a decision gate rather than pretending a small cushion resolves it.

Use rounded estimates at a level the team can explain. Arithmetic may produce an exact total, but that does not make the inputs exact. A negative balance means the existing plan needs repair before new work is considered.

3. Filled worksheet: a fictional team's coming week

Fictional worked example: All people, hours, requests, and decisions below are hypothetical. This is a planning illustration, not a staffing benchmark or an Alactic customer result.

A four-person operations team reviews its coming week. Ana handles process design, Ben provides technical review, Cara prepares customer-facing materials, and Dev handles operational implementation. These descriptions identify relevant constraints; they do not imply that their hours are interchangeable.

HYPOTHETICAL WEEKLY CAPACITY WORKSHEET
Unit: hours of effort during the coming week

Person                 Ana   Ben   Cara   Dev   Team
Scheduled time          40    40     40    40    160
Known absences           0     8      4     0     12
Available time          40    32     36    40    148
Fixed obligations       10     8     10    12     40
Existing commitments    20    18     18    20     76
Uncertainty allowance    4     4      4     4     16
Planning room            6     2      4     4     16

FIXED OBLIGATIONS INCLUDED ABOVE
Ana: meetings 4; routine administration 6
Ben: meetings 3; scheduled support coverage 5
Cara: meetings 4; routine content maintenance 6
Dev: meetings 4; scheduled operational coverage 8

EXISTING COMMITMENTS: REMAINING EFFORT THIS WEEK
Ana: process revision 12; handover guide 8
Ben: integration review 10; outstanding fixes 8
Cara: customer guide 12; launch materials 6
Dev: workflow rollout 14; reporting cleanup 6

CONSTRAINTS AND ASSUMPTIONS
Ana: new design work can begin after Tuesday's review.
Ben: only 2 uncommitted hours; unavailable Friday.
Cara: new materials require a settled brief before drafting.
Dev: rollout estimate assumes access is ready Monday.
All: estimates include the currently expected review work.

The team has 16 hours of planning room, not the 160 hours suggested by headcount and scheduled time. Even those 16 hours are conditional: Ben's two hours cannot cover a larger technical review, and Dev's balance depends on access arriving as expected.

The equal uncertainty allowances are a simplifying choice in this example, not a recommended default. In a real review, one person's allowance might need to be larger because their work is less predictable. Explain that difference rather than forcing identical deductions for neatness.

4. Turn the balance into explicit acceptance decisions

Do not approve requests in the order they happen to be mentioned. First identify what the team must protect, then compare incoming requests by consequence, timing, scope flexibility, and required skills.

In the hypothetical example, the manager records four incoming requests and the decision for each:

HYPOTHETICAL REQUEST AND DECISION LOG

A. Process workshop package
Original request: 10 hours, needed this week.
Decision: REDUCE SCOPE, subject to requester's agreement.
Offer: a focused outline and review, not the full package.
Accepted effort: Ana 4 + Ben 2 = 6 hours.
Condition: Ben's review happens Thursday, not Friday.

B. Customer briefing update
Request: 4 hours, needed this week.
Decision: ACCEPT.
Accepted effort: Cara 4 hours.
Condition: settled brief available Monday.

C. Reporting expansion
Request: Dev 12 hours, needed this week.
Decision: DEFER.
Accepted effort this week: 0 hours.
Next step: reconsider in next week's review; no date promised.

D. Workflow launch
Original request: Dev 10 hours, launch this week.
Decision: RENEGOTIATE deadline and stage the work.
Offer: Dev 2 hours of preparation this week; no launch promise.
Remaining work: reassess before agreeing a launch date.

NEWLY ACCEPTED EFFORT
Ana 4 | Ben 2 | Cara 4 | Dev 2 | Team 12

PLANNING ROOM AFTER THESE DECISIONS
Ana 2 | Ben 0 | Cara 0 | Dev 2 | Team 4

Uncertainty allowances remain reserved: 16 hours total.

The team has not accepted the original workshop package or the original launch date. Until the requesters agree to the revised terms, those offers remain proposals. Record that distinction so an internal planning decision does not become a misunderstood external promise.

The remaining four hours are also not a general-purpose slot. They sit with Ana and Dev. A further request requiring Ben or Cara would still need a trade-off, even if the team total looks positive.

5. Check feasibility beyond the total

An effort balance is necessary, but it cannot establish whether a deadline is feasible. Before accepting work, test three constraints.

Does the right person have room?

A specialist review can be the limiting factor. In the example, accepting the reduced workshop uses all of Ben's uncommitted time. Another task needing his review cannot be justified by Ana's remaining hours unless a credible change in how the work is done removes that dependency.

Is the time available before it is needed?

A deliverable due early in the week cannot use capacity that becomes available later. Check the order of drafting, review, revision, and handoff. A calendar helps validate those sequences after the effort estimate; it should not substitute for the estimate.

Are the inputs ready?

Cara's accepted update depends on a settled brief. If that brief arrives late, the manager should revisit the deadline rather than quietly compressing review. Dev's access dependency needs a similar trigger. Record who will confirm readiness and when the decision must be revisited.

These checks explain why a team may reasonably decline work while showing some unused time. Capacity is constrained by skills, sequence, and dependencies, not just totals.

6. Run the review as a commitment meeting

Prepare the worksheet before the discussion. Ask team members to update remaining effort, flag absences, and name unresolved dependencies. The meeting should resolve choices, not reconstruct every task from memory.

A practical review sequence is:

  1. Correct the opening balance. Confirm absences and fixed obligations, removing duplicates.
  2. Test existing promises. Identify commitments that no longer fit, even before new requests.
  3. Expose uncertainty. State which estimates are fragile and what would change them.
  4. Evaluate new requests. Check effort, required contributors, timing, and inputs.
  5. Record the decision. Name the accepted scope, conditions, owner, and next communication.

For each accepted request, write what completion means. “Help with the workshop” is too open-ended; “produce the outline and complete one review” defines a boundary that can be checked.

Keep the worksheet wherever the team can maintain a shared view. A document or spreadsheet is sufficient. The important control is that changes to commitments are visible and someone is responsible for communicating them.

7. Recover when the week stops matching the plan

The worksheet will be wrong in places. Its value is making the consequences visible early, not proving that the original estimate was good.

If an urgent request arrives, estimate its required effort and name the work it would displace. When it exceeds the remaining planning room, choose a change: move an existing deadline, reduce scope, decline the request, or seek help whose availability has actually been confirmed. Do not accept it merely because it is labelled urgent.

If an allowance is used, record the reason. Ordinary interruptions covered by that allowance do not require inventing extra capacity. If the interruption exceeds it, recalculate the balance and communicate the resulting trade-off.

If a dependency fails, distinguish a blocked deliverable from usable time. Dev might be able to bring other work forward while waiting for access, but that does not automatically preserve the rollout deadline. Confirm whether later review and implementation time still exist.

Avoid turning these updates into individual performance judgments. Repeated overruns might reflect unclear scope, omitted review work, or recurring duties that were never counted. Investigate the category before attributing the gap to someone's speed. Likewise, do not reward estimates that look small but repeatedly require unplanned rescue work.

8. Test the worksheet in the next weekly review

For the next review, fill one row per person and list every new request considered. Finish with an explicit decision for each request and an owner for communicating it. That is the first observable outcome: no new promise should depend solely on a team-level total or an empty calendar.

At the end of the week, compare the plan with what happened using a few concrete checks:

  • Which accepted deliverables were completed within their agreed scope?
  • Which commitments changed, and were the affected people told before the deadline?
  • What consumed the uncertainty allowance?
  • Which recurring duties or review steps were missing from the opening estimate?
  • Which assumptions failed, and when did the team notice?

Use the answers to correct the next worksheet, not to claim precise capacity from a single week. If omitted duties caused the shortfall, add them. If scope expanded, tighten the acceptance boundary. If a specialist repeatedly has no room, stop using spare hours elsewhere as evidence that the team can accept more.

The next action is measurable: bring a completed opening balance, a constraint list, and a decision log to the next weekly review. Leave with named commitments and explicit trade-offs—not just a larger task list.

Capacity planningManager routinesWorkload managementTeam commitments

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications