The Executive Summary
Creator operations at $60–$150K/year lose $12K–$20K per contractor departure, and 59% of full-time creators burned out in 2023. The Team Energy Protocol closes the governance gap.
Who this is for: Creators at $60–$150K/year managing one to two contractors with no energy tracking system in place
The governance problem: 59% of full-time creators burned out in 2023 (ConvertKit, n=1,004); burnout-related contractor departures cost $12K–$20K per exit from degraded output and replacement onboarding
What you’ll learn: Weekly Capacity Check, Workload Calibration, Recovery Protocols, Capacity Audit, Burnout Signal Identification
What changes if you apply it: Energy becomes a tracked number with defined thresholds and predetermined actions, not a feeling managed through conversation
Time to implement: Full protocol installs in 14 days; weekly check runs 15 minutes per week; capacity audit takes 3 hours total; recovery protocols scheduled in 30 minutes
Written by Nour Boustani for creators at $60–$150K/year who want to keep trained contractors and prevent burnout without managing the aftermath of a departure that already happened.
› Library Navigation: Quick Navigation · Internet Solos and Creators
Team Energy Protocol: Preventing Burnout Before It Costs You
Burnout in a creator business is not an emotional problem. It is a governance problem.
When 59% of full-time creators reported burnout in 2023, according to the ConvertKit 2024 State of the Creator Economy report (n=1,004), they were not necessarily failing because the work was too difficult. They were failing because no one in the operation was monitoring capacity against output: not the creator, not the contractor, and not anyone else.
The Team Energy Protocol is a three-layer governance system covering weekly energy scoring, workload calibration, and structured recovery. It prevents burnout by treating energy the way a real business treats cash flow: as a resource that must be tracked, protected, and replenished before it runs out.
For a Scaling-band creator earning $60,000–$150,000 per year and managing one to two contractors, the protocol installs in 14 days and can prevent the $12,000–$20,000 cost of a single burnout-related contractor departure.
Where are you with this right now?
“My contractor and I are both running on empty and the work quality is slipping.” You’re inside this constraint. The protocol below installs in the order that stops the bleeding first. Start at the Weekly Capacity Check.
“I don’t have a contractor yet — this is just me.” Creator-only energy governance is a different constraint covered in the energy management and sustainable creative rhythm frameworks. The Team Energy Protocol specifically governs operations with at least one active contractor. Return when that hire is in place.
“We burned out six months ago and I’ve been operating at reduced capacity ever since.” This is the recovery scenario. Start with The Recovery Protocol: When Governance Delays But Does Not Prevent Burnout before running the installation sequence. Attempting to install governance on top of active burnout compounds the problem rather than solving it.
Try This Now
Ask yourself and your contractor separately:
On a scale of 1–10, what is your average energy level across the last three weeks?
Write down the number before comparing your answers.
If either score is below 6, the intervention threshold has already been crossed. You do not need to finish reading this article before acting on that signal.
Burnout in a small creator operation rarely arrives as a crisis. It develops as gradual degradation that looks like a performance problem until it becomes expensive to address.
How Burnout Builds in a Creator Business
The failure mechanism is specific.
A creator in the Scaling band adds a contractor, typically their first hire. Both begin at a pace that feels sustainable during the first week. The creator is still doing most of the heavy lifting while the contractor is ramping up.
Over time, the workload grows faster than the systems needed to manage it. Neither person says anything because both assume the pressure is temporary.
By week eight, the signs are visible:
Missed deadlines.
Output that requires more revision than it saves.
Shorter fuses on calls.
Creative work that feels mechanical.
The creator attributes the problem to contractor underperformance. The contractor attributes it to unclear direction.
Both diagnoses are wrong. The actual cause is structural: nobody tracked energy against capacity, so nobody saw the problem building until it became expensive.
What Is Actually Happening
The pattern is consistent across creator types at this revenue stage.
Newsletter Creator: $85K Per Year
A newsletter creator hires a part-time contractor to handle content repurposing and scheduling. The first two months go smoothly. By month three, the contractor is handling tasks beyond the original scope, with each addition seeming reasonable on its own.
The creator is now spending 3–4 hours per week correcting contractor output that previously took 45 minutes. Weekly content falls behind, so the creator works evenings to compensate.
The contractor notices the tension and begins second-guessing every deliverable. By month four, the creator is considering firing the contractor, not because the contractor is wrong for the role, but because over-capacity has degraded the work and damaged the relationship.
The replacement cost includes:
4–8 weeks of onboarding for the next hire.
6 weeks of degraded output while the operation runs short-staffed.
High-Ticket Coach: $110K Per Year
A high-ticket coach runs a two-person team: herself and an operations contractor who manages scheduling, client onboarding, and follow-ups.
Both operate at peak capacity for a full quarter without structured recovery. Because revenue is strong, the coach takes on two additional clients.
The contractor absorbs the added administrative load without flagging the strain. By week ten, the coach’s energy score, if anyone had been tracking it, would be 4.
She is delivering coaching sessions on four hours of sleep, producing client work she is not proud of, and dreading the calendar she once protected carefully.
Three weeks later, the contractor resigns, citing “poor communication and unclear expectations.”
The estimated cost is:
$2,000 per month for the contractor.
6 weeks of degraded output.
Onboarding and replacement time.
$12K–$20K in recoverable cost from one departure that a governance protocol could have prevented.
Course Creator: $75K Per Year
A course creator has a contractor managing community moderation and student support. The course launches on schedule, and enrollment exceeds projections.
The contractor’s workload triples in two weeks. No one recalibrates the workload, and no existing work is removed to make room for the surge.
The contractor begins responding to community posts with shorter, less thoughtful answers. Students notice, and refund requests increase.
The creator interprets the refunds as a product-quality problem and launches a full content audit. That is the wrong diagnosis for a capacity problem.
The Structural Failure
All three examples share the same underlying failure:
No one monitored energy against capacity.
Workload increased without recalibration.
No recovery time was built into the operating system.
Performance symptoms were mistaken for individual problems.
The operation had no system for detecting strain before it damaged output or the working relationship.
THE BURNOUT ARRIVAL PATTERN
Week 1-4: Both at capacity
No signal visible yet
|
v
Week 5-8: Workload creep
Small additions, no removals
|
v
Week 9-12: Degradation begins
Output quality drops
Tension increases
|
v
Week 13+: Crisis visible
Departure, breakdown,
or forced reset
Cost: $12K-$20KBy the time the crisis becomes visible, the recoverable cost has already compounded through months of degraded output, strained relationships, and creative work that does not reflect what either person can actually produce.
Single Points of Failure And What to Build Instead
The Team Energy Protocol has three built-in vulnerabilities. Identify them before installation so they do not silently weaken the governance system.
SPOF 1: Single-Person Honest Reporting
The protocol depends on both parties scoring themselves accurately. If one person reports honestly while the other scores upward to protect the relationship, avoid appearing weak, or because they have normalized being at 5, the system shows green while one person is declining.
Redundancy protocol:
Add one observable behavioral signal to the weekly check alongside the energy score.
Review one piece of contractor work against a defined quality standard.
Track response latency, measured as the time between a message being sent and answered.
These leading indicators do not rely on self-reporting. Two data streams are harder to manage than one.
SPOF 2: Capacity Audit Run Once
The ceiling defined on Day 3 becomes outdated as scope drifts. An operation that runs the audit once in month one and never repeats it may have an accurate capacity ceiling for approximately 90 days before scope creep makes the number unreliable.
Redundancy protocol:
Re-run the capacity audit every 90 days, regardless of current energy scores.
Schedule the re-audit on the same day as the first planned no-meeting week of each quarter.
This pairing ensures that the audit happens during a low-pressure window, when estimates are more accurate.
SPOF 3: Recovery Protocols Treated as Optional
The quarterly no-meeting week and async week work only when protected. If the operation treats them as adjustable based on client demand, they will be overridden during every high-demand quarter, which is exactly when they are most needed.
Redundancy protocol:
Communicate recovery weeks to clients as fixed infrastructure, not personal time.
Use language such as: “My team operates on a quarterly async cadence. These weeks are scheduled a year in advance.”
“My team operates on a quarterly async cadence” creates a fixed operating expectation. “I’m taking a lighter week” invites negotiation.
The Advice That Made It Worse
The most damaging advice in small-team creator management is: “Communicate more openly with your contractor.”
A contractor who is already over capacity and stressed may not have the cognitive bandwidth to diagnose or clearly communicate their own burnout. The creator may be overloaded as well. This advice places responsibility for identifying a structural problem on the people least equipped to see it clearly while they are inside it.
More communication is a tactic. It addresses the symptom.
The structural cause is that no one defined maximum sustainable output per role before over-capacity began. No one built a mechanism to track whether output was approaching or exceeding that ceiling.
When the ceiling has no number attached to it, “communicate more” produces uncomfortable check-ins that do not change the workload or prevent the outcome.
The protocol that works does not ask people to communicate more clearly about their stress. It creates a weekly mechanism that produces an energy score and defines in advance what that score requires.
The Real Cost Of Burnout
The ConvertKit 2024 State of the Creator Economy report found that 59% of full-time creators experienced burnout in 2023. At the Scaling band, the financial structure makes burnout particularly expensive.
A two-person creator operation with one contractor earning $2,000 per month that experiences a burnout-related departure faces:
4–8 weeks of onboarding for the replacement hire.
6 weeks of degraded output while the operation is understaffed.
4–6 weeks of reduced creative capacity for the creator after a sustained over-capacity period.
At the conservative end, the estimated cost is:
6 weeks of degraded output at a creator operation generating $6,000–$10,000 per month: $8,400–$14,000 in revenue impact from reduced delivery quality and capacity.
Replacement contractor onboarding: 20–30 hours of creator time at a $75 per hour equivalent, or $1,500–$2,250.
Total recoverable cost of one departure: $12K–$20K.
The Daily Cost Of Operating Without Governance
For creator operations without energy governance, a burnout-related departure occurs once every 12–18 months, based on the ConvertKit burnout data applied to small-team turnover patterns.
Amortized across 260 working days:
$12,000 ÷ 260 days = $46 per day at the conservative end.
$20,000 ÷ 260 days = $77 per day at the high end.
Every working day without a governance protocol in place carries $46–$77 in burnout risk. That risk compounds until it becomes a preventable departure.
Calculate Your Single-Departure Cost
Use this formula:
Contractor monthly rate × 6 weeks of degraded output ÷ 4.3 weeks per month + Replacement onboarding hours × $75 = Your single-departure costUnderstand The Retention Payback
A trained contractor who stays becomes a compounding asset. After 12 months in the role, the contractor typically produces higher-quality output with less creator time per task than a new hire who is still ramping up.
At the Scaling band, the true customer acquisition cost of a contractor hire includes:
Recruiting time.
Onboarding hours.
Creator time invested in training the contractor to full productivity.
Estimated total cost: $3,000–$6,000.
A contractor retained for 24 months instead of 12 generates that acquisition cost once instead of twice. Retention alone therefore creates a 2× payback improvement.
The governance protocol requires approximately 10 hours to install. Preventing one replacement cycle pays back that installation cost. Every retained quarter afterward creates additional leverage from the original investment.
Stage Filter: When This Framework Applies
This framework is specific to the Scaling band, defined as $60K–$150K per year, and applies to creators with at least one active contractor.
At this stage, creators experiencing team burnout often frame the problem as a personnel issue:
The contractor is wrong for the role.
The creator’s management approach is the problem.
Communication needs to improve.
The structural pattern in creator operations that successfully prevent burnout is different. The solution is an energy governance protocol installed before degradation begins.
Creators without contractors are facing a solo capacity problem, not a team governance problem. That constraint is addressed in the energy management and sustainable creative rhythm frameworks.
If The Damage Is Already Done
The correct intervention depends on how far the operation has progressed into the failure cycle.
Within 30 Days
If energy scores are below 6 but the contractor has not resigned and output quality is only beginning to decline:
Install the weekly energy check and capacity audit simultaneously.
Do not add new work until the audit shows that current capacity is sustainable.
Expected stabilization time: 2–3 weeks.
Within 30–90 Days
If the contractor has indicated they are overwhelmed or the creator has experienced one missed deliverable cycle:
Reduce the workload before installing the full protocol.
Identify the lowest-value task in the contractor’s current scope.
Remove that task immediately.
Run the capacity audit after the workload has been reduced.
Allow 4–6 weeks for energy scores to return to a sustainable range.
Estimated cost already incurred:
Approximately $3,000–$5,000 in reduced output quality and strained relationship capital.
After 90 Days
If the contractor has departed or is actively serving notice:
Run the recovery protocol from Structured Recovery Before Rebuilding Governance first.
Do not attempt to install governance while the operation is actively understaffed.
Rebuild the team before installing governance.
Install the protocol on day one of the new contractor’s onboarding, not three months later after the same pattern has begun again.
Estimated cost already incurred:
$12K–$20K.
The only recoverable variable at this stage is preventing the cycle from repeating.
The Governing Diagnosis
Burnout in a small creator operation is a governance failure, not a personnel failure. The difference between those diagnoses determines whether the fix costs two weeks or $20,000.
The failure mechanism is structural. The framework that closes it is structural as well: three governance layers that make capacity visible before it collapses.
The next section, Weekly Energy Scoring, covers the first layer in full.
The Team Energy Protocol: Three Layers That Keep A Small Creator Operation Functional
Energy in a two-person creator operation behaves like cash in a business. You can run a deficit for a while before the consequences appear, but when they do, they arrive quickly and become expensive.
The Team Energy Protocol treats energy as a tracked resource. It is not a feeling to manage through better communication. It is a number, a threshold, and a protocol that defines the action required at each score.
The three layers install in sequence:
The first layer makes energy visible.
The second layer defines the capacity ceiling before it is breached.
The third layer builds recovery into the schedule before recovery becomes forced.
Layer 1: The Weekly Capacity Check Makes Energy A Number
The weekly capacity check is a five-minute, end-of-week ritual that produces one energy score from 1–10 for each team member. Each person completes the check independently and records the answers before comparing them.
When a creator asks a contractor, “How are you doing?” at the end of a long week, the contractor may answer based on what they think the creator wants to hear or on how much they believe the creator is struggling.
The honest answer, such as “I’m at a 4 and I haven’t been sleeping,” requires psychological safety that many contractor relationships have not yet built. It also requires the contractor to deliver difficult news to someone whose perception affects their continued employment.
Completing the check independently removes some of that social pressure. Both people answer the same five questions about their own experience, record their scores, and then compare the results.
The five questions:
Energy level this week (1–10): How much capacity do you have left compared with a fully rested version of yourself?
Output quality (1–10): How satisfied are you with what you produced this week? Rate what you actually created, not only what was delivered.
Cognitive load (1–10, inverted): How heavy did the work feel? A score of 10 means light; a score of 1 means crushing. Did you have mental space to make good decisions, or were you reacting all week?
Recovery signal (yes/no): Did you have at least one full day this week when you did not think about work?
Flags (open field): Is there anything in next week’s scope that you are worried will not get done or will not get done well?
Scoring thresholds:
7–10: Sustainable. No intervention is required. Record the number and continue.
5–6: Warning. One week at this level is normal. Two consecutive weeks are a signal. Three consecutive weeks require an active response.
Below 5: Immediate response required. Remove work this week, not next week or after the current deliverable cycle closes.
Worked example:
A course creator earning $75K per year runs the weekly check on Friday afternoon.
Week 1: Creator score = 6; contractor score = 5.
Week 2: Creator score = 5; contractor score = 4.
Intervention: The contractor’s score below 5 triggers the intervention threshold. The creator removes the lowest-value task from the following week’s scope: a social media repurposing batch that can be skipped once without consequences.
Following Friday: Contractor score = 7.
The intervention cost was one skipped repurposing cycle. The prevention value was stopping the trajectory before it reached the contractor-departure threshold.
The three-consecutive-weeks rule:
Three weeks at or below 6 for either team member require an intervention, even if none of the scores dropped below 5.
A score of 6 on its own is not a crisis.
Three consecutive weeks at 6 indicate that the operation is running at sustained over-capacity.
The team is burning out slowly, and a departure is becoming more likely.
Quick signal:
Review your contractor’s output from last week and assess it honestly. Would you have produced the same work yourself during a good week?
If the answer is no, and you can see the shortcuts, reduced effort, or slightly lower standard, the energy score for that week was likely below 6. Output quality is a lagging indicator of the energy score you did not track.
Layer 2: Workload Calibration Defines The Capacity Ceiling
The second layer defines the maximum sustainable output for each role before workload exceeds capacity.
Most creator operations do not experience a sudden workload spike. They experience workload creep: a gradual accumulation of small additions that seem reasonable individually but collectively push both roles beyond sustainable capacity.
Workload calibration prevents this by establishing a number in advance:
Maximum sustainable weekly output for each role.
Available hours for the role.
Specific task categories included in the scope.
Verification by the person performing the work, not an estimate from the person assigning it.
The calibration process:
Each team member lists every recurring task in their current scope. List what they actually do each week, not only what they were hired to do.
Each person estimates the actual time required for every task. Include back-and-forth communication, revision cycles, and transition costs between tasks. Do not use ideal or theoretical times.
Add the hours together. Compare the total with the contracted or available hours per week.
Check for over-capacity. If the actual total exceeds available hours by more than 10%, the operation is already over capacity. Remove work before adding anything new.
Define the capacity ceiling. Maximum sustainable output = available hours − 15% buffer.
The 15% buffer is not padding. It is the capacity required to handle unexpected events, such as a client revision request, a technical problem, or a week when personal responsibilities demand time.
Operations that budget 100% of available hours have no capacity for variability. They eventually snap.
The Workload Calibration Rule
New work may be added only when existing work is removed or compressed.
Make that decision before the new work begins:
Not after the current deliverable cycle.
Not when things slow down.
Not after the workload becomes difficult to manage.
This rule can feel counterintuitive when the creator is growing revenue. The instinct is that growth justifies more work.
The governance principle is different: growth requires more capacity. That means adding people or removing scope, not adding work to roles that are already calibrated to their ceiling.
Worked Example: Newsletter Creator At $85K Per Year
A newsletter creator has a contractor handling:
Content repurposing: 8 hours per week.
Email scheduling: 3 hours per week.
Social media posting: 4 hours per week.
The contractor is contracted for 20 hours per week.
Total recurring scope: 15 hours.
Available buffer: 5 hours, or 25%.
Initial assessment: The buffer appears healthy.
The creator launches a new lead magnet series and asks the contractor to handle distribution coordination, described as “just a couple hours per week.”
Week one is manageable. In week two, the launch requires more coordination than expected. Distribution takes 8 hours, leaving only 12 hours for the existing 15-hour scope.
Three existing tasks are compressed, and quality drops.
The calibration protocol would have required removing one existing task before adding distribution coordination. One week without social media repurposing costs the creator almost nothing. Six weeks of degraded output costs significantly more.
Decision Rules For Adding Work
If adding new work:
Name the specific task being removed or compressed in the same conversation where the new work is introduced.
Do not leave the scope reduction as a separate follow-up.
If the creator absorbs the new work themselves:
Apply the creator’s workload calibration using the same rules.
Do not exempt the creator from the capacity ceiling.
Creators who exempt themselves from capacity limits are one of the most common burnout patterns at the Scaling band.
Edge Case: Launch Periods
Define launch capacity in advance:
How many additional hours does the launch require from each role?
What work will pause during the launch to create that capacity?
Which deliverables will be delayed, reduced, or removed?
If the answer is “nothing gets paused,” the launch plan is incomplete.
Layer 3: Recovery Protocols Build Rest Into The Schedule
The third layer is the most commonly skipped and the most structurally important.
Scheduled recovery costs nothing. Recovery forced by a burnout event costs $12K–$20K.
The three recovery protocols operate on a quarterly cadence.
Protocol 1: One no-meeting week per quarter
Schedule one week every quarter with no synchronous calls, check-ins, or live sessions for the creator or contractor.
Work continues, but communication happens asynchronously. Scheduled interruptions create cognitive load, even when they are useful. A no-meeting week removes that accumulation for five days without reducing output.
Protocol 2: One async week per quarter
Schedule one week every quarter when all communication moves to async-only:
No Slack.
No direct messages.
No real-time responses required.
This protocol is distinct from the no-meeting week and does not have to occur during the same week. The two weeks may coincide or take place during different weeks in the quarter.
The async week allows both people to work in uninterrupted blocks, protecting the deep work that burnout degrades first.
Protocol 3: No delivery commitments during the final week of each month
Schedule the final week of every month with zero external delivery commitments:
No client deliverables.
No published pieces.
No live content requiring both parties to be fully present and performing.
Reserve the final week for maintenance:
Finish work in progress.
Prepare the following month’s schedule.
Run the capacity audit.
This protocol prevents sustained delivery sprints in which every week becomes a deadline week.
Worked Example: High-Ticket Coach At $110K Per Year
A high-ticket coach earning $110K per year runs a two-person team and implements all three protocols.
The Q2 no-meeting week falls in the second week of May because the client renewal cycle runs in April and the first week of May is consistently high-demand.
The async week falls in the third week of June.
The month-end buffer has been scheduled for two quarters.
In the previous year, before the protocols were installed, the contractor left in June, citing an “unsustainable pace.”
In the year with the protocols in place, the contractor scores above 7 in every weekly check from April through June, historically the highest-burnout window in the operation.
Protect The Recovery Schedule
Recovery protocols work only when protected.
A no-meeting week overridden by “just one important call” is no longer a no-meeting week. Communicate the protocol to clients before it begins:
My team has a scheduled async week during that period. I’ll be available via email with a 24-hour response window.
Treating the protocol as optional trains everyone in the creator’s ecosystem to treat it as negotiable.
What This Framework Teaches
The Team Energy Protocol teaches one transferable principle: capacity is a budget, and like any budget, it must be managed before it runs out, not after.
Creators who internalize this principle stop treating energy as a renewable resource that will automatically return with enough motivation. They also stop treating contractor fatigue as a management or communication problem.
Instead, they ask at the beginning of every week:
What is our capacity this week?
What is our ceiling?
Does the current scope fit?
That question, asked before the work begins and supported by a number, is the entire discipline.
The five-question energy check, workload calibration formula, and quarterly recovery cadence are mechanisms for making the question answerable without requiring either person to initiate a difficult emotional conversation.
Why The Team Energy Protocol Works
The Team Energy Protocol produces more consistent burnout prevention than informal check-ins because it translates subjective experience into an actionable number. That removes some of the social negotiation that makes honest reporting difficult.
When a creator asks a contractor, “How are you doing?” the contractor may calculate:
How much is the creator struggling?
What does the creator need from me right now?
Will an honest answer make me seem less capable or committed?
The answer that emerges from that calculation is often managed rather than accurate.
A 1–10 scale with defined thresholds changes the interaction. The contractor is not being asked to assess the creator’s capacity for difficult news. They are being asked to provide a number.
That number has a predetermined meaning:
Below 5 requires action.
Three consecutive weeks at 6 require review.
No one has to decide in the moment how serious the situation is or what it demands. The protocol determines the response. The people provide the input.
The second mechanism is workload concreteness. Most burnout spirals remain invisible because over-capacity accumulates gradually and never feels like one decision that could have been made differently.
The capacity audit makes the ceiling visible:
- Maximum sustainable capacity = available hours × 0.85When the actual scope exceeds that number, over-capacity is no longer only a feeling. It is arithmetic, and arithmetic creates a clearer basis for action.
Together, honest reporting through scoring and visible ceilings through arithmetic explain why the protocol addresses the type of burnout that informal communication and good intentions often fail to prevent.
What AI-Assisted Team Energy Governance Looks Like
Manual capacity tracking involves maintaining a weekly energy log, comparing scores with workload data, and identifying patterns. Across both team members, this takes 2–3 hours per month.
AI-assisted governance reduces the pattern-identification work to 15–20 minutes per month.
The highest-value use case is identifying the earliest signal of a burnout trajectory before it reaches the three-week threshold.
Tool: Claude, available at claude.ai.
Copy and paste this prompt:
Here are the last four weeks of energy scores for my team:
- Creator scores: [enter scores]
- Contractor scores: [enter scores]
- Here is the current scope for each role:
- [List each task and the hours required]
Analyze the information and provide:
1. Whether either person shows a declining trend, even if no single week is below the intervention threshold.
2. Whether the total scope hours for each role fall within the sustainable capacity ceiling, calculated as available hours minus 15%.
3. The single task to remove from the lowest-scoring person’s scope this week if the trend continues for one more week.
- Show the calculations, identify the relevant threshold, and state the recommended action clearly.AI-assisted review can identify:
Gradual declines that do not cross a threshold in any single week but show a consistent downward slope across four weeks.
Scope creep in which individual additions are small but the total workload quietly exceeds the capacity ceiling.
Asymmetric workload distribution in which one role is at 90% capacity and another is at 50%, creating friction without either person naming it as a workload problem.
The time difference is significant:
Manual tracking and analysis: 2–3 hours per month.
AI-assisted pattern identification: 15–20 minutes per month.
The speed gap matters because the earliest intervention is usually the cheapest.
An energy decline identified in week two may require removing one task. The same decline identified in week eight may result in a contractor departure.
The energy check does not prevent every form of burnout. It prevents the kind that develops slowly while both people are too tired to notice it.
Creators can lose trained contractors to burnout that a weekly five-minute check might have exposed earlier. In those cases, the relationship was not necessarily the first thing to break down. The missing governance was.
A score of 4 on a Friday morning is solvable. A resignation letter on a Monday is not.
Premium Toolkit available for members
The Team Energy Protocol includes:
Weekly Energy Check Template — spot declining energy early with weekly scores and clear action thresholds.
Capacity Audit Template — compare actual workloads with sustainable capacity before scope creep damages output.
Burnout Signal Identification Guide — recognize when a capacity conversation or immediate work removal is needed.
Intervention Protocol — respond to sustained low scores before a contractor departure becomes the only reset.
Sustainable Output Definition Worksheet — set a realistic ceiling for each role so new work doesn’t silently overload the team.
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.
Catch overload before it costs a trained contractor and an estimated $12K–$20K in degraded output and replacement effort.
Cancel anytime. Every download you’ve accessed stays with you.
This toolkit is for Scaling-band creators ($60-150K/year) with at least one active contractor who want to prevent burnout before it becomes a departure, not manage the aftermath of one that already happened.
If you’re still operating solo, the energy governance frameworks in Stop Running Empty: The Energy Management Audit for Solo Business Owners address the creator-only capacity constraint first.
The complete system to keep a small creator operation functional — before the energy score tells you it’s too late.
One thing from this section:
The Team Energy Protocol doesn’t prevent burnout through willpower or communication — it prevents it by making capacity a number that triggers a specific action before the decline becomes irreversible.
The protocol is defined. The next section covers the installation sequence, from the first energy check to a fully calibrated operation, with time benchmarks and specific outputs at every step.
Installing The Team Energy Protocol In 14 Days
The protocol does not ask either person to work less. It asks the operation to know its ceiling and stay below it.
Each step below has a named output, time estimate, and failure mode. For a Scaling-band creator with one active contractor, installation takes 14 days from the first energy check to running governance.
Step 1: Run The First Energy Check
Day 1: 15 minutes
Action:
Both the creator and contractor complete the five-question energy score independently.
Compare the numbers only after both scores have been recorded.
How to execute:
Send the contractor the five questions as a written form.
Do not send them as a Slack message or conduct the check as a verbal conversation.
Both parties complete the form before the weekly review call.
During the call, share numbers only. Do not discuss explanations or justifications.
Ask: “Is there anything in next week’s scope that you’re worried about?”
Tool:
The Weekly Energy Check Template (PDF).
A shared notes document works for the first session before the PDF is available.
Cost: Free.
Time: 15 minutes for both parties combined.
Output:
Two energy scores.
One open-field flag from each person.
A baseline energy score for week one.
Correct output:
Both scores are written down before the conversation.
Neither person negotiates or defends their score.
If either score is below 5, the intervention decision is made during this session.
Failure mode:
If the session takes longer than 15 minutes, it has moved from scoring into problem-solving.
Stop the discussion.
Treat the first session as a baseline only.
Address problem-solving in Step 2.
The purpose of this session is to record the scores.
Step 2: Run The Capacity Audit
Days 2–3: 3 hours total
Action:
Each team member independently lists every recurring task in their current scope.
Estimate the actual time required for each task.
Total the hours and compare them with available hours.
How to execute:
Complete the audits separately.
List what each person actually did last week, not what they were supposed to do.
Include coordination tasks, revision cycles, and transitions between tasks.
Estimate each task in 15-minute increments.
Compare the total with contracted or available hours.
Tool:
The Capacity Audit Template (PDF).
A blank spreadsheet works for the first pass before the PDF is available.
Cost: Free.
Time:
90 minutes per person for the separate audits.
30 minutes to compare the results.
Output:
Total actual hours per role.
Comparison with available hours.
Identification of whether either role exceeds the sustainable ceiling.
Sustainable capacity ceiling:
- Available hours − 15% bufferCorrect output:
Every listed task has a realistic time estimate approved by the person performing it.
If the creator disputes an estimate, the person doing the task has the stronger evidence.
The creator’s estimate does not override the contractor’s actual time data.
Failure mode:
If either role exceeds the ceiling, remove the lowest-value task before the audit conversation ends.
Do not wait until the current deliverables are complete.
Name the task being removed.
Name the week when it will be removed.
Finish the decision before ending the conversation.
Step 3: Define Maximum Sustainable Output Per Role
Day 3–4: 2 hours
Action:
Use the capacity audit data to define the maximum sustainable weekly output for each role.
Express the ceiling in hours and specific task categories.
How to execute:
Take the total available hours for each role.
Multiply the available hours by 0.85.
Treat that result as the sustainable capacity ceiling.
Document every task category that fits within the ceiling.
Remove an existing task before adding any work that would push the total scope above the ceiling.
Tool:
The Sustainable Output Definition Worksheet (PDF).
Cost: Free.
Time: 2 hours.
Output:
A written capacity ceiling for each role.
A task list that fits within each ceiling.
A documented rule: new work enters only when existing work exits.
Correct output:
Both parties can answer, “What is your maximum weekly output?” with a number of hours and a task list.
If either person answers, “It depends on the week,” the ceiling has not been defined clearly enough.
Step 4: Schedule The Recovery Protocols
Day 5: 30 minutes
Action:
Place all three quarterly recovery protocols in the shared calendar for the next 12 months.
How to execute:
Open the shared calendar.
Schedule one no-meeting week in each quarter.
Choose a genuinely low-demand week, not the week before a launch or a week with a client deadline.
Schedule one async week in each quarter. It can occur during the same week as the no-meeting week or during a different week.
Mark the final week of every month as “no external delivery commitments.”
Add the note: “Maintenance and preparation only.”
Tool:
Any calendar. Google Calendar works.
The calendar entries are the output, not a plan to add them later.
Cost: Free.
Time: 30 minutes.
Output:
Twelve months of recovery protocols visible in the calendar.
Confirmation from both parties.
Correct output:
The creator and contractor can see all recovery weeks in their calendars.
Any client-facing deadline scheduled during a recovery week is moved before this step is complete.
Step 5: Run The Weekly Check For Four Consecutive Weeks
Days 7–28: 15 minutes per week
Action:
Run the five-question energy check every Friday.
Record and compare the scores.
Trigger a workload calibration review immediately if either score is below 5.
Trigger a workload calibration review if either score is 6 or below for two consecutive weeks.
How to execute:
Set a recurring Friday calendar event for both parties labeled “Weekly Energy Check.”
Send the form at the same time every week, preferably Friday morning before the week is complete.
Share scores on the call or through an asynchronous message.
Record the numbers and any flags. No additional processing is required.
Tool:
The Weekly Energy Check Template (PDF).
Use one form per team member per week.
Cost: Free.
Time: 15 minutes per week.
Output:
Four weeks of energy scores.
A baseline trend.
Confirmation that both parties understand the threshold rules and will act on them.
Correct output:
Four consecutive weeks of documented scores for both parties.
If a flag resulted in action, record the action beside the relevant score.
Examples of action include removing work or compressing a task.
Apply The Framework Across Three Creator Situations
Newsletter creator at $85K per year:
One contractor handles repurposing and scheduling.
The capacity audit in Step 2 will often show that the contractor is closer to the sustainable ceiling than expected.
Repurposing tasks expand with content volume, while the hours may not have been recalibrated since the contractor was hired.
The no-meeting week is the highest-leverage recovery protocol because newsletter operations rely on consistent communication rhythms, and interruption costs are high.
Target energy scores during the first four weeks: both parties at 7 or higher before introducing new scope.
High-ticket coach at $110K per year:
One operations contractor manages scheduling and onboarding.
Launch periods create demand spikes that may not appear in the regular weekly check because they occur infrequently.
Add a launch-specific capacity protocol.
Before each launch, define which tasks pause during the four-week launch window and who is affected.
The default rule is to pause all non-essential administrative tasks for the contractor during the launch.
The creator defines what is essential in advance. The contractor does not have to determine it during the launch.
Course creator at $75K per year:
One contractor manages community and student support.
Community moderation creates an energy drain that hours alone do not capture.
The work requires sustained emotional availability, including reading community mood, managing student frustration, and handling escalations.
Standard capacity audits can understate the actual drain.
Apply a 1.25× cognitive load modifier to community and support tasks when calculating the capacity ceiling.
A contractor spending 12 hours per week on community moderation is carrying a 15-hour equivalent cognitive load.
Checkpoint: Confirm The Protocol Is Installed
By the end of Day 14, these four items must exist:
Two weeks of documented energy scores for both team members.
A completed capacity audit for both roles, with the ceilings defined in writing.
Maximum sustainable output per role agreed upon and documented.
Recovery protocols scheduled on the calendar for the next 12 months.
If any item is missing after 14 days, the protocol has been discussed but not installed.
That distinction matters because only the installed version prevents the $12K–$20K departure.
Protocol Installation Checkpoint
Energy scores documented: 2 consecutive weeks for both team members
Capacity audit complete: both roles, ceilings in writing
Maximum sustainable output agreed: hours and task categories documented
Recovery protocols scheduled: 12 months in calendar
PASS: All four criteria are met by Day 14.
FAIL: Any criterion is missing.
If the result is FAIL:
Do not add new scope to either role.
Install the missing checkpoint criteria first.
Do not add tasks to an uncalibrated operation. Each additional task pushes both parties closer to the departure threshold.
The protocol is installed only when four specific outputs exist in writing:
Energy scores.
Capacity ceilings.
Sustainable output definitions.
Recovery protocols scheduled on the calendar.
Everything else is a conversation.
The protocol is now running. The next section, Validate The Protocol And Confirm Stabilization, covers how to confirm that it is working, simulate the intervention conversation, and build milestones that show the operation has stabilized.
Testing And Validating The Team Energy Protocol
A running protocol is not a working protocol until the data confirms that the trend is stable.
Your Burnout Risk Cost Calculator
Completed example: newsletter creator with one contractor earning $2,000 per month.
- Contractor monthly rate: $2,000/month
- Weeks of degraded output before departure: 6 weeks
- Degraded output weekly revenue impact: $1,500–$2,500/week
- Average weekly revenue impact: $1,750
- Total degraded output cost: 6 × $1,750 = $10,500
- Replacement onboarding cost: 25 creator hours × $75/hour = $1,875
- Total departure cost: $10,500 + $1,875 = $12,375
- Daily cost without a governance protocol: $12,375 ÷ 365 = $33.90/dayThe daily cost is amortized across one year of operating risk.
Fill in your numbers:
- Contractor monthly rate: $[amount]/month
- Estimated weeks of degraded output before departure: [number] weeks
- Estimated weekly revenue impact from degraded output: $[amount]/week
- Total degraded output cost: [weeks] × $[weekly impact] = $[amount]
- Replacement onboarding cost: [hours] × $75 = $[amount]
- Total departure cost: $[degraded output cost] + $[onboarding cost] = $[amount]
- Daily cost without governance: $[total departure cost] ÷ 365 = $[amount]/dayRun The Simulation Before You Build
Before the first energy check, run this scenario.
Tool: Claude, available at claude.ai, or pen and paper.
Time: 20 minutes.
Starting scenario:
High-ticket coach earning $110K per year.
Contractor earning $2,000 per month.
Contractor manages operations.
The team is in week six of a sustained busy period.
The discovery:
The creator has not asked about the contractor’s energy level in three weeks because she has been focused on a client renewal cycle. She assumes the contractor is fine because deliverables are still arriving on time.
The resistance:
“I don’t want to introduce a formal weekly check because it will make my contractor feel monitored or suggest that I don’t trust them to flag issues.”
The simulation:
The creator sends the five-question form.
The contractor completes it independently.
Contractor score: 4.
Creator score: 6.
The contractor would not have raised the issue independently because they did not want to appear to be struggling. The weekly check surfaces what the relationship dynamic was suppressing.
The result:
The creator removes one task from the contractor’s scope for the following two weeks.
The contractor’s score the following Friday: 7.
No departure occurs.
No degraded output occurs.
No replacement onboarding is required.
The entire intervention costs one paused task for two weeks.
The simulation shows that the formal check is not surveillance. It is a mechanism for honest reporting without requiring a difficult conversation.
The score does the work that the relationship dynamic prevents.
Two Futures Over Six Months
Without The Team Energy Protocol
Month 1–2:
The operation runs normally.
Both parties perform well.
No visible warning signals appear.
Month 3:
Workload creep adds 4 hours per week to the contractor’s scope without removing existing work.
Both parties reach their capacity ceiling, but neither tracks it.
Month 4:
The creator’s untracked energy score would be 5.
The contractor’s untracked energy score would be 4.
Output quality begins to decline.
The creator attributes the problem to unclear briefs.
The contractor attributes it to unclear direction.
Month 5:
The first deliverable is missed.
Relationship tension increases.
The creator begins questioning the quality of the hire.
Month 6:
The contractor resigns.
The creator begins searching for a replacement.
Total cost:
$12K–$20K.
The operation runs understaffed for 6–8 weeks.
With The Team Energy Protocol Installed
Month 1:
The protocol is installed during the first 14 days.
Baseline energy scores are established.
The capacity audit shows that the contractor is operating at 91% of the ceiling.
One task is removed before the protocol launches.
Starting scores: Creator 7; Contractor 7.
Month 2:
Workload creep adds two small tasks without removing existing work.
The capacity audit in week six catches the drift.
The scope is recalibrated.
One task is compressed rather than removed.
Scores hold at 6–7.
Month 3:
The scheduled no-meeting week creates the first full week without synchronous interruptions for either party.
Creator score: 8.
Contractor score: 8.
These are the highest scores since the protocol launched.
Month 4:
A client renewal cycle creates a workload spike.
The launch capacity protocol is activated.
Two contractor tasks are paused for the four-week cycle.
Contractor score holds at 7.
No degraded output occurs during the quarter’s highest-demand period.
Month 5–6:
The operation remains stable.
Both parties score above 7 for 10 consecutive weeks.
No departures occur.
No interventions are required beyond the routine weekly check.
Maintenance cost: 15 minutes per week.
What Good Looks Like At Each Stage
Day 14:
All four checkpoint criteria are met: documented scores, completed audit, defined capacity ceiling, and recovery protocols on the calendar.
Both parties understand the threshold rule and have agreed to act on it.
If the criteria are not met:
Recovery protocol scheduling is the most likely missing item because it requires planning conversations the creator may have deferred.
Complete the calendar step before adding anything to either role’s scope.
Week 4:
Four consecutive weeks of documented energy scores.
At least one workload calibration adjustment completed: a task removed, compressed, or redistributed.
Both parties score 6 or higher in at least 3 of the 4 weeks.
If the criteria are not met:
The workload calibration has not been enforced.
Scores below 6 without a corresponding task removal mean the protocol is being tracked but not acted on.
The rule is binary: a score below the threshold triggers work removal.
If no task has been removed, run the capacity audit again and identify the specific task that exits this week.
Week 8:
Neither party has experienced a consecutive three-week decline in energy score.
The capacity ceiling is confirmed in writing for both roles.
Recovery protocols have been protected, with no overrides of scheduled no-meeting or async weeks.
If the criteria are not met:
A recovery week was overridden by a “just this once” exception.
Document the exception and reset the quarterly calendar.
The first override is recoverable.
A pattern of overrides indicates that recovery protocols are not integrated into how the operation presents itself externally.
Clients and partners may be scheduling into protected windows because they do not know those windows exist.
If It Does Not Work: Roll Back And Retest
If energy scores do not stabilize above 6 after four weeks of protocol operation, revert one variable at a time.
Revert the workload first.
If the capacity audit shows that either role is still above the ceiling after adjustments, remove one additional task. The protocol cannot work if the capacity ceiling is not enforced. The problem is not necessarily the questions. The root cause, over-capacity, is still present.
If scores are above 6 but output quality continues to decline:
The energy check may be answered socially rather than honestly.
Switch to a written, asynchronous-only format.
Require scores to be submitted before the review call.
Do not discuss the scores verbally.
The verbal format may be reintroducing the social pressure that the written form was designed to remove.
If one party’s scores are consistently inconsistent with the other party’s observations:
Run the AI pattern-identification prompt from the AI-Assisted Team Energy Governance section.
Review whether the trend shows a decline that the person is not recognizing in their own weekly scores.
Pay particular attention to creators who chronically underreport their own depletion.
What This Framework Trains You To See
Signal 1: Output quality declines before scores drop
Contractor output quality can begin to slip 1–2 weeks before the energy score crosses the intervention threshold.
Early signs include:
A shortcut in a section that usually receives more attention.
Slightly less polished copy.
Reliance on a template instead of a customized approach.
Work that shows visible effort but falls below the usual standard.
Treat declining output quality as an energy indicator, not automatically as a skill indicator.
Signal 2: Response latency increases
When a contractor who normally responds to asynchronous messages within a few hours begins taking 24–48 hours, the change may indicate increased cognitive load rather than a behavior problem.
Processing a message may require more recovery time. This signal can precede an energy-score decline by one or two weeks, creating a correction window before the threshold is breached.
Signal 3: The creator begins doing contractor tasks
When the creator quietly takes back tasks that belong in the contractor’s scope, the creator may already recognize that the contractor is over capacity.
Watch for task re-absorption:
The creator takes back work “just this week.”
The creator completes tasks “just to get them done.”
Delegated work gradually returns to the creator.
This usually indicates that the contractor is struggling in a way neither person has named directly.
The energy score turns a relationship dynamic into a governance mechanism. Governance is what separates a $46-per-day risk from a $12,000 departure.
The mechanisms are validated. The next section, Recover After Burnout Has Already Arrived, covers the scenario the governance protocol cannot always prevent and the specific recovery action required when burnout occurs despite the system.
The Recovery Protocol: When Governance Delays But Does Not Prevent Burnout
When energy scores remain below 6 for three consecutive weeks despite the governance protocol being active, burnout has already begun.
The protocol worked by delaying the problem, but it did not prevent it. That distinction matters.
The governance protocol is not a guarantee against burnout. It is a system designed to detect drift early enough to correct it before the problem becomes structural.
The protocol may not catch the problem in time when:
A launch period compresses the recovery window.
One party underreports their scores.
An external life event reduces capacity faster than the protocol can respond.
When that happens, use the recovery protocol.
The Recovery Protocol Rule
The recovery protocol has one rule:
One full week off.
No client delivery.
No exceptions.
This is not a workload reduction or a lighter week. It is a full stop.
The recovery week is a business intervention, not a vacation.
A two-person creator operation that has operated above capacity for three or more consecutive weeks has accumulated cognitive debt. Gradual workload reduction may not be enough to restore the baseline. A complete break from the delivery cycle is required.
What A Full Stop Means
No client deliverables:
Move anything due during the recovery week to the following week or the week after.
Notify clients in advance with one direct message: “I’m implementing a scheduled team recovery week, and your deliverable has moved to [specific date].”
No asynchronous task completion:
Do not clear the inbox.
Do not moderate the community.
Do not work through the repurposing queue.
Produce no output during the recovery week.
No strategy or planning work:
Strategy uses the same cognitive resources as delivery work.
Planning the next quarter while recovering from the current one does not provide a full reset.
What The Stop Week Costs
For a creator operation generating $8,000 per month:
Revenue impact of a one-week pause: $0–$2,000.
Most creator revenue comes from ongoing engagements rather than single-week delivery cycles, so the actual impact may be lower than it feels.
Contractor cost for one non-delivery week: $500, based on a $2,000-per-month contractor rate.
Relationship repair avoided: not calculable, but a contractor who receives a full recovery week before reaching the departure threshold may remain with the operation.
Compare that with the alternative:
Six months of degraded output plus a departure: $12K–$20K.
Estimated stop-week cost: $500–$2,500.
Potential prevented cost: $12K–$20K.
This is why “full stop” is the rule rather than “take it a bit easier.” Partial recovery can leave the person in a marginal state, with degraded output and a weakened baseline before the next period of over-capacity.
After The Stop Week
Return to normal protocol operation the following week.
Run the energy scores immediately.
Re-run the capacity audit.
Ask one question: “What is currently in scope that should not be?”
The recovery week gives both parties a reset. Re-entry gives the operation a recalibrated ceiling.
Recalibration after a recovery stop will often result in the permanent removal of one or two tasks. The stop week reveals which tasks were being completed from inertia rather than actual business necessity.
When the operation asks, “Which tasks from last month do we actually need to restart?” the list is often shorter than expected.
When burnout arrives despite the governance protocol, recovery requires a full stop: one week, no delivery, no exceptions. The cost of the stop is a fraction of the departure it may prevent.
Running This System in Your Current Condition
Contraction: Revenue Declining Or Unstable
During contraction, the Team Energy Protocol creates one specific risk: using governance as permission to reduce output when the business needs protection.
Scaling back work may be correct when revenue declines, but the governance protocol should not be the justification.
The protocol monitors energy, not revenue. Contractors may fall below the energy threshold because revenue uncertainty creates psychological strain, not because workload is too high.
Minimum viable Team Energy Protocol during contraction:
Run the weekly energy check.
Do not run the full capacity audit until revenue stabilizes.
A capacity audit during contraction may identify scope items that appear removable but are actually required to stop the revenue decline.
The key question is not:
“What can we remove?”
It is:
“What does the contractor need to keep doing to protect the business?”
These questions can produce different answers.
Signal that the protocol is making contraction worse:
Energy-check conversations become venting sessions about revenue anxiety.
The conversation stops producing workload information.
The check becomes stress release rather than a governance instrument.
Keep the check short and focused on scope. Address revenue concerns in a separate conversation.
Stability: Revenue Consistent But Not Growing
During stability, the Team Energy Protocol addresses a specific blind spot: the creator has a functioning contractor relationship but has never formally calibrated the sustainable capacity ceiling.
Stability is the ideal phase to install the protocol because neither party is under acute pressure. The capacity audit can therefore produce accurate data rather than estimates shaped by a current crisis.
The first capacity audit during stability will often reveal that the contractor absorbed scope creep during previous busy periods and is operating at 85–95% of available hours without anyone noticing.
Stability gives the creator an opportunity to right-size the scope before the next growth phase demands expansion.
An operation entering growth at 78% capacity has headroom.
An operation entering growth at 94% capacity is likely to snap.
Track the average weekly energy score across a rolling four-week window.
During stability, both team members should maintain an average score of 7 or higher. If the four-week average falls below 7 without a corresponding increase in scope, the work may be becoming less enjoyable or meaningful.
That is a different constraint, and governance alone does not solve it.
Expansion: Revenue Growing And Complexity Increasing
During expansion, the first part of the Team Energy Protocol to break is usually the workload calibration rule.
Revenue growth creates legitimate reasons to add scope. Because the business is performing well, every addition feels justified. The pattern of adding work without removing existing work returns while energy scores remain in the green.
Creators often over-rely on energy scores as a ceiling indicator during expansion.
Scores can remain at 7–8 while a role approaches its sustainable ceiling. The person is still performing well, but has no buffer left.
The score drops only after the buffer runs out and the ceiling has already been breached. During expansion, monitor capacity audit numbers more closely than energy scores.
The guardrail:
Run the capacity audit monthly instead of quarterly.
Treat the capacity audit as the leading indicator.
Treat the energy score as the lagging indicator.
The capacity threshold changes when adding scope requires adding a person rather than removing an existing task.
If both roles are operating at their calibrated ceilings and more work needs to happen, the operation has reached the two-contractor governance threshold. That requires a different architecture than the Team Energy Protocol covers.
The Team Energy Protocol in the Creator Operating System
Org Chart for a One-Person Business: Defining What Your First Hire Actually Owns defines a contractor’s responsibilities before you assess their workload. Use this when role boundaries are unclear.
Stop Running Empty: The Energy Management Audit for Solo Business Owners assesses your own capacity before adding team capacity. Use this when you were overloaded before hiring.
I Keep Saying Yes to Clients But My Team Is Already Breaking - The Capacity Planning System checks whether your team can absorb new client work. Use this when new commitments keep expanding workloads.
Why You Crash After Every Big Push: Building a Sustainable Creative Rhythm structures creative work around sustainable output. Use this when intense production cycles end in crashes.
I Feel Like I’m Doing Something Wrong If I Take a Day Off - The Rest Architecture System addresses why recovery gets postponed even when capacity is strained. Use this when taking time off feels unacceptable.
Where are you in this sequence?
If the contractor’s role is not clearly defined, build the org chart first.
If the creator is already operating above solo capacity, run the individual energy audit first.
If role clarity and individual capacity are stable, install the Team Energy Protocol in 14 days.
After installation, the protocol runs indefinitely at 15 minutes per week.
Your Energy Governance Fix Starts Now
At Week 8, you’ll be able to say:
“My contractor and I both have a number every Friday. I know what that number means and what it requires from me when it drops.”
“The capacity ceiling for both roles is documented. No new scope enters either role without a named removal happening in the same conversation.”
“The recovery protocols are on the calendar and I’ve protected them at least once. One no-meeting week has happened. The operation didn’t break.”
Three time-boxed actions:
In the next 15 minutes:
Ask yourself and your contractor the five energy questions.
Write down both numbers before comparing them.
If either score is below 6, the intervention threshold has been crossed.
Run the capacity audit today, before completing this week’s deliverables.
This week:
Run the capacity audit for both roles.
List every actual task.
Estimate the actual hours required for each task.
Total the hours against available hours.
If either role exceeds 85% of available hours, remove one task before the audit conversation ends.
Before next month:
Schedule the recovery protocols for the next 12 months.
Add one no-meeting week per quarter.
Add one async week per quarter.
Reserve the final week of every month for maintenance only.
Confirm that both parties can see the recovery protocols in the calendar.
Team Energy Protocol Progress Milestones:
Milestone 1: Both parties have completed the first energy check independently and compared numbers. Baseline scores documented. Any score below 5 acted on immediately.
Milestone 2: Capacity audit complete for both roles. Total actual hours mapped against available hours. Maximum sustainable output defined in writing for each role.
Milestone 3: Recovery protocols scheduled in both calendars for 12 months. No client-facing deadlines sitting inside protected recovery weeks.
Milestone 4: Four consecutive weeks of energy scores documented. At least one workload calibration made based on score data. Both parties above 6 in at least 3 of 4 weeks.
Milestone 5: One recovery protocol completed and protected (a no-meeting week or async week has passed without override). Post-protocol energy scores 1-2 points higher than the week prior, confirming the recovery effect is real.
If you take one thing from each section:
Burnout in a small creator operation is a governance failure, not a personnel failure. The difference between these diagnoses determines whether the fix costs two weeks or $20,000.
The Team Energy Protocol does not prevent burnout through willpower or communication. It makes capacity a number that triggers a specific action before the decline becomes irreversible.
The protocol is installed only when four outputs exist in writing: energy scores, capacity ceilings, sustainable output definitions, and recovery protocols on the calendar.
The energy score turns a relationship dynamic into a governance mechanism. Governance is what separates a $46-per-day risk from a $12,000 departure.
When burnout arrives despite the governance protocol, recovery requires a full stop: one week, no delivery, and no exceptions. The cost of the stop is a fraction of the departure it may prevent.
But if you remember only one thing:
The weekly energy score doesn’t ask your contractor how they’re feeling. It asks them to give you a number, and a number has a threshold, and a threshold has a protocol, and a protocol removes the need for anyone to have the difficult conversation that neither party is willing to start. That’s the entire value of the governance layer.
Team Energy Protocol Checklist
Reference this checklist to confirm the governance system is fully installed.
☐ Both team members completed five-question energy check independently before comparing scores
☐ Capacity audit totaled actual task hours against available hours for each role
☐ Maximum sustainable output defined as available hours minus 15% buffer, in writing
☐ Recovery protocols — no-meeting week, async week, month-end buffer — on calendar for 12 months
☐ Four consecutive weeks of energy scores documented with at least one workload calibration made
When complete, the protocol runs at 15 minutes per week indefinitely.
FAQ: Team Energy Protocol
Q: Why does the energy check have to be done independently before comparing scores?
A: When a contractor is asked directly how they are doing, they almost always answer based on what the creator needs to hear. A contractor worried about their job security or their creator’s stress level will manage their answer upward.
Q: What happens if a contractor consistently scores themselves higher than their output quality suggests?
A: Add a second data stream alongside the self-reported score. Output quality review — where the creator assesses one piece of contractor work against a defined standard — and response latency are both observable behavioral signals that do not require self-reporting.
Q: How is the 15% capacity buffer calculated and why not 10% or 20%?
A: The ceiling is available hours multiplied by 0.85. The buffer represents the capacity required to absorb the unexpected — a client revision request, a technical problem, a week where something personal demands time. Operations budgeted to 100% of available hours have no room for variability.
Q: When should a creator run the capacity audit more frequently than quarterly?
A: In expansion — when revenue is growing and scope additions feel justified by business performance — run the capacity audit monthly rather than quarterly. Energy scores can hold at 7 or 8 while a role approaches its sustainable ceiling because the person is still performing well but has no buffer remaining.
Q: What is the actual cost of one contractor departure at the Scaling band?
A: At a creator operation generating $6,000–$10,000 per month with a contractor at $2,000 per month, the conservative departure cost is $12K–$20K. This includes six weeks of degraded output at $1,500–$2,500 per week, plus 20–30 hours of creator time for replacement onboarding at a $75 per hour equivalent.
Q: Can the recovery protocols be moved if a client deadline falls in the scheduled week?
A: No. Recovery protocols work only when protected. Treating a no-meeting week or async week as adjustable based on client demand means they get overridden in every high-demand quarter — exactly when they are most needed. Communicate recovery weeks to clients as fixed infrastructure scheduled a year in advance, not as personal time.
Q: What does a full recovery stop week actually look like in practice?
A: One week with no client deliverables, no async task completion, and no strategy or planning work. Anything due in the stop week moves to the following week. Clients receive one matter-of-fact notification with the rescheduled date. The week produces no output.
Q: How does the protocol handle a contractor in a community moderation or student support role?
A: Standard capacity audit hours understate the real drain for support-heavy roles because they require sustained emotional availability beyond what task time captures. Apply a cognitive load modifier of 1.25x to community and support task hours when calculating the ceiling.
Q: What is the three-consecutive-weeks rule and when does it trigger?
A: Three weeks at or below a score of 6 for either team member — even if no single week dropped below 5 — requires an active intervention. A score of 6 in isolation is not a crisis. The pattern of three consecutive weeks at 6 is evidence that the operation is running at sustained over-capacity.
Q: What if the protocol is installed but energy scores do not stabilize above 6 after four weeks?
A: Revert one variable at a time. First, check whether the capacity ceiling has actually been enforced — if either role is still above 85% of available hours, one additional task requires removal.
⚑ 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 Team Energy Protocol just showed you how to prevent a $12K–$20K contractor departure before it happens, share it with one founder stuck in the same burnout spiral.
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 Team Energy 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: One burnout departure costing $12K–$20K at $60–$150K/year.
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.
