Weekly workload planning around real capacity
Use weekly workload planning to compare remaining task hours with real availability and decide what to accept, defer, or reassign.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What weekly workload planning is
Weekly workload planning starts by comparing the work people still owe with the time they actually have on the dates that matter. Start with current tasks and their remaining effort, subtract the time already reserved on each person's calendar, then decide what each owner can deliver. The result should give people a workable set of commitments and make the choices about displaced work visible before the week starts.
Team capacity planning happens at two useful levels. A weekly budget tells you how much effort someone can reasonably take on. Daily availability tells you whether that effort can land before a particular deadline and whether dependencies leave enough time. Give each proposed task a clear outcome, and label the plan according to what you checked. A task with a sensible weekly allocation can still need a date or a decision before the owner can promise it.
What it does for the business
- Tell stakeholders what they can expectA deliverable and a date give stakeholders something concrete to plan around. Where a tradeoff needs a decision, they can choose between the affected outcomes before making a promise to a customer.
- Use limited time on the work that mattersWhen you see which discretionary work conflicts with a deadline, you can defer the item with the smallest consequence. You can also protect work that has already been promised by showing exactly what any new request would displace.
- Make reassignments easier to approveA proposed move can show the current owner's constraint, the candidate's available time, and the skills or access the work requires. The manager can review that specific move and arrange a handoff while both people still have time to prepare.
- Carry decisions into the following weekA record of accepted and deferred work gives the team a starting point at the next planning meeting. If a dependency slips or a person's working dates change, you can reopen the affected decision and trace why it changed.
Weekly workload planning, step by step
Set the week and reconcile the task list
A commitment stays on the list until you have evidence that it changed.
What to do
- Write the exact start and end dates for the planning week. Confirm which dates each owner works and which time zone governs the work, especially when teams share a handoff across locations.
- Pull the current task list and retain a stable ID for each item. Capture its current owner, status, hours left, priority, due date, fixed working date, and any dependencies that affect delivery.
- Compare current records with the last accepted plan. If a prior commitment is missing from the export, check whether it moved, was canceled, or was completed and keep it visible until you have evidence.
- Confirm the business priorities and the work already promised. Where two discretionary requests compete and the business has supplied no ranking, write down who needs to choose between them.
Why
A task export shows the records present at the time it was taken. Work can vanish from that view when a filter changes or ownership moves. Comparing stable IDs prevents a quiet drop from the list, and explicit dates give every owner the same week to review.
Calculate the time each person really has
Time already reserved can support only one commitment.
What to do
- Start with confirmed working hours on each working date. Use the individual's actual arrangement, including part-time days, approved leave, and any variation from the previous week.
- Subtract meetings and other reserved time on those dates. Reconcile overlaps first so a meeting that falls during leave does not reduce the same day's capacity twice.
- List routine obligations such as support coverage. Include them as task allocations or as time reserved on the calendar, using whichever source better reflects the obligation and counting it once.
- Mark dates with incomplete coverage as unknown. Keep the affected owner or date visible alongside a specific request for a schedule, confirmation of working dates, or the missing calendar information.
Why
Two people assigned similar hours may face very different weeks. Confirmed time helps you decide where a transfer is plausible, and incomplete coverage tells you where to ask before promising delivery. A person's capacity in this plan reflects their working constraints for this week.
Propose what fits and check the dates
A weekly total only helps when the work fits the dates it needs.
What to do
- Allocate hours to fixed commitments first. Check when the work has to occur and identify any discretionary item that must move to make room, along with the consequence of moving it.
- For each remaining task, propose accept, defer, reassign, or review. Put a reason and a concrete owner action next to the decision. Name a candidate for reassignment only after checking relevant skills and available time.
- When only part of a task fits, describe the usable outcome for this week and the effort that stays open. For example, commit to preparing a parts list and leave supplier confirmations for a later decision.
- Check daily hour budgets where dates matter. Put prerequisites on compatible earlier dates when possible. Ask the people involved to confirm same-day order and time-of-day deadlines before treating them as settled.
Why
Weekly capacity can look comfortable even when a deadline falls before most of the available hours. The date check shows where to adjust a proposal or raise a decision. Writing down the partial outcome also prevents a small allocation from turning into a promise to finish the whole task.
Review changes and make decisions explicit
A proposal becomes a commitment when the responsible person confirms it.
What to do
- Ask another reader to check the largest tradeoffs against the original task and calendar records. Start with a decision that would move a deadline, change an owner, or delay a prerequisite.
- Recheck weekly totals and the daily budgets for any date-sensitive change. If you move work between people, recheck both owners' capacity and the work that depends on the handoff.
- Keep earlier confirmed decisions unless current evidence changes the reason for them. Record the changed fact alongside the decision so the team can see why an item resurfaced.
- If the plan still needs a choice, present the options and the consequence of each. Give the decision to someone with authority over the competing commitments.
Why
Correct arithmetic cannot establish whether a customer promise can move or whether a teammate can take ownership. A source review catches unsupported assumptions while they are still easy to correct. A clear decision queue keeps unresolved choices from looking like work already booked.
Give each owner a handoff they can use
Every owner should be able to see their next action without rebuilding the plan.
What to do
- Lead with the work that can proceed and the most urgent choice. Put the affected deliverable and deadline beside each decision so stakeholders can see what changes if they wait.
- Give each owner their proposed outcomes, budgeted hours, applicable dates, key prerequisites, and one next action. Flag anything still waiting on their confirmation.
- Carry deferred and unconfirmed work forward with its reason and stable task ID. Keep a record of who confirmed decisions and which facts the next planning cycle should check again.
- Ask the owners to confirm the proposal and have the authorized people update their task records and calendars once the decisions are made.
Why
A plan is useful when owners can act on it and decision makers know what they must settle. Keeping confirmed decisions and proposals identifiable also makes the next planning cycle faster, because the team can start with the evidence that actually changed.
Common mistakes
- Using the original estimateReestimate the effort left after completed work and any changes in scope.
- Carrying last week's calendar forwardConfirm this week's working dates and leave before treating time as available.
- Smoothing effort across daysCheck whether the actual working dates and task order can support the due date.
- Moving fixed work quietlyAsk the person who owns the commitment to approve any change and explain the consequence.
- Treating a suggested transfer as acceptedConfirm the proposed owner, their availability, and the applicable constraints before allocating work to them.
What a good result looks like
- An exact planning week and confirmed working dates and time zones for the people covered.
- A current task list with source-backed remaining hours and explicit gaps.
- A decision, reason, and next action for each item, including missing prior commitments.
- Weekly hours and daily checks labeled at the level the evidence supports.
- A short owner handoff and a decision queue with the consequences of waiting.
And then what? Using the result
- Bring the highest-impact tradeoff to the person who can approve it before communicating a change to stakeholders.
- Ask proposed owners to confirm the work and surface missing estimates, access, or prerequisite decisions.
- Update the task system and calendar after approval, then tell the people who depend on the changed dates.
- At the next planning cycle, compare confirmed commitments against current effort and calendars and reopen decisions where the facts changed.
When to run it
- Before the weekly planning meetingPrepare a short set of choices while there's still time to move discretionary work or ask for better estimates.
- When leave or a new deadline changes the weekRecalculate affected dates and owners, then identify which previously planned outcomes need a decision.
- When a team shares work across locationsCheck working dates and time zones for both sides of the handoff so the receiving owner has a usable window.
Questions people ask
How do you do weekly workload planning?
Confirm the dates, calculate each person's available hours, and propose commitments from the remaining work and its priorities. Then check dates and dependencies, and give owners the proposed outcomes and decisions to confirm.
How do you calculate team capacity for next week?
Start with each person's confirmed working hours and subtract meetings, leave, and other reserved time after reconciling overlaps. Show where coverage is incomplete so a total of known hours does not suggest that every schedule was checked.
What if a task has no estimate?
Put it in review and ask its owner for the hours remaining and the outcome those hours would buy. Keep its demand visible while you plan other tasks with confirmed effort.
How do you handle tasks that carry over from last week?
Keep their stable IDs and prior confirmed decisions, then check current effort, availability, priority, and dependencies. If a task disappears from the current source, ask for its status and keep the earlier decision visible.
Does a weekly workload plan prove that every deadline fits?
A weekly workload plan only shows the hour budget unless it also checks allocations by date. For a time-of-day deadline, confirm the usable hours and task order directly with the owners.
Who approves a proposed reassignment?
The person authorized to change ownership approves it after the candidate's skills, availability, and handoff constraints are checked. Until that decision, keep the reassignment as a proposal.
More jobs in Ops
Plan next week's workload, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac