Module 6 of 6

Compliance That Keeps You Safe

This is the whole rulebook in one place. Every other module taught you how to grow. This one makes sure nothing you say -- on the phone, in an ad, in a DM, on a flyer -- ever turns into a claim you cannot defend. Learn it, drill it, make your team sign it.

Rewrite any sentence into "supports" language

You will convert outcome claims into DSHEA-safe wording on sight, using the drill patterns in Lesson 1.

Hold the three lines that never move

Never diagnose, never promise, never discuss medication -- and run the escalation script without hesitating.

Gate testimonials and ad copy correctly

You will know exactly what may be published, what needs a written release, and what only counsel-cleared documents may say.

Run the staff sign-off ritual

Day 1, read aloud, signed, filed, re-run on drift -- for every hire, clinic or platform.

Estimated time: 60-75 minutes including drills and quiz. The quiz in this module is the hardest in the Academy -- it is all scenarios. That is on purpose.

Lesson 1

The "Supports" Discipline -- Your Entire Vocabulary

Concept

Summit Metabolic (REHEARSAL — fictional) is a metabolic wellness business. It is not a drug company and not a medical practice making disease claims. Under DSHEA-style language discipline, everything the business offers is described one way: it supports. It supports healthy habits. It is designed to support your routine. It is part of a structured program. It helps you build consistency.

The moment a sentence connects your program to a disease or promises a health outcome, it stops being marketing and becomes a claim -- the kind regulators read letter by letter. The fix is not to whisper the claim more carefully. The fix is to never make it.

Your approved vocabulary lives in the assets you were shipped. The words there were chosen deliberately. Your job is to stay inside them.

The word lists -- memorize both columns

Green words (use freely)Red words (never attach to your program)
supports, is designed to support, helps you build, is part of, structured, mapped, accountability, routine, habits, consistency, energy for daily life, overall wellness, healthy lifestyle treats, cures, prevents, diagnoses, reverses, heals, fixes, eliminates, "clinically proven to," any disease or condition name attached to your program, any drug name, "FDA approved"

The red column is banned even inside softeners. "May help reverse" is still a reversal claim. "Some say it can heal" is still a healing claim. Quotation marks, hedges, and emojis do not launder a claim.

Rewrite drills -- do these out loud

Each drill shows a sentence a well-meaning partner has actually tried to publish. Say your rewrite out loud before you open the answer.

Bad "Our program reverses insulin resistance in 12 weeks."tap for rewrite
Rewrite: "Our 12-week program supports the daily habits that matter for metabolic wellness -- with structure and real accountability."
Why: removed the disease mechanism, removed the outcome promise, kept the concrete structure (12 weeks, accountability) that actually sells.
Bad "Members lose 15-20 lbs on average."tap for rewrite
Rewrite: "Everyone starts from a different place, so nobody here promises a number. What we promise is a mapped process and a real person who checks in."
Why: numeric outcome claims are promises. The rewrite is the same honest answer your staff scripts use in operations/STAFF_HIRING_TRAINING_PACK.md.
Bad "A natural alternative to weight-loss medication."tap for rewrite
Rewrite: "A structured metabolic wellness program built on habits, accountability, and a mapped weekly process."
Why: "alternative to [medication]" is a drug comparison -- it puts your program in the drug conversation. There is no compliant version of that sentence. Delete the comparison entirely.
Bad "Doctors recommend our approach for prediabetes."tap for rewrite
Rewrite: "Talk to your own doctor about what is right for you. What we offer is a structured wellness program that supports healthy routines."
Why: a condition name attached to your program is a disease claim, and "doctors recommend" is an authority claim you cannot substantiate. Both go.
Bad "Feel 10 years younger -- guaranteed."tap for rewrite
Rewrite: "Built for people who want more consistent energy for daily life -- and a program that does not leave them guessing."
Why: "guaranteed" plus a felt-health outcome is a double violation. The rewrite sells the feeling of structure, not a promised body result.
Exactly how to apply this in your build
  1. Open site/disclosures.html in your website folder and read the "Informational-content boundary" section. That page is the legal floor under every word on your site -- know what it says before you write anything new.
  2. Open marketing/social/SOCIAL_CAPTION_BANK_v1.md and marketing/email-bank/consumer-email-bank.html. Notice: every caption and email already uses supports language. When you post, copy from the bank. When you improvise, run the two-column word check above first.
  3. Open consumer-program/CONSUMER_PROGRAM_12WEEK_MASTER.html and skim any week. This is the tone standard for anything you hand a customer: structure, habits, accountability -- never outcomes.
  4. Before publishing ANY new sentence, run the 3-second test: (a) does it name or imply a disease, condition, or drug? (b) does it promise an outcome, number, or timeline? (c) would it still be true for the least-typical customer you will ever have? Fail any one -- rewrite.
