Five lessons, about an hour. The inbox is where you prove you are useful. The calendar is where you prove you can be trusted — because a calendar mistake is public, it involves other people, and it cannot be quietly undone.
Adaeze has taken on two remote clients — one in London, one in New York. In your second week you book a call for "2pm" and someone joins an empty room. It is the most common way a new assistant loses a client, and it is worth understanding precisely why, because the reason is not carelessness.
Most people learn the difference between two cities once and treat it as permanent. Lagos is an hour ahead of London. Lagos is six hours ahead of New York. Then they do the sum correctly for four months and get it wrong in April without ever finding out why.
Here is what is actually happening. Nigeria does not observe daylight saving. Britain and America both do — and they do not switch on the same days.
So the gap between Lagos and London is one hour in winter and zero in summer — for several months of the year, they are simply the same time. And the gap to New York is six hours in winter, five in summer.
Worse, look at those switching dates again. America moves in the second week of March; Britain in the last. For about two weeks every spring, and about one week every autumn, every relationship between all three cities is different from the rest of the year.
Nobody memorises that table, and you should not try. The point of the table is to convince you never to do this arithmetic in your head again. Those two highlighted rows are the weeks when a confident assistant, doing the sum she has done correctly a hundred times, is wrong.
"Hi Mark, confirming our call for 2pm on 05/04. Speak then."
Two zones unstated, a date that reads as 5 April or 4 May depending on the reader, and no invitation. Three separate ways for this to fail, and the assistant will believe she confirmed it.
"Hi Mark, confirming our call for Thursday 4 September, 2pm London / 2pm Lagos — we're on the same time until late October. Invitation is in your diary with the link.
Adaeze"
Day and month in words, both zones, the reason they match, and an invitation carrying the real moment. The parenthetical about October also quietly tells Mark that someone here is paying attention.
It will happen once. When it does: message within minutes, take the blame without elaborating, offer two specific new slots, and do not explain the mechanics of your error — nobody wants a lecture on daylight saving from the person who just wasted their morning. "Mark, that was my mistake on the time and I'm sorry you waited. I can do 3pm today or 10am tomorrow, both your time — which is less annoying?" Clients forgive the error. What they do not forgive is a defensive explanation.
Find today's date. Work out the current gap between your city and London, and between your city and New York. Then work out what it will be on 1 December and on 1 July. Write all six down. If any two of them are the same, check again — you have probably made the exact mistake this lesson is about.
Adaeze told you in module 1 that eleven clients a week is as many as she can hold without going hollow. Last month she saw fourteen. Nobody forced her — her booking link was simply open, and people booked.
A calendar with nothing defended in it fills up with other people's priorities.
This is the lesson where you stop being someone who schedules things and start being someone who protects a person's capacity. It is also, quietly, the lesson that keeps your client in business long enough to keep paying you.
The order matters and almost everybody gets it backwards. Do not start with an empty week and add meetings. Start by blocking everything that is not a meeting, then offer whatever is left.
What gets blocked before anything else:
Two bookable windows on a full working day. That will feel wrong to you the first time you build one — it looks like you are throwing away money. You are not. You are making eleven sessions sustainable instead of fourteen sessions followed by a month of exhaustion and two cancelled weeks.
Every booking tool has dozens of settings and four that change anything:
Three calls at 9am, 1pm and 4pm do not cost three hours. They cost the day — nothing substantial fits into the pieces between them, so the whole day becomes waiting.
So cluster them. Calls on Tuesday and Thursday afternoons; Monday untouched. Then when someone asks for "a quick fifteen minutes on Monday", you have somewhere to put it that is not Monday, and a reason.
You will need a way to say no to a booking without saying no to a person. This works, and you can use it forever: "She's fully booked on Monday — I can do Tuesday at 11 or Thursday at 2, both of which give her time to prepare properly for you." You have declined, offered two specific alternatives, and framed the refusal as being in their interest. Nobody argues with it.
Set up a free booking link for yourself. Configure all four settings deliberately, then book a slot in it from another device and see what your invitee actually receives — the confirmation, the reminder, the wording. Most assistants have never seen their own booking flow from the outside, and it is where the embarrassing errors live.
Adaeze messages at 7:50am. Her son is ill and she cannot work until midday. Four appointments need to move.
What almost every new assistant does now: opens the first client's message and starts typing. Twenty minutes later there are four conversations running, two people have accepted slots that conflict with each other, one has replied asking why, and the week is worse than when it started.
Solve the entire chain on paper before you send a single message.
Move Chinelo from 10am to 3pm, and 3pm belonged to Bola. Bola goes to Thursday, and Thursday's slot was the only one a new enquiry could have taken. Every move displaces something, and the displacement is invisible until you have mapped it.
So: paper first. Write the four appointments, the constraints on each, and the empty slots you actually have this week. Then find the arrangement that moves the fewest people. That is the objective — not the neatest week, not the fullest week. Fewest people disturbed.
Now, and only now, do you write. One message per person, sent in one batch, each with two concrete alternatives already checked against every other move.
"Hi Chinelo, I'm so so sorry but Adaeze has had a family emergency this morning and needs to cancel. She feels terrible about it. Could you possibly let me know when you might be free this week or next? Sorry again for the inconvenience!!"
Three apologies, a private detail that was not yours to share, and it hands Chinelo the work of finding a slot. She now has a task, and she is being asked to feel sympathetic while doing it.
"Hi Chinelo,
I'm sorry — Adaeze has to move this morning's session. I've held two slots for you: today at 3pm, or Thursday at 10am, whichever is easier.
Just reply with one and it's done. If neither works, tell me roughly when suits and I'll sort it.
Best,
Adaeze's office"
Apologises once. Gives no reason. Two specific slots, already held, chosen because they move nobody else. Chinelo replies with one word and it is over.
This is the rule beginners break most often, always out of kindness. Adaeze's son being ill is her private information, and it belongs to her family, not to her client list. Sharing it feels warm and considerate. It is a small breach of confidence, it is not yours to make, and if it reaches her it damages you more than a late cancellation ever would.
"Adaeze has to move this morning's session" is complete. It needs nothing after it. If someone presses — and occasionally they will — the answer is "Something came up at short notice, I'm sorry", and then you stop.
The same applies in reverse and it is the harder half: you may never explain a move by referring to another client. Not "another client had an emergency", not "we had to fit someone urgent in". Every person on that list is now wondering whether they are the one who gets moved for someone else. In a therapy practice, or a law firm, or anywhere confidential, the mere existence of another named client is information you do not have the right to release.
If solving a chain takes more than three moves, stop and go back to the client. "Moving all four means disturbing five other people. Alternative: we cancel today's two and I offer everyone next week — quieter, but two clients wait. Which do you prefer?" Some chains are not yours to solve, and recognising one is judgement, not failure. What you must never do is quietly disrupt half the week because you were too proud to ask a question.
Write the reschedule message you would send to someone who has already been moved once before. It needs to do something the standard message does not — acknowledge the repetition without over-apologising for it, and offer something that makes it right. Try three versions and keep the shortest one that still lands.
A meeting is never just the meeting. It is the getting there, the preparing for it, and the recovering from it — and a calendar that only records the middle hour is a calendar that lies to the person following it.
Book it as one, with a title, in the calendar, blocking the time. Not a mental note. Not "she knows how long it takes."
Three rules that stop the failures:
If a meeting needs preparation, it needs two calendar entries. A board meeting at 2pm with no prep block means the preparation happens at 1:55pm or at midnight. Both of those are your failure, not hers.
Where you put it matters: prep goes the day before for anything that needs thought, and immediately before for anything that just needs the documents in hand. Thinking does not happen well in the twenty minutes before a meeting.
This is the highest-value ten minutes of your day, and it is what a client means when they say an assistant is "on top of things". It goes out the evening before, every working day.
Three sessions and one call.
10:00 — Chinelo O. Regular. This was moved from Tuesday, so she's due an easy one. Nothing outstanding.
11:05 — Ify M. Regular. Mentioned last time she might want to reduce to fortnightly — she may raise it.
13:00 — New: Grace A. First session. Found you through Bola's referral. Intake form is attached and I've put it in your folder. She asked about evening slots — you have none, and I've already told her.
15:30 — Call with Mark (London). 15:30 Lagos / 15:30 London, same time until late October. It's about the insurance appeal — the claim reference is 4471 and the rejection letter is attached. He'll want a decision on whether to escalate.
You need to bring: nothing. Everything's in the shared folder.
Already handled: Bola's rescheduling, the supplier order, and the two rate enquiries.
Read what that brief is actually doing. It is not a list of times — she can see times in her calendar. It is context she would otherwise have to remember: that Chinelo has been moved once, that Ify may raise something awkward, that Grace is new and came from a referral, that a question is coming at 3:30 and a decision will be wanted.
The last line matters as much as the rest. "Already handled" is where invisible work becomes visible — the same principle as the end-of-day summary in lesson 2.5, applied to the morning she is about to have.
Write tomorrow's brief for yourself, in this format, for your own day — including your travel and prep as booked appointments. Then compare it with what your day actually looked like when tomorrow arrives. The gap between the two is the thing you are learning to close.
Adaeze keeps Friday mornings free. She has never explained why, and you have never asked. Three weeks in, a good client asks for a Friday 10am and there is nothing in the diary.
Do you book it?
No. And understanding why not is the last thing this module has to teach you, because it is the difference between someone who operates a calendar and someone who can be trusted with one.
An empty slot is not the same as an available slot, and you cannot tell them apart by looking.
Friday morning might be her supervision session — a professional requirement, unbookable, and not something she would put in a calendar you can read. It might be when she sees her own therapist. It might be the only three hours a week she is not responsible for anybody. All of those look identical to blank space.
You are not going to learn her reasons by guessing, and you cannot ask about every slot forever. So you do it once, in week one, with a specific question rather than a vague offer to help:
"Four questions about the diary, then I'll stop asking.
1. What in here can never move, whatever happens?
2. What can move if I give you notice, and how much notice?
3. Is there anything that looks empty but isn't available? I don't need to know why.
4. What's the most you want to see in one day, and one week?"
That third question is the one that matters, and note how it is worded. "I don't need to know why." You are asking for the boundary without asking for the private reason behind it — which makes it easy to answer honestly, and tells her something reassuring about the kind of person she has hired.
Write the answers into a shared document and give each level a colour in the calendar. Now you both have a language, and most of your future questions answer themselves.
Twenty minutes of conversation and one page. From this point on you can answer almost every scheduling question alone, which is precisely the point — you asked once so you would never have to ask a hundred times.
Alongside the key, keep a running note of reasons you pick up as you go. Not private ones — operational ones. Mark prefers afternoons because his mornings are with the New York office. Chinelo cannot do Mondays, term-time only. The insurance company only answers the phone before 11am.
Nobody will ever tell you these in one sitting. You collect them, one at a time, and within a few months you hold a picture of how this business actually works that the client herself has never written down. That is not administration. That is the thing that makes leaving you expensive.
Once a quarter, look at every recurring meeting and ask a simple question: is this still earning its slot?
Recurring meetings almost never get cancelled. They get created for a reason, the reason expires, and the meeting continues for years because cancelling it would require someone to have an opinion. That someone can be you.
"I went through the recurring items this quarter. Two things:
The Monday supplier check-in hasn't produced an action in eleven weeks — I'd suggest dropping it to monthly, which gives you back three hours a month.
The Thursday admin block gets eaten by overruns about half the time. Moving it to first thing Wednesday would protect it. Happy to do either or neither."
Three hours a month, found by looking at something nobody looks at, brought to her with a recommendation attached. That is the rung-four behaviour from lesson 1.4, in its most ordinary and most repeatable form. Do this four times a year and you will not be replaced by anybody.
Look at your own week and identify every slot that is empty but not available. Write the key for your own calendar — Never, With notice, Freely, Not empty. It is a useful exercise for its own sake, and it will show you how strange it feels to be asked about the grey category, which is why the wording of that question matters so much.
You are given Adaeze's calendar for a week in late October, three client time zones — Lagos, London and New York — and a message that arrives at 07:50 on Monday morning saying she cannot work until Wednesday.
Eleven appointments are affected. Two people believe they are the priority and both have said so in writing. One is a first appointment. One person has already been moved once this month. And the week crosses the last Sunday in October, which is the point of setting it then.
Whether you can hold a system in your head — people, constraints, clocks and consequences — and still make a decision at the end of it. Module 2 tested whether you could tell loud from load-bearing in a pile of messages. This tests whether you can do the same thing when every option costs somebody something, and there is no arrangement in which nobody is inconvenienced.
You should now have: a booking link you have configured and tested from the outside, a calendar key for your own week, a day-before brief you have written and checked against reality, and a reschedule message for someone being moved a second time. Module 4 takes files and documents — where all of the attachments in that day-before brief actually live, and why finding them takes most assistants far longer than it should.