Last reviewed: September 2026.
What is Surge?
Surge is a time-boxed meeting cycle where you see many clients in focused blocks on specific days, with clear start/stop times and protected prep and wrap-up windows. The goal is to reduce context switching, increase quality, and Deliver Massive Value (DMV) consistently.
Surge is not: ad-hoc scheduling, "always available" meeting habits, or marathon meetings that run long and drain client attention.
Why Surge Works
Deep focus: Fewer interruptions = better thinking and advice.
Predictability: Your team knows what is happening and when.
Throughput: Standardized meeting length and flow increase capacity without sacrificing quality.
Client experience: Consistent, on-time meetings with clear takeaways.
Common Myths (Debunked)
"Two meetings a week is Surge."
Not enough volume to build rhythm or improve process. Aim for at least 4 meetings/day during Surge days."All Surges must look the same."
They do not. Your cadence should solve your goals (travel, family time, growth, etc.)."You can't prep between meetings."
You can, by doing a short, structured post-meeting dictation that preps the next visit (see Running a Surge Cycle).
Define Your "Why"
Decide what you are solving for:
More family/travel time
Higher client throughput
Shorter, better meetings
Cleaner team handoffs
Your "why" sets your capacity targets and calendar rules.
Choose Capacity and Cadence
Meeting length: Cap at 60 minutes or less. Longer meetings yield diminishing returns.
Daily volume starter models:
Conservative: 4/day, 3 days/week
Standard: 5 to 6/day, 3 days/week
Advanced: 7 to 8/day, 4 days/week
Ramp carefully: If you run 2 to 3/day now, add +1 per day this cycle, then reassess.
Design a Weekly Template
Pick your meeting days (for example Tue to Thu) and protect non-meeting days for deep work.
Sample day (adjust to taste):
08:15 to 08:45: Finalize packets and agenda
09:00 to 10:00: Client 1
10:15 to 11:15: Client 2
11:30 to 12:00: Admin and buffer
12:00 to 12:45: Lunch (protected)
12:45 to 13:15: Quick prep
13:15 to 14:15: Client 3
14:30 to 15:30: Client 4
15:30 to 16:00: Post-meeting dictation block
16:00 to 16:30: Team handoffs and shutdown
Time-Blocking Rules
Meetings only in designated blocks.
Start/stop on time. Use a visible timer.
Keep a backlog for ideas/changes; never change process mid-Surge.
Protected breaks are mandatory.
Client Communication and Boundaries
Set expectations like any professional practice (think dentist's office): pre-defined slots, not on-demand drop-ins.
Copy-paste scheduling script:
"We hold focused client days on Tue to Thu. I can do Tue 10:00 or Thu 1:15. What works best for you?"
Copy-paste availability script:
"To give every client our best, we meet in focused cycles. If something urgent comes up between cycles, email or call. Our team will route it the same day."
Quick Start (30 Minutes)
Pick 2 to 3 Surge days for the next 4 to 6 weeks.
Set daily capacity (start with 4).
Add fixed lunch and two 30-minute buffers.
Publish booking windows (for example Calendly or Acuity). SurgeTK can pull Calendly meetings into a Surge's calendar.
Share the scheduling script with staff.
Success Checklist
Daily meeting cap set (60 minutes or less each)
At least 4 meetings/day on Surge days
Time-blocks published and enforced
Scripts in use by staff
Backlog created for improvements