Do this now: Take the last three things you wrote or posted about Summit Metabolic (REHEARSAL — fictional) (or, if pre-launch, three lines you were planning to use). Run each through the 3-second test. Rewrite any that fail, using the drill patterns above. Keep the rewrites -- you will want them for the quiz.
Lesson 2

The Three Lines That Never Move

Concept

Marketing compliance protects you in public. Conversation compliance protects you one customer at a time -- on the phone, in DMs, at the front desk. Your operations/STAFF_HIRING_TRAINING_PACK.md Section 1.1 ("The Compliance Guardrails") sets three lines. They apply to you, Sam Summit (fictional), exactly as much as to any hire:

  1. Never diagnose. No naming conditions, no "sounds like," no interpreting symptoms, labs, or health history. Ever.
  2. Never promise outcomes. No numbers, no timelines, no "you will," no repeating another client's result as a prediction.
  3. Never discuss medication. Not prescriptions, not dosing, not comparisons, not "instead of," not "alongside." The word medication ends the staff portion of the conversation and starts an escalation.

Notice the trap inside line 3: "alongside" and "instead of" feel helpful and neutral. They are still medication discussion. There is no safe angle into that conversation for staff -- the only move is the escalation.

The escalation reflex

Section 1.1 of the staff pack lists ten triggers that route to the owner the same day, no judgment call required. Learn the big ones cold:

The escalation script is one sentence: "That is exactly the kind of question that goes straight to Sam Summit (fictional). I am flagging it right now, and you will hear back today. What is the best number or email for that?" Then log the contact and route it. A person who mentioned medication does not get booked until the escalation clears.

Hard line: "Let me confirm and get back to you today" never hurts anyone. A wrong answer travels. If a fact is not final, the answer is "that goes in the written follow-up." Never guess.

Where the two models diverge

Clinic model
  • The danger zone is live and fast: front desk, walk-ins, phone. Your Front Desk Coordinator and Wellness Coach hear condition and medication questions daily.
  • Drill the phone script in operations/STAFF_HIRING_TRAINING_PACK.md until the guardrail lines come out mid-call without breaking rhythm: answer the guardrail, then return to booking.
  • Anyone who asks for "the doctor" or assumes a clinician is on staff gets escalated -- staff never confirm or deny credentials on the fly.
Platform model
  • The danger zone is written and permanent: DMs, comments, texts, email. Every reply is a screenshot waiting to happen -- which is why replies come from the scripted bank, not from improvisation.
  • Use the DM/text reply scripts in the staff pack verbatim -- especially the medication reply ("That is a question I am not allowed to touch...") -- and log every reply in the CRM.
  • Remote staff and VAs are covered by the same three lines and the same sign-off ritual (Lesson 5). Distance changes nothing.
Exactly how to run this in your build
  1. Print Section 1.1 of operations/STAFF_HIRING_TRAINING_PACK.md -- the three lines, the Say-This / Never-Say table, and the ten escalation triggers. It is written to be printed.
  2. Post the escalation trigger list where the phone gets answered (clinic) or pin it in your team chat (platform).
  3. Open binder/ and find Section 14 of your Atlas Partner Binder ("Claims, Evidence, Supplier, and Customer-Education Control"). Its "Staff guide: say, do not improvise, escalate" block is the same rule at binder depth -- bookmark it.
  4. Role-play the three hardest inbound lines with whoever answers your channels: "I'm on [medication name]," "I have [condition name]," and "How much weight will I lose?" Do not stop until the answers come out of the table, not out of memory.
