Remote Executive Assistant

An administrative assistant supports the work. An executive assistant supports a person. The tasks overlap, and the difference is authority and judgment. An administrative assistant handles data entry, document management, scheduling, filing, and the recurring operational work of an office. An executive assistant manages one or two people's time and attention. Guarding the calendar, triaging the inbox, and preparing them for meetings. Following up on commitments, and deciding what does and does not reach them. That second job requires context and trust rather than instructions. It takes longer to become useful, and it is worth more once it does. Firms that need volume should hire the first. Principals drowning in their own calendar need the second. Hiring the first and expecting the second is the most common disappointment in this category. It is a briefing problem rather than a talent problem.

The judgment calls. On day one an EA schedules what you ask them to schedule and drafts what you ask them to draft. By month three, in a working arrangement, that changes. They are declining meetings on your behalf and protecting blocks of time without being asked. They are drafting responses that go out with a minor edit, and telling you what needs your attention this week. That progression is the whole value, and it does not happen automatically. It requires you to explain the reasoning behind corrections rather than just the correction. Firms that treat an EA as a task queue never get past day one, no matter how good the person is. Explaining why a correction was a correction is the whole investment, and it is the part most founders skip.

Calendar, email, and whatever systems the role touches, granted through your own IT rather than shared informally. The practical setup is delegated calendar access rather than a shared password. Delegated or shared mailbox access rather than your credentials. A password manager for anything else, and multi-factor authentication throughout. Travel and expense systems come next, then whatever project or CRM tools the role needs. Financial systems get read-only access unless the role genuinely requires more than that, and most assistant roles do not. Handling sensitive communication is part of the job description, and the professionals we place hold to strict confidentiality. That is not a substitute for configuring access properly. The rule is simple. Grant the access the job needs, review it when the role changes, and remove it the day an engagement ends.

In your voice, within limits you set in writing. An EA who cannot speak on your behalf is a scheduling tool. One who can, without agreed boundaries, is a risk. So the boundaries get written down early. Which people they correspond with directly. What they can commit to, what always comes to you first, and how they sign. Most firms start with scheduling and logistics, then widen it as trust builds. They work your hours in your time zone, so a client email at nine in the morning is answered at nine, not overnight. Everyone they deal with should know who they are and what their role is. An assistant nobody has been introduced to is one who cannot help, because every request they make has to be explained first.

By handing over outcomes, not steps. The common failure is delegating a task so precisely that describing it takes longer than doing it, then concluding that delegation does not work. What travels well is a defined outcome, the constraints around it, and an example of a good result. What does not travel is anything held only in your head, which is most of it in a firm run by its founder. The practical method is to narrate the first few decisions rather than just make them, and to write down the rules as they surface. It is a few weeks of extra effort that buys back years of them. Almost nobody makes that trade, because the cost comes first and the return comes later. Pick the outcome you would notice if it went wrong, and hand that one over first.