The 6pm Singapore meeting that broke my faith in scheduling tools
Three years ago, I was consulting for a SaaS company with engineers in San Francisco, product managers in Berlin, and a support team in Manila. Their calendar tooling was top of the line. Calendly, Clockwise, Notion, the works.
Every week, the Manila team joined a “quick sync” at 9pm their time. Every week, the meeting ran long. Every week, one of them muted their camera, and I knew exactly why.
I pulled the data. In six months, the Manila team had attended 41 meetings outside their working hours. The San Francisco team had attended three. Nobody in leadership had noticed, because nobody was measuring it.
That project changed how I think about scheduling forever. After ten years of doing this, I can tell you the tools matter far less than you think, and the decisions matter far more than you’d like. Here is everything I have learned, including the mistakes, the numbers, and the opinions that will annoy people.
Find your overlap before your next invite , open the Global Time Zone Meeting Planner.
The Biggest Mistake: Treating Scheduling as a Math Problem
In my experience, the number one failure mode is this: a team realizes time zones are hard, so they buy a tool, and then they assume the tool solved it.
Time zone math is easy. Fairness is hard. What actually happens in most companies is that the scheduling defaults to wherever the most senior person sits. If your CEO is in Austin, your company operates on Austin time with a thin veneer of “global flexibility.”
I used to believe that better tools would fix this. I now think that belief was naïve, because I have watched companies with terrible tools and excellent meeting culture run circles around companies with pristine tooling and lazy defaults.
The fix costs nothing. Someone, by name, owns meeting fairness. Every recurring cross-zone meeting has a documented rotation policy. That’s it. No software required.
The Tools I Actually Recommend (And the Ones I Tell People to Drop)
Let me be specific, because most “best tools” articles read like sponsored content.
For external booking: Calendly is the default for a reason. It is reliable, everyone recognizes it, and it handles time zones correctly. I use it for sales calls and vendor meetings without hesitation.
For higher-stakes client calls: SavvyCal. It lets the other person overlay their calendar on yours, which sounds like a small thing until you watch a busy executive book a call in twenty seconds instead of four emails. The conversion difference is real. In my own tracking, SavvyCal links converted about 30 percent better than plain Calendly links for executive-to-executive scheduling.
For quick time zone math: World Time Buddy. I keep it open all day. Nothing fancy, nothing better.
For team calendar optimization: Clockwise. It genuinely reduces meeting fragmentation, and I have seen it free up three to five hours per person per week in meeting-heavy organizations. But read section 8 before you deploy it.
For group scheduling: Doodle polls, but only for one-off events with many participants. For recurring internal meetings, Doodle is where good intentions go to die. Nobody wants to fill out a poll every week for a meeting that happens every week.
Drop this: Google Calendar’s “suggested times” for cross-zone meetings. It optimizes for the calendar owner’s convenience and will happily propose a time at 11pm for half your team. I have seen it do exactly that more than once.
Reading about tools? Try the actual one, plan a meeting across zones here.
Scheduling Link, Poll, or Shared Calendar? The Decision Framework
This sounds basic, but confusing these three categories causes most of the scheduling friction I am hired to untangle.
Use a scheduling link when one person is booking time with you and your availability is the constraint. Sales calls, interviews, vendor intro calls. Calendly or SavvyCal.
Use a poll when three or more people need to converge on one slot and there is no recurring pattern. Launch planning, a quarterly review, a workshop. Doodle or a Slack workflow.
Use a shared calendar view when a team needs ongoing visibility into each other’s time. This is where Clockwise or even a well-maintained Google Calendar with shared working hours beats everything else.
The trap I see constantly: using a poll for a recurring meeting. One client came to me where a team lead sent a Doodle poll every single Monday for a meeting that happened every single Wednesday. That is 52 polls a year for a meeting that could have been solved once with a rotation policy. We killed the poll, picked three rotating time slots, and gave everyone their Monday mornings back.
The Rotation Policy: The Single Highest-ROI Practice I Know
Here is a number that should bother you. In my project data across roughly a dozen global teams, without a documented rotation, the same one or two people ended up absorbing the after-hours slots within six weeks. Every time. Not because anyone was malicious. Because entropy.
A rotation policy is a written rule that says, for any recurring meeting spanning more than four hours of time zones, the “pain” of the early or late slot rotates on a fixed schedule, usually every four to six weeks.
I now make this non-negotiable in every engagement. The results are consistent: complaints about meeting times drop to nearly zero within two cycles, because people can see the fairness. They stop optimizing for “my ideal time” and start optimizing for “my turn will come.”
Fairness you can see is fairness people tolerate. Fairness you have to trust evaporates under stress.
Fixing the APAC Problem When Leadership Won’t Move
This is the controversial part, so let me be blunt. If your company is headquartered in the US or Europe and you have a significant team in Asia, your current meeting schedule is almost certainly extractive. You just do not feel it because the pain is happening while you sleep.
One client had 40 percent of their engineering team in Singapore and a weekly architecture meeting at 9pm Singapore time. I did not find them a better time, because one did not exist. Instead, we split the architecture discussion into two parts: a written proposal with comments open for 24 hours, and a 30-minute live session held at a rotating time between the two largest groups.
Live attendance dropped 60 percent. Decision quality, measured by how often decisions had to be reopened, went up. The written record meant Singapore engineers could engage at 9am their time with the same authority as someone arguing live at 9am Pacific.
The lesson: when no fair time exists, the answer is not a better time. The answer is less dependence on a shared time.
The Four Metrics That Actually Matter
Most meeting analytics dashboards are noise. I track exactly four numbers, and I recommend you do the same.
Average meetings per person per week. If this number exceeds 21 for a knowledge worker, you do not have a scheduling problem, you have a decision-making problem. Meetings are a symptom.
Percentage of recurring cross-zone meetings with a documented rotation. Target: 100 percent. This is the fairness metric.
Percentage of meetings that end with written notes or decisions. Target: above 80 percent. If a meeting produced no written output, ask yourself what it produced at all.
After-hours attendance rate per region. This is the one nobody tracks and the one that matters most. Divide each region’s outside-hours meeting attendance by their total attendance. If any region exceeds 20 percent, your schedule is extractive toward that region, full stop.
When I introduced these four metrics at that SaaS company with the Manila team, the 9pm meeting was restructured within three weeks. Not because anyone was shamed, but because the data made the invisible visible. You cannot fix what you refuse to measure.
The Async Test: When Live Meetings Are a Failure
I used to believe that complex decisions needed meetings. I ran workshops, I facilitated debates, I scheduled the follow-up meeting to schedule the real meeting. I now think that belief, held by most managers, costs companies millions of hours a year.
Here is the test I use with every client. Ask one question: does this decision require real-time emotional alignment, or does it only require information exchange and judgment?
A layoff conversation, a co-founder dispute, a crisis response: those need live time. Almost everything else, roadmap prioritization, design feedback, status updates, policy decisions, works better async.
The format that works: a Loom video under four minutes or a written proposal under one page, a 24-hour comment window, and a designated decision-maker who closes the thread with a call. The comment window is the secret. It gives introverts, non-native speakers, and people in inconvenient time zones equal footing, which live meetings never do.
The Hidden Pitfalls of AI Scheduling Assistants
I like Clockwise and Reclaim. I recommend them. And I have watched them cause real damage.
The failure mode looks like this. A company deploys Clockwise with no meeting culture policy. The AI dutifully protects everyone’s focus time by shifting flexible meetings into the only gaps left, which are, of course, the edges of the day. Within a month, the APAC team is in 7am calls five days a week, and the AI considers the schedule “optimized” because focus blocks are intact.
The AI optimized what you told it to optimize. You told it to protect individual focus time. You never told it to protect fairness across regions.
Garbage policies in, garbage schedules out. Before deploying any AI scheduler, write down three rules: maximum after-hours burden per region, mandatory rotation on cross-zone meetings, and which meeting types are allowed to be auto-scheduled at all. Then let the AI work within those constraints. It will do a genuinely excellent job.
The Zero-Overlap Playbook
One of the hardest engagements I ever had: a company with staff from São Paulo to Manila and literally zero shared working hours. No rotation could save them because there was nothing to rotate.
The solution was brutal and simple. No recurring live meetings, at all. Async by default for everything. A single four-hour weekly live window, on rotation, reserved exclusively for true emergencies and relationship building. Documentation discipline enforced by making the written record the canonical decision source, not the meeting.
It worked, but only because the CEO enforced it personally for the first ninety days. Culture changes fail at the leadership layer first. If your executives keep demanding live calls outside the policy, the policy is dead.
If you are in this zero-overlap situation, accept the truth early: you are not a meeting company with a time zone problem. You are an async company that occasionally meets. Design for that from day one and it works. Pretend otherwise and you will burn out your most distant people first.
Where This Is All Going by 2027
My predictions, and I will stand by them.
Predictive scheduling replaces polling. Within two years, your calendar AI will propose times based on the actual attention patterns of every attendee, not just empty slots. The “when are you free?” email will look as dated as a fax cover sheet.
Cross-company scheduling gets solved. Today, Calendly links break down when five companies need to meet. The next generation of tools will negotiate times across organizations automatically, which will quietly transform partner meetings, vendor negotiations, and multi-agency projects.
Meeting attendance stops being the metric. As async matures, leaders will stop counting who showed up and start measuring decision velocity and rework rates. The teams that win will be the ones that treat meeting hygiene as a design discipline, the way great engineering teams treat code hygiene.
The tool landscape will consolidate. Expect Calendly, Clockwise, and the calendar giants to absorb most of the point solutions. Buy for workflow fit today, not feature checklists.
Run your 15-minute audit with real numbers, check your overlap window now.
The One Thing to Do This Week
Here is my specific, actionable takeaway. Do not buy anything. Instead, run a 15-minute audit: list your five most frequent recurring cross-zone meetings, check whether each one has a written rotation policy, and calculate your after-hours attendance rate per region. That number, which takes one hour to produce, will tell you more about your meeting health than any demo from any vendor.
If any region is above 20 percent after-hours attendance, fix that this week by restructuring the worst offender into an async format with a 24-hour comment window.
Global teams do not fail because of time zones. They fail because nobody owned the fairness. Own it, measure it, and the tools will finally do what you hoped they would.
Own the fairness this week: use the Global Time Zone Meeting Planner, free, in your browser.
How do you use Global Time Zone Meeting Planner?
Open the Global Time Zone Meeting Planner in your browser (Schedule meetings across time zones with one glance). Type or paste your input, adjust the options, and copy the result. Everything runs locally on your device with no account and nothing stored, so the three steps below take seconds even for confidential work.
- Enter your numbers into the fields. The result recalculates as you type.
- Switch any unit or option to see the updated answer instantly.
- Copy the result with the copy button, or read the summary beneath it.
Try Global Time Zone Meeting Planner free. It opens right in your browser.
Leave a comment