What to Hand Off to Your EA on Day One (and What to Wait On)

I had my first EA for eleven days before I realized I was still doing most of the work myself.

Not because she was not capable. She was. I had hired through a managed service, gone through their matching process, and ended up with someone who had five years of experience supporting founders at fast-growing companies.

The problem was me.

I had handed her a vague list. "Take over scheduling." "Help with email." "Handle travel when I have trips." Then I kept doing all of it myself because nothing felt ready to transfer. Nothing had clear enough rules. Nothing was documented.

By day eleven, I had paid for eleven days of support and recovered about three hours of my own time. That math does not work.

I have since figured out what actually makes a new EA hire succeed in the first thirty days. The answer is not about the EA. It is about the sequence.

The two ways founders get this wrong

Most founders make one of two mistakes when they bring on an EA.

The first: they hand off everything at once. "You are now responsible for my calendar, inbox, travel, vendor coordination, and all my follow-ups." That list is not a delegation. It is a stress transfer. The EA has no context for your standards, your priorities, or how you make decisions. She starts guessing. Some of her guesses are wrong. You start correcting her. She feels like a burden instead of support.

The second: they hand off almost nothing. "Can you help me schedule this one call?" And that is it for three weeks. The EA is underutilized. You are paying for capacity you are not using. You tell yourself EA support is not for you.

Both outcomes share the same root cause: no plan for the first thirty days.

A good onboarding sequence is not complicated. But it has to be intentional. You cannot wing it and expect to save time. That is backwards. You spend time upfront to create a system that runs without you.

Week one: the three things to hand off immediately

Do not try to hand off everything in week one. Hand off these three things and do them completely.

Scheduling.

This is the highest-leverage first handoff. Every founder spends more time on scheduling than they realize. The math on how much admin time actually consumes each month is worth reading before you start.

Hand your EA access to your calendar on day one. Then spend ninety minutes documenting your rules. Not your preferences. Your rules.

Example: No calls before 9am. No back-to-back meetings. Always leave thirty minutes after any call over an hour. No meetings on Fridays unless revenue is directly involved. Block Tuesday mornings for deep work.

Write these down explicitly. Your EA cannot read your mind. She can follow clear instructions.

Once she has the rules, let her handle all scheduling. Every request. Zero exceptions for the first two weeks. Even if you think a request is quick and easy, route it to her. The habit of rerouting saves more time than any individual meeting.

Travel logistics.

This is the second handoff for week one. It also surprises founders most. Most underestimate how many hours go into travel research, booking, and coordination. I spent 21 hours in a single month on travel logistics before I had an EA. That is more than half a week of work.

Hand your EA a travel preferences document on day one. Seat preference, hotel chain, loyalty numbers, preferred airports when you have options, how much buffer time you need before important meetings, what you want from the hotel room.

Send her one upcoming trip to plan. Let her do it. Review her itinerary. Give specific feedback: too many connections, wrong hotel category, this airline charges for seat selection so avoid them. Then back off on the next one. By trip three, she should need almost no correction.

The research stack.

Every founder has recurring research tasks they do themselves because they feel like they need to know the details. Competitive pricing checks. Vendor option scans. Event logistics. Conference registrations.

None of these require you to do them.

In week one, pick one recurring research task and hand it off completely. Describe the output you want: format, level of detail, what decisions you need to make from the information. Let her run it. Review the output. Tell her specifically what was useful and what was not.

One task. Fully handed off. That creates the template for everything else.

Weeks two and three: adding inbox triage

Do not add inbox triage in week one.

I know this sounds counterintuitive. Email is usually the biggest time drain. But it is also the most context-dependent. Your EA needs to understand how you communicate before she can screen your communication.

Spend week one observing your inbox together. Give her read access. Ask her to flag the five emails per day she thinks you should respond to personally. Review her choices. Tell her what she got right and what she missed.

Do this for five to seven days. By the end of the first week, she will have developed a working model of your priorities. She will know which senders always get a response. She will know which subject lines signal noise. She will know which threads you care about and which ones are just looping you in for no reason.

