The first month is a transfer of keys. After that, the failure mode changes. Founders who handed off the inbox still drown, because nothing in the week tells the assistant what matters now. How to work with an executive assistant is the rhythm you keep once access is no longer the project: a weekly sync, a priorities doc, and decision rights both of you can open.
If you are still inside month one, start with the first 30 days with a virtual EA. If you are still choosing what to hand off, start with how to delegate to an executive assistant. This post begins the week those are finished. Two meetings already arrive briefed. The tempting move is to “just ping them” for everything else. That move hands the seat back to you, with an audience.
The stretch between “they have the logins” and “they run the week” is a craft, and the people who train EAs already teach it as one.
The machinery below is what we put in place with founders. A weekly sync. A priorities doc. Decision rights. Keep those three current. They are how the week stays visible when Slack gets loud.
The weekly sync
Put 25 minutes on the calendar. Same time, every week. Treat it like a customer call. Moving it is fine. Canceling it is how the doc dies, usually with a note that says you were “slammed,” which is the condition the sync exists to shrink.
The agenda stays fixed.
- What moved, in a few sentences they send ahead of the call. You read it before you join.
- What is stuck and needs a decision from you. This is the only block that should take real minutes.
- Next week’s priorities, in order. You set the order. They tell you what that order will break.
- One expansion and one kill. Something they should start owning, and something both of you will stop pretending is alive.
A sync that retells the whole company means the doc is stale, or you are using the meeting as a diary. Cut it back to the stuck items. A good one ends with a short list and no new folklore about how busy everyone is.
Arrive having read the note. If you show up cold and make them perform the week out loud, you have built a status meeting. They will start writing for the performance. The work will get a little worse, and the meeting will get a little longer, every month.
The priorities doc
One page. Three lists. If it needs a wiki, it is already too big to run a week.
- This week. The few outcomes that matter, in order. “Close the vendor renewal” is an outcome. “Emails” is a mood.
- Waiting on. A name, what they owe, and the date you will nudge. Follow-ups live here or they die in a sent folder.
- Not now. Work you can both see and will not do. This list is what stops a sharp assistant from being helpful on the wrong project. Helpful and wrong is how founders end up with a beautiful tracker for a launch they already killed.
They update the facts before the sync. You update the order in the doc, not in a side thread that only one of you will find on Friday. When a Slack message outranks the page, the message is the real system and the page is decoration. The first time it happens, say so, then put the message on the page or kill it.
A doc that is two weeks old is a souvenir. Rebuild it in the sync. Skip the apology. Apologies do not move the waiting-on list, and your EA has already noticed the gap.
How to work with an executive assistant when a decision shows up
Decision rights feel stiff the first time you write them. They are also the reason you stop living in the weeds. Three buckets, with examples from your actual work, kept where either of you can open them during the sync.
They decide, and they tell you. Rescheduling inside rules you already set. Declining a meeting with no purpose. Nudging a vendor on day three. Filing the FYI. Booking travel to a standard you have written once. They do not need a yes. They need you to read the note and reply only when the call was wrong. Silence, in this bucket, means the call stands.
They draft, you send. Anything a customer or an investor will treat as a commitment. Pricing. A date you cannot slip. A tone that is still yours. The draft should arrive with the assumption on the first line: “I told them Thursday. Change it if that is wrong.” You edit the decision. You leave the comma alone unless the comma changes the promise.
They stop and ask. Money above a number you pick and write down. Legal. Hiring. A surprise that would embarrass you if it surfaced in the meeting. A conflict between you and a cofounder. Stopping here is not a lack of initiative. It is the fence. Assistants who climb the fence “to be proactive” create the cleanup you hired them to prevent.
When you override a bucket, write the override into the doc the same day. An unwritten override becomes a secret rule. Secret rules teach good assistants to get cautious. Cautious assistants return the work one ping at a time, and then you conclude they “lack ownership.” They lack a stable rule. Give them one.
Put the rhythm where you can both see it. A dedicated bilingual EA on your hours can run the week when the sync, the doc, and the decision rights are real. Meet your assistant →
The daily note
The sync is weekly. The work is not. A short written note covers the days in between. Five lines. Not a call, unless something in “needs you” is actually a conversation.
- Done
- Blocked
- Needs you, one to three items, each with a recommendation
- Tomorrow
- Anything that changed the priorities doc
You answer “needs you.” You can ignore “done.” Answering every line rebuilds the inbox with extra steps. Answering none of them forces guesses, and then the review becomes a trial of the guesses. Pick the middle and stay there for a month before you invent a new format.
Same-day hours matter for this note. An assistant on your clock can take a decision at 2 p.m. and use it at 2:10. A reply that lands the next morning builds a queue of maybes. Teleforce seats work U.S. hours so the 2 p.m. version is available. The rhythm still fails if you treat the note as optional reading.
When the rhythm slips
It will slip. You will rewrite a draft that was theirs to send. They will ask about a call that sits in “they decide.” A launch will stale the doc. Repair the artifact. A talk about ownership, with no edit to the page, expires by Thursday. Pep talks are cheap. A rewritten bucket is the management.
Once a month, spend the last ten minutes of the sync on the buckets alone. What moves from “ask” to “decide” because they kept getting it right? What moves the other way because a call surprised you? That is the performance review a founder actually needs. Keep a formal review if you want the ritual. The buckets are the job description, and they should change on purpose.
A few honest boundaries. A principal who wants a mind reader, and will not keep a page current, will be disappointed by every EA on earth. Physical work stays physical: a front desk, a package, a room. Five hours of chores a week is not a full-time rhythm. Kill the meeting that has no decision before you staff a person to sit in it. The seat amplifies the system you already have. A messy system, run faithfully, is still a mess. That part is on you.
What to bring to Teleforce
We match one dedicated EA. English and Spanish. LatAm. Your U.S. hours. Employed by us. Your Partnership Manager stays on the engagement for oversight and for working habits like this one, if you do not have them yet. The rate is $3,000 a month on a 3-month commitment or $2,700 a month on a 12-month commitment. See Terms.
Onboarding will ask for priorities and a first pass at the decision line. We cannot keep the doc current for you after that. The page is the shared job. An assistant who maintains it alone is guessing at your order, which puts you back in the ping loop this whole rhythm is meant to end.
See pricing or bring us the week. How to work with an executive assistant gets quiet once the three artifacts exist. Before that, it is a series of pings, and pings are the bottleneck wearing a new tool.
Frequently asked questions
How often should I meet with my executive assistant?
A 25-minute weekly sync, same time, with a note they send ahead. Add a short daily written update: done, blocked, needs you, tomorrow. The daily piece does not need to be a call. Canceling the weekly sync is how the priorities doc goes stale.
What goes in an EA priorities doc?
One page with three lists: this week, in order; waiting on, with a name and a nudge date; and not now, so helpful work does not creep onto the wrong project. They update the facts before the sync. You update the order in the doc, not in a side thread.
Which decisions can an executive assistant make alone?
The ones you have written down. Typical 'they decide' items: rescheduling inside your rules, declining a meeting with no purpose, nudging a vendor on a set day, booking travel to a standard. Commitments a customer or investor will rely on, money above your line, legal, and hiring stay with you.
See what a dedicated bilingual EA costs
Teleforce matches U.S. executives with a dedicated bilingual executive assistant — English and Spanish, on your hours, employed on a Fortune 500-grade support backbone. Tell us how you work and we'll come back with a fit.
Get matchedTeleforce places dedicated bilingual (English/Spanish) executive assistants for U.S. leaders — one person on your hours, on a Fortune 500-grade support backbone. Get matched →