Do this now: Say the escalation script out loud three times, from memory, with Sam Summit (fictional)'s name in it. Then text or tell your team: "If anyone mentions medication, a condition, or feeling unwell -- you stop, you log it, you send it to me the same day. Feeling unwell is same-hour."
Lesson 3

Testimonial Rules -- Other People's Results Are Not Your Claims

Concept

A happy customer's story feels like free marketing. Handled wrong, it is the most expensive sentence you will ever publish, because a testimonial you select, post, or amplify becomes YOUR claim. If a customer says "this fixed my blood sugar" and you repost it, you just made a disease claim -- with a witness.

The staff pack already sets the conversational rule: "People's experiences are their own, and we never turn one person's experience into a promise for the next." Publishing has three more gates.

The three gates every testimonial must pass

GateThe ruleWhat fails it
1. Written releaseA signed written release on file before anything is published. [CONFIG: written release form and process -- counsel] -- until counsel supplies your release form, the publishable testimonial count is zero."She said I could use it" (verbal). A DM screenshot. A public review copied onto your site.
2. Content checkThe testimonial itself must pass Lesson 1: no disease or condition names, no medication mentions, no "cured / fixed / reversed," no implication the result is typical or predicted."Down 22 lbs!" as a headline. "My doctor was amazed." "Better than [drug name]."
3. Framing checkPresented as one person's experience, never as a prediction, with results-vary framing per site/disclosures.html. Never "typical," never "average," never "you will too.""Results like Maria's every week!" A before/after grid implying a standard outcome.
[CONFIG: testimonial release form, storage location, and review workflow -- counsel] -- route this through your attorney before your first testimonial goes anywhere. Until then, the rule is simple and absolute: collect stories privately, thank people warmly, publish nothing.

The trap nobody warns you about: content on channels you control

A customer posts on YOUR page: "This program cured my [condition]!!" You did not write it -- but it now lives on a channel you moderate. Leaving it up (or liking it) is adoption. The move: hide or remove it per your platform policy, reply privately with thanks and a gentle correction, log it, and flag it to Sam Summit (fictional). Comment moderation is claims control.

Clinic model
  • Google reviews of your location will appear whether you like it or not. You cannot edit reviews -- but never quote a review with outcome or condition language in your own marketing, and never reply in a way that confirms a result ("So glad it worked!"). Reply with gratitude only.
  • In-clinic wall art, framed stories, before/after boards: same three gates. Physical display is publication.
Platform model
  • Community spaces, group chats, and comment sections you run are moderated channels. Set the norm early: celebrate consistency and process wins, not medical outcomes.
  • Screenshots of member messages are testimonials. All three gates apply before any screenshot appears in a story, ad, or email.
Exactly how to run this in your build
  1. Read the "Relationships and compensation disclosures" and results-vary language in site/disclosures.html -- that page is what your testimonial framing must agree with.
  2. Check marketing/ad-bank/ad-bank.html and note what is NOT there: no testimonial-driven creatives ship in your bank. That is deliberate. Do not add any until the [CONFIG] release process exists.
  3. Create a "Stories -- HOLD" folder (or CRM tag) where kind messages from customers get saved privately with date and contact. When counsel delivers your release process, you will have a warm list to go back to -- compliantly.
  4. Add one line to your weekly staff huddle (the 15-minute huddle from operations/STAFF_HIRING_TRAINING_PACK.md): "Any praise, reviews, or member posts this week? Route them to the HOLD folder -- publish nothing."
Do this now: Create the "Stories -- HOLD" folder or CRM tag this minute. Then check your existing social pages for any customer comment with a condition, medication, or outcome number sitting on a channel you control -- and moderate it per the trap rule above.
Lesson 4

