The short version
- A call in the middle of an afternoon takes more than the slot it books. Preparing for it and writing it up are both real work, and neither shows on the calendar.
- Every client call we run lands on a Monday or a Tuesday. That is the only reason Thursday and Friday can hold work that needs a whole problem kept in your head.
- Batching without a processing day behind it produces two days of conversation and a backlog nobody converts into work.
- Monday and Tuesday are bad days, and anything urgent on a Thursday waits until Monday. We pay both of those rather than lose the unbroken days.
Every client call we run happens on a Monday or a Tuesday. Wednesday turns those recordings into action items with an owner and a date against each one. Thursday and Friday hold nothing scheduled at all, and that is where the gain lands, because long work only finishes inside a block nobody is allowed to interrupt.
Why does a scattered meeting schedule cost more than the meetings do?
Because the gap between two meetings is not working time. The time before a call goes on half-preparing and half-waiting. Whatever follows it gets spent writing up what was just agreed, which is real work, but it is not the work you sat down to do. A calendar with calls scattered across a day holds no block long enough for anything that requires keeping a whole problem in your head.
The shape of the week, and what each day refuses:
| Day | What it is for | What it refuses |
|---|---|---|
| Monday | Client calls | Deep work |
| Tuesday | Client calls, internal syncs | New scope |
| Wednesday | Recordings into action items, briefs | New meetings |
| Thursday and Friday | Building and writing | Anything scheduled |
What does a batched week look like?
Monday and Tuesday absorb every client call and every internal sync across 8 client accounts and 11 brands. Wednesday processes them. Recordings turn into action items with an owner and a date, and the work those items imply gets assigned before anybody has to reconstruct what a client meant. Thursday and Friday are for making.
Weekly delivery on every account is what holds the shape. Something goes out on every account every week, and the days that produce it are the two nobody is allowed to book.
What breaks when you batch?
Monday and Tuesday are bad days. A full day of calls leaves nobody sharp by the last one, and the fix is to put the hardest conversation first rather than pretend the fatigue is not there.
Four time zones complicate the first hour and the last. A client on the far side of the world gets an early Monday or a late Tuesday, since the hour is the part that can move without costing anything. The overlap window is the only synchronous resource the team has, and a meeting parked outside the batch spends it twice.
The second cost is that something urgent on a Thursday waits until Monday unless somebody breaks the rule. We handle that with one shared channel per client relationship, so urgency has an outlet that is not a calendar invite.
How do you protect the making days?
The default answer to a new meeting is no, and it holds because nobody has to enforce it in the moment. No recurring internal meeting lands on a Thursday or a Friday. A new external request gets offered a Monday or a Tuesday slot before any other option is mentioned. The wording carries most of the load: send two specific times rather than asking when suits, because open availability is how a Thursday gets booked.
One exception is worth keeping, which is a live incident. If a site is down or a campaign is spending badly, the rule is off.
Every client call we run lands on a Monday or a Tuesday, and the recordings become action items on the Wednesday, each with an owner and a date.
Who should not batch their week?
Anyone whose output is response time. Support, and sales teams taking inbound demos, lose more from a two-day delay than they gain from an unbroken Thursday. The same goes for a founder in year one, where the meeting is the work and there is nothing else to protect yet.
The test is whether the role produces a finished artefact or a fast answer. Artefacts need long blocks. A support queue does not care what shape your week is in, and batching it only makes the reply late. One team can hold both, as long as it is honest about which roles are which instead of applying a single calendar policy to everyone.
Related reading: turning recordings into action items, and what an office did for free.
Frequently asked questions
What is meeting batching?
Meeting batching is the practice of putting every scheduled call into a small number of fixed days so the remaining days carry no interruption. We hold every client call on a Monday or a Tuesday, process the output on Wednesday, and keep Thursday and Friday free of anything scheduled.
How many meeting-free days does a week need?
We protect two consecutive days, Thursday and Friday, so a piece of work can start on one and finish on the next without being reloaded in between. A single protected day sitting between two days of calls does not give you that.
Why do scattered meetings cost more than the time they take?
Because the gaps between them are not working time. Preparing for a call and writing up what was agreed are both real work, and a day broken into those gaps holds no block long enough for anything that needs a whole problem in your head.
How do you batch meetings across multiple time zones?
Vary the hour instead of the day. Our team works across four time zones, so a client on the far side of the world gets an early Monday or a late Tuesday, and the batch survives. Open availability across the whole week is what destroys the shape.
What has to happen the day after a block of meetings?
Processing. Recordings become action items with an owner and a date, and briefs get written before the detail fades. Batching without a processing day produces two days of conversation and a backlog nobody ever converts into work.
Does meeting batching work for sales teams?
Not for inbound demos, where response time is the product and a two-day delay costs more than an unbroken afternoon is worth. It works for roles whose output is a finished artefact. Apply it by role rather than as one calendar policy across a whole company.
Sources
- Chua Network delivery data across 8 client accounts (internal fact bank)
- Chua Network engagement records, anonymized (internal experience bank)
