Home/Blog/Modern Work & Data
Modern Work & Data · 12 min read

The executive assistant operating system: how to run an executive's time, inbox, meetings and travel

The short answer

An executive assistant operating system is a small set of agreements, rules, logs and rhythms: a written working agreement with decision rights, a calendar audit and meeting defaults, request triage against response standards, a meeting lifecycle, board and travel timetables, a call-back rule for payments, AI rules, a desk manual for cover, and weekly impact measures.

Want the tools, not just the method? The The Executive Assistant Operating System kit turns this guide into ready-to-use templates, spreadsheets and printables, with an instant download.

Key takeaways
  • Write decision rights in four levels: act, act and tell, draft for approval, escalate.
  • Audit one typical week by meeting type before changing any rule; count matters as much as hours.
  • Every request gets a priority and a clock; track MET and LATE, not effort.
  • Every payment or bank-detail change is confirmed by calling a known number.
  • If nobody else can run your desk from the manual, the system is not finished.

What is an executive assistant operating system?

It is the way an executive office runs when it does not depend on one person's memory. It has four parts: agreements (a working agreement and decision rights, the call-back rule), rules (meeting defaults, response standards, access rules, AI rules), logs (requests, actions, board papers, travel, decisions) and rhythms (a daily check-in, Monday planning and a Friday review).

The test is simple: if the assistant is off sick tomorrow, can someone else run a normal day from the desk manual and the logs? If not, the office is running on memory, and memory does not scale to two executives, a board and a travel calendar.

How an executive spends time matters. Research using time-use diaries from 1,114 chief executives in six countries found distinct patterns in how they spend their hours, linked to differences in firm productivity. The assistant who shapes that time is doing strategic work.

  • Agree: working agreement and decision rights
  • Audit: one typical week of meetings
  • Set rules: defaults, buffers, focus blocks
  • Triage: priorities and response clocks
  • Run meetings, board papers and travel to a timetable
  • Protect: call-back rule, delegated access, AI rules
  • Hand over and measure

How should an EA agree decision rights with an executive?

