ExecutiveSupportStaff Editorial Team | Published
One EA supporting multiple executives works when three conditions are met. First, the executives have compatible schedules, meaning the calendar windows do not constantly collide. Second, the task volume across all the executives is realistic for one full-time role. Third, the EA has strong systems and the executives respect those systems.
The model breaks down when any of those conditions fail. The most common failure is treating shared support as if it scales linearly, when in reality the coordination overhead grows faster than the head count would suggest.
The single most important element of multi-executive support is an explicit priority protocol. Most effective setups designate one primary executive whose work gets default priority, then define how non-primary executive requests are queued or escalated. The protocol is written down, agreed to in advance, and referenced when conflicts arise.
Without a written protocol, the EA defaults to whoever asks last, which produces inconsistent service and resentment. With a written protocol, conflicts become administrative rather than political.
A shared task or project management system is the source of truth for all executive requests. Each request lives there, with the requesting executive, the priority, and the deadline visible. Individual channels (Slack DMs, email) handle private or confidential items and quick acknowledgments.
The most common mistake is using only email. Email loses context, hides the queue from the EA, and makes it impossible for the executives to see what the support team is currently handling. A shared system fixes all three.
The minimum-viable cadence is 15 minutes daily with the primary executive and 15 minutes weekly with each of the other executives. The daily sync covers context, priorities, and any conflicts on the horizon. The weekly check-in keeps the non-primary executives aligned on what is in flight and gives them a regular opportunity to raise items without competing for the EA day-of attention.
The signals are practical. If the EA is regularly working more than 50 hours per week, the load is unsustainable. If quality is slipping (missed follow-ups, calendar errors, briefs that arrive late), the volume has exceeded what one person can handle at a high standard. If conflicts between executives requests are surfacing weekly rather than monthly, the priority protocol is being stress-tested beyond its design.
At that point, the right next step is either a second EA (each handling one or two executives) or a coordinator structure with a lead EA and a junior support role.
For the broader structural choices around supporting a leadership team, see supporting an entire leadership team. For the cost of staffing a multi-executive arrangement, our piece on executive assistant cost covers the budget across different models.
| Setup variable | Recommendation |
|---|---|
| Number of executives | 2-4 for one EA; beyond that, add a second EA or coordinator |
| Priority protocol | Written; one primary executive, explicit queue rules for others |
| Tooling | Shared task system + per-executive private channels |
| Standing sync | 15 min daily with primary; 15 min weekly with each other executive |
| Confidentiality | Each executive can mark items "EA only"; explicit access boundaries |
How many executives can one EA realistically support?
A skilled EA can effectively support two to three very active executives or three to four executives with more moderate support needs. Beyond that, the conflict-resolution load and context-switching cost typically exceed what one person can absorb without quality degradation.
How are priorities handled when two executives need the same thing at the same time?
With a written priority protocol established up front. The most common version: a primary executive whose work has default priority, and an explicit rule for how non-primary executives requests get queued or escalated. Without this, every conflict becomes an ad-hoc judgment call, which exhausts the EA and frustrates the executives.
Should each executive have a separate communication channel with the EA?
Yes. Most effective setups use a shared task or project management system as the source of truth, plus individual channels (Slack DM, email, phone) for each executive private items. The shared tool gives the EA visibility; the individual channels respect confidentiality.