Ad Claims Discipline -- Publish From the Bank, Not From the Hip

Concept

Ads are your highest-risk surface: paid distribution means maximum reach for any bad sentence, plus platform ad review, plus screenshots that outlive the campaign. Your build ships pre-written, language-disciplined creative precisely so you never have to improvise under deadline pressure:

  • marketing/ad-bank/ad-bank.html -- approved ad creatives in feed (1080x1080), story (1080x1920), and wide banner formats.
  • marketing/social/SOCIAL_CAPTION_BANK_v1.md -- captions ready to post.
  • marketing/email-bank/consumer-email-bank.html -- consumer email sequences.
  • marketing/reel-scripts/reel-script-bank.html -- short-video scripts.
  • marketing/lead-magnet/consumer-metabolic-scorecard.html -- your lead magnet, plus its LEAD_MAGNET_DEPLOYMENT_SHEET.md.
  • marketing/print/flyer-2sided.html and marketing/print/referral-card.html -- print pieces.

The rule: publish from the bank. The banks are not inspiration -- they are the approved claim set. Anything new you write must clear the same bar before money goes behind it.

The pre-publish gate -- run it on every new line of copy

  1. Word check (Lesson 1): no red-column words, no disease/condition names, no drug names, no outcome numbers or timelines, no "guaranteed."
  2. Implied-claim check: read it as a hostile regulator would. "Finally, something that works when nothing else did" names no disease -- but it implies a health outcome and superiority. Implied claims count.
  3. Substantiation check: your Atlas Partner Binder Section 14 runs a claims register and evidence index -- every factual statement you publish must trace to a source recorded there. No source in the register, no publication. This is also where the binder's rule lives: never inflate a testimonial, vendor assertion, article, or draft into a general claim.
  4. Consistency check: does the copy agree with site/disclosures.html? An ad may never promise what your own disclosures page takes back.
  5. Landing-path check: the ad's promise must match where it sends people -- your booking route (https://summit-metabolic.example/book) or summit-metabolic.example pages. No bait-and-switch between ad language and page language.
Hard line on money language: never publish earnings-style or outcome-number promises of any kind -- health numbers or otherwise. Pricing questions route to the consult (per your staff scripts); program value is described by structure, not by numbers you would have to defend.

Where the two models diverge

Clinic model
  • Local surfaces count as ads: Google Business Profile posts (see marketing/local-seo/LOCAL_SEO_GBP_KIT_v1.md), window signage, flyers on counters. Same gate, every surface.
  • Print is unforgiving -- there is no edit button on marketing/print/flyer-2sided.html once 500 copies exist. Run the gate BEFORE the print order.
Platform model
  • Organic content at volume is your ad surface: reels, captions, emails. Velocity is the risk -- posting daily means daily chances to drift. Publishing from reel-script-bank.html and the caption bank keeps velocity AND discipline.
  • Boosted posts are paid ads the moment you boost them. A caption that was fine organically still needs the full gate before boost.
Do this now: Open marketing/ad-bank/ad-bank.html and pick the three creatives you will run first. Then write one NEW headline of your own and run it through all five gate steps in writing. If it survives, add it to your claims-register notes for Binder Section 14. If it does not -- good, the gate worked.
Lesson 5

Counsel-Cleared Documents and the Staff Sign-Off Ritual

Concept -- two classes of language

Everything your business says falls into exactly two classes, and mixing them up is how good operators get hurt:

Class A -- operating language (you and staff may use)Class B -- only counsel-cleared documents may say it
Supports language, program structure, scheduling, logistics, the scripted answers in the staff pack, copy published from the banks after the Lesson 4 gate. Legal disclaimers and their exact wording; terms of service and privacy commitments; refund and guarantee terms; testimonial releases; anything about regulatory status; any response to a regulator, legal threat, or media inquiry.

