Coordinating a Hybrid Team as an Administrative Assistant

An admin who supports an executive whose team is fully in-office or fully remote has a clearer problem than one whose team is mixed. The fully in-office team has the conventions of in-office work; the fully remote team has the conventions of remote work; the hybrid team has neither, and quietly invents new conventions every week. Most of those conventions favor whoever happens to be in the room. The admin's job is to keep that from becoming the team's default.

This page is for the in-house administrative or executive assistant supporting a hybrid team — usually the admin's executive plus their direct reports, sometimes a wider department. If you yourself work remotely full-time, the remote administrative assistant page covers the personal-discipline side; this page is about the team-coordination side.

The Core Problem: Two-Tier Drift

The single most predictable failure mode of a hybrid team is two-tier drift. Decisions get made in the office, in the corridor, in the unscheduled coffee, in the moments when the in-office members are in physical proximity. The remote members find out later, sometimes much later, sometimes only by accident. They start to feel — correctly — that they are not in the same conversation as the in-office members.

This is rarely intentional. It is the path of least resistance. An in-office leader who wants to discuss a half-formed idea will turn to whoever is sitting near them, not schedule a call. The remote member, even if they would have been the most useful person in that conversation, is structurally outside it. Repeat that pattern across many small conversations and the gap becomes large.

Most of the discipline below is aimed at preventing two-tier drift. It is the single thing that, if you do nothing else, an admin running a hybrid team should care about.

Meeting Design

The general meeting practices in the meeting coordination guide still apply. Hybrid meetings have additional rules that are easy to break by accident.

Decide the meeting modality before the invite goes out

Three modalities — and they are not interchangeable:

• Fully remote. Everyone joins from their own device, even people who happen to be in the office. This is the format that produces the most equal participation. Use it for anything where decisions are being made and remote attendance is significant.
• Room-plus-remote. Some attendees in a meeting room with shared mics and a screen, others on their own devices. This works for short briefings and for meetings where the in-room group is large enough to use a room productively. It does not work for decision-making meetings — the room dominates.
• In-room only with a recording. The remote members watch later. Acceptable only for one-way information sharing — never for discussions where someone might have wanted to weigh in.

The default for any meeting where remote members would normally participate should be fully remote. The cost to the in-office members is small (each opens their laptop instead of walking to a room). The benefit to the remote members is large (they can hear, contribute, and read the room equally well).

Camera norms have to be set explicitly

If half the team has cameras on and half has cameras off, the cameras-on group reads the cameras-off group as disengaged. Pick a default — typically cameras on for any meeting under twenty people — and have your executive or the team lead post it as a working agreement. Without an explicit rule, the camera-on group quietly resents the camera-off group, and trust frays.

Give the room a chair, give the call a moderator

The chair is in the room and runs the agenda. The moderator monitors the chat, watches the queue of remote hands raised, and feeds them to the chair at the right moments. The two roles are different and should not be the same person. The moderator role is one of the most useful contributions an admin can make in a hybrid meeting — it does not require seniority, it requires attention.

The Operating Document: Who's Where This Week

One of the highest-leverage things an admin running a hybrid team can produce is a single document, updated weekly, showing who is in the office which days, who is travelling, and who is remote-only. Its existence sounds trivial. Its absence is the source of much of the friction.

What it does

• Lets the executive and the team plan in-office days that maximize whoever they actually wanted to overlap with.
• Surfaces patterns — like a quiet trend toward Tuesday-Thursday in-office that the remote members noticed before anyone else did.
• Makes scheduling decisions visible. A meeting that happens to be on a day everyone is remote can be fully remote without controversy.
• Reduces the awkwardness of remote members guessing whether the office is busy or empty on a given day.

How to keep it accurate

Two practices:

• Self-service. Give the team members the ability to update their own row each week. The admin does not maintain everyone's calendar; the admin maintains the structure that makes self-update easy.
• The Friday refresh. Send a short message Friday afternoon: "Here's next week's posted plan; flag any changes by Monday morning." That single weekly nudge keeps the document trustworthy.

Decision-Making Across Modalities

