The Executive Summary
Solo creators at $60–$150K/year carrying 10+ weekly call hours lose an estimated $52K/year in deep work value to a meeting schedule built by accommodation, not design.
Who this is for: Solo creators and freelancers at $60–$150K/year with 3+ active client engagements and 10+ weekly call hours consuming production time
The call accumulation problem: A 5-client creator at the Scaling band runs 14–18 hours of calls per week — up to 60% of which are status updates and approvals that don’t require real-time exchange
What you’ll learn: Async-First Default, 25/50-Minute Rule, Call Consolidation, Client Communication Norms Script, Async Adoption Timeline
What changes if you apply it: Call hours drop 40–60% with the same client relationships; 3+ uninterrupted production hours become available daily
Time to implement: Call audit in 60–90 minutes (Days 1–2); 25/50-minute rule in 30 minutes (Days 3–5); communication norms sent to all clients by end of Week 2; full protocol holding by Week 4
Written by Nour Boustani for solo creators and freelancers at $60–$150K/year who want 3 hours of uninterrupted deep work daily without abandoning client relationships.
› Library Navigation: Quick Navigation · Internet Solos and Creators
Meeting Governance Protocol: Reclaiming Deep Work From Call Overload
Cutting call time is not a productivity hack. It is a revenue decision.
Creators in the Scaling band ($60–150K/year) with three or more active client engagements can lose an estimated $52K/year in reclaimed deep-work value to a meeting schedule that was never designed. It simply accumulated.
The Meeting Governance Protocol is a three-component framework covering async-first defaults, structured call durations, and client touchpoint consolidation. It reduces total call time by 40–60% in 30 days while maintaining every client relationship.
The result is not fewer clients. It is three hours per day of uninterrupted production capacity, making the work clients pay for possible.
Where are you with this right now?
“I spend 4-5 hours on calls daily and I’m too exhausted to do the deep work I’m billing for.” You’re inside this constraint. The protocol below installs the governance layer that reclaims that time. Start at Component 1: Async-First Default and run the call audit before changing anything else.
“I have 1-2 clients right now and calls feel manageable.” The Meeting Governance Protocol delivers its highest return with 3+ active client engagements. Install the async-first default now as a foundation - it prevents the problem from building as your client load grows. Return here when you add a third engagement.
“I’ve tried cutting calls before. Clients pushed back and I gave in.” That’s a protocol failure, not a client relationship problem. The Client Communication Norms Script in Write And Send The Client Communication Norms Script and the async adoption timeline in The Async Adoption Timeline exist because client boundary-testing is predictable and manageable when you have the right language and do not break the protocol.
Try This Now
Pull your calendar from the last two weeks. Count every call and assign it to one of these categories:
Status update
Decision
Relationship maintenance
Complex problem-solving
Count how many calls were status updates or approvals that could have been handled in writing. If more than 40% fall into that category, you are paying for a scheduling problem with production time.
The call schedule harming your output did not begin as a schedule. It began as accommodation.
How Call Overload Accumulates Across Client Work
Solo creators in the Scaling band share one defining pattern: their current meeting load is not the one they agreed to when clients signed. It accumulated through small concessions:
A quick call here.
An additional check-in there.
A “just 15 minutes” conversation that became a standing weekly meeting.
None of these felt like a problem when added. Together, they became the full-time job the creator performs before starting the work clients actually pay for.
The compounding effect remains invisible until it becomes disruptive:
At 2 clients, the call load may be manageable at 6–8 hours per week.
At 4 clients following the same pattern, it can reach 12–16 hours per week.
At 6 clients, it can exceed 20 hours per week.
The creator has not necessarily taken on more clients than they can handle. They have repeated the same unmanaged meeting pattern six times.
What Is Actually Happening
The failure mechanism looks similar across creator types at this revenue stage.
A content strategist earning $95K/year has 5 active retainer clients. Each client has a standing weekly call that began at 30 minutes but now consistently runs 45–60 minutes. Two clients have added biweekly check-ins “just to stay aligned.”
Total weekly call time: 14–18 hours.
Core work: strategy and content, which require deep focus.
Constraint: no 3-consecutive-hour block of uninterrupted production time.
Result: deliverable quality is slipping, and evening work has become necessary.
She attributes the problem to being “too busy.” The actual issue is a call architecture that was never designed.
A freelance copywriter and course creator earning $80K/year has 3 active clients and a course cohort running simultaneously. He scheduled weekly calls with each client at the start of every engagement, and the cohort includes a weekly live session.
When projects hit a rough patch, ad hoc calls get added.
Typical weekly call time: 10–12 hours.
Common call content: status updates that could have been sent as a three-paragraph email.
Stated problem: “I’m bad at protecting focus time.”
Actual problem: no protocol defines what qualifies for a call.
A brand consultant earning $110K/year serves 4 high-value clients who expect responsive communication. She has never defined what “responsive” means, so each client supplies their own standard.
One client calls without scheduling.
Another sends messages at 8 p.m. and expects a same-day reply.
She checks messages constantly to manage the anxiety of not knowing what will arrive next.
She describes this as “just how client services work.” It is actually an undefined communication standard that clients are filling with their own defaults.
All three creators have the same problem:
Not too many clients.
Not necessarily the wrong clients.
No meeting governance layer.
The Call Accumulation Pattern
Client 1: 1 call per week
Client 2: 1 call per week
Client 3: 1 call per week plus ad hoc check-ins
Status update calls
“Quick 15-minute” requests
The result:
14–20 hours per week spent in calls
0 uninterrupted production blocks
The Advice That Made It Worse
The most damaging advice in the creator-services world is: “Always be available. Clients pay for access.”
Availability without governance trains clients to expect instant access as the default. The creator who is always available for a call gets called constantly, not necessarily because clients are demanding, but because the shortest path to an answer becomes, “Just get on a call.”
Clients are not necessarily trying to consume the creator’s time. They are taking the shortest path to an answer.
The fix is not less availability. It is a defined protocol that makes async communication the shortest path for the right types of communication and reserves calls for interactions that genuinely require them.
The Real Cost
Microsoft’s 2024 Work Trend Index, “AI at Work Is Here. Now Comes the Hard Part,” reports that knowledge workers spend 60% of their Microsoft 365 time on communication, including email, chat, and meetings, and only 40% on creative work tools.
For solo creators who are simultaneously the account manager and the producer, a meeting-heavy schedule does more than reduce output time. It eliminates the deep-work capacity that makes the creative work possible.
Deep work is uninterrupted, high-focus production used to create strategy documents, course content, copy, and high-stakes deliverables. It is not possible in 45-minute windows between calls.
The math for recovering that time:
Three hours of deep work recovered per day at $75/hour
Daily value: $225/day
Annual value based on 231 working days: $52K/year
That is the reclaimed capacity value of hours currently consumed by calls that do not require a call.
Cost calculator formula:
Current daily call hours: _ hours
Hours that could be async from your two-week audit: _ hours
Recoverable hours per day: _ hours × $75/hour = $_/day
Annual reclaimed value: $_/day × 231 working days = $_/yearStage Filter
This article is for creators in the Scaling band ($60–150K/year) with 3 or more active client engagements requiring regular calls.
The Meeting Governance Protocol delivers its highest return when call load has accumulated to 10 or more hours per week. Creators with 1–2 clients rarely feel enough constraint to install governance. The pain usually arrives with the third client and compounds with every additional engagement.
If you have 2 clients and do not yet feel the constraint, install the async-first default now. You will be better prepared when the third client signs.
Creators in the Validation band ($0–10K/year) or Survival band ($10–60K/year) with 1–2 clients may still benefit from a call protocol, but the leverage is lower. Focus first on client acquisition, then return to this system when call load becomes a real constraint.
If the Damage Is Already Done
If your client relationships have already been trained to expect frequent access and real-time availability, use a staged reset.
Within 30 days:
Do not change the protocol without an announcement. Clients who experience a sudden drop in responsiveness without explanation may interpret it as disengagement.
Run the call audit first and identify which calls can move to async communication.
Do not implement changes yet.
From 30–90 days:
Introduce the new protocol explicitly to each client using the Client Communication Norms Script.
Frame the change as a service improvement, not a constraint.
I’ve redesigned how I work so I can give you better output, not faster replies.Most clients adapt within 2–3 weeks when the rationale is stated clearly.
After 90 days:
Any client still demanding the old access level after 60 days under the new protocol has communicated their actual expectation.
Decide whether to revise the engagement terms, transition the client out, or determine whether your rate justifies the access level being demanded.
That is a business decision, not a communication problem.
Availability without governance is a business model. It simply happens to be one where the client sets the terms.
The meeting load consuming your production time did not begin as a problem. It accumulated through small accommodations that felt harmless one at a time.
Readiness Check: Before Installing the Protocol
Criteria:
Call audit completed: every recurring and ad hoc call from the last two weeks is listed and categorized.
Total weekly call hours calculated and confirmed above 8 hours.
At least 3 active client engagements currently require regular calls.
Pass: all 3 criteria are met.
Fail: fewer than 3 criteria are met.
If you fail, stop. Run the call audit first. It takes 30 minutes; see the Try This Now block at the top of this article.
Proceeding without the audit means implementing governance on a call schedule you do not fully understand. You will govern the wrong things, and the reduction will not hold.
The failure mechanism is named. Install the Meeting Governance Protocol to apply the fix: a three-component system that reduces call time by 40–60% while maintaining every client relationship intact.
The Meeting Governance Protocol: Reduce Client Calls and Reclaim Deep Work
Governance is not about taking calls away from clients. It is about replacing calls that serve no one with communication that works better.
The Meeting Governance Protocol has three components that operate simultaneously, not in sequence:
Component 1 defines what requires a call.
Component 2 defines how long those calls run.
Component 3 defines how often they happen.
Together, they produce the framework’s 40–60% call-time reduction.
Component 1: Async-First Default: What Actually Needs a Call
The first component is the most important and the most consistently misapplied.
The async-first default does not mean “avoid calls.” It is a classification system. Specific communication types are handled asynchronously by default, while calls are reserved for interactions that genuinely require real-time exchange.
The four communication categories and their default channels are:
Status updates: handled asynchronously, always. “Here’s where the project stands” is a written update. It does not require a real-time reply. A client who needs to discuss a status update needs a decision call, not a status update call.
Approvals: handled asynchronously, always. “Please review and approve Section 2” is an email or message. Approvals that require discussion become decision calls.
Non-urgent questions: handled asynchronously by default. “What format do you prefer for the final deliverable?” is a message, not a call. A response within 24 hours on business days is a reasonable standard.
Decisions, relationship maintenance, and complex problem-solving: handled through calls. These interactions benefit from real-time exchange, tone, and the ability to think out loud together. Status updates do not.
Async-First Classification
Status update?
- Async: written update
Approval needed?
- Async: review and comment
Non-urgent question?
- Async: message with a 24-hour reply
Decision needed?
- Call
Relationship maintenance?
- Call
Complex problem?
- CallDecision rules:
If the question has a single right answer that the creator already knows, handle it asynchronously. Send the answer. No call is needed.
If the interaction requires the client’s real-time thinking or reaction, use a call. Their thinking needs to happen live, not in a message.
If you are unsure, ask: “Would a written message produce the same outcome as a call?” If yes, handle it asynchronously.
Urgent issues are the exception. Async does not mean slow. If a client’s live event starts in 2 hours and there is a problem, a call is appropriate. The async default applies to the 80% of communication that is not urgent.
The 12-call-type classification in the toolkit classifies 12 specific call types, from project kickoffs and weekly check-ins to “quick questions,” as async or call. It also explains the reasoning for each classification.
This classification removes ambiguity for the creator and makes the protocol easier to explain to clients.
What This Framework Is Really Teaching You
The async-first default is not a communication preference. It is a diagnostic instrument.
Every time a creator is tempted to schedule a call instead of sending a message, that temptation is data. Sometimes the situation genuinely requires a call. More often, it signals one of two problems:
The creator has not communicated clearly enough in writing.
The client has been trained to expect a call for issues that do not require one.
Creators who install the async-first default discover which client relationships consume disproportionate communication overhead, often before the financial cost becomes visible.
A client who always needs a call is revealing something about how the engagement is structured.
Component 2: The 25/50-Minute Rule: Why 30-Minute Calls Run 45
The second component addresses one of the most consistent time leaks in creator call schedules.
Thirty-minute and 60-minute calls are often broken by design:
A 30-minute call has no buffer before the next commitment. When it runs 10 minutes over, the creator is late for the next call or loses the first few minutes of a production block.
A 60-minute call creates little scheduling pressure to close. It can expand to fill the full hour, even when less time was needed.
The 25/50-minute rule replaces both formats.
25-minute calls: use for status reviews, brief decisions, and check-ins that do not require extended problem-solving. The 5-minute buffer allows the creator to close the call, process notes, and begin the next task without falling behind.
50-minute calls: use for strategic sessions, complex decisions, and relationship maintenance that require depth. The 10-minute buffer serves the same function at a larger scale.
Why the buffer matters for deep work:
A creator who moves directly from a call into production work carries cognitive residue from the conversation for an average of 15–23 minutes before reaching full focus depth.
A 5- or 10-minute buffer does not eliminate that residue, but it creates processing time that reduces it. Use the buffer to write three sentences of post-call notes and close communication tabs before entering the production block.
Call Format Comparison
30-Minute Call: Broken 25-Minute Call: Fixed
9:00 Call starts 9:00 Call starts
9:28 Still going 9:25 Call ends on time
9:30 “Just 2 more minutes” 9:25–9:30 Process and transition
9:35 Finally ends 9:30 Production block starts
9:35 Immediately next task Clean start, no residue
Behind, stressed, distractedDecision rules:
If the meeting is a status review, brief check-in, or single-decision call, schedule 25 minutes. Use this as the default unless there is a specific reason to schedule more time.
If the meeting requires strategic discussion, multiple decisions, or relationship depth, schedule 50 minutes.
If a 25-minute call consistently runs over, the problem is agenda clarity, not call length. A call without a written agenda will expand. See the 25-minute call agenda template in the toolkit.
Discovery calls with prospective clients are an exception. These are relationship calls, not governance calls. The 25/50-minute rule still applies, but the purpose is discovery, not production. Schedule them for 50 minutes and treat the full time as an investment.
Component 3: Call Consolidation: One Call Per Client Per Week Maximum
The third component addresses the structural cause of ad hoc calls.
Ad hoc calls do not necessarily happen because clients are demanding. They happen because there is no defined touchpoint for accumulating communication.
A client with one standing call per week and a defined agenda has a container for questions. Questions that arise between calls go on the agenda for the next call instead of becoming a Slack message that triggers, “Can we jump on a quick call?”
The standing call is the container. Without it, every question becomes an immediate need.
Call consolidation installs that container:
One call per client per week maximum. This means one call per client relationship, not one call per project. If a client has two active projects, cover both in one weekly call.
A structured rhythm replaces ad hoc scheduling. Use a recurring agenda covering project status, decisions needed, and relationship items.
Async communication between calls is the default. Clients can send messages between calls, but non-urgent items are addressed during the next weekly call.
Urgent items receive a same-day written response or, if genuinely call-worthy, a scheduled 25-minute call added to the week.
The recurring weekly agenda covers:
Project status: what is complete, in progress, and coming next.
Decisions needed: items requiring the client’s input that week.
Relationship: anything outside the project scope that needs attention.
This structure tells the client what will be covered every week and removes the need for separate status-update calls.
The consolidation math for a 5-client creator:
Before consolidation:
5 weekly standing calls × 45 minutes average = 225 minutes per week
3–4 ad hoc calls per week × 20 minutes average = 60–80 minutes per week
Total weekly call time: 285–305 minutes, or 4.75–5+ hours
After consolidation:
5 weekly standing calls × 25 minutes, structured and on time = 125 minutes per week
0–1 genuinely urgent calls per week × 25 minutes = 0–25 minutes per week
Total weekly call time: 125–150 minutes, or 2–2.5 hours
Reduction: 50–60% in total call time.
The clients remain the same. The relationships remain the same. Only the architecture changes.
Ad hoc calls do not necessarily happen because clients are demanding. They happen because there is no defined container for their questions.
What AI-Assisted Meeting Governance Looks Like
Manual implementation of the Meeting Governance Protocol, including auditing calls, drafting the async classification, and rewriting agendas, can take 2–3 weeks of iterative work.
AI-assisted implementation compresses the same work to 3–5 days.
The specific use case is call classification. Many creators struggle to classify their own calls as asynchronous or call-worthy because they are too close to the client relationships to see the pattern objectively.
Tool: Claude, available at claude.ai.
Use this prompt:
I have a list of recurring calls in my client work. For each call, I will describe who it is with, what we typically cover, and how long it runs.
Classify each call as one of the following:
- Async: should be handled through a written update or message.
- Borderline: could be handled either way. Explain the criteria for choosing async communication or a call.
- Call-worthy: genuinely requires real-time exchange.
For each call, provide:
- The classification.
- The reasoning.
- The communication type being handled.
- The recommended channel.
- Any changes needed to the agenda or call duration.
Then review the full list for patterns. Identify:
- Calls covering the same type of content.
- Status updates that could be consolidated.
- Calls that have expanded beyond their original purpose.
- Meeting creep between the original agenda and the current agenda.
- Opportunities to reduce call frequency or duration.
Recommend a revised async-first protocol and call schedule. Preserve calls that genuinely require real-time exchange.
Here are my calls:
[list each call with the client, purpose, typical topics, current frequency, and duration]AI-assisted review can identify patterns that manual review often misses. A creator may see each call individually, while AI can identify that 4 of 7 weekly calls cover the same type of content, such as status updates, and recommend consolidation.
It can also identify meeting creep by comparing what a call was originally scheduled to cover with what it covers now.
Timeline comparison:
Manual implementation: 2–3 weeks to classify calls, draft the async protocol, and rewrite agendas.
AI-assisted implementation: 3–5 days to produce the same output with explicit classification logic.
The speed gap matters because every week of delay is another week of foregone deep-work value.
At a recovery rate of $225 per day, one week represents $1,575 in foregone deep-work value.
Single Points Of Failure And What To Build Instead
The Meeting Governance Protocol has three vulnerabilities that can collapse the system if they are not addressed.
SPOF 1: The protocol exists only in the creator’s head.
A governance system that is not written down and shared with clients is a personal preference, not a protocol. If the creator is unavailable for a day, there is no document for the client to reference about how communication works.
Redundancy protocol:
Write the async communication standard in 1–2 paragraphs.
Include it in every new client onboarding document.
Send it to existing clients through the Client Communication Norms Script.
SPOF 2: The weekly call has no written agenda.
A call without a written agenda expands to fill its scheduled time and often runs beyond it because there is no agreed endpoint for coverage. A call with a written agenda ends when the agenda ends.
Redundancy protocol:
Use the 25-minute and 50-minute agenda templates in the toolkit for every recurring client call.
Send the agenda 24 hours before each call.
Encourage clients to add questions to the agenda instead of requesting ad hoc calls.
SPOF 3: One high-value client is exempt from the protocol.
Every creator has one client who feels different because of higher revenue, a longer relationship, or greater demands. When that client is exempted from the call governance standard, two problems follow:
The creator loses the deep-work recovery benefit on the highest-revenue engagement.
The exemption signals to other clients that the protocol is negotiable.
Redundancy protocol:
Apply the same standard across all client relationships.
Adjust the support tier for high-value clients by offering more frequent calls within the structured format.
Do not exempt high-value clients from the format itself.
Stress-Test The Protocol Under Volatility
The Meeting Governance Protocol does not just hold under stable conditions. It becomes more valuable when conditions deteriorate.
Revenue drops 30% and you lose one client:
Without governance, the creator scrambles to replace the lost revenue and adds ad hoc communication to reassure remaining clients.
That consumes the production time needed to create acquisition content.
With governance, the creator already has structured weekly touchpoints, protected production blocks, and a documented protocol that makes onboarding a new client easier.
The crisis reveals the protocol’s value.
A new client arrives with a demanding communication style:
Without governance, the creator accommodates the new client’s defaults.
That trains the existing client base to expect the same access level.
With governance, the creator sends the Client Communication Norms Script during onboarding.
One document establishes the standard before a new pattern forms.
You need to take a 2-week break:
Without governance, the creator cannot step away without risking relationship deterioration.
With governance, clients already expect written async updates and one weekly call.
A 2-week absence supported by pre-scheduled async updates and rescheduled weekly calls can occur without relationship deterioration.
Why This Framework Works
The three components reduce call time by addressing three separate mechanisms that cause call accumulation.
Async-first removes the path of least resistance to a call.
Clients often request calls because a call appears to be the fastest way to get an answer. When async communication becomes faster than scheduling a call, call requests decrease without changing the client relationship. The mechanism is friction design.
The 25/50-minute rule prevents meetings from expanding to fill their time container.
A 60-minute meeting can become a 60-minute meeting even when only 40 minutes of content exists. The 25-minute slot creates scheduling pressure, while the 5-minute buffer changes closing behavior. The mechanism is time pressure as a behavioral governor.
Call consolidation removes the demand trigger that generates ad hoc calls. Without a standing weekly touchpoint, every client question becomes an immediate need. With a weekly container, questions accumulate on the agenda. The mechanism is deferred urgency.
All three mechanisms operate at the behavioral level. They change what clients and creators reach for, not merely what they are allowed to do.
Governance systems that restrict behavior get worked around. Systems that redesign the path of least resistance change behavior more consistently.
The 40–60% call-time reduction does not come from having fewer clients. It comes from three architectural changes that make the same client load sustainable.
The architecture is now defined. Install the Meeting Governance Protocol using the exact implementation sequence, time benchmarks, and output checks in the next section.
Installing the Meeting Governance Protocol in 30 Days
Every governance framework that does not produce a measurable reduction in call hours within 30 days is a plan, not a protocol.
Each step below includes a named output, time estimate, tool, and failure mode.
Total protocol time: 8–12 hours across 4 weeks.
Step 1: Run The Call Audit
Week 1, Days 1–2
Time: 60–90 minutes
Action:
Classify every recurring and ad hoc call from the last two weeks against the four categories:
Status update
Decision
Relationship maintenance
Complex problem-solving
Then flag each call as async-eligible or call-worthy.
How to execute:
Pull the last two weeks of calendar records.
List every call.
Write one sentence describing what the call actually covered, not what the meeting was called.
Apply the async-first classification.
Ask whether a written message would have produced the same outcome.
Flag the call as async-eligible or call-worthy.
Tool: Claude, available at claude.ai, for pattern recognition across multiple calls. Paste your list and use the call-classification prompt from What AI-Assisted Meeting Governance Looks Like.
Cost: Free.
Output:
A list of all recurring calls with their classifications, plus the total weekly call-hour count before and after reclassification.
A correct output might look like this:
- 8 of 14 weekly calls are async-eligible.
- 5 are standing status check-ins.
- 3 are approval calls.
- Reclassifying them as async recovers 3.5 hours per week.Failure mode:
If the audit takes longer than 90 minutes, you are trying to decide in the moment instead of applying the decision rule.
Apply the rule first: “Would a written message produce the same outcome?”
Only deliberate on calls where the answer is unclear.
Step 2: Implement The 25/50-Minute Rule
Week 1, Days 3–5
Time: 30 minutes
Action:
Reschedule every existing recurring call to either 25 or 50 minutes.
Do not contact clients yet. Reschedule the calendar entries and update your booking link if you use one.
How to execute:
For each call-worthy recurring call, apply the decision rule.
Schedule status reviews and single-decision calls for 25 minutes.
Schedule strategic or relationship calls for 50 minutes.
Update each calendar entry.
Add a 5- or 10-minute buffer block immediately after each call.
Tool: Calendar app. No additional software is required.
Cost: Free.
Output:
All recurring calls are rescheduled to 25 or 50 minutes, with buffer blocks in place.
Failure mode:
If the change takes longer than 30 minutes, you are deliberating about call length instead of applying the rule.
Default to 25 minutes when uncertain. You can extend a 25-minute call to 50 minutes when needed, but the default length shapes behavior over time.
Step 3: Write And Send The Client Communication Norms Script
Week 2
Time: 2–3 hours
Action:
Write a brief communication norms statement for each active client and deliver it in the format appropriate for the relationship.
How to execute:
Use the Client Communication Norms Script template in the toolkit.
Customize the language for each client.
Use a warmer tone for a 3-year client than for a 3-month client.
Keep the core message consistent: you have redesigned how you work to produce better output, calls are reserved for decisions and relationship maintenance, and async communication handles everything else.
Send the statement by email or raise it during the next weekly call.
Tool: Client Communication Norms Script from the toolkit. Email or direct message for delivery.
Output:
Every active client has received a written communication norms statement.
A correct output might look like this:
- Sent to all 4 active clients.
- Two replied acknowledging it.
- One asked what counts as “urgent.”
- One has not replied. I will reference the statement during our next call.Failure mode:
If the process takes longer than 3 hours, you are over-customizing the message for each client.
Use the template as the base. Change only the tone and 1–2 specific details that apply to each relationship. The core message remains the same across clients.
Step 4: Set Up The Weekly Call Rhythm
Week 2–3
Time: 1–2 hours
Action:
Define the standing agenda for every recurring client call and send it to each client with the next call invitation.
How to execute:
Use the 25-minute or 50-minute agenda template from the toolkit.
Create a recurring version for each client.
Include project status: what is complete, in progress, and coming next.
Include decisions needed that week.
Include anything else that requires attention.
Send the agenda 24 hours before the first structured call.
Tool: Agenda templates from the toolkit. Use Google Docs or Notion for the shared agenda document.
Output:
Every recurring client call has a written, shared agenda template, and the first structured call has been completed with each client.
Checkpoint:
You are ready to track progress when you can state:
Every recurring call is 25 or 50 minutes, has a written agenda sent 24 hours in advance, and covers decisions and relationship maintenance, not status updates.This Framework Across Three Creator Situations
Content strategist at $95K/year with 5 retainer clients:
The audit reveals that 11 of 16 weekly calls are async-eligible, including all standing status check-ins and approval calls.
She implements the 25/50-minute rule and call consolidation simultaneously.
She sends the communication norms statement to all 5 clients during Week 2.
Three clients adapt immediately.
One client pushes back: “I need more regular touchpoints.” The creator offers a 10-minute Monday async written update to replace the second weekly call, and the client accepts.
One client does not engage with the new format during Week 1 but adopts it naturally by Week 3 as the agenda is sent consistently.
By Week 4, total weekly call time falls from 17 hours to 7 hours.
Recovered production capacity: 10 hours per week.
Freelance copywriter at $80K/year with 3 clients and a course cohort:
The audit reveals that most async-eligible calls are weekly project-status calls with Clients 1 and 2.
The course cohort’s live session remains unchanged because teaching and relationship maintenance are both call-worthy.
He implements 25-minute structured calls for project status with Clients 1 and 2.
He keeps a 50-minute strategic call with Client 3 because it is a higher-complexity engagement.
He adds written weekly status updates for Clients 1 and 2 every Monday morning, replacing the status calls.
By Week 4, he recovers 6 hours per week.
He uses the recovered time to create a second course cohort, producing a direct revenue addition.
Brand consultant at $110K/year with 4 high-value clients:
Two clients have had ad hoc access for more than 18 months and consider it part of the service.
The consultant uses the staged approach from If the Damage Is Already Done.
Instead of introducing the communication norms statement immediately, she introduces it during Month 2 after demonstrating that the structured call format produces better output.
By Week 8, 3 of 4 clients have adapted.
One client continues testing the protocol during Weeks 5–6 by calling outside the scheduled slot.
The consultant responds asynchronously to the first two requests and schedules a brief call for the third, saying: “I want to make sure we cover this properly in our Thursday session.”
The client stops calling outside the scheduled slot during Week 7.
The call audit is the starting point, not the protocol. You cannot install governance before you know what you are governing.
Protocol Installation Check: Week 4 Readiness
Criteria:
Every active client has received the communication norms statement in writing.
All recurring calls run for 25 or 50 minutes, with a written agenda sent 24 hours in advance.
Weekly call hours are at least 30% below the pre-protocol baseline, confirmed by calendar data.
At least one communication type previously handled by call is now handled fully asynchronously.
Pass: all 4 criteria are met.
Fail: fewer than 4 criteria are met.
If you fail, stop. Do not move to validation before identifying the missing criterion.
A protocol with an uncontacted client, an agenda-free call, or no measurable reduction in call hours is only partially installed. Partial installations tend to drift back to the original pattern within 30 days.
Restart cost:
Another 8–12 hours of setup
Continued $225/day production loss during the gap
Premium Toolkit available for members (adjust)
The Offer Stack Pricing System includes:
Channel Resilience Audit — scores all 5 channels across pipeline contribution, risk exposure, and owned-vs-rented status, producing concentration risk score and ranked diversification action plan
Plug-and-play AI diagnosis sessions — drop into Claude, Gemini or ChatGPT, answer a few questions, save hours of guessing, get your exact next move
Audio key points — concentrated frameworks you can absorb in minutes, implement while you move
Unlock 750+ ready-to-use constraint toolkits — built to solve every business problem operators actually face.
Cancel anytime. Every download you’ve accessed stays with you.
A creator at $80K/year running a broken offer stack at $590/day in suppressed ascension revenue is losing $17,700/month in revenue the audience is positioned to generate but the pricing architecture prevents.
Validate Your Meeting Governance Protocol Before Implementation
Your Meeting Time Recovery Calculator
Use your actual numbers. Run this calculator before making governance decisions.
Pre-filled creator example:
- Scaling band
- 5 active client engagements
- Current weekly call hours: 17 hours
- Calls classified as async-eligible from the audit: 10 of 16 calls
- Current average call duration: 45 minutes
- Calls remaining after reclassification: 6 call-worthy calls per week
- Average duration after the 25/50-minute rule: 30 minutes, using a mix of 25- and 50-minute calls
- New weekly call hours: 3 hours
- Hours recovered per week: 14 hours
- Hours recovered per day based on a 5-day week: 2.8 hours, approximately 3 hours
- Daily reclaimed value at $75/hour: $225
- Annual reclaimed value based on 231 working days: $51,975, approximately $52KUnit Economics Of The Protocol
- One-time implementation cost: 8–12 hours of setup × $75/hour = $600–$900
- Annual reclaimed value: $52,000
- Payback period: less than 1 week of recovered deep work
- Return ratio: $52K ÷ $750 average setup cost = 69:1 in Year 1Scaling friction point:
The Meeting Governance Protocol reaches diminishing returns when the creator’s client count exceeds 8–10 active engagements.
At that point, even one fully optimized 25-minute structured call per client per week consumes 10 or more hours. The constraint shifts from call governance to client portfolio architecture.
The signal is clear:
You have run the full protocol.
Call hours are at minimum viable levels.
Production time is still insufficient.
That is a portfolio-size problem, not a governance problem. See Productized Service Architecture: Fixed Scope, Published Price for the next constraint.
Fill in your numbers:
- Current weekly call hours: _ hours
- Calls classified as async-eligible: _ of _ calls
- Calls remaining after reclassification: _ calls per week
- Average duration after the 25/50-minute rule: _ minutes
- New weekly call hours: _ hours
- Hours recovered per week: _ hours
- Hours recovered per day: _ hours
- Daily reclaimed value at $[hourly rate]/hour: $[amount]
- Annual reclaimed value based on 231 working days: $[amount]Run The Simulation Before You Build
Before sending the communication norms statement to any client, test the protocol on your most challenging relationship.
Starting scenario:
You have worked with the client for 2 years.
The client currently calls without scheduling.
The client expects same-day replies.
The client represents 30% of your annual revenue.
You are considering implementing the Meeting Governance Protocol.
Use Claude at claude.ai with this prompt:
I am implementing a new communication protocol with a long-term client who currently has informal access. The client represents a significant portion of my revenue.
I want to reduce ad hoc calls while maintaining the relationship.
Write a communication norms introduction message that:
- Positions the change as a service improvement.
- Defines what qualifies for a call versus async communication.
- Sets a 25-minute weekly standing call as the new touchpoint.
- Provides a clear path for urgent issues.
Tone: warm and direct.
Then identify:
- Likely client objections.
- A concise response to each objection.
- Any risks in introducing this change.
- Language that should be adjusted for a long-term, high-value client.The simulation surfaces:
The client objections you should expect.
Language that works for long-term, high-value relationships versus newer clients.
Whether your instinct to preserve ad hoc access is based on relationship necessity or an accommodation habit.
Two Futures
Without the protocol: 12-month trajectory
Call load remains at 14–18 hours per week.
Production blocks remain fragmented.
Deliverable quality slowly degrades as exhaustion compounds.
Client 3 says the work “hasn’t felt as sharp lately,” and you attribute it to a busy period.
By Month 6, you consider hiring an assistant or turning down new clients, not because you lack capacity, but because you cannot find enough production time to maintain your current standard.
By Month 12, revenue and client count remain unchanged, but deep work is still unavailable and service-quality risk continues to accumulate.
With the protocol: 12-month trajectory
Month 1: Call audit complete, the 25/50-minute rule implemented, and communication norms sent to all clients.
Month 2: Async-first default holding, with weekly call hours below 7.
Month 3: First full month with 3 or more uninterrupted production hours per day.
Deliverable quality improves, and Client 3 specifically says, “The work feels sharper.”
Month 6: Recovered production capacity is used to add a fourth client engagement or launch a course cohort.
Month 12: $52K in annual reclaimed production value, stronger service quality, intact client relationships, and room for expansion.
What Good Looks Like At Each Stage
Day 14:
Call audit complete, with every call classified.
25/50-minute rule implemented across all recurring calls.
Communication norms statement sent to at least 2 active clients.
Adjustment if below threshold:
You are deliberating about which clients to approach first. Start with the most accommodating client and build confidence with an easy relationship before approaching the most challenging one.
Week 4:
All active clients have received the communication norms statement.
Weekly call hours are measured and at least 30% below the pre-protocol level.
At least one async-eligible call type has moved fully async, such as delivering status updates as written summaries.
Adjustment if below threshold:
One or more clients have not acknowledged the protocol or are still calling ad hoc. Do not resend the script. Reference it during the next weekly call:
I want to make sure the communication format I described last week is working for you. Do you have any questions?A conversational reference usually lands better than a second written reminder.
Week 8:
Weekly call hours are 40–60% below the pre-protocol level.
At least 3 uninterrupted production hours are available per day on at least 3 days per week.
No client relationship has deteriorated, based on engagement quality and renewal or continuation signals.
Adjustment if below threshold:
If one specific client is still consuming disproportionate call time, the issue is no longer a protocol question. It is an engagement-terms question.
Review whether the current rate reflects the actual access level being provided.
If It Doesn’t Work: Roll Back And Retest
If a client relationship shows signs of deterioration after implementing the protocol, use a controlled adjustment rather than abandoning the system.
Revert step:
Add one 25-minute relationship call to the week. This is not a status call. It is specifically for relationship maintenance.
Ask:
I want to make sure the new communication format is working well for you. Is there anything that’s falling through the cracks?This reopens the feedback channel without abandoning the protocol.
Re-diagnosis:
Identify whether the deterioration is caused by:
Communication: the client does not feel informed.
Relationship: the client feels less valued.
Output quality: the deliverable standard has dropped independently of call frequency.
Each cause requires a different solution.
One-variable adjustment:
Do not relax the entire protocol because one element is not working. If status updates are not landing well in written form, improve the written format instead of reverting to a status call.
The written update template in the toolkit uses a 3-section structure covering what clients need to feel informed.
Retest timeline:
Give each adjustment 2 weeks before evaluating whether it works.
What This Framework Trains You To See
The Meeting Governance Protocol develops a pattern-recognition skill that extends beyond call management.
Early signal 1:
A client begins asking questions during the weekly call that belong on the agenda but were not added beforehand.
This signals that the agenda is not being populated between calls. Add a shared running document that the client can update throughout the week.
Early signal 2:
Weekly call hours begin creeping upward over 3–4 weeks.
Check for new clients who were not onboarded with the protocol or an existing client whose project has entered a high-complexity phase requiring a temporary increase in call frequency.
Early signal 3:
You continue working evenings or weekends despite reducing call hours.
The call reduction created production capacity, but a downstream constraint, such as scope creep or poor project scoping, is consuming it. The next diagnostic is project scoping, not call governance.
The recovery value is $52K/year only if the recovered hours remain protected for production instead of being immediately filled with new communication overhead.
The Async Adoption Timeline
The protocol installs in days. The client relationship adapts over weeks. Confusing these timelines is one of the most common reasons creators abandon the protocol too early.
Clients accustomed to frequent, informal calls do not immediately trust async communication. This is not necessarily resistance. It is learned behavior that developed over months and can take 3–4 weeks to replace.
Creators who expect immediate adaptation may break the protocol during Week 2 to accommodate a client who “needs” a call, resetting the adoption timeline.
Week 1: Introduce The Protocol And Explain The Rationale
Send the Client Communication Norms Script. Frame the change as a service improvement:
I’ve redesigned how I structure client communication to give you better output and more focused work on your behalf. Here’s what’s changing and what stays the same.What to expect:
Most clients acknowledge the change.
One or two clients remain silent.
One client asks what counts as urgent.
All of these responses are normal.
What not to do:
Do not pre-apologize for the change.
Do not say, “I’m sorry, but I need to…”
Do not frame the protocol as a personal limitation.
The protocol is a service-design decision, not a personal limitation. How you frame it affects how clients receive it.
Weeks 2–3: Clients Test The Boundary
Some clients will test the protocol during Weeks 2–3. A client who previously sent a “quick question” and received a call may try the same approach after receiving the communication norms statement.
This is not necessarily defiance. It is habit.
The protocol response:
Respond asynchronously.
Give a brief, warm, complete written answer.
Do not offer a call automatically.
Do not apologize for not calling.
If the question genuinely requires real-time exchange because it is complex or urgent, schedule a 25-minute call and describe it by its purpose:
This needs some back-and-forth. Let’s schedule a decision call on Thursday.The language matters. “Quick call” can mean anything. “Decision call” defines the purpose.
The rule that cannot be broken:
Do not take a call outside the scheduled protocol simply because a client “really needs” it. One exception teaches the client that the protocol has a workaround, and each subsequent test will move toward that workaround.
Creators who break the protocol once to accommodate a client reset the adoption timeline to Week 1.
Week 4: Most Clients Have Adapted
By Week 4, most clients have learned the new pattern:
Questions that previously triggered call requests arrive as messages.
Status-update calls have been replaced by written summaries.
The weekly structured call has a functioning agenda that clients populate between sessions.
One or two clients may still test the boundary during Week 4. The response remains the same: async by default and decision calls for genuinely complex needs.
A signal of full adoption is when a client sends a message that previously would have triggered a call request, then answers their own question in the next message 10 minutes later.
They have learned to think through the question before escalating it. That shift shows the protocol is working at the behavioral level.
What The Protocol Does Not Solve
The Meeting Governance Protocol solves call accumulation. It does not solve:
Scope creep that creates new communication overhead regardless of call governance.
Client relationships where the rate does not reflect the access level. These require an engagement-terms review, not better call management.
Production blocks filled with other tasks instead of deep work. Recovering 3 hours from calls is valuable only if those hours are used for production. See How To Protect Your Focus Time When You Are The Entire Company: The Deep Work Protocol for the next layer.
Breaking the protocol once to accommodate a client resets the adoption timeline. Consistency during Weeks 2–3 is what makes Week 4 work.
Running This System in Your Current Condition
Contraction
During a contraction period, revenue declines, client count drops, and pipeline anxiety increases. The Meeting Governance Protocol creates one specific risk: reverting to high availability as a retention strategy because “now isn’t the right time” to reduce call access.
That is the wrong trade.
Clients do not renew because their creator is always available. They renew because the work is high quality.
Call availability does not produce better work. It produces exhausted creators who deliver worse work. Reducing call hours during contraction protects the production capacity needed to deliver better output to the engagements that remain.
Minimum viable protocol during contraction:
Maintain the 25/50-minute rule.
Require a written agenda for every recurring call.
If current client pressure prevents full implementation of the async-first default, maintain format discipline.
Protect the buffer time and structured agenda, which are the highest-leverage individual elements of the protocol.
Signal that contraction is weakening the protocol:
You give a client informal call access “just until the project is done,” and the project remains “almost done” 6 weeks later.
Stability
During a stable period, revenue is predictable, the client load is manageable, and the operating rhythm functions reliably. The Meeting Governance Protocol’s specific amplifier is the meeting-free block.
Once call hours are reduced and the protocol is stable, decide where the recovered hours go. For creators in the Scaling band, the highest-leverage use is a defined daily deep-work block with at least 3 hours of uninterrupted production.
The meeting-free block is not, “I’ll use this time for production if nothing else comes up.” It is a calendar entry that:
Does not move for client requests.
Does not shrink for urgent items that can wait.
Does not fill with administrative tasks that could be batched elsewhere.
Drift signal:
If recovered production hours are consistently occupied by communication tasks instead of deliverables, the async-first default is not holding. Re-run the classification audit.
Expansion
During an expansion period, new clients arrive, revenue grows, and production demand increases. The Meeting Governance Protocol’s first failure point is onboarding new clients without the protocol.
A creator who reduces call hours with existing clients but adds 2 new clients without the communication norms statement can see call hours return to pre-protocol levels within 60 days. The new clients repeat the pattern that existed before governance was installed.
Guardrail:
Include the communication norms statement in every new client onboarding package.
Include the structured call format in the onboarding package.
Use the first call with each new client to introduce the protocol explicitly.
Present it as a standard of service, not a limitation.
Capacity signal requiring adjustment:
If weekly call hours rise despite the protocol being in place, the source is usually new clients who were not onboarded with the standard.
Identify which clients are outside the protocol and bring them into it within 2 weeks.
The Meeting Governance Protocol in the Creator Operating System
My Calendar Is Full of Meetings That Solved Nothing: The Async-First Operating System — provides deeper architecture for async-first operating model across all communication. Use this when building full async-first system beyond client calls.
The Communication Manifesto - Internal and External Response Protocols — provides internal operating standards making external norms sustainable. Use this when introducing and maintaining communication standards.
Project-or-Process Sort: How to Eliminate Client Status Update Emails — installs project governance layer alongside call governance. Use this when reducing status update requests.
How to Protect Your Focus Time When You Are the Entire Company - The Deep Work Protocol — protects recovered production capacity from other interruptions. Use this when reduced call hours create available deep work time.
Stop Wasting Your Weekly Meeting - The Level 10 Rhythm for Small Teams — structured cadence model informing 25/50-minute rule and weekly rhythm. Use this when adapting structured meeting methodology for solo creator-client relationships.
After implementing the Meeting Governance Protocol, track where the recovered hours go for 2 weeks.
If they consistently fill with communication tasks or administrative work instead of deep production, the next constraint is focus protection, not call governance.
Your Meeting Governance Fix Starts Now
What You’ll Be Able To Say At Week 8
My weekly call hours are below 7.
Every recurring client call is 25 or 50 minutes.
A written agenda is sent the day before every recurring call.
Async communication handles status updates, approvals, and non-urgent questions.
I have 3 hours of uninterrupted production time on at least 3 days per week.
Every active client relationship is intact.
Three Time-Boxed Actions
In the next 30 minutes:
Pull your calendar from the last two weeks.
List every call.
Write one sentence next to each call describing what was actually covered.
Mark each call as async-eligible or call-worthy.
Count the total hours.
You now have the audit that everything else builds from.
This week:
Reschedule every recurring client call to 25 or 50 minutes.
Add a 5- or 10-minute buffer block after each call.
Do not contact clients yet. Change only the calendar entries.
Run the call-classification prompt in Claude using your full call list.
Before next month:
Send the Client Communication Norms Script to every active client.
Use the template from the toolkit.
Customize the tone for each relationship.
Keep the core content identical.
Meeting Governance Progress Milestones
Milestone 1: Call audit complete - every recurring and ad-hoc call from the last two weeks is classified as async-eligible or call-worthy, with a total weekly hour count before and after reclassification
Milestone 2: 25/50-minute rule implemented across all recurring calls - no 30-minute or 60-minute calls remain on the schedule; buffer blocks in place after each call
Milestone 3: Communication norms statement sent to every active client and acknowledged by at least 3 of 4; first structured weekly call with written agenda completed with at least 2 clients
Milestone 4: Weekly call hours measured at 40%+ below pre-protocol level - confirmed by calendar data, not estimate
Milestone 5: Three or more uninterrupted production hours available on at least 3 days per week for 2 consecutive weeks - confirmed by blocking in calendar and protecting against interruption
If you take one thing from each section:
The meeting load consuming your production time did not begin as a problem. It accumulated through small accommodations that felt harmless individually.
The async-first default is not a communication preference. It is a diagnostic instrument showing which client relationships consume disproportionate communication overhead.
The 30-minute call is broken by design. It has no buffer and tends to run over, while the 25-minute call ends on time because its 5-minute buffer creates pressure to close.
Ad hoc calls do not necessarily happen because clients are demanding. They happen because there is no defined container for their questions.
The call audit is the starting point, not the protocol. You cannot install governance before you know what you are governing.
The recovery value is $52K/year only if the recovered hours remain protected for production instead of being filled with new communication overhead.
Breaking the protocol once to accommodate a client resets the adoption timeline. Consistency during Weeks 2–3 is what makes Week 4 work.
But if you remember only one thing:
The call schedule harming your output was not designed. It accumulated.
Governance does not remove your availability. It replaces the default pattern with one you chose deliberately.
Meeting Governance Protocol Checklist
Pull your last two weeks of calendar data before changing anything else.
☐ Audit every call from the last two weeks; classify each as async-eligible or call-worthy
☐ Reschedule all recurring calls to 25 or 50 minutes with buffer blocks after each
☐ Send the Client Communication Norms Script to every active client in writing
☐ Set a shared recurring agenda for every weekly client call; send 24 hours before
☐ Confirm weekly call hours are at least 30% below pre-protocol baseline by Week 4
When complete, every client relationship is intact and production blocks are protected.
FAQ: Meeting Governance Protocol
Q: How do I know if my call load is actually a problem worth fixing?
A: Run the two-week audit from the article. If more than 40% of your calls are status updates or approvals that could have been a written message, you are paying for a scheduling problem with your production time. The math is straightforward — at $75/hour, three recoverable hours per day is worth $52K annually.
Q: What if a client pushes back when I introduce the new communication protocol?
A: Client pushback in weeks 2–3 is normal and expected — it is habit, not defiance. Respond to off-protocol requests in writing, completely and warmly. Do not offer a call as a concession. One exception resets the adoption timeline to week one.
Q: Can I still take calls with clients when something genuinely urgent comes up?
A: Yes. The async-first default applies to roughly 80% of communication — status updates, approvals, and non-urgent questions. Genuine urgency warrants a 25-minute call, scheduled and named by purpose. The protocol trains clients to distinguish between what needs real-time exchange and what does not, which reduces urgency inflation over time.
Q: What is the difference between a 25-minute call and a 50-minute call under this framework?
A: A 25-minute call covers status reviews, single decisions, and brief check-ins where no extended problem-solving is needed. A 50-minute call covers strategic sessions, complex decisions, and relationship maintenance requiring depth.
Q: Do I need to apply this protocol to every client at the same time?
A: The framework works best when applied across all active clients within the same two-week window. Selective application creates an internal inconsistency — the creator who exempts one high-value client loses the deep work benefit on their highest-revenue engagement and signals to other clients that the protocol is negotiable.
Q: What happens to my weekly call hours once I have more than eight active clients?
A: The Meeting Governance Protocol reaches diminishing returns around eight to ten active engagements. Even a fully optimized 25-minute structured call per client per week at that count consumes ten or more hours.
Q: How do I handle a client who was never onboarded with the protocol when I add them mid-stream?
A: Send the Client Communication Norms Script at the start of the first working week together, not after the pattern has set. Frame it as your standard of service rather than a change.
Q: What if I run the protocol for four weeks and call hours don’t drop by 30%?
A: A partial installation is the most common cause.
Q: What should I do with the recovered production hours once the protocol is holding?
A: Protect them with the same calendar discipline as a client call. The highest-leverage use at the Scaling band is a defined daily deep work block — a minimum of three hours of uninterrupted production that does not move for client requests and does not fill with administrative tasks.
Q: Can I use AI tools to speed up the call audit and classification process?
A: Yes. The article recommends Claude for pattern recognition across multiple calls — paste your full call list with a one-sentence description of what each call actually covers and ask for async versus call-worthy classification with reasoning.
⚑ Found a Mistake or Broken Flow?
Spotted a math error, unclear framework, or broken link? Use this form to flag it — helps me keep the articles accurate and useful. Report a problem →
› More to Explore: Quick Navigation · Internet Solos and Creators
➜ Help Another Founder, Earn a Free Month
If the Meeting Governance Protocol just showed you how much deep work time your call schedule has been consuming, share it with one founder stuck in the same pattern.
When you refer 2 people using your personal link, you’ll automatically get 1 free month of premium as a thank-you.
Get your personal referral link and see your progress here: Referrals
Get The Meeting Governance Protocol Toolkit
You’ve read the system. Now implement it.
Premium gives you:
Ready-to-use PDF toolkit—every template, diagnostic, and formula pre-filled, zero setup, immediate use
Plug-and-play AI diagnosis sessions—drop into Claude, Gemini or ChatGPT, answer a few questions, save hours of guessing, get your exact next move
Audio key points—concentrated frameworks you can absorb in minutes, implement while you move
Unrestricted access to the complete library—every system, every update
What this prevents: Losing $52K/year in production capacity to unmanaged call accumulation.
What this costs: $49/month.
Download everything today. Implement this week. Cancel anytime, keep the downloads.
Already upgraded? Scroll down to download the PDF, audio, and your AI session.