Then, in week two, give her draft access. Let her write responses to the routine messages. You review and send. This phase usually lasts five to ten days.

By week three, you should be able to cut your direct involvement to thirty minutes a day. She processes, drafts, and flags. You review the flags and approve the drafts that need your attention.

This sequence takes longer than handing over the inbox on day one. It also actually works.

What to wait on

Three things should not move in the first month.

Vendor relationships with real stakes. If a vendor relationship involves significant contract terms, ongoing negotiation, or anything where your judgment changes the outcome, keep it yourself until month two. Your EA can coordinate logistics and send reminders. She should not be representing your position in a negotiation before she understands how you think.

Client-facing communication. If your EA is going to interface with clients directly, that needs to wait until she has a strong model of your voice and your standards. Rushing client-facing handoffs is how you damage relationships that took years to build.

Anything with no documentation. If you cannot explain a task in writing, you are not ready to hand it off. Undocumented tasks handed off verbally produce inconsistent results. Write the standard before you delegate the work.

These three categories are not permanent holds. They are month-two work.

The context problem

Here is what most founders miss entirely.

A task without context is not a handoff. It is a guess.

When you tell your EA to "handle my follow-ups," you have given her a task. You have not told her what a good follow-up looks like, when to push and when to back off, which relationships are sensitive, or how you want to come across in writing.

She will guess. Some of her guesses will be wrong. You will fix them. You will start to feel like the EA creates more work than she removes.

That is not an EA problem. It is a context problem.

Every task you hand off needs a standard. Not a full manual. A standard. Three to five sentences that explain what good looks like. "For follow-up emails, keep them short, reference what we talked about specifically, and give them an easy out. No more than three follow-ups before you flag it to me."

That is enough. That is the context she needs to make decisions without involving you.

The founders who struggle with EA relationships are usually the ones who hand off tasks and withhold context. They expect the EA to reverse-engineer their standards from the corrections they receive. That works eventually. It takes months instead of weeks.

The specific format that works

Write each handoff as a two-part document.

Part one: the task description. What is being done and how often.

Part two: what good looks like. Three to five bullet points describing output that would not require your attention. Be specific. "A clean itinerary" is not specific. "A PDF with flight info, hotel confirmation number, and ground transport for each leg, organized by day" is specific.

This format sounds simple. Most founders skip it anyway. Then they spend weeks correcting avoidable mistakes and conclude that delegation does not work.

The contrarian take

Everyone talks about delegation as an output problem. You give the EA tasks. She produces output. You are freed.

That is not how it works.

Delegation is an information problem. Your EA is as good as the context you give her. She can be exceptional at her job and still produce mediocre results for you if you never tell her what excellent looks like in your specific situation.

The founders who get the most out of EA support are not the ones who delegate the most tasks. They are the ones who communicate their standards most clearly.

I spent the first month of my first EA relationship frustrated by output that did not meet my standards. When I finally sat down and wrote out what I actually expected, she started producing it within a week. The standards I had been holding in my head, never written down, were not obvious to her. They were just obvious to me.

That is a management failure. Not a hiring failure. And it is correctable.

The thirty-day benchmark

By the end of month one, here is what you should have:

Scheduling: completely off your plate. No exceptions.

Travel: handed off with a working preferences doc. You receive itineraries and approve them.

Inbox: down to thirty minutes of daily review from whatever it was before.

At least one recurring research task: fully running without you.

One area of client or vendor coordination: in progress.

That is not the full picture of what an EA can do. That is the foundation. The compounding starts in month two when all of those systems run without your attention and you start handing off the next layer.

Understanding what this kind of support actually costs across different service models is worth doing before you start. The pricing range is wide and what you get at each tier varies significantly.

The first thirty days will be slower than you expect. They will also determine whether your EA becomes one of the best decisions you made this year or a frustrating experiment you eventually give up on.

Get the sequence right and the savings compound. Get it wrong and you will spend several months wondering why you are still busy.

If you are ready to find an EA and get the onboarding sequence right from day one, apply for access and we will match you with someone who has been through this transition before.