Phase 6 installs the weekly structure that makes Brava scalable. You’ll learn the exact cadence you run inside each business—leadership touchpoints, employee check-ins, async support, implementation follow-ups, and signal tracking—so your work stays calm, repeatable, and measurable.
What you’ll be able to do
Run a repeatable “Business Health Week” per client • stay ahead of risks • close loops without chasing people.
Why this matters
Brava wins by rhythm. When cadence is consistent, systems stabilize, trust increases, and you can manage 10+ businesses without burnout.
12) The Business Health Week (This Is Critical)
Cadence
Brava does not operate as “random support.” It operates as a weekly rhythm that makes business health measurable and predictable. Every client gets the same core structure—then you choose the smallest moves based on signals. The win is consistency: same lanes, same sequence, same follow-through.
The weekly structure (what happens every week)
Core
This is the non-negotiable Brava cadence per business. If you keep this rhythm stable, your work becomes calm—and you stop chasing chaos.
1 leadership touchpoint: a short weekly check with owner/manager to align on priorities + risks.
2–4 employee check-ins: quick, structured 1:1s or short pulse check-ins based on signal priority.
Async support lane: a protected window for questions, clarifications, and micro-guidance (not 24/7).
Implementation follow-ups: revisit installs until “proof of done” is real and repeatable.
Signal tracking: convert check-ins + observations into patterns and risk markers (no stories, no drama).
Rule
If you can’t describe what happens each week in one simple sentence, your system is not installed.
Example weekly layout (simple + repeatable)
Template
You don’t need a complicated calendar. You need a predictable sequence. Use this as a baseline—then swap check-in targets based on signals.
MONDAY (Set the week)
• Leadership touchpoint (15–25 min)
• Confirm: top 3 priorities + top 1 risk + current install being followed up
TUESDAY–THURSDAY (Run the system)
• 2–4 employee check-ins (7–12 min each) OR 1–2 deeper check-ins if signals are hotter
• Implementation follow-ups (proof-of-done checks)
• Async support window (batch responses)
FRIDAY (Close loops)
• Track signals + patterns for the business
• Mark: installs completed vs pending
• Decide next week’s check-in targets (based on risk + drift)
What makes this powerful
You’re not improvising. You’re running a repeatable machine: align → check → install → follow up → track.
Leadership touchpoint (what you actually do)
Owner-ready
This touchpoint is short, calm, and structural. It protects priorities, keeps leadership honest about follow-through, and prevents “initiative chaos.”
Confirm priorities: “What are the 3 things that matter most this week?”
Confirm the risk: “What’s most likely to break execution if we ignore it?”
Check follow-through: “Which install from last week is now standard?”
Choose check-in targets: “Who needs a check-in this week based on signals?”
Leadership touchpoint script (copy/paste)
“Quick alignment: What are the top 3 priorities this week? What’s the #1 execution risk? Which install from last week is now real (proof-of-done)? Who should I check in with based on signals?”
Signal tracking (how Brava stays ahead)
Signals
Signals are not feelings. They are patterns that predict cost: churn, mistakes, delays, rework, customer friction, and leadership instability.
Enter code to reveal trainer cues, tests, and what to look for.
Incorrect code. Try again.
Mastercoach cues: The Business Health Week
The failure mode is “random helpfulness.” They’ll drift into being on-call, over-meeting, and losing the weekly sequence. Your job is to train: cadence discipline + proof-of-done follow-up + signal tracking.
Pass test: give them a messy business scenario → they must build a one-week plan with: 1 leadership touchpoint, 2–4 check-ins, async window, follow-ups, and signals to track.
Watch for: “more meetings” as the default solution. Require small installs + follow-up checks instead.
Watch for: no proof-of-done. If they “recommend” but don’t schedule follow-up, they fail the rhythm.
Scoring: 1–5 on: cadence clarity, check-in structure, follow-up discipline, signal quality (patterns not stories), owner-ready language.
Correction phrase
“Stop being available. Start running the week. Align → check → install → follow up → track.”
13) Managing 10+ Businesses Without Burnout
Scale
Brava scales when you stop acting like each business is a custom world. Managing 10+ businesses is not about working harder—it’s about time blocks, energy control, pattern recognition, and reuse. You do not customize from scratch. Brava already did the thinking.
Time-blocking system (how you don’t drown)
Schedule
You can’t scale if your calendar is random. You need lanes. Lanes create calm. Calm creates capacity.
Leadership lane: batch leadership touchpoints on 1–2 days to reduce context switching.
Check-in lane: cluster employee check-ins in a repeating block (ex: Tues/Thurs afternoons).
Follow-up lane: a dedicated proof-of-done block (ex: Friday mornings) so installs become real.
Async lane: one or two “response windows” daily—not constant messaging.
Context-switch rule
Every time you switch businesses, you pay a mental tax. Lanes reduce that tax and protect your energy.
Energy management (how you stay sharp)
Capacity
Burnout is not always too much work—it’s too much emotional load, too many open loops, and too many “unbounded” expectations.
Boundaries are part of the service: you set response windows, meeting lanes, and follow-up cadence.
Protect calm: your tone sets the temperature. Calm creates compliance. Panic creates chaos.
Close loops weekly: open loops drain energy more than meetings do.
If you feel drained, ask:
1) Do I have too many open loops?
2) Am I being “on-call” instead of running lanes?
3) Am I holding stories instead of converting to patterns?
Pattern recognition (how you get faster every month)
Reuse
Most businesses share the same root problems. You build speed by recognizing patterns and reusing frameworks—then installing small adjustments.
Common patterns: unclear priorities • weak handoffs • leader overload • fear of feedback • role confusion.
Framework library: you keep a “menu” of installs that solve predictable problems (no reinvention).
Repeat what works: when an install works in 3 businesses, it becomes your default.
Pattern → install conversion (memorize)
Pattern: “Priority chaos”
Install: “3 priorities per week + owner touchpoint confirmation + Friday close-loop”
Proof of done: “Team can name priorities without guessing”
Not reinventing work (the Brava rule)
Rule
The biggest scaling mistake is acting like each client is a custom project. Brava is an operating system—your job is to apply it with discipline.
Default to templates: weekly plan, check-in script, signal note, follow-up cadence.
Customize only the smallest layer: who you check in with and which install you choose.
Batch communication: handle client messages in response windows, not all day.
Protect your lane: you’re a strategist running a system—not a personal assistant for every problem.
Key Rule (as written)
They do not customize from scratch — Brava already did the thinking.
Mini drill (10+ business capacity)
Design your weekly lanes as if you had 10 businesses. List your leadership day(s), check-in blocks, follow-up block, and async windows.
Leadership lane (day/time):
Employee check-in lane (day/time):
Follow-up lane (day/time):
Async windows (times):
How you’ll prevent context switching:
Mastercoach (locked)
Enter code to reveal trainer cues, tests, and what to look for.
Incorrect code. Try again.
Mastercoach cues: Managing 10+ businesses
The failure mode is over-customization + being on-call. They’ll try to “do it perfectly” for each client and burn out. Train: lanes, reuse, and boundary discipline.
Pass test: ask them to schedule a week for 10 businesses in under 10 minutes (lanes required). If they can’t, they don’t understand scale.
Watch for: customization from scratch. Make them name 3 reusable installs and where they apply.
Scoring: 1–5 on: lane design, boundary clarity, reuse discipline, pattern recognition, loop closure habit.
Correction phrase
“You don’t scale by doing more. You scale by repeating lanes and reusing installs.”
Phase 6 — What to Memorize + Pass Conditions
Gate
Phase 6 is installed when you can run a stable weekly cadence per business and manage 10+ businesses through lanes, reuse, and follow-up discipline—without becoming on-call, over-meeting, or reinventing work.
Memorize: the Business Health Week
Must
“Per business, every week:
1 leadership touchpoint
2–4 employee check-ins
Async support lane
Implementation follow-ups
Signal tracking”
Memorize: the scale rule
Must
“I do not customize from scratch.
Brava already did the thinking.
I run lanes, reuse frameworks, and close loops.”
Phase 6 pass conditions (simple + strict)
You pass Phase 6 when you can: (1) build a one-week plan for a business that includes leadership touchpoint, 2–4 check-ins, async window, follow-ups, and signal tracking; (2) run a leadership touchpoint using owner-ready language; (3) convert check-in inputs into patterns + installs + proof-of-done follow-ups; and (4) design a scalable weekly calendar for 10 businesses using lanes (not improvisation).
Mastercoach (locked)
Enter code to reveal trainer scoring + remediation plan.
Incorrect code. Try again.
Mastercoach cues: Phase 6 scoring
Phase 6 is all about cadence discipline. If they can’t articulate the week, or they default to “more meetings,” they’re not installed. If they can’t run lanes for 10 businesses, they’ll burn out.
Score 1–5: weekly cadence clarity (can they state the Business Health Week cleanly?)
