Working With Other Assistants: Admin-to-Admin Coordination

Almost every meaningful logistical task an admin handles eventually requires coordinating with another admin — the EA on the other side of an external meeting, the office manager at a partner company, a peer admin inside the same building, the assistant to a board member you have never met. The quality of that coordination determines whether the meeting happens cleanly or whether two weeks of email ping-pong produces a half-broken arrangement at the last minute.

Most admin schools and onboarding programs do not teach this directly. It is one of those skills that gets absorbed by watching how it goes well or badly, and then internalized once a few cases compound. This page is the explicit version.

The Default Setting Is Allyship

The single most important orientation in admin-to-admin work is the assumption that the other admin is on your side. Both of you are trying to make a meeting happen between two busy people. Both of you have access to information neither of your principals has time to read. Both of you are operating against the same kind of constraints. Approach the conversation as a peer collaboration, not a negotiation.

This sounds obvious. The failure mode — treating the other admin as an obstacle, or as someone to extract concessions from — is more common than admins realize once they see it from the receiving end. Tone matters enormously here. A short opening message that names what you are trying to do and why opens the conversation differently than a calendar request landing cold.

The First Outreach

When you are reaching out to an admin you have not worked with before, three lines do most of the work:

• Identify yourself and who you support. "Hi, I'm [name], I work with [executive] at [company]."
• Name the substance of the meeting. Not just the calendar invite — what the conversation is actually about, why it is being scheduled, and any context you have about urgency.
• Offer a flexible opening. "What's the best way to find an hour for them in the next two weeks?" works better than sending three calendar holds and asking which works.

The reason this opener works is that it gives the other admin enough information to flag any constraints early — "actually, [their executive] is travelling that whole window, can we look at the week after?" — instead of trading three rounds of failed proposals.

Sharing the Information That Matters

Two pieces of information consistently make admin-to-admin coordination smoother. Volunteer them; do not wait to be asked.

Your executive's actual constraints

• Standing meetings that absolutely cannot move.
• Personal commitments you know about — early-morning workouts, school pickup, a class once a week — without naming them more specifically than necessary.
• Travel days that are firm.
• Time-of-day preferences (some executives are useless before 10 AM; some are useless after 4 PM).

What kind of meeting your executive is expecting

"They expect this to be a 30-minute introductory conversation, not a working session" tells the other admin enormously more than "30 minutes please." If your executive is expecting a deal-closing meeting and the other side is expecting an introduction, the meeting fails before it starts. The admins are in a position to surface this mismatch in advance.

What You Do Not Share

The flip side of being open is being explicit about what you do not share. Other admins will sometimes ask for information you should not give:

• The specific reason your executive cannot attend something — beyond a general "scheduling conflict."
• Internal personnel matters, even at a high level. "He's interviewing candidates that morning" is too much.
• Travel destinations or itinerary details.
• Anything about active deals, M&A, legal matters, or pre-announcement personnel changes.
• Information about a third executive who is not part of this meeting.

The general framing is: share what helps the other admin do their job better, do not share what serves only their curiosity. The default-closed rule from the confidentiality guide applies in admin-to-admin conversations the same way it applies inside the company.

Negotiating Conflicts Without Burning Goodwill

Real coordination work involves saying no — to a meeting time that does not work, to an attendee list that is too large, to a date that conflicts with something more important. The script that works:

• Be specific about the constraint, not the conclusion. "He's flying back from [city] that morning and lands at 11" lands much better than "that morning won't work for us."
• Offer alternatives in the same message. Two or three concrete options, not "let me know what else works." The other admin is also under time pressure; making them propose round two is friction you can save them.
• Acknowledge their side. "I know this is the third reschedule on our end — really sorry, the fall is just brutal for [executive]'s travel schedule." Brief, sincere, no excessive apology.

The admins who never push back on a request are not actually serving their executives well; they are just deferring the conflict to the executive level. Pushing back early, with concrete alternatives, is part of the job.

The Long Game: Building the Network

Every admin you coordinate with cleanly today is a peer who can help you tomorrow. Treating each interaction as transactional misses the compounding value of the network.

