The Executive Support Checklist: Every Recurring Task Your Business Runs On

Key takeaways

Recurring work goes first. It is the part of the week that never finishes, so it is the part that has to leave your plate.
A task is only delegable when it has four things written down: a trigger, a standard, what done looks like, and when to escalate.
The checklist is what makes a handover survive. If your operator changes, the next one picks up the same list, not a blank page.

Ask a founder what they would hand over if they had the perfect assistant tomorrow and you get a vague answer. "The admin." "The inbox stuff." "All the scheduling." Ask them to write down every recurring task in the business, how often it happens and who does it today, and something different happens. The list is long. It is specific. And almost none of it needs them.

That list has a name at Atlas. We call it the Executive Support Checklist, and building it is the first real piece of work we do with every client.

Why Recurring Work Goes First

Everything that crosses your desk is either recurring or a project. Projects finish. Recurring work does not, which is why it is the bucket that quietly eats the week. You can push through a project in a sprint and be done. There is no sprint that finishes next Monday's inbox.

Recurring work has three other properties that make it the right place to start.

It is predictable. You know when it happens and roughly what it involves, which means it can be written down once and done the same way every time.
It is where the mistakes hide. The invoice nobody chased. The travel booked for the wrong day. The follow-up that went out two weeks late. Almost every "dropped ball" story is a recurring task with no owner.
It compounds. Hand over a project and you save its hours once. Hand over a weekly task and you save its hours every week for as long as the business exists.

Most founders do not have a delegation problem. They have a documentation problem that looks like one. The checklist is the documentation.

Most founders do not have a delegation problem. They have a documentation problem that looks like one.

What Goes on the Checklist

The simplest way to build it is by cadence, then by area. Here is the skeleton we start from. Yours will have rows we have never heard of, which is the point of doing it properly.

Daily

Inbox and comms. Triage to zero, replies drafted in your voice, anything that needs you flagged with a one-line summary.
Calendar and meetings. The next-day brief sent the evening before, agendas checked, prep attached.
Travel and logistics. Confirmations for anything in the next 48 hours.
Money and admin. Receipts captured as they arrive.
Team and operations. Slack and project-tool sweep, blockers surfaced to you in one place.
Home and life. Household messages answered, bookings made.

Weekly

Inbox and comms. Follow-ups chased, newsletters filed, the "waiting on" list reviewed.
Calendar and meetings. The ideal week protected, next week built, one-to-ones confirmed.
Travel and logistics. Upcoming trips assembled end to end.
Money and admin. Invoices sent and chased on day 7 and day 14, expenses reconciled.
Team and operations. The weekly report pulled, CRM hygiene, vendor check-ins.
Home and life. Family calendar merged, appointments booked.

Monthly

Inbox and comms. Contacts and lists cleaned.
Calendar and meetings. Recurring meetings reviewed, the calendar audited against the ideal week.
Travel and logistics. Loyalty points and travel preferences updated.
Money and admin. Bookkeeper handoff, subscriptions reviewed.
Team and operations. New hires onboarded from the written sequence, SOPs updated, KPIs assembled.
Home and life. Bills, renewals, gifts and dates.

Quarterly

Inbox and comms. Rules and filters rebuilt around what changed.
Calendar and meetings. Offsites, board or investor meetings planned.
Travel and logistics. The year's travel mapped.
Money and admin. Budget against actuals, insurance and documents.
Team and operations. Hiring coordination, the tool stack reviewed.
Home and life. Holidays booked, school and activity calendars loaded.

Two rules while you fill it in.

First, pull from evidence, not memory. Your sent folder, your calendar and your bank statement for the last thirty days will tell you what actually recurs. Memory tells you what you resent, which is a different list.

Second, do not filter yet. "Only I can do that" is the single biggest reason checklists come out short. Write it down anyway and mark it as yours. You will revisit that mark later, and about half of them change.

How to Write a Task So Someone Else Can Own It

A line on a list is not a delegable task. "Chase invoices" is a wish. A task someone else can own has four parts.

Trigger. When does it start? An invoice is seven days past its due date.
Standard. How is it done, in enough detail to be done your way? Email the billing contact from the shared inbox using the day-7 template, friendly tone, copy of the invoice attached.
Done looks like. How do you both know it is finished? Reply received or payment confirmed, logged in the tracker, next step dated.
Escalate when. Where is the line that brings it back to you? No reply by day 14: phone call. No reply by day 21: flag to me with the account history, I decide.