Turn 'just handle it' into four levels. Level 1, act: do it with no need to tell (accepting internal meetings within the rules). Level 2, act and tell: do it and mention it in the daily summary (moving an internal meeting once). Level 3, draft for approval (external replies in the executive's name). Level 4, escalate (money, protected time, media).

Write each recurring decision in a matrix with a limit and a review date 90 days out. Money is always level 4 for the assistant. Levels move down as trust grows, and recording the date of each move is a quiet measure of the partnership.

Agree the rest in the same 45-minute meeting: which channel means what, a daily check-in of 10 to 15 minutes, a 30-minute Monday planning slot, the top three priorities, protected time and what counts as urgent out of hours. Ireland, for example, has had a Code of Practice on the Right to Disconnect since 1 April 2021, and Australia has a legal right to disconnect; check your own country.

How do you reduce an executive's meetings without upsetting people?

Audit one typical week by meeting type and make one of six decisions for each type: keep, shorten, replace with a written update, batch into office hours, delegate or drop. Keep every board, customer and recruitment meeting untouched at first; it makes the rest easy to accept.

Reduce the number of meetings, not only their length. In two studies of 676 and 304 employees, the number of meetings was more often related to well-being than hours in meetings, and perceived meeting effectiveness was the strongest predictor. Separate research on attention residue shows that switching away from an unfinished task lowers performance on the next one.

Here is the worked example from the kit, a fictional 200-person medtech company in Galway. Expect some drift: the plan was 18.5 hours a week, the measured result at week 12 was 21.0, because two status meetings crept back.

MeasureBeforePlannedWeek 12
Meetings per week291820
Meeting hours per week28.518.521
Focus hours protected288
Executive hours returned (estimate)08.25

How should an EA triage the inbox and requests?

Give the executive less email, not a better inbox. A short VIP list, five folders (action today, decide, read, waiting, reference), agreed reply types sent 'on behalf of', and a daily summary of decisions needed, what was answered and what is waiting.

Give every request a priority and a clock: P1 today (4 hours), P2 within 48 hours, P3 this week. Log the time received and the time answered, and flag MET, DUE SOON or LATE. In the worked example the median response to P1 and P2 requests fell from 9.5 hours to 2.5 over 12 weeks.

On how often to check email, the evidence is cautious. In a two-week field experiment, checking three times a day lowered daily stress compared with unlimited checking. A separate field study found more time on email went with lower perceived productivity and higher stress, but batching did not reduce stress. The best-supported point is less email time for the executive.

How do you support two or more executives fairly?

Write the rules down and make the workload visible. One working agreement per executive plus a shared page of rules; a priority rule everyone knows (board, customers and regulators first, then deadlines, then first come, first served); fixed check-in slots; and one request log with a column for which executive each request serves.

When two urgent requests collide, tell both executives within the hour and let the agreed decision-maker choose. Silent choices create resentment. Review the split monthly and renegotiate if one executive takes more than 60% of requests for a month. US labour statistics note that many executive assistants already support more than one manager.

What is the call-back rule, and why do assistants need it?

Any request to pay, or to change bank details, is confirmed by calling a known number from the desk manual, contract or finance system, never a number in the request, whoever seems to ask. The assistant never approves payments.

The FBI's Internet Crime Complaint Center recorded 24,768 business email compromise complaints in 2025 with reported losses of about USD 3.05 billion. Ireland's National Cyber Security Centre advises a phone call to a known contact for any bank-detail change and warns that most funds are unrecoverable if not flagged within hours. The FBI has also warned of AI-generated voice messages impersonating senior people.

Red flags: urgency, secrecy, a new account, a change of channel, gift cards or crypto, and tone or timing unlike the real person. Any one is enough to stop and call.

Measure where you are

Reading helps; measuring tells you what to work on. These AI-graded assessments on AssessAll pair with this topic:

What should an EA check before an executive travels?

One itinerary with local and home times, confirmations and contacts, shared with the traveller, cover and the emergency contact. Then a duty-of-care check: official travel advice from the traveller's own government, entry rules for the traveller's nationality, emergency contacts, insurance and assistance, and a check-in plan.

Check twice: at booking and again within seven days of departure, because advice changes faster than itineraries. ISO 31030:2021 frames travel risk as an organisational process, so if advice rises to 'avoid non-essential travel', the decision goes to the executive and whoever owns travel risk.

Schedule for the body clock: the CDC says it adjusts by about 1.5 hours a day after westward travel and about 1 hour a day after eastward travel. Avoid critical decisions on the first morning after a long eastward flight.

How should EAs use AI assistants safely?

Three rules. Use your organisation's approved tool only; the UK NCSC recommends not including sensitive information in queries to public large language models. Keep no-go material out: board papers, people and health data, legal and deal material, passwords and bank details. Verify every name, number, date and action before anything is sent.

The research supports both enthusiasm and care. A study of 5,179 support agents found a 14% average productivity gain with an AI assistant, and 34% for novices. A field experiment with consultants found AI helped on suitable tasks but made people 19 percentage points less likely to reach a correct answer on a task outside its capability.

What are the most common mistakes executive assistants make with these systems?

Most failures come from good intentions applied without a written rule. The fixes are simple, and each one is a habit rather than a tool.

  • Treating 'just handle it' as a mandate: turn it into four levels of decision rights and review them at 30 days.
  • Fixing the calendar without fixing the priorities: write the three priorities at the top of the audit and colour meetings by priority.
  • Choosing between two executives in silence: tell both within the hour and let the agreed person decide.
  • Answering everything yourself: keep the handling levels honest; too few escalations means you may be deciding things that are not yours.
  • Checking travel advice once, at booking: re-check within seven days of departure.
  • Trusting a familiar voice or address: apply the call-back rule to every payment and bank-detail change.
  • Sending an AI summary unread: check every name, number, date and action against your own notes.
  • Overstating impact: show the trend, the low case first and what drifted back; call estimates estimates.

How can an EA measure and show their impact?

Track a handful of numbers every Friday in two minutes: executive meeting hours, number of meetings, focus hours, median response hours, agendas sent 24 hours ahead, a 1-5 meeting pulse, and executive hours returned (meeting hours saved, less the share that becomes other work, plus inbox time saved).

Put a value on it honestly with four cases and the low case first. In the worked example, with set-up of EUR 4,386 and every input the assistant's own estimate, the low case (1 hour a week returned) does not pay back in year one; the expected case (5 hours) breaks even in 7.7 weeks. Call estimates estimates, and say what drifted back.

Bodhih Pro Kit

Run the whole executive office from one kit

The Executive Assistant Operating System gives you the master workbook, five fillable forms, nine Word templates including a desk manual and a 40-message library, the call-back rule and a step-by-step e-book. Not affiliated with or endorsed by ISO, any regulator or any software vendor named; tool names are examples only.

Common questions

Questions people ask next

What does an executive assistant operating system include?

A working agreement with decision rights, calendar and inbox rules, a scheduling triage, response standards, a meeting lifecycle, board and travel processes, confidentiality and fraud controls, AI rules, a desk manual and impact measures. This kit gives you all of them as 26 files plus a 12-chapter e-book.

How do I set up a working agreement with a new executive?

Book 45 minutes in week one, use the working agreement form to cover channels, check-ins, decision rights in four levels, top priorities, protected time and personal admin, then review it at 30 days. Chapter 1 and the worked example show a filled version.

How do I reduce my executive's meetings?

Audit one typical week by meeting type and decide keep, shorten, replace with a written update, batch into office hours, delegate or drop for each. In the worked example the audit planned a cut from 28.5 to 18.5 hours a week and measured 21 at week 12.

How do I support two or more executives fairly?

Use one working agreement per executive plus shared rules, fixed check-ins, one request log with a 'For executive' column, and a clash rule: when two urgent requests collide, tell both within the hour and let the agreed person decide. The protocol card has seven rules.

Can I use AI tools as an executive assistant?

Yes, with three rules: your organisation's approved tool only, no board, people, health, legal or deal material, and every name, number, date and action checked before anything is sent. The prompt pack has 25 prompts with a human-review rule each.

Is this kit suitable for the UK, Ireland, the US, Canada, Australia and New Zealand?

Yes. The method works in any market. A dated crosswalk maps privacy and breach rules in all six markets, plus payment fraud, travel advice, right to disconnect and board minutes rules where they differ, to official sources. Laws change, so check the sources and your adviser.

How long does it take to set up?

The 15-minute quick start gets you scoring and booked in. The full system runs over 12 weeks, about 60 hours of your time in the worked example, with reminders in the calendar file and tasks in the CSV board.

Does it need special software?

No. It is tool-agnostic. The workbooks open in Excel, Google Sheets or LibreOffice, the forms in any PDF reader, the templates in Word or Google Docs. A dated Tool notes sheet names example tools with no affiliation.