ExecutiveSupportStaff Editorial Team | Published
In an office, context transfers through proximity. The EA overhears a conversation, sees the executive's reaction to a meeting, and picks up signals that inform their judgment without anyone having to document them. In a remote arrangement, that ambient context disappears. The tools are how it gets replaced.
A remote EA with the right access and the right tools can operate at the same level of effectiveness as an in-house hire for the core executive support tasks. A remote EA with incorrect access, view-only permissions, or no shared task system operates at a significant disadvantage. The tool setup is a one-time investment that removes friction from every future week of the engagement.
For the broader context of what to expect from a remote working relationship, see the guide to working with a virtual executive assistant.
Full edit access to the executive calendar is not optional for an effective remote EA. View-only access means the EA cannot make changes without the executive's direct involvement, which puts the scheduling back-and-forth through email rather than giving the EA independent ownership of the calendar.
Google Calendar and Microsoft Outlook both support delegate access natively. In Google Calendar, this is calendar sharing with "make changes and manage sharing" permission. In Outlook, this is delegate access in Exchange settings. Both approaches give the EA their own auditable login, which is cleaner than shared credentials. Before the EA starts, configure time zone settings, establish naming conventions for meeting types, and confirm which calendars the EA needs access to (some executives maintain separate personal and work calendars).
Delegate access is the standard and correct setup for executive inbox management. Gmail delegation and Outlook delegate access both allow the EA to read, respond, and organize using their own login without requiring the executive to share a password. Password sharing is not the right approach: it creates a shared audit trail, cannot be scoped to specific permissions, and is harder to revoke cleanly if the engagement ends.
For day-to-day async communication between the EA and the executive, a messaging tool (Slack, Microsoft Teams, or a comparable platform) works better than email. Messaging creates faster feedback loops for questions and approvals without clogging the executive inbox. Establish a shared convention for urgency: which channel gets used for routine questions, and which channel means something needs a response within the hour.
A shared task system gives both the executive and the EA visibility into what is open, what is in progress, and what is blocked, without requiring a status meeting. The minimum functional setup is a shared list that both parties can read and update. Asana, ClickUp, Notion, and a shared Google Sheet all work; the right choice is the one that fits the executive's existing preferences and does not require them to learn a complex new interface.
For more on how EAs use project management tools for multi-step work tracking, see the guide to delegating effectively to a virtual executive assistant. The most important configuration is a weekly priorities view: the top open items for the week, organized by urgency, visible to both parties without a meeting.
A remote EA booking travel for an executive needs either a virtual card with a clear spending authority or delegate access to the company's corporate travel booking platform. Requiring the executive to provide a card number for each booking creates friction and slows down the booking process on time-sensitive trips.
A virtual card with a defined spending limit and a clear category scope (flights and accommodation only, for example) gives the EA genuine booking autonomy while maintaining expense controls. The EA should also have access to the expense reporting system so they can submit receipts and documentation without creating a handoff step that the executive has to manage.
A shared cloud drive with appropriate folder access is the baseline for remote EA document work. Google Drive, Microsoft SharePoint, and Dropbox Business all support folder-level permission controls that allow the EA access to the documents they need without access to everything. Local files are a remote EA anti-pattern: an EA who cannot access a document because it is on the executive's laptop cannot do their job.
The one-folder principle simplifies this: establish a single shared folder structure for active work (current projects, active travel bookings, ongoing correspondence drafts) that both parties use as the source of truth. An EA who knows exactly where to find anything does not need to ask and does not lose time searching.
| Tool category | What the EA needs | Why it matters |
|---|---|---|
| Calendar | Full edit access, not view-only | EA can create, move, and decline meetings without asking the executive to approve each action |
| Delegate access (not shared password) | Auditable, revocable, secure; EA can read and respond under their own login | |
| Task management | Shared visible task board or tracker | Both executive and EA can see priorities and status without a meeting |
| File access | Shared cloud drive with EA-appropriate folder access | EA can find and update any document from anywhere without requesting files each time |
Does a remote EA need admin access to company systems?
No. The EA needs scoped access to the specific systems relevant to their work: calendar (full edit), email (delegated access), travel booking, task management, and shared files. Admin rights are not part of the role and add unnecessary security surface area. The right principle is least-privilege access: the EA should have exactly the permissions they need to do their job, and no more.
What if the EA has not used our specific tools before?
Onboarding to a new tool is rarely a blocker for an experienced EA. Most calendar, email, and project management platforms share enough common patterns that a 30-minute walkthrough of your specific setup is usually enough. The more important factor is that access and permissions are configured correctly before day one. An EA who cannot get into the systems they need on their first day loses time that is hard to recover.
How do we handle tasks that require in-office tools or physical access?
Tasks that genuinely require physical presence (badge readers, on-premises servers, in-office printing) fall outside the remote EA scope and should be assigned to someone on-site. For most executive support tasks, cloud-based equivalents exist and are the right default. If a category of work routinely requires in-office access, that is a scoping conversation to have before the engagement starts, not something to work around after the fact.