Workload and Capacity Conversation
A manager and team member compare competing commitments, decide what continues or moves, and record the rationale, owners, and review date. The fictional example shows how to make a workload tradeoff explicit without treating it as a productivity score.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Professional services · Public-sector service teams
Overview
The Workload and Capacity Conversation page gives a manager and team member a practical sequence for resolving competing work. It starts by making commitments, deadlines, dependencies, and realistically available time visible. Participants then compare what happens if each item is completed now, later, or not at all, distinguishing fixed deadlines and dependencies from preferences. They agree what continues, pauses, stops, or moves, and record the rationale, owners, and review date.
The filled-in example uses fictional Northstar Service Desk work: an urgent backlog review takes the available work block, while the weekly queue summary moves to the next planning period. Its decision record explains the choice without inventing backlog size, service targets, or customer impact. The role-based handoffs show what the manager, team member, and established People Development route do when follow-up or escalation is needed.
Use this page when a change in workload, timing, or urgency requires a specific priority decision and a later check. Adapt the sample work, responsibilities, and escalation route to your organization; the displayed decision date and review date are illustrative, not live reminders. Do not use the page as a productivity score, staffing dashboard, formal legal assessment, or substitute for an authoritative policy or procedure. If a conflict cannot be resolved, record the open issue and use the organization's established support route rather than implying every commitment remains feasible.
Standards & compliance context
- This page is a decision-recording aid, not a legal or regulatory workload assessment; use applicable organizational policies and formal processes for those determinations.
- Limit decision records to information needed to explain the work choice and follow-up, and follow organizational access, retention, and privacy rules for personnel-related records.
- For an audience-restricted page, apply WCAG 2.1 AA accessibility practices, including meaningful headings, readable content, and text alternatives for informative images.
- Keep the fictional Northstar decision clearly identified as illustrative and do not present its dates or work details as verified organizational facts.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Agree what fits, and what moves
This introduction defines the page's purpose and distinguishes a priority conversation from productivity measurement or a staffing dashboard.
-
When the work on hand exceeds the time available, use this conversation to agree priorities and record the decision. In this fictional example, Northstar Service Desk weighs an urgent backlog review against its weekly queue summary. This is a work-prioritization conversation, not a measure of productivity or a staffing dashboard.
Work through the decision together
Use these steps to compare commitments and consequences before agreeing what continues, stops, or moves.
-
Keep the discussion specific to the work, the time available, and the consequences of moving a commitment. Make the work visible List current commitments, deadlines, dependencies, and the time realistically available in the period being discussed. Identify what has changed since the work was planned. Compare urgency and consequences For each item, discuss what happens if it is done now, later, or not at all. Distinguish a fixed deadline or dependency from a preference, and name who or what is affected. Choose what continues, stops, or moves Agree which work stays first and which work pauses, stops, or is deferred. Surface any work that needs a separate decision rather than assuming everything still fits. Name an owner and review date Record the choice and its rationale, assign each follow-up to a role or participant in the conversation, and set a date to check whether the priorities still fit.
Worked example: protect time for the urgent review
The fictional comparison shows how choosing one work item can defer another within a defined work period.
-
Fictional Northstar Service Desk decision. The work details are illustrative, not live operational data. This week's work block Prepare the weekly queue summary Use the available time for the urgent backlog review Tradeoff Less time remains for the backlog review The weekly summary moves to the next planning period Decision dated 10 October 2026
Decision record
This sample records the reason, deferred work, role-based ownership, and date for checking the decision.
-
Fictional sample: Northstar Service Desk Decision date: 10 October 2026 Priority: Use this week's available work block for the urgent backlog review. The team chose this option because unresolved items need assessment before the next planning period. Deferred work: Move the weekly queue summary to the next planning period. Do not count it as completed or silently add it back into this week's workload. Evidence considered: The pair compared the backlog review need, the remaining work time, and the consequence of delaying each activity. No backlog size, service-level target, or customer impact is assumed in this example. Owners: The manager communicates the priority change and raises unresolved priority conflicts. The team member records the backlog review findings and tells the manager if workload or timing changes. Review date: 17 October 2026. At that check-in, the pair will confirm whether the review is complete, whether the summary still needs to be done, and whether new work changes the plan. If competing demands remain unresolved, raise the conflict through the organization's established manager or People Development route.
Role-based handoffs
These responsibilities clarify who communicates the change, records follow-up, and receives unresolved conflicts.
-
Helps resolve priority conflicts and communicates agreed changes Manager Manager role Makes work and timing changes visible; records agreed follow-up Team member Team member role Established support route when competing demands remain unresolved People Development Role-based handoff
How to use this template
- Replace the Northstar example with the work under discussion, confirming each commitment, deadline, dependency, and the realistic time available for the period.
- Have the manager and team member compare the consequences of doing each item now, later, or not at all, and identify which constraints are fixed versus preferred.
- Agree which work continues, pauses, stops, or moves, and note any unresolved item that needs a separate decision.
- Record the decision date, reason, deferred work, and a role or participant responsible for each follow-up.
- Set a review date that fits the work, then use the check-in to confirm completion, reconsider deferred work, and account for changes in workload or timing.
- If priorities remain in conflict, document the unresolved issue and use the organization's established manager or People Development route.
Best practices
- List current commitments and available time for the same defined period so the comparison is grounded in actual capacity.
- For each item, write down a specific consequence of doing it later instead of relying on labels such as urgent or important.
- Separate fixed deadlines and dependencies from preferences before choosing which work moves.
- Record deferred work explicitly and do not silently add it back into the current period as if it were still feasible.
- Assign follow-up to a role or participant and state an observable action, such as communicating the change or recording review findings.
- Choose a review date that allows the participants to verify whether the decision worked and whether new work has changed the plan.
- Keep the conversation about commitments, time, and consequences rather than using it as a measure of an individual's productivity.
- Keep the escalation handoff accurate; confirm the internal route before replacing the sample's general People Development reference.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What situation is this template designed for?
Use it when current commitments compete for the time available and a manager and team member need to agree what continues, pauses, stops, or moves. The example considers an urgent backlog review alongside a weekly queue summary. It is not a productivity measure or a staffing dashboard.
How often should we have a workload and capacity conversation?
Use the conversation when priorities or available time change enough to put existing commitments in conflict. The fictional example sets a review one week after the decision, but that date is illustrative rather than a required cadence. Agree a review date that matches the work and revisit sooner if timing or workload changes.
Who should lead and record the conversation?
The manager and team member compare the work and agree the priority decision together. In the sample, the manager communicates the change and raises unresolved conflicts, while the team member records the review findings and flags changes in workload or timing. Adapt these role responsibilities to your organization's established process.
Does this template satisfy a legal or regulatory workload assessment?
No. The page supports a practical priority conversation and records a decision; it does not assess legal compliance, health and safety risks, working hours, or staffing requirements. If a workload concern triggers a formal policy or regulatory process, use that authoritative process and route. Do not treat this example as a substitute.
What should we do if the manager and team member cannot agree?
Record the conflict and the consequences that remain unresolved rather than implying that all work still fits. The sample points to the organization's established manager or People Development route for unresolved competing demands. Replace that general handoff with the correct internal route before publishing the page.
Can we use the worked example as a live record?
No. Northstar Service Desk and its 10 October 2026 decision are fictional sample content, not live operational data. Replace the example with a real, appropriately managed decision record or keep it clearly labeled as illustrative. Avoid adding sensitive personnel details to a broadly accessible intranet page.
How should we customize this page for our organization?
Keep the sequence of making work visible, comparing consequences, choosing what moves, and setting a review date. Update the role-based handoff and escalation route to match your process, and revise the example to reflect familiar work without implying unverified targets or impact. Keep one authoritative home for any related policy or procedure and link to it when your site provides a valid destination.
Does the template connect to a calendar, workload system, or approval workflow?
The supplied page contains static sample content and does not specify a connected calendar, workload system, or approval workflow. The review date in the example is written into the page content; it does not create a reminder. If you add a live block, configure its source through the site's supported setup and explain what it displays.
Why use this page instead of an informal chat?
A conversation can resolve a short-term conflict, but without a record the deferred work, rationale, owner, or review date can be forgotten. This page makes those decisions visible and gives both participants a shared point to revisit. It does not replace ongoing planning or the formal route for unresolved concerns.
Related templates
Go deeper on the topic
-
A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
-
Employee experience (EX) is the cumulative perception an employee forms across every interaction with their company — recruiting, onboarding, the day-to-day...
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Workload and Capacity Conversation ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