Class B lives in documents -- site/disclosures.html, site/terms.html, site/privacy.html -- and in counsel's files. Staff never paraphrase Class B. If someone asks a Class B question, the answer is a pointer to the document or an escalation, never an improvised summary. Your builds mark every unset legal value with [CONFIG: ... -- counsel] tags: those are not placeholders to fill creatively. They are holes only your attorney fills.

The sign-off ritual -- how the rulebook becomes real

Rules on paper protect nobody. The staff pack makes the guardrails enforceable with a ritual, and it is not optional:

  1. Print Section 1.1 of operations/STAFF_HIRING_TRAINING_PACK.md -- the three lines, the Say-This / Never-Say table, and the escalation list.
  2. Day 1, read aloud together. The new hire reads it out loud with you -- not silently, not at home. Reading aloud surfaces the questions.
  3. Sign and date the bottom. Both of you.
  4. File the signed copy in the employee file. This is your evidence that training happened, on a date, in writing.
  5. Re-run on drift. The moment you hear a guardrail bend -- a "sounds like," a number promised, a medication opinion -- re-run the ritual that week. No shame, no exceptions. Drift is normal; unrepaired drift is a choice.
  6. Re-run on change. New scripts, new offer, counsel updates a document -- everyone re-signs the current version.
Clinic model
  • The ritual happens in person on Day 1 afternoon -- it is already on your Day-1 onboarding checklist in the staff pack, between accounts setup and shadowing.
  • Every role signs: Front Desk Coordinator, Wellness Coach, and anyone who ever touches the phone -- including fill-ins and family helping out "just for the afternoon."
Platform model
  • Run the ritual on a video call, camera on, reading aloud together; signature by e-sign the same day, filed the same day.
  • It covers every contractor, VA, and community moderator who replies on any channel under your brand -- if they can type to a customer, they sign first.
[CONFIG: counsel review calendar] -- set a standing cadence with your attorney to re-review disclosures, terms, testimonial process, and any new claim you want to make. Your binder's Section 14 acceptance tests assume these control documents stay current.
Do this now: Print Section 1.1 and run the ritual with your current team this week -- including yourself. Yes, sign your own copy: Sam Summit (fictional) signs first, dated today, filed. When the owner signs first, the team learns this is real.
Printable

Compliance One-Page Checklist -- Summit Metabolic (REHEARSAL — fictional)

Module 6, Summit Metabolic (REHEARSAL — fictional) Academy (Boise, ID, clinic model). Post where content gets written and phones get answered.

Language -- every sentence, every surface

  • Supports language only: supports / designed to support / helps you build / is part of
  • No disease, condition, or drug names attached to the program -- ever, including hedged ("may help...")
  • No outcome numbers, timelines, "you will," or "guaranteed"
  • No "FDA approved" and no drug comparisons ("instead of," "alongside," "alternative to")

Conversations -- the three lines that never move

  • Never diagnose: no condition names, no "sounds like," no interpreting symptoms or labs
  • Never promise outcomes: no numbers, no timelines, no repeating a client result as a prediction
  • Never discuss medication: the word ends the conversation and starts an escalation
  • Escalate same-day to Sam Summit (fictional): medical/medication questions, pregnant or nursing, minors, refund/legal threats, media, regulators, uncertainty. Bad reaction or feeling unwell = same-hour
  • Not final = not answered: "that goes in the written follow-up" -- never guess

Testimonials

  • Zero published until [CONFIG: written release process -- counsel] exists; kind words go to the Stories--HOLD folder
  • Every future testimonial passes all 3 gates: signed release / content check / results-vary framing
  • Outcome or condition claims posted by others on channels we control get moderated, logged, escalated

Ads and publishing

  • Publish from the banks: ad-bank, caption bank, email bank, reel scripts, print files
  • New copy passes the 5-step gate: words / implied claims / claims-register source (Binder Sec. 14) / disclosures consistency / landing-path match
  • Boosted or printed = full gate first; no edit button after money or ink