The small habits that build the network

• Remember names. The third email exchange with the same external admin should not start "hello, this is [name] from [company]" if you have already exchanged emails. Build a small private contact list with notes — who they support, what worked last time, what to remember about them.
• Send a quick thank-you when something goes well. A meeting that took three weeks to schedule ends with one short message: "Thanks for working through that — appreciated your flexibility." It costs you nothing; it lands meaningfully.
• Reciprocate when you can. If another admin urgently needs a slot for their executive that you can shift to make room for, do it — even when it is slightly inconvenient. The favor will be returned within three months.
• Pass real information, not gossip. "Just so you know, our team is finalizing the budget this week — your executive's request might be more time-sensitive than it looks" is the kind of useful intelligence that builds long-term trust. Gossip is the kind of thing that breaks it.

Internal admins matter even more

The network of admins inside your own company is the single most underrated professional resource a new admin has. They know things you cannot find written down — the unwritten rule about which meetings actually run on time, how the CEO's spouse prefers to be addressed, which conference room is unbookable on Mondays for reasons no one can explain. Make peer-admin lunches a recurring habit — not as networking but as colleagues — and the institutional knowledge transfer over a year is enormous.

Working With External Gatekeepers

Some external assistants are gatekeepers in the strict sense — they actively screen who gets through to their executive, and they have explicit authority to say no. This is a different conversation from admin-to-admin coordination of an already-agreed meeting.

What works with gatekeepers

• Be honest about the value proposition. "My executive thinks there's a partnership opportunity here; I want to be transparent that we don't yet know if it's mutual" is better than overselling. Gatekeepers have heard every version of every pitch; honesty is differentiated.
• Offer to do the work. "I'm happy to draft a one-pager for [their executive] to review, so they can make an informed decision about whether the meeting is worth it." This converts the gatekeeper's job from a guarded yes-or-no into something concrete they can route.
• Take no for a real answer. If the gatekeeper says now is not the right time, accept it. Persisting marks you as the kind of caller who will be auto-deferred forever. Coming back six months later with new context is far more effective than calling back next week.

When the Other Admin Is Difficult

Occasionally — rarely, but it happens — the other admin is unhelpful, slow, or actively obstructive. Three responses, in order:

1. Stay polite, even after they are not. The conversation may be reviewed by both executives. Your tone is your reputation.
2. Be more explicit about the substance. Some difficult admin interactions are downstream of an executive who has not actually committed to the meeting. More information, sent calmly, sometimes unblocks the conversation.
3. Escalate to your executive only as a last resort. "[Their EA] is having trouble finding a time" is the right framing — never "their EA is being difficult." Your executive will sort it out at the principal level if it matters; you will have stayed clean.

The worst possible outcome is a public exchange where one of the admins comes off as petty. Even when the other side is genuinely at fault, restraint protects you and your executive's reputation in ways that being right does not.

Common Mistakes

• Treating the other admin as a vending machine. "Send me three times that work" with no context lands cold. A sentence of context produces faster, better answers.
• Cc'ing the executive on routine coordination. The point of admin-to-admin coordination is that the executives do not have to be in the loop until something is decided. Looping them in early signals you cannot run the coordination yourself.
• Not introducing yourself. A request from an unfamiliar admin with no introduction lands lower in the priority list than a request from someone whose context is clear.
• Letting the calendar invite carry the substance. The invite is the artifact, not the explanation. A three-line email alongside the invite saves the other admin from having to guess what the meeting actually is.
• Forgetting that the other admin has their own constraints. Asking for a 30-minute hold "anytime in the next two weeks" sounds flexible to you and looks impossible to them.

None of this is glamorous. All of it is the discipline that turns "we can never seem to get on each other's calendars" into a meeting that just happens. Done well over years, the network of admins who know your work — inside your company and across the industry — is one of the most durable professional assets the role builds. The broader operating disciplines that pair with this work are in managing a shared or delegated inbox and supporting multiple executives; the underlying default-closed information rules sit in the confidentiality and discretion guide.