Most decisions on a hybrid team should leave a written trace. This is not bureaucracy; it is the only way remote members get equal access to the reasoning behind a decision. The discipline:

• Decisions made in meetings get summarized immediately. One sentence, in writing, in the same channel the team uses for working communication. "Just decided in the room: we are moving the Tuesday standup to Wednesday so [name] can attend live." Posted within minutes, not hours.
• Decisions made in side conversations come back to the channel. If two in-office members agreed on something while walking to lunch, that decision needs to be posted to the team space before it is treated as final. The act of posting is what makes it a team decision rather than a side deal.
• Decisions that affect work hours, travel, or compensation never happen verbally only. Get them in writing, regardless of where the conversation started.

The admin is often the person best placed to enforce these conventions, because the admin is the one who sees the decisions flow past in calendar invites, meeting summaries, and task trackers. Pointing out missing written records gently — "should we drop a quick note in the channel about that?" — is a high-leverage habit.

Office Days That Actually Use the Office

If the team has nominal in-office days, an admin can substantially improve their value by ensuring those days are designed for what offices are good at. The failure mode is in-office days that are filled with the same video calls people would have taken from home — except now they are taking them from open desks with worse audio.

The principle

Reserve in-office days for the work that the office uniquely enables: collaborative whiteboarding, hands-on review of physical materials, longer-form team discussions, social time that builds trust, and one-on-ones that benefit from being in person. Push solo deep work and recurring video meetings to remote days where possible.

Practical moves

• When an in-office day is anchored by a specific in-person purpose — a team retro, a planning session, a customer visit — surface that purpose in the calendar invite so it is the reason people came in.
• Block lunch on in-office days as protected social time. The team that eats together once a week trusts each other in ways that are hard to rebuild over video.
• If the office has limited meeting rooms, prioritize them on in-office days for the discussions that benefit from being in person — and route routine video calls to dedicated booths or private spaces, not shared open desks.

Fairness Signals That Matter

Remote members of a hybrid team often look for small signals that they are being treated equally with in-office peers. The signals are usually not loud. The admin can make them visible:

• Promotions and recognition announced in the same channel, on the same day, with the same level of detail regardless of who is where. A remote promotion announced two days after an in-office one is read — accurately or not — as a hierarchy of attention.
• Travel for company events covered consistently. If in-office members get casual lunches paid for and remote members do not, the remote members notice.
• Birthday and milestone recognition handled deliberately. A card passed around the office for an in-office colleague produces the same gesture as a card mailed to a remote colleague — but only if someone is paying attention.
• Office perks visible to remote members. A snack drawer that exists for in-office staff is fine; gloating about it on the team chat is not. A periodic stipend for remote members to spend on equivalent comforts is the kind of equalizing signal that some companies do well and others ignore. Either policy is defensible; ignoring the question is not.

None of this is the admin's policy to set. All of it is the admin's policy to notice and to flag to the executive when something is drifting. A short, specific observation — "I noticed the in-office team's recognition tends to land on Slack faster than the remote team's; want me to standardize how we post that?" — is the kind of intervention that compounds over a year.

Failure Modes Worth Watching For

• The "we should hop on a call" reflex. An in-office leader who responds to every nuance with "let's just hop on a call" is structurally excluding remote members from the easier asynchronous version of the conversation. Suggest the async path first when reasonable.
• Meetings that started fully remote and drifted. A standing meeting was set up as fully remote two years ago, but increasingly people gather in the office room and the remote attendees become passive. Reset the format periodically.
• The remote member who has stopped asking. A remote team member who used to push back and is now going quiet is a signal worth surfacing — to your executive, gently. Disengagement is reversible early; it is much harder to reverse late.
• Ad hoc decisions that never made it to the channel. Watch for decisions you only learn about by accident. Each one is a small data point about whether the team is operating in a hybrid-friendly way or not.

Most of the work on this page is aimed at preserving fairness across modalities — a discipline that has to be rebuilt every quarter as the team changes, the office configuration changes, and the cycle of in-office and remote weeks evolves. The structural documentation that makes it sustainable belongs in the desk manual; the meeting-coordination fundamentals are in the scheduling and meeting coordination guide.