Four lines. Once a task is written like this it can be handed to a new operator, an agent, or a cover person during leave, and it will be done the same way. Until it is written like this it lives in your head, and anything that lives in your head is yours forever.

Note. you do not need to write all of them yourself. In the first two weeks, your operator takes the first pass at every task on the checklist and you correct it. Correcting is ten times faster than authoring, and it is how your preferences get captured without you sitting down to write a manual.

A Filled Example

A founder running a seven-figure marketing agency with a team of eleven came to us with the usual answer: "I need help with the admin." Her checklist, built from thirty days of calendar and sent mail, came to forty-one recurring tasks. Here is a slice of it.

Task	Cadence	Owner before	Owner after
Inbox triage and drafted replies	Daily	Founder, 90 min	Operator, founder reviews flags in 10 min
Client weekly status emails (6 clients)	Weekly	Founder, Friday afternoon	Operator drafts from the project tool, founder approves
Proposal follow-ups	Weekly	Nobody, reliably	Operator, day 3 and day 10 templates
Contractor invoices approved and paid	Weekly	Founder	Operator prepares, founder approves in one batch
New-client onboarding sequence	Per client	Founder improvises each time	Operator runs the written sequence
Monday metrics report	Weekly	Founder, 2 hours Sunday night	Operator, automated pull with a human read
Travel for the monthly client visit	Monthly	Founder	Operator, end to end
Kids' activity and school calendar	Weekly	Founder, evenings	Operator, merged into the family calendar

Of the forty-one tasks, four stayed with her. Approving money above a threshold. The first conversation with a new client. Hiring decisions. The weekly team meeting, which she now walks into with an agenda she did not write.

Her number on the growth question went from eight percent to a little over thirty within two months. Not because she worked harder. Because thirty-seven recurring tasks stopped being hers.

How It Survives an Operator Change

This is the part most people only appreciate after it has gone wrong once.

When the checklist lives in a document rather than a person, the person can change and the system does not. Your operator goes on leave: cover picks up the same list, with the same triggers and standards, and your week looks the same. The fit is not right and you are rematched: the next operator starts from forty-one written tasks, not from "so, tell me how you like things done."

At Atlas the checklist lives inside your Executive Atlas, the operating manual your operator works from, and it is reviewed with your account manager every month. New tasks get added as they appear. Tasks that have been automated get marked as such, with a note on who checks the output. Nothing goes back into your head.

What Happens to the Projects

Projects do not go on the checklist, but they do not disappear either. Once the recurring work is owned, a strange thing happens: you have capacity for projects, and so does your operator.

The pattern that works is the one from the loop. You solve the hard problem. You explain the approach once. Your operator writes it down, runs the first version, and if it turns out to recur, it joins the checklist. If it does not, it is finished and nobody has to think about it again.

That is the handoff founders are usually missing. Not the solving. The part where it leaves your plate and stays gone.

Build Yours in Forty Minutes

Open your calendar and your sent folder for the last thirty days.
Write down every task that happened more than once. Area, cadence, rough time, who did it.
Do not filter. Mark the ones you believe are yours, but write them down.
Count them. The number is usually between thirty and sixty.
Pick the five that happen most often and write each one to the four-part standard: trigger, standard, done, escalate.

That is the whole first step. If you would rather do it with someone who has done it a few hundred times, the Energy Audit is where it happens, and it is the first week of working with Atlas.

Frequently Asked Questions

How Long Does It Take to Build the Checklist?

The first complete pass takes about forty minutes if you do it from your calendar and sent folder rather than from memory. Writing each task to the four-part standard takes longer, and that is work your operator does with you in the first two weeks, not work you do alone.

What About the Things That Only I Can Do?

Put them on the list anyway, marked as yours. Half of them turn out to be delegable once they are written down. The other half are your actual job, and seeing them as a short list is clarifying.

Is This Different From a Job Description?

A job description describes a person. The checklist describes the work. It outlives any individual, which is the point: when your operator is on leave or the fit changes, the next person inherits the list, not a job title.

Do Atlas Operators Use This Exact Format?

Yes. The Executive Support Checklist is built during the Energy Audit and the first two weeks of handover, lives in your Executive Atlas, and is reviewed with your account manager every month.

Atlas places and trains executive operators, and coaches the founders who work with them. See what you are actually buying or book a call.

The Executive Support Checklist: Every Recurring Task Your Business Runs On

Why Recurring Work Goes First