Onboard an executive assistant in four stages: access and context in week one, diary ownership in week two, inbox triage in week three, and the first automated process in week four.
The difference between an assistant who is useful in a month and one who is still asking permission in a quarter is almost entirely down to the first thirty days. The pattern below is the one that works most consistently.
Diary comes first because it is bounded and the feedback loop is immediate. Agree the rules once: meeting lengths, buffers, protected focus blocks, who gets accepted automatically and who gets a holding reply. Then stop accepting invitations yourself.
With the diary settled, move to triage and drafted replies. Expect to correct tone in the first week. That correction is the training, so do it properly rather than rewriting silently.
By now your assistant has seen enough of the recurring admin to name a candidate for automation. Pick one, map it, build it with a human checkpoint, and document it. One finished process beats four half-built ones.
Agree before you start what success looks like. Hours returned each week is the most honest measure, and it is easy to check against the fortnight you tracked before hiring.
Most onboarding failures are not about capability. They are about a vague first fortnight, where the assistant is waiting for instruction and the leader is too busy to give it. A written plan removes that entirely.
Start with the work that is high frequency and low consequence. It builds context quickly and the cost of a mistake is small. Scheduling, expenses, meeting notes and routine supplier email all qualify.
Resist starting with the thing that annoys you most. That task is usually annoying precisely because it needs your context, and handing it over in week one produces a bad experience for everyone.
The leaders who get the most from an assistant do three unglamorous things: they hold a fifteen minute daily check-in for the first two weeks, they write decisions down rather than explaining them twice, and they give corrective feedback within a day rather than saving it.
After the first month, the check-in usually drops to twice a week and then weekly. The written record is what makes that reduction safe.
Onboarding advice usually stops at day 30, which is a shame, because month two is where the arrangement either compounds or plateaus. The basics are covered by then, the assistant knows how you work, and the question becomes whether they are given room to change the work rather than simply absorb it.
Practically, that means protecting time for build work and being clear that it is expected. If every hour is consumed by the reactive queue, no process will ever be mapped and you will have hired capacity rather than leverage. Half a day a week is usually enough.
It also means widening access carefully. The processes with the most automation potential tend to sit in finance, reporting and client operations, all of which require permissions that felt premature in week one. Reviewing access at day 30 with a least privilege mindset unlocks the next tranche of work without creating a security problem.
The last piece is visibility. A short written summary each Friday covering what moved, what slipped and what should be automated next keeps the relationship honest and gives you something to review in ten minutes rather than a meeting.
How long before an executive assistant is fully embedded? Most are handling the diary within two weeks and the inbox within a month, with the first automated process delivered by week four.
What should I prepare before day one? System access, a recorded walkthrough of a typical week, your key contacts, and the three tasks you most want to hand over.
How much of my time does onboarding take? Plan for around two to three hours in week one, then short daily check-ins that taper off as the rules settle.
More insights | Alvara Partners