Protect Planned Work While Leaving Room for Unplanned Requests
Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.
The week begins fully assigned. By Wednesday, several urgent requests have arrived, and the original commitments are still on the plan. Nobody has explicitly cancelled or delayed anything, but the team is already choosing what will slip through late starts, fragmented attention, or extra hours.
To plan team capacity for unplanned work, leave a provisional reserve based on recent interruptions rather than assigning every available hour. Define which requests may use it, track the balance, and require an explicit trade-off when it is exhausted. Then compare the reserve with actual qualifying demand and the planned work that spilled over.
The reserve is not a promise that every urgent request will fit. It is a way to make the cost of accepting one visible before another commitment silently moves.
1. Start with the work that actually interrupted the plan
Before choosing a buffer, reconstruct a recent working week. Use calendars, task histories, and team recollections to identify requests that arrived after the plan was agreed. You do not need minute-by-minute records. You need enough detail to distinguish necessary interruptions from work that merely arrived with an urgent label.
For each request, record its type, why someone wanted it immediately, approximate effort, and the planned work it displaced. Include coordination and rework caused by the interruption where these are identifiable. Do not record elapsed waiting time as effort.
Also record whether the request would qualify under a reasonable reserve rule. This retrospective judgment matters: copying every past interruption into next week's buffer would protect avoidable disruption as well as necessary work.
A late task is not automatically unplanned demand. If a recurring report was known before planning but omitted, correct the planning process. If a task took longer than expected, record an estimation issue rather than disguising it as an incoming request.
2. Use a filled interruption log to expose displacement
Fictional worked example: All people, requests, hours, and outcomes below are hypothetical. A business operations team had 120 usable team-hours after leave, standing meetings, and routine duties. It assigned all 120 hours to planned work. The following log reconstructs what happened.
Hypothetical interruption log: baseline week
- Monday — incorrect figures in a decision pack. Request type: correction to an active commitment. Effort: 5 hours. Reason for acting now: the pack was due for use that day. Planned work displaced: 5 hours of process documentation. Reserve eligibility: yes, because waiting would leave the immediate decision dependent on incorrect information. Reserve use: none existed; the full 5 hours displaced planned work.
- Tuesday — an approval needed by another team. Request type: dependency unblock. Effort: 4 hours. Reason for acting now: a scheduled handoff could not proceed without it. Planned work displaced: 4 hours of forecast preparation. Reserve eligibility: yes, after confirming the dependency and deadline. Reserve use: none; 4 hours displaced planned work.
- Wednesday — a newly requested presentation. Request type: discretionary internal request. Effort: 4 hours. Reason for acting now: the requester preferred to review it before the weekend. Planned work displaced: 4 hours of an onboarding guide. Reserve eligibility: no; a preference was presented without a consequence of waiting. Reserve use: none; the team nevertheless accepted it.
- Thursday — correction to a scheduled partner handoff. Request type: correction to an active commitment. Effort: 3 hours. Reason for acting now: the handoff could not be completed accurately as prepared. Planned work displaced: 3 hours of records cleanup. Reserve eligibility: yes. Reserve use: none; 3 hours displaced planned work.
- Thursday — a request to reformat an internal summary. Request type: presentation preference. Effort: 2 hours. Reason for acting now: the requester wanted a different layout. Planned work displaced: 2 hours of process documentation. Reserve eligibility: no; the existing summary was usable. Reserve use: none; the team accepted it without changing a commitment.
- Friday — coverage for an unexpected absence. Request type: continuity of an existing commitment. Effort: 6 hours. Reason for acting now: a scheduled review still needed preparation and attendance. Planned work displaced: 6 hours of process documentation. Reserve eligibility: yes. Reserve use: none; 6 hours displaced planned work.
The baseline contains 24 hours of incoming work: 18 hours that would qualify for a reserve and 6 hours that would not. Planned work lost 24 hours. That distinction gives the manager two separate decisions: protect capacity for necessary incoming work, and stop accepting discretionary requests without a trade-off.
The log also reveals that process documentation absorbed 13 of the displaced hours. Without named displacement, the team might describe that work as persistently slow rather than repeatedly deprioritized.
3. Set a provisional reserve against usable capacity
Calculate usable capacity before reserving any of it. Subtract known absences, standing obligations, and recurring operational work from the team's working time. Do not reserve capacity for routine work that has already been deducted.
Then use recent qualifying demand as a starting point, not as a precise forecast. If several comparable weeks are available, examine the range and the reasons for unusually high or low demand. A week dominated by a one-off event should not automatically determine the permanent buffer.
In the hypothetical example, the manager starts with an 18-hour reserve because that matches the reconstructed qualifying demand. With 120 usable hours, the team can commit 102 hours to planned work. The reserve is 15% of usable capacity, but the percentage is a consequence of the example, not a recommended universal target.
Capacity must also be usable by the right people. Eighteen spare hours spread across a team will not solve a request that needs one specialist who is fully committed. Assign a reserve owner or coverage arrangement, and check skill constraints before treating hours as interchangeable.
A larger reserve protects against more variation but reduces the work the team can confidently commit to at the start. A smaller reserve permits a fuller initial plan but requires more frequent decisions about what moves. Choose provisionally and make the review date explicit.
4. Define entry rules before the next urgent request
A reserve without entry rules can become an open invitation to bypass planning. Use a short test that a manager can apply without creating a second planning bureaucracy:
- Why can this not wait? Identify the specific consequence of waiting until the next planning point.
- Is it genuinely new? Check whether it was knowable before the plan was agreed or is already part of routine work.
- What is the smallest useful response? Separate an immediate correction or unblock from optional improvements.
- Who can do it, and how much effort is likely? Use a rough estimate and identify uncertainty.
- Who authorizes the allocation? Name the person who can spend the reserve and change commitments.
For this example, qualifying work includes corrections needed for active commitments, verified dependency blocks, and unexpected coverage for existing commitments. Formatting preferences, optional presentations, and known recurring tasks do not qualify.
A nonqualifying request can still be important. Put it into the next planning discussion, or make an explicit priority swap now. Do not charge it to the reserve simply because a senior requester asked.
When effort is unclear, authorize a bounded assessment first. Record that time against the reserve, then decide whether to proceed. This avoids approving an apparently small request whose full scope has not been understood.
5. Fill the reserve decision worksheet before the week starts
The worksheet below connects capacity, admission rules, and the exhaustion decision. It can be kept beside the ordinary work plan; it does not require a separate system.
Hypothetical filled worksheet: first reserve week
- Usable capacity: 120 team-hours, after known obligations and absences.
- Evidence used: the baseline interruption log, with 18 qualifying hours and 6 nonqualifying hours.
- Provisional reserve: 18 hours.
- Initial planned commitment: 102 hours.
- Reserve allocation authority: the operations manager; individual contributors do not have to promise completion before that decision.
- Qualifying request types: time-sensitive corrections to active commitments, confirmed dependency blocks, and unexpected coverage for existing commitments.
- Excluded request types: optional presentation changes, preference-only deadlines, and foreseeable recurring work.
- Request record: requester, consequence of waiting, smallest useful scope, effort estimate, responsible person, decision, and remaining reserve.
- Balance review: update after each accepted request; compare remaining capacity with likely outstanding effort at the daily coordination check.
- Exhaustion rule: no additional completion commitment until the manager identifies work to defer, reduces scope, or negotiates a later response.
- Unused reserve rule: pull forward short, ready tasks that can stop cleanly; do not quietly convert them into new promised deadlines.
- Review point: the end-of-week planning review.
Make the reserve visible in the same place as planned commitments. A hidden buffer invites two contradictory expectations: requesters assume availability, while managers assume all planned work will still finish.
6. When the reserve runs out, name what moves
Exhaustion is a decision point, not a reason to keep accepting work informally. First check whether a smaller response can address the immediate consequence. If not, choose between delaying the request, moving an existing commitment, or obtaining genuinely available help.
In the hypothetical first reserve week, qualifying demand reaches 22 hours. The 18-hour reserve covers the first 18 hours. A final request requires another 4 hours, so the manager explicitly moves 4 hours of onboarding-guide work to the following week before accepting it.
We can take this request this week. It needs 4 hours beyond the remaining reserve. That means moving the final onboarding-guide edits to next week. Please confirm that trade-off before we commit.
The decision record should name the affected work, its owner, the revised timing, and who needs to know. Merely writing “capacity exceeded” does not help the person still expecting the original deliverable.
If the team accepted work before checking the balance, recover openly: reconstruct the remaining effort, identify the commitments now at risk, and renegotiate them promptly. Do not reset the reserve balance to hide the overrun or assume extra hours will close it.
7. Review spillover, not just reserve consumption
A fully used reserve is not automatically well sized, and an unused reserve is not automatically waste. Review what happened to both incoming demand and planned commitments.
Hypothetical completed worksheet: review and adjustment
- Qualifying demand received: 22 hours.
- Reserve used: 18 hours.
- Overflow accepted: 4 hours, with an explicit displacement decision.
- Nonqualifying demand received: 6 hours, deferred to the planning backlog rather than admitted to the reserve.
- Planned work completed: 98 of the original 102 hours.
- Planned work moved: 4 hours of onboarding-guide edits; no other planned carryover in this fictional example.
- Capacity check: 98 planned hours plus 22 incoming hours equals 120 usable hours.
- Next-week adjustment: provisionally reserve 22 hours and commit 98 hours, including the deferred guide edits.
- Reason for adjustment: qualifying demand exceeded the initial reserve. The manager will check whether that demand is likely to recur before retaining the larger reserve.
Separate authorized displacement from unexplained spillover. If planned work still slips while reserve hours remain unused, investigate skill mismatches, fragmented availability, estimation errors, or requests that were never logged. Increasing the buffer may not address those problems.
If spare reserve remains across comparable weeks, consider reducing it. If repeated overflow comes from the same predictable activity, schedule that activity as ordinary work instead. The useful signal is not simply hours consumed; it is whether the reserve makes incoming work and its consequences more visible.
8. Run one observable planning cycle
For the next planning cycle, reconstruct a recent week, choose a provisional reserve, and publish the entry and exhaustion rules alongside the work plan. Record each accepted interruption and any named displacement. Keep the first version simple enough that the team will maintain it.
At the review, answer three questions: How much qualifying demand arrived? What planned work moved because of it? What moved without an explicit decision? Use those answers to adjust the next reserve and fix gaps in the decision process.
The immediate test is whether the team can point to each accepted interruption and explain where its capacity came from. That makes the next urgent request a visible choice rather than an invisible rewrite of the week.
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