Workload balancing starts with a better question than how
Workload balancing starts with a better question than how busy is everyone. Ask which leadership outcomes are protected, which commitments are at risk, and what work is consuming attention without moving a decision. An executive assistant, chief of staff, or project coordinator can prepare this view, but the executive team still decides which priorities win. Begin with a two-week inventory of recurring meetings, inbox work, board preparation, project follow-up, travel or event logistics, and unscheduled interruptions. Record the trigger, expected output, owner, review point, and consequence of delay. The inventory is not a performance score. It is a map of demand that lets support and leadership discuss tradeoffs using the same facts.
Separate fixed obligations from negotiable work
Separate fixed obligations from negotiable work. Board cycles, leadership meetings, confidential correspondence, and time-sensitive approvals may have firm windows, while some reports, check-ins, and reminders can move or become written updates. Mark each item as fixed, movable with approval, delegable within the support role, or requiring a leadership decision. This classification prevents a common failure: treating every incoming request as equally urgent because the queue has no operating rule. Support may suggest a reordering and show what would be displaced, but it should not quietly cancel a commitment or promise a new response on behalf of a leader.
Use capacity bands instead of a single utilization percentage
Use capacity bands instead of a single utilization percentage. A week can look manageable in total hours while still being fragile because all preparation lands before one leadership meeting or because confidential work cannot be handed to a backup. Note planned capacity, protected recovery time, known coverage gaps, and the amount of interruption the role can absorb before quality or timing changes. The point is not to optimize every minute. It is to expose the margin that allows an executive support function to handle a surprise without borrowing time from another consequential workflow.
Build a tradeoff conversation around consequences
Build a tradeoff conversation around consequences. When a new request arrives, show the requested outcome, its deadline, the source of the request, the work it would displace, and the decision required from the accountable leader. A concise choice may be to move a lower-risk preparation task, add a reviewer, defer the request, or narrow the requested output. Avoid presenting a long list of every open item. Leaders need a small set of defensible options and enough context to understand what each option protects or puts at risk.
Give recurring work an owner and a definition of complete
Give recurring work an owner and a definition of complete. Calendar coordination may be complete when the required participants, purpose, preparation window, and follow-up owner are confirmed. A decision brief may be complete when its sources, open questions, requested choice, and review deadline are visible. A project update may be complete when the change, dependency, risk, and next action are recorded. Clear completion conditions reduce hidden rework, which is often the largest capacity drain in executive support because an item appears finished while still requiring clarification or another review.
Design the interruption lane deliberately
Design the interruption lane deliberately. Reserve a visible place for requests that cannot be scheduled in advance, then define what information is needed before they enter the priority conversation. A support professional can acknowledge receipt, identify missing context, and protect the current queue while waiting for an answer. If the request affects an external promise, sensitive information, policy, or a material priority, route it to the accountable leader. The interruption lane should keep urgent work visible without allowing urgency alone to become authority.
Review the week at two different distances
Review the week at two different distances. A short daily check asks what changed, what is blocked, and what needs a same-day decision. A longer weekly review asks whether the demand pattern itself is changing: repeated last-minute requests, meetings with no decision, recurring work that lacks an owner, or a backup who cannot recover the process. Use those patterns to adjust the operating model. Do not respond to every busy week by adding a new tracker; first identify whether the problem is unclear scope, poor timing, missing access, or a leadership choice that has not been made.
Protect the evidence behind the capacity view
Protect the evidence behind the capacity view. Keep detailed correspondence, private documents, credentials, and personal information in their authorized systems. The workload record should contain only the minimum context needed to coordinate, with a link or reference to the source where appropriate. When two records disagree, preserve the discrepancy and ask for resolution rather than selecting the version that makes the queue look healthier. A trustworthy capacity conversation depends on accurate signals and on confidence that sensitive material is not being copied into a broad operational surface.
Plan for continuity before demand peaks
Plan for continuity before demand peaks. A backup needs the current queue, definitions of complete, source locations, response expectations, access boundaries, and escalation route. Pairing one person with every task is not enough if the handoff requires private memory. Test a bounded handoff and observe where the backup has to ask the same questions again. Improve the record or narrow the scope before expanding access. Continuity is a capacity control because it prevents a single absence from turning ordinary work into a reconstruction exercise.
Close the playbook with a leadership agreement
Close the playbook with a leadership agreement. State which work the executive support function owns, which choices remain with leaders, how new requests are ranked, what response windows mean, and when the arrangement will be reviewed. Pilot the rules on one leadership cadence and compare the expected workload with what actually arrived. Keep the changes that reduce rework or clarify decisions, and discard measures that create reporting without better choices. Balanced workload is not equal distribution of tasks; it is a visible agreement about which leadership work receives attention, by whom, and under what boundary.
Frequently asked questions
Should one assistant support the whole executive team?
Sometimes. It works when priorities are clear and executives share one operating rhythm.
What should happen before a consult?
List the meetings, inbox rules, recurring reports, and decisions that need support.
Ready to define the role?
Use a recent leadership week to scope the support that would make the biggest difference. The consultation is a working conversation, not a generic pitch.
Book a consultation