Documents and ritual

  • Class B language (disclaimers, terms, refunds, releases, regulatory, media) lives ONLY in counsel-cleared documents -- staff point, never paraphrase
  • All [CONFIG: ... -- counsel] items routed to the attorney; none filled in-house
  • Every person who talks or types to customers has read Section 1.1 aloud, signed, dated, filed -- re-run on drift or change
Team member -- signature and date
Sam Summit (fictional) -- signature and date
Self-check

The Hardest Quiz in the Academy

Eight scenarios, all drawn from situations partners actually face. Pass mark is 7 of 8. Wrong answers here are cheap; wrong answers in the wild are not. The full answer key appears after you submit.

Scenario 1 of 8
A DM arrives: "I'm already on a GLP-1 from another clinic. Can I stack your program with it?"

What does whoever runs your inbox do?

Key: C. B is the trap -- "alongside any medication" IS discussing medication. There is no compliant angle into that conversation. Script, flag, escalate, and hold the booking until it clears (staff pack, Section 1.1 and DM Scenario 3). D is worse: it is medication advice.
Scenario 2 of 8
A thrilled member texts: "Down 22 lbs and my energy is back! Use my story anywhere you want!!"

What can you publish today?

Key: C. A casual text is not a release (Gate 1), "down 22 lbs" fails the content gate (Gate 2), and screenshots you post are testimonials you published (Lesson 3). Save it to the Stories--HOLD folder and thank her warmly.
Scenario 3 of 8
Four draft headlines are on the table for your next campaign.

Which ONE survives the pre-publish gate?

Key: B. A is an implied outcome and superiority claim ("works when everything else failed"). C is a drug comparison. D attaches a condition name -- "designed to support" cannot launder a disease claim. B sells structure, which is the whole playbook.
Scenario 4 of 8
At the front desk (clinic) or in a comment thread (platform), someone says: "My doctor says I'm prediabetic. Will this help me?"

Best response?

Key: B -- straight from the Say-This table. A and D both offer an opinion on a named condition ("exactly what you need" / "should be fine for that" = diagnosing lite). C obeys the letter but fails the person: the guardrails come with a warm route, not a door slam.
Scenario 5 of 8
A local reporter emails: "Doing a piece on wellness programs. Can you tell me exactly what your disclaimers cover and whether you're FDA approved?"

What happens next?

Key: D. Two triggers stack here: media contact (escalation trigger) and Class B subject matter (regulatory status, disclaimer wording). B is the subtle trap -- that FDA line exists in the staff pack for CUSTOMERS asking in good faith, not for on-the-record press. Class B questions from media go up, not out.
Scenario 6 of 8
Your best caption performed great organically last month. You decide to put ad spend behind it. A teammate says: "It already ran fine -- boost it."

What is the correct process?

Key: C. Boosting converts a post into a paid ad (Lesson 4, platform box). Bank copy is your approved claim set, but the gate still checks context -- especially the landing-path match, which changes with the boost destination. A confuses reach with review; D is compliance in reverse.
Scenario 7 of 8
Your new hire starts Monday. You are slammed. It would be easy to email them the staff pack PDF and have them "read it before Friday."

What does the sign-off ritual actually require?

Key: B. Read aloud, together, Day 1, signed, dated, filed, re-run on drift (staff pack 1.1; Lesson 5). C fails the platform rule: if they can type to a customer under your brand, they sign first. A and D produce no defensible training record when you need one.
Scenario 8 of 8
A member posts on YOUR business page: "This program CURED my diabetes. Best decision of my life!!" It is getting likes.

You did not write it. What do you do?

Key: C. Adoption is the trap: leaving it (A), liking it (B), or leaving-while-archiving (D) all keep a cure claim live on YOUR channel. The HOLD folder is for compliant story material -- this post could never pass the content gate anyway. Moderate, correct kindly, log, escalate.

The answer key with explanations is now shown under each question. Review every miss, re-read the lesson it points to, and retake until you clear 7 of 8. Your best score is saved on this device.

← Module 5 Finish: Back to the Academy Hub →