Project manager workload management starts with a record of the whole week. A PM’s task list may omit meetings, preparation, follow-up, and review. For AI-assisted work, include the time someone spends checking whether an output fits the project and its stakeholders.
Audit one week of commitments, then decide with stakeholders what can change. A clear record lets the team see where time goes and which work needs attention.
Map the work that competes with delivery
Put the week’s commitments on a list. Include project tasks, recurring meetings, preparation, follow-up, operational support, and miscellaneous requests. Estimate the time each takes and rank the work by priority. This gives you a concrete basis for discussing trade-offs with stakeholders.
PMI’s Work overload article recommends compiling individual work into categories such as projects, operations, and miscellaneous activities, estimating time, and discussing the resulting priorities with a manager. It suggests drawing a “capacity line” on the prioritized project list to show what can be staffed and what must wait (Project Management Institute, Work overload, date unknown). The article offers practical guidance and does not establish a universal formula for how many projects one person can handle.
Use the line to decide what fits. If the work above it fills the available week, ask which commitment should move, shrink, or go to another owner. The manager can then choose whether to protect current priorities or add work and accept the effect on other commitments.
Count AI review and coordination, not just AI output
AI-supported work still calls for professional judgment. A qualitative study based on 46 semi-structured interviews with project professionals in UK consulting and technology found that AI-supported work can shift effort toward reviewing, shaping, and adapting outputs. The authors describe changes in communication, coordination, and problem-solving, rather than a simple replacement of project work (Emerald Publishing, Artificial intelligence in project work: reshaping communication, coordination and problem-solving in project teams, accepted 10 August 2026).
The interview study does not measure how many hours AI adds to a PM’s week. Its evidence is qualitative and sector-specific. A separate PM World Journal paper argues that AI-related integration work may concentrate in the project manager’s role. The paper synthesizes research and practitioner observations, rather than offering a generalizable workload benchmark (PM World Journal, The Coordination Tax: Who Pays When AI Joins the Team, October 2026).
During the audit, include the work around each AI-supported task. Record time spent supplying context, checking accuracy and fit, resolving conflicting recommendations, and communicating the final decision. If those activities recur, consider sharing the review, clarifying who approves outputs, or changing the workflow.
PM Solutions’ 2026 report gives organization-level context, not a PM-level time estimate. The report surveyed 99 respondents and found that 63% of organizations cited integrating AI into existing workflows as a challenge (PM Solutions, The State of Project Management 2026: Project Management in an AI-Focused World, 2026). That survey reports an organizational challenge; it does not measure an individual PM’s workload change.
Audit meetings for purpose and decisions
Meetings take time and can support coordination. A 2025 survey of approximately 9,000 workers in Norway found an average of 4.7 hours per week in meetings; managers and professionals spent substantially more time in meetings than other workers. The researchers describe meetings as a way to exchange information and coordinate specialized work. They also caution that their findings are descriptive rather than causal (VoxEU / CEPR, Why we spend so much time in meetings, date unknown).
For each recurring meeting, note its purpose, required participants, the decision or coordination it supports, and the follow-up it creates. Ask the organizer to clarify the purpose before changing a meeting that has none. For a routine status update, consider whether an asynchronous update can carry the information. Keep real-time discussion for questions or alignment that need it.
Use the Norwegian average as context, not as a PM benchmark. The survey does not measure project managers alone. Its meeting-time estimate also excludes preparation, follow-up, travel, and attention-switching costs. Track those surrounding tasks in your own one-week audit.
Protect focus time and make interruptions visible
Set aside blocks for work that needs sustained attention. Count those blocks as planned capacity, and show the trade-off when someone proposes another meeting or request. The plan cannot prevent every interruption, but it can show what each interruption displaces.
An experiment on interruptions found that participants completed tasks faster while reporting higher stress, frustration, time pressure, and effort. The study did not examine project managers (Association for Computing Machinery, The cost of interrupted work: more speed and stress, 6 April 2008). Faster completion alone does not show that interruptions are harmless.
When a focus block gets displaced, record what took its place. Note whether the interruption required a meeting, a quick decision, a review, or follow-up. Use those notes to distinguish urgent coordination from routine requests that could be batched or moved async. Keep published telemetry in perspective: Microsoft’s interruption figure uses Microsoft 365 signals and is based on the top 20% of users by ping volume, not a representative measure of PMs (Microsoft WorkLab, Breaking down the infinite workday, telemetry through 15 February 2025).
Review the week with stakeholders and agree on one change
Take the workload map to someone who can change the work. Show the commitments, time estimates, and priority order. Identify work above capacity, then agree what will stop, shift, shrink, or move to another owner. PMI’s capacity-line approach gives the group one way to structure that discussion (Project Management Institute, Work overload, date unknown).
Put coordination activities alongside deliverables in the workload map. Base estimates on what you observed during the audit, and note uncertainty rather than presenting rough counts as precise measurements.
In Parallel’s company-published Coordination Tax Index reports that 247 managers across five countries self-reported an average of 16.5 hours per week across status meetings, re-explaining, and searching. The publisher says those figures are directional, not audited, so use them as a prompt to measure your own week, not as a target or forecast (In Parallel, The Coordination Tax Index 2026, fielded June 2026).
Use the map to identify the demand, choose which work matters most, and change one commitment that crowds out delivery.
Audit one week, then renegotiate one commitment
For the next week, track planned project work alongside meetings, preparation, follow-up, operational demands, and AI review. Compare the record with your commitments. Flag recurring work with no clear purpose, interruptions, and tasks whose review or coordination has no explicit owner. Take the audit to stakeholders and agree on one low-value commitment to remove, reduce, or renegotiate.
One person’s calendar cannot establish a universal capacity number. Use the audit.
Call to action: Audit one week of your calendar and work, then renegotiate or remove one low-value commitment.
Key takeaway
A capacity plan should count coordination and review alongside delivery work, then make trade-offs visible so stakeholders can decide what changes.

Andrii founded It’s a Plan and leads its product and roadmap, from the open-source edition to Pro for teams. He works with the project’s contributors and the teams that run It’s a Plan.
All posts by Andrii Poluosmak