Session Delivery Guide

Click a week to open its session script. Each week has phase tabs — Opening, Evidence, Core Work, and Closing — so you can jump straight to the part you need during a Zoom call.

12 sessions 60 minutes each Internal use only
How the portal connects to this guide Every item listed as "homework" below lives in the client's portal as a workbook exercise — they fill it in between sessions, you read it in the admin panel before the next one. The weekly Baseline Check-in (6 sliders, top of each week page, 90 seconds) auto-saves and plots on their dashboard trend chart — 12 weeks of dimension data by the final session.
  • Read client workbook entries in the admin panel before every session
  • Check their Baseline Check-in scores — which dimensions shifted?
  • OS Builder unlocks after Week 7 is marked complete in the portal

Standard Session Shape

0–5 minArrival and state check
5–15 minEvidence review — what did they do this week?
15–45 minCore work — teaching, exploration, NLP where appropriate
45–55 minIntegration — key takeaway in client's own words
55–60 minCommitment — exact homework agreed, not vague
Week 1
Awareness
Seeing the Pattern
Week 2
Understanding
The Origin Story
Week 3
Acceptance
Ending the Internal War
Week 4
Responsibility
The Agency Shift
Week 5
Self-Trust
Building the Evidence
Week 6
Alignment
Congruence by Design
Week 7
Momentum
The Forward Lean
Week 8
Consolidation
What Has Shifted
Week 9
Architecture
How I Actually Operate
Week 10
Values
Your Hierarchy
Week 11
Integration
Your Operating System
Week 12
Maintenance
The Forward Plan
1

Week 1

Awareness Seeing the Pattern

← All weeks
What this session is actually for The client stops being a person who is their patterns and starts being a person who has them. That shift sounds subtle. It isn't. The Client Brief debrief is your most important tool today — handle it with curiosity, not sympathy.

Before the session — admin panel

Week 1 has no prior workbook entries. Check that their portal access is active and their intake Baseline Score is recorded.

  • Their Baseline Index scores — highest and lowest dimensions
  • Any responses that stood out: very high, very low, incongruent
  • The patterns that surfaced most clearly across multiple dimensions
  • Their Client Brief prepared in advance
"I had the pattern." Not "I am the pattern." Even once. Even briefly. That's the breakthrough. Sometimes it happens in session; sometimes you hear it in the way they describe their Pattern Journal at the start of Week 2.
Intellectualising. Perfectly articulate accounts with zero emotional contact. Slow them down: "Where do you feel that in your body right now?"
Performing insight. Real recognition is slower and sometimes uncomfortable. If it's too smooth: "What's the part of this you're not sure about? What doesn't fit?"

The one-word opener State Elicitation

Don't start with "How are you?" It invites a social answer and you learn nothing. The one-word check-in is deliberate NLP state elicitation — it bypasses the social reflex and gives you real information about where they actually are before you do anything else.

"Before we get into anything — just one word. What's your state right now, walking into this?"

After you get the word — pace it first, then lead. Say the word back: "Okay, [nervous]." Then move. Whatever they give you is your starting material.

They say…What to do
Energised / curious / readyMatch and amplify. "Good — let's use that." Bridge straight to content.
Anxious / nervous / apprehensiveAcknowledge and normalise. "That tells me it matters to you. Let's go." Don't over-explore — move forward.
Resistant / flat / tiredName it directly. "Okay. What would need to happen in this call for it to have been worth showing up?" Future-pace them into the session.
Blank / confused / can't find a wordOffer a sensory bridge: "If that feeling had a colour or texture, what would it be?" Then continue. This unlocks people who live analytically.
Overwhelmed / lots going on"What percentage of you is here?" If below 50%, spend 2 minutes on a state break before proceeding: "Take a breath. We're not going anywhere for 60 seconds."
Never skip the one-word check-in to save time. The word they give you is the session's first data point — and sometimes it's exactly what the session ends up being about.
NLP in this phase
State Elicitation

Open question + short answer + pace → lead. Gets real internal state before the social mask goes up.

Pacing & Leading

Repeat their word back (pace), then bridge to your direction (lead). Don't skip the pace — matching first builds permission to lead.

Future Pacing

For flat/resistant clients: "What would make this worth your time today?" orients them toward outcome rather than away from discomfort.

Setting the programme contract

Week 1 has no homework to review. Use the evidence slot to land the contract — what the programme asks of them and what they're committing to. Get a real answer, not a polite one.

"Before we look at your results — I want to make sure we're on the same page about how this works. There will be things to read and exercises between sessions. The sessions are only as useful as what you bring into them. I'll always check what you've done at the start. Not to police it — but because the work between sessions is where change actually happens. Does that feel like something you can commit to?"

If they hedge or give a vague "yes, sure" — push once: "What would make it hard to do? Let's name it now rather than at Week 3."

Point them to the portal. Show them where the exercises live, how the weekly check-in works, and that you can see their entries before each session. Transparency about the admin view builds accountability.

The portal walk-through

If they haven't logged in yet — walk them through it briefly:

  • Week page → reading + exercises + weekly check-in sliders
  • Check-in: 6 dimensions, rate 1–10, takes 90 seconds
  • Workbook saves automatically as they type
  • Dashboard shows their score trend across all 12 weeks

Debriefing the Client Brief Sensory Acuity

Start with surprise, not summary:

"When you read through your results — what surprised you? What felt most uncomfortable to look at?"

The thing they want to argue with is usually the thing. Note it but don't push yet — stay curious. Walk through their lowest-scoring dimensions exploratorily, not diagnostically:

"What does your life actually look like in this area right now? Paint me a picture."

Then the timeline question — this is where the session deepens:

"When did this start to feel like this? Can you place it on a timeline?"

The observer position Perceptual Position

"Most people live inside their patterns the way a fish lives in water — it's the background, not something you can look at. What I want for you this week is the ability to step back and just watch. Not fix, not judge — watch. You'll start to notice: 'Oh, there it is. That's the thing.' That shift — from being the pattern to seeing the pattern — is the foundation of everything."

Identifying the three patterns

Get specific. Don't let this stay abstract:

"Give me a situation from the last two weeks where you saw your pattern in action. Walk me through it in detail."
"What did the pattern do? What did it make you avoid, pursue, or protect?"
"And what is this pattern actually competent at? Because every pattern is competent at something."

That last question is a reframe. Do it for each of the three patterns. By the time you're done, the Three Patterns Inventory exercise is already mostly complete in the conversation — the written version is just capturing what was just said.

NLP in this phase
Meta-Model — Recover Specifics

When they generalise ("I always do this"), recover specifics: "Always? Give me the most recent example."

Perceptual Position Shift

The observer position is 2nd-position work — asking them to watch themselves from outside. If they struggle: "Imagine watching yourself on CCTV in that moment. What do you see?"

Competence Reframe

"What is this pattern competent at?" shifts from deficit to resource. Every pattern has a positive intention — find it.

Timeline

"When did this start?" begins the timeline work that deepens in Week 2. Don't excavate here — just open the door.

Integration (45–55 min)

"Before homework — what's the one thing from today that you want to make sure you carry out with you? Say it in your own words."

Let them state the insight. Don't summarise for them — their language for it is more durable than yours.

Commitment (55–60 min)

  • 1Daily Pattern Journal — 5 minutes every evening (in portal). Same time each day.
  • 2Drift Timeline — portal exercise, completed before Week 2
  • 3Three Patterns Inventory — portal exercise, brought to Week 2
  • 4Weekly Baseline Check-in — 6 sliders at the top of the Week 1 portal page
"Not a vague intention. Five minutes, same time each evening. When will that be?"Get a specific time. Anchor it to something they already do — morning coffee, after dinner. Not "when I remember."

Closing well

End at 60 minutes. Not 65. Not "just one more thing." Starting and ending on time is the programme's first piece of evidence that you model what you teach.

After the call — no action needed. Week 1 post-session admin is minimal. Just confirm portal access if there's any doubt.

2

Week 2

Understanding The Origin Story

← All weeks
What this session is actually for The shame breaks this session. Or it starts to. Most clients leave Week 2 with a fundamentally different relationship to their patterns — they start feeling explained rather than condemned. Hold compassion without softening honesty. Those are different things and clients feel the difference.

Admin panel — before this session

  • Read their Pattern Journal entries — how do they describe their patterns? What language and tone?
  • Read their Three Patterns Inventory — which patterns did they name? How did they describe each one?
  • Check Week 1 check-in scores on their dashboard — which dimensions are lowest?
  • Note any themes you want to trace back to origins
The client describes the origin of a pattern with warmth — not criticism. Sometimes there are tears. Sometimes a long silence followed by "that actually makes sense." Sometimes they say something generous about their younger self for the first time. Don't try to summarise it. Just stay with it.
Shame flooding.If origins work gets overwhelming — voice changes, sentences trail off — come back to resources: "And you got through that. What did it build in you?"
Blaming others."That's real. And you're not here to resolve that relationship — you're here to understand the pattern so you can decide what to do with it now."

The one-word opener State Elicitation

Same structure as Week 1. Same pace-then-lead rule.

"Before we get into it — one word. Your state as you arrive today."

Pace the word, then bridge to the Pattern Journal. The bridge is important — don't just pivot without transition. Connecting the state to the work makes the move feel natural:

Bridging to the Pattern Journal

"[Word]. Okay. Let's use that as a starting point. You've had a week of watching your patterns — tell me about that. Not a summary of the whole week. One specific moment where you caught the pattern in action. The most vivid one."

The move from "one word" to "Pattern Journal" is this bridge sentence. The instruction "not a summary — one specific moment" is what makes the review useful rather than abstract. Without it, clients give you a week-in-review. With it, they give you material.

Why "one specific moment"?
Specificity Principle

Generalisations ("I kept people-pleasing all week") are cognitive and distant. One specific incident has sensory data — where they were, what they saw and heard, what happened in their body. That's where the real information is.

NLP Anchoring

Getting them into a specific memory creates a mild re-experiencing of the state. This is useful — you want them in the pattern's neighbourhood, not narrating it from a distance.

The Pattern Journal review protocol Sensory Replay

The Pattern Journal review is not a summary session. It's a structured incident replay. Most coaches rush this and lose the best material of the whole programme. The 5-step protocol below is the method — you don't need to name the steps aloud, just follow them.

Step 1 — Select one incident

"Don't tell me about the week as a whole. Tell me about one specific moment — the most vivid one you recorded, or the one that stayed with you. Where were you?"

Wait for them to land in the memory before continuing. The "where were you?" grounds the incident physically. If they start narrating from a distance ("So I was at work and I basically..."), slow them down: "Actually be there. Describe what you see."

Step 2 — Sensory replay VAKOG

"Walk me through it. What were you seeing — who was there, what was around you?"
"What were you hearing? From them — from yourself?"
"Where did you feel it in your body first? Before you did anything — what happened physically?"

Don't rush to the next question. The bodily sensation question is often where the most significant material surfaces — many clients haven't been asked this before. If they pause or look surprised, stay with it: "Take your time with that."

Step 3 — Find the trigger point

"When exactly did the pattern kick in? Was it something they did? Something you anticipated? Or was it already running before anything external happened?"

The trigger is almost never where they first think it is. They'll say "when he said X" and the real trigger was three sentences earlier, or the night before when they anticipated the conversation. Keep probing: "And before that — was there a moment even earlier?"

Step 4 — Meta-programme direction Meta-Programme

"In that moment — was the pattern moving you away from something, or toward something?"

Away from = avoiding pain, conflict, rejection, risk.
Toward = seeking approval, certainty, comfort, control.

The answer shapes how you frame the reframe in Week 3 onward. Note it. This is a meta-programme — a deep sorting mechanism. Most patterns have a dominant direction.

Step 5 — The observer check Perceptual Position

"And as you're describing this — are you watching it from the outside, or are you still inside it?"

If they're still inside the memory (associated), they'll answer in present tense and feel the emotion. If they're watching from outside (dissociated), their tone is cooler and more descriptive. You want them to be able to access both — associated for contact with the experience, dissociated for learning from it. "Step back from it slightly. Watch it like a filmmaker. What do you notice now?"

Quick reference — the 5 steps
1. Select one incident

"Most vivid one. Where were you?"

2. Sensory replay (VAKOG)

See → Hear → Body. Don't skip the body question.

3. Find the trigger

"When exactly?" — it's almost always earlier than they think.

4. Direction

Away from pain / Toward comfort? Note it.

5. Observer check

Inside or outside? Help them access both.

If they didn't do the journal

Don't skip the protocol — use a recalled incident from before the programme instead. "Okay. Think of a moment in the last month where the pattern showed up clearly. Walk me through it." Then run steps 2–5. The review still works.

Every pattern was once a solution Reframe

"Every pattern you've identified was once a solution. At some point it was the right answer to a real situation. The people-pleasing wasn't a flaw — it was a way of keeping peace in an environment where peace mattered. The perfectionism wasn't neurosis — it was a way of avoiding a specific kind of pain. Before we go further, I want to trace each pattern back to where it began."

Pattern biography — the question sequence Timeline

"How long have you had this pattern?"
"When was the earliest time you remember doing this?"
"What was happening around that time?"
"What problem was it solving?"
"Who taught it to you — or what situation taught it to you?"
"How has it tried to help you since then?"

Don't rush this. The moment a client starts describing the origin with warmth rather than criticism — stay with it. That's the session's most important moment.

The reframe Reframe

"So this pattern was intelligent. It was the best answer you had to a real problem. The difficulty isn't that you're broken — it's that you're running software written for a situation you're no longer in. Does that land?"

Watch how they receive this. Real acceptance is slower and quieter than quick agreement. If they agree instantly — probe: "What's the part that's harder to accept?"

Letter to the Younger Self Parts Work

"There's an exercise this week — writing from the you who understands this now, to the younger version of you who first figured out that pattern. Let the Pattern Biography settle first. Then write the letter when it feels right — not at the last minute."
NLP in this phase
Positive Intention Reframe

Every behaviour has a positive intention behind it — even destructive ones. Finding it removes shame and creates choice.

Timeline Regression

"Earliest memory" is a light regression. Don't excavate — just open the door. The pattern biography does this safely.

Parts Work

The Letter to the Younger Self is implicit parts integration — the adult part communicating with the part that created the pattern. It's gentle and safe without naming it as NLP.

Dissociated Position — Optional

When the pattern biography is done but the memory still carries clear emotional charge, ask the client to imagine floating above their timeline and watching the origin moment from outside. "What do you notice about that younger version of you from up there?" Creates spatial distance from the emotion without requiring full reliving. The client will have had a loose attempt at this in their Week 2 portal prep — build on what they found. Use only when the charge is still present after the reframe.

Integration (45–55 min)

"What's the thing that shifted for you today? In your own words — not what you think it should be."

Commitment (55–60 min)

  • 1Pattern Biography — portal exercise, all three patterns
  • 2Letter to the Younger Self — portal exercise, this week
  • 3Protection Inventory — portal exercise, before Week 3
  • 4Pattern Journal continues — new prompt: "What was this pattern protecting?"
  • 5Weekly Baseline Check-in — top of Week 2 portal page
After deep sessions like Week 2, some clients feel raw. It's fine to name it: "You've done some real work today. Be gentle with yourself this week — the exercises will help you process what came up."

What to watch for in the portal this week

Mental and Pattern & Identity dimensions often shift in the Week 2 check-in after the origins work — either upward (relief/insight) or downward (overwhelm). Both are useful. Either way, it's information for Week 3.

3

Week 3

Acceptance Ending the Internal War

← All weeks
What this session is actually forMost of a client's available energy is consumed by fighting themselves. When the war pauses — even briefly — they feel it. That felt difference is the session's most important moment. Acceptance here is not resignation — it's the decision to stop spending energy denying reality so it's available for responding to it.

Admin panel — before this session

  • Read the Acceptance Statement they drafted (honest or performed?)
  • Read the Two Chairs if submitted
  • Pattern Journal — what's the ratio of self-observation to self-attack?
  • Week 2 check-in scores — any shifts in Mental or Pattern & Identity?
Client pauses. Something changes in their face or voice. They describe — often with surprise — a feeling of something lifting. "Room to breathe." "Space I didn't know I didn't have." Name it quietly: "Notice what that feels like. That's what was going into the war."
Pseudo-acceptance. Too easy, no grief in it. Push: "What would it actually mean to stop fighting yourself here? What would that feel like?"
"But won't I just stay here?" Answer directly: "Everyone who has made lasting change accepted their starting point first. Acceptance isn't where you stay — it's where you start from."
"One word — your state. Then: how did the Pattern Journal go this week? Not the summary — one moment where you saw the pattern and something was different about how you watched it."

That last clause is the key shift: "something was different about how you watched it." You're checking whether the Week 1 observer position has started to stick.

Review the Protection Inventory — this is essential setup for the core work:

"For each pattern — what is it protecting you from? What would you have to feel if it wasn't there?"

Listen carefully. These answers often reveal the session's live material. Also ask: "Did the Pattern Journal change anything about how you experience the patterns — not the patterns themselves, but your relationship to watching them?"

Making the war visible

"Before we talk about acceptance — I want to count the cost of the war first."

Walk through the Cost of the War Audit together. For each form of self-attack, ask what it looks like for them. When done: "Add it up. Roughly how many hours a week does the war cost you?" Let the number land. Then: "Has any of this ever produced lasting change? Not temporary compliance — lasting change."

The acceptance reframe Reframe

"Acceptance isn't resignation. It isn't saying this is fine. It isn't giving up. It's the decision to stop spending energy denying reality — so all of that energy is available for responding to it."
"A swimmer who stops thrashing doesn't sink. They float. And then they can actually swim."

Acceptance Statement

Structure: "This is where I am. This is how I got here. It makes sense. And it is workable."

Have them draft one in the session if time allows. Push for specificity — vague statements are aspirations, specific ones are claims backed by evidence.

NLP in this phase
Cost/Benefit Reframe

Making the cost of the pattern visible creates motivation to change. Asking "has it ever worked?" challenges the unconscious belief that self-attack is effective.

Metaphor

The swimmer metaphor bypasses resistance — it's embodied and visual. Use it if the conceptual explanation isn't landing.

  • 1Cost of the War Audit — portal exercise
  • 2Acceptance Statement — portal exercise, read aloud each morning
  • 3Two Chairs — portal exercise
  • 4Pattern Journal continues
  • 5Weekly Baseline Check-in — top of Week 3 portal page
4

Week 4

Responsibility The Agency Shift

← All weeks
What this session is actually forThe gear changes here. First three weeks were warm and backwards-looking. This week turns the chair around. "No one is coming" — used correctly — doesn't feel like blame, it feels like liberation. Delivery matters.

Admin panel — before this session

  • Acceptance Statement — honest or performed?
  • Pattern Journal — how much victim grammar? ("they made me", "I had no choice")
  • Two Chairs if submitted
  • Week 3 check-in — Directional dimension often signals readiness for this session
"I've been choosing this. I didn't realise I was choosing it." That sentence — or any version of it — is the breakthrough. Sometimes the client makes the deferred decision in the room and something visibly settles.
The blame flip."That's fault, not responsibility. Fault beats you up for the past. Responsibility asks what you're doing next."
Waiting to feel ready."Readiness is usually a feeling, and it comes after the action, not before."
"One word — state. And then — how did the Acceptance Statement go? Were you actually saying it aloud?"

The "actually aloud" question is deliberate. Clients who do it in their head are cognitively processing. Clients who say it aloud are embodying it. The difference is significant and worth naming.

"I want to look at your language this week. In your journal — how often did you catch yourself saying 'I can't', 'I have to', 'I have no choice', 'they made me'?"

This primes the Language Audit that's the core homework. Let them report it. Don't interpret yet.

Fault vs. responsibility

"Fault looks backwards. Responsibility looks forwards. You may not be at fault for the patterns you learned — you didn't choose the circumstances. But you are now the only person alive who can change them."

The Responsibility Line Language Pattern

"What's below the line right now — things happening to you? Name them."
"Now let's move the first one. 'This is happening to me' becomes 'I am choosing this because...' Can you finish that sentence?"
[Client finishes the sentence]
"That's not a moral judgement. It's just accurate. What do you notice about that sentence?"

The First Owned Decision

"I want you to make one decision this week that you've been deferring. Not a big life decision — just one that's been taking up quiet energy. You know what it is."

Ask them to name it in the session. Then: "What would it mean to make it right now, before the end of our call?"

NLP in this phase
Language Pattern — Owner Grammar

"I can't" → "I won't / I choose not to." "I have to" → "I choose to because..." Small rewords, massive internal shift in locus of control.

Decision Anchoring

Getting them to make the deferred decision in the session creates an in-session experience of agency. Much more powerful than assigning it as homework.

  • 1Responsibility Line — portal exercise
  • 2Three-day Language Audit — portal exercise
  • 3First Owned Decision — made and recorded in portal as first Evidence Log entry
  • 4Pattern Journal — new prompt: "Where did I have more choice than I admitted today?"
  • 5Weekly Baseline Check-in — top of Week 4 portal page
5

Week 5

Self-Trust Rebuilding the Evidence Account

← All weeks
What this session is actually forThis is the engineering session. The central challenge: clients will propose commitments that are too big. Your job is to cut them, then cut them again, until what's left would survive their worst day.

Admin panel — before this session

  • Evidence Log — did they record the First Owned Decision?
  • Responsibility Line — what moved above the line?
  • Language Audit entries — what rewrites came up?
  • Week 4 check-in — Directional and Behavioural dimensions are your signal
Around day 10–14 of consistent micro-commitments, something shifts. Decisions get faster. They trust execution will happen. "If I can rely on myself here, where else?" — usually heard at the start of Week 6.
Heroic commitments."I believe you on a good day. I need something that survives your worst day."
Collapse after a break.The question at Week 6 isn't "what went wrong" — it's "what did you do next?"
"State — one word. And the decision from last week. Did you make it?"

If yes: "How did it feel after?" Let them describe it — this is the first deposit in the evidence account.
If no: stay curious, not disappointed. "Walk me through what happened."

"What's the last promise you made to yourself that you silently abandoned? And what did abandoning it teach you about your own word?"

This is the Integrity Audit question — opening it in the evidence slot primes the core exercise.

The evidence account

"Most people stuck don't have a motivation problem. They have an evidence problem. Years of abandoned plans have taught them, rationally, that their own word doesn't mean much. Not because they're weak — because that's what the evidence says."

Three Micro-Commitments — the four rules

Rule 1: Sized for your worst day, not your best. Would it survive a terrible Wednesday?
Rule 2: Under ten minutes. Not as a destination — as a minimum.
Rule 3: Binary. Done or not done. No grey area.
Rule 4: Within your sole control — no dependency on others.

Calibration dialogue when they propose too much:

"I'll exercise for 30 minutes every morning."
"Your worst realistic day — exhausted, slept badly, running late. Would you exercise?"
"Probably not."
"What's the version that survives that day?"
"...five minutes?"
"Which one feels almost embarrassing to call a commitment?"
"Five minutes."
"That's the right one."

The repair protocol

"When you break a commitment — and you will, once — repair it within 24 hours at reduced scale, without self-punishment. No ceremony. Just do the smaller version and continue."
NLP in this phase
Evidence Reframe

Reframing low self-trust as an evidence problem (not a character flaw) removes shame and makes the solution practical: create different evidence.

Future Pace

After they set a commitment: "Picture yourself at 10pm on a bad day this week. You've done your 5 minutes. What do you notice?" Anchor the win in advance.

  • 1Integrity Audit — portal exercise
  • 2Three Micro-Commitments — set and recorded in portal
  • 3Repair Protocol — portal exercise
  • 4Evidence Log — starts now, portal exercise, nightly, kept promises only
  • 5Weekly Baseline Check-in — top of Week 5 portal page
6

Week 6

Alignment Congruence by Design

← All weeks
What this session is actually forThe client can now see themselves, accept themselves, own their future, and keep their word to themselves. This week asks: in what direction? Values elicitation often feels like peeling back a layer to find what was always there but never looked at directly.

Admin panel — before this session

  • Evidence Log — how many commitments kept?
  • Did they use the repair protocol?
  • 6 weeks of check-in data now visible — look at the arc. Which dimensions are lagging?
  • Prepare the observation: "I've been reading your entries and I noticed..."
Client uses a Decision Filter on a live decision — and says no to something they'd previously accepted, or yes to something they'd deferred. Alignment stops being abstract. It has now cost something, or paid something.
Values performed for the coach.Test against the calendar and bank statement, not against eloquence.
Borrowed self.Some clients discover they've been living according to inherited values. Hold it without rushing to resolve it.
"State. And the Evidence Log — how many days did you hit the micro-commitments? Which one was hardest? Did you use the repair protocol?"

If they used the repair protocol: "That's more significant than hitting all three. You proved that a bad day doesn't end the system."

"Looking at your calendar and your bank statement from last month — without me giving you any framing — what do you notice about where your time and money actually went?"

Let them answer first. This is the setup for the Two Honest Documents audit. Don't rush to values elicitation before they've seen the gap.

Values elicitation Values Elicitation

"What actually matters to you? Not what should matter. Not what sounds good. What genuinely does?"

Keep asking: "And what does having that give you?" — this ladders up to the core value beneath the surface value.

Force-ranking

"I want you to force-rank your top seven. If you could only have one — which would you keep? Remove it. Now which one? Keep going."

Decision Filters

"From your top three values, build three questions that every significant yes must pass. Specific enough that they'd actually change a decision."

Test them immediately on a real live decision: "What's something you're currently deciding? Run it through the filters now."

NLP in this phase
Values Elicitation + Laddering

"What does having X give you?" drills down from surface value (security) to core value (freedom). Keep laddering until they arrive somewhere that has real emotional charge.

Force-Ranking

Eliminates intellectual hedging. You can't have everything at number one — the ranking reveals the real hierarchy.

  • 1Values Elicitation — portal exercise, top 7, force-ranked
  • 2Two Honest Documents audit — portal exercise
  • 3Decision Filters — portal exercise, minimum 3 questions
  • 4One real decision run through filters — recorded in portal before Week 7
  • 5Evidence Log and micro-commitments continue
  • 6Weekly Baseline Check-in — top of Week 6 portal page
7

Week 7

Momentum Sustainable Progress

← All weeks
What this session is actually forEverything built so far gets turned into structures that don't depend on motivation or mood. Willpower runs a distant third to identity and environment. The client's most reliable existing habit already has a trigger, a location, and a minimum dose — study it and copy it for new behaviours.

Admin panel — before this session

  • 7 weeks of Evidence Log — where is consistency strongest?
  • Decision Filters — are they using them?
  • Check-in trend chart — which dimensions have moved most? Which are lagging?
  • Values from Week 6 — which ones are currently underserved by their structure?
Client has a bad day — and the system holds anyway. They miss the morning, run the repair protocol, and continue without a spiral. They experience the difference between being carried by motivation and held by structure. Usually reported in the final phase (Weeks 9–12).
System perfectionism."I want you to do the first Weekly Review before our next session — rough is fine, just done."
Ambivalence about arriving.Sudden collapse in micro-commitments near the end. Ask: "What would it mean if this actually worked?"
"State. And the Evidence Log — six weeks in now. What do you notice about the pattern across the weeks? Where are you most consistent?"
"What's your most reliable existing habit? Something you do consistently regardless of motivation. Walk me through exactly how it runs — time, location, trigger, what kicks it off."

You're reverse-engineering their strongest existing habit to use as a template for the micro-commitments they want to build. The answer to "why does this work?" is the blueprint.

The friction principle

"The client who keeps a consistent habit isn't more disciplined — they've made the good version slightly easier and the bad version slightly harder."

Walk through the Friction Audit: "For each behaviour you want — what makes the good version hard right now? What makes the drift version easy?" Then make one friction change per behaviour. Boring and specific. Moving a phone charger. Opening a document the night before.

The Weekly Review

"30-minute standing appointment. Every week. Same time, same place. This is the heartbeat of your Operating System. When will it happen — exact time, exact day?"

Have them put it in their calendar while you're on the call. Not later. Now.

The 90-Day Plan

"One page. Three outcomes — things that will have happened, not things you'll try. The weekly action that produces each. And the things you're deliberately not pursuing this quarter — because that list matters as much as the first."
NLP in this phase
Strategy Elicitation

Uncovering the structure of their most reliable habit (trigger → response → reward) so you can replicate it for new behaviours.

Environmental Design

Change the environment, not the willpower. Friction reduction is behavioural NLP — make the good behaviour the path of least resistance.

  • 1Friction Audit changes — implemented this week
  • 2First Weekly Review — scheduled and completed before Week 8
  • 390-Day Plan — portal exercise, drafted for Week 8
  • 4OS Builder — unlocks in portal after Week 11 is marked complete (Phase 3 only).
  • 5Evidence Log and micro-commitments continue
  • 6Weekly Baseline Check-in — top of Week 7 portal page
8

Week 8

Consolidation What Has Shifted

Note: The final session is now Week 12 (Maintenance). The closing session script below applies to Week 12. Use this session to take stock of Phase 1–2 before entering the Operating System phase.

← All weeks
What this session is actually forThree equal parts: measurement (before/after Baseline Index comparison), articulation (completing the OS), and rehearsal of return (preparing for drift to happen again). Closing the coaching relationship well is itself part of the work.

Admin panel — before this session

  • Before/after Baseline Index comparison ready
  • 12 weeks of check-in trend data — which dimensions moved most? Which lagged?
  • OS Builder — how complete is it? Note which parts need finishing
  • Full arc of 12 weeks' entries — prepare 2–3 specific observations they may not have noticed
Reading the before/after side by side, the client recognises the change is real, measured, and theirs. And then — if you've done your job — they say something that makes clear the coaching has become internal. They're asking themselves the questions. They know the way back.

Baseline is not a place they visited. It's a place they now know how to return to.
Premature flight.Some clients go efficient and summary-focused before the session ends. "I notice we're wrapping up quickly. Is there anything that hasn't been said?"
Clinging."This isn't the end of the work. The programme ends here. The work continues in you."
"State — one word. And before we go into the session: one word for how it feels to be at Week 12."

Two state checks. The first word is their present state. The second is their relationship to the ending. Let both land.

"The Weekly Review — how did the first one go? And looking at the Evidence Log across the whole programme — what does the account look like compared to when we started the Integrity Audit?"

Let them hear the difference themselves. Don't summarise for them.

The before/after comparison

Pull up the Baseline Check-in trend chart on their dashboard — 12 bars of dimension data. Then put the original Baseline Index score alongside the current one.

"Where did the most movement happen? What produced it?"
"Where was there least movement? What does that tell you?"
"Which dimension feels most different — not in score, but in how you experience it day to day?"

The Identity Statement Identity Reframe

"Write it evidenced, not aspirational. Not who you're trying to become — who the evidence of the last twelve weeks says you are. Start with: 'I am someone who...'"

Push for specificity. Vague identity statements are aspirations. Specific ones are claims backed by evidence.

Closing the relationship

"Before we close — what do you know about yourself now that you couldn't have written twelve weeks ago?"
"Which single practice, if you kept only one, would protect the most of what you've built?"
"What do you want to say about the work you've done here — not for my benefit, for yours?"

That last question often produces the most honest thing said in twelve sessions. Stay with whatever comes.

NLP in this phase
Identity-Level Reframe

"I am someone who..." shifts from behaviour-level change (I do X) to identity-level change (I am someone who X). Far more durable.

Evidence Anchoring

The before/after comparison makes subjective change objective. Change that felt gradual becomes visible as something concrete.

Future Pace

The Drift Warning Signs protocol is a future pace — rehearsing return before drift happens so the pattern is already installed when it's needed.

Integration + commitment (45–60 min)

"Two or more Drift Warning Signs appearing at the same time — that's the signal. What's your first move?"

Establish the sequence: see the signs → open OS at Drift Warning Signs page → do the Weekly Review → contact Sam for a check-in if needed.

After the session — within 48 hours

  • Send before/after Baseline Index comparison (from admin panel)
  • Remind them to export their OS as PDF from the OS Print page in the portal
  • Ask for a testimonial — now, while the result is still felt
  • Offer optional 30/60/90-day check-in
  • Portal access stays active for post-programme reference
9

Phase 3 — Week 9

Architecture How I Actually Operate

← All weeks
What this session is actually forPhase 3 begins. The shift is from building raw material to assembling a coherent, documented system. Week 9 identifies the specific conditions under which this client functions at their genuine best — not performing, actually themselves. This becomes the blueprint for the OS.

Admin panel — before this session

  • Review all 8 weeks of check-in data — which dimensions moved most during Phase 1 & 2?
  • Re-read the Client Brief — how does the client's trajectory compare to the starting point?
  • Note any patterns still showing up that haven't fully shifted
The client identifies a specific period when they were genuinely functioning well — not their best ever, just a real time when they felt like themselves. They describe it in detail and realise: the conditions are replicable. The OS is no longer abstract; it has a blueprint.
Idealised best.The client describes a fantasy version of their best, not a real one. Push for a specific time, a specific place. "When did you actually feel like this — not in theory, in your real life?"
"State — one word. And: what's the most notable thing that's happened since we last spoke?"
"Week 8 — you looked back at the last eight weeks and named what shifted. What's still sitting with you from that?"

This bridges Phase 2 and Phase 3. The client carries the consolidation forward.

When I am at my best

"Think of a period in the last two years — not the best you've ever been, just a time when you were genuinely functioning. What was different about that time?"
"What environment were you in? What were you doing with your time? Who were you around?"
"What would a good day have looked like during that period — from morning to evening?"

Write their answers down as they speak. These become the raw material for OS Part 1 (Who I Am At My Best) and Part 4 (My Systems).

The blueprint

"What you've just described — that's the blueprint. Not the perfect version. The real version. That's what we're building the OS from."
Key questions for this session
Specificity over aspiration

Keep returning to real examples. If the client drifts into what they want to be like, redirect: "When did this actually happen?"

Conditions, not character

The goal is to identify circumstances, not just traits. "I work best when I have uninterrupted mornings" is more useful than "I work best when I'm motivated."

Integration + commitment (45–60 min)

"This week: write the 'When I Am at My Best' section of the OS — use what you described today as your starting point. Don't polish it. Write the version that's actually true."

After the session

  • Unlock Week 9 in admin if not yet done
  • Note which conditions the client identified — useful for spotting drift in later sessions
10

Phase 3 — Week 10

Values Your Hierarchy

← All weeks
What this session is actually forThe values were elicited in Week 6. Week 10 tests, refines, and locks the hierarchy — because stated values that have not been tested against real trade-offs are not operational values. The client now has enough data from their own recent decisions to be honest about the order. This session produces the Values section of the OS and the Decision Filters.

Prep

  • Re-read client's Week 6 values work
  • Note any decisions the client has described in sessions 7–9 — which values were in play?
  • Prepare to test the ranking against real examples
The client revises their values ranking — not because they got it wrong, but because they now have evidence. The version they write today is truer than the version from Week 6. They experience the difference between stated values and lived values.
Values performed for the session.The client writes what sounds right rather than what's true. Test everything against the calendar and bank statement.
"State — one word. What's the most significant decision you've made since we last spoke?"
"Review your Week 9 work — the blueprint. What did you notice when you actually tried to write it?"

Testing the hierarchy

"Pull up your Week 6 values. Read them out. Now: in the last month, when two of these were in conflict — which one won?"
"Was that the deliberate choice, or did it just happen?"
"If you had to rank these based on what your actual decisions say rather than what you want them to say — what order would they go in?"

Decision Filters

"Draft three to five questions that every significant yes must pass. The question isn't 'is this a good idea?' — it's 'does this align with what I actually care about?'"

OS Builder opens at the end of this session — unlock it in admin before Session 11.

NLP in this session
Values elicitation refinement

Return to the laddering: "What does having [value] give you?" Run this for any values that still feel vague or inherited.

Congruence check

Test decisions somatically — state the choice and calibrate the response. Which decisions produce a clear yes or clear no in the body?

Integration + commitment (45–60 min)

"This week: complete the Values section in the OS Builder, including your ranked hierarchy and at least three Decision Filters. And — use one of the filters on a real decision before Session 11."

After the session

  • Unlock Week 10 in admin
  • Remind client to open the OS Builder from their dashboard — all chapters are now available
  • Note the revised values order — compare to Week 6 in your session notes
11

Phase 3 — Week 11

Integration Your Operating System

← All weeks
What this session is actually forWeek 11 is the assembly session. Everything built across the programme gets compiled into one document. The client begins drafting before this session (OS Builder opened at end of Week 10). The session is used to review each section together, complete gaps, and ensure the OS reflects who the client actually is — not the polished version. The OS is not finished here; it is completed enough to be functional.

Prep

  • Open the client in admin → OS Draft tab — read every chapter, then write your OS review note before the session (the client sees it as a highlighted banner in their OS builder, so they arrive having already read your feedback)
  • Prepare specific questions for any sections that appear vague or aspirational rather than honest
  • Have the Identity Statement prompt ready
The client reads their Identity Statement out loud and it lands as true — not aspirational, not performed. The difference between "I am trying to become" and "I am" is felt, not just said. The OS stops being a template and becomes their document.
Polished inaccuracy.The OS sounds great but isn't quite honest. "Would you stake something on this being true right now — or is this who you're aiming at?"
"State — one word. And: when you read through your OS draft before today — what surprised you?"
"Review your Week 10 work — the Decision Filters. Did you use one? What happened?"

OS review — section by section

Work through each OS section together. For any section that's vague, ask: "What's the specific, honest version of this?"

The Identity Statement Identity Level

"Write it evidenced, not aspirational. Not who you're trying to become — who the evidence of the last eleven weeks says you are. Start with: 'I am someone who...'"

Push for specificity. Vague identity statements are aspirations. Specific ones are claims backed by evidence.

The Recovery Protocol

"This is the section you'll turn to first when you drift. Is it specific enough to be useful at 2am when you're not at your best? Read it as if you're the future drifted version."
NLP in this session
Identity-level anchoring

Anchor the integrated state to the Identity Statement so reading it re-accesses the state, not just the words.

Future pace the OS

Mentally rehearse using the OS six months from now: "Which section do you open first when things get hard?"

Integration + commitment (45–60 min)

"Before Session 12: finalise every section of the OS. If something isn't true yet, write a placeholder that says 'still developing' rather than leaving it polished but false. And: write the Letter from Baseline."

After the session

  • Unlock Week 11 in admin
  • Open OS Draft tab in admin → write or update your OS review note (the client will see this as a banner the next time they open their OS builder)
  • Add private session notes — which OS chapters need the most work before Session 12?
  • Remind client: Session 12 is the final session — Baseline Index retake due before it, and all OS chapters should be complete
12

Phase 3 — Week 12 · Final Session

Maintenance The Forward Plan

← All weeks
What this session is actually forThis is the final session. Three equal parts: measurement (before/after Baseline Index comparison makes twelve weeks of subjective change objective), completion (OS finalised together), and rehearsal of return (the client leaves knowing not just what changed, but how to return when drift comes back). Closing the relationship well is itself part of the work.

Admin panel — before this session

  • Before/after Baseline Index comparison ready
  • 12 weeks of check-in trend data — which dimensions moved most? Which lagged?
  • OS Builder — how complete is it? Note which parts need finalising
  • Full arc of 12 weeks' entries — prepare 2–3 specific observations they may not have noticed
Reading the before/after side by side, the client recognises the change is real, measured, and theirs. And then — if you've done your job — they say something that makes clear the coaching has become internal. They're asking themselves the questions. They know the way back.

Baseline is not a place they visited. It's a place they now know how to return to.
Premature flight.Some clients go efficient and summary-focused before the session ends. "I notice we're wrapping up quickly. Is there anything that hasn't been said?"
Clinging."This isn't the end of the work. The programme ends here. The work continues in you."
"State — one word. And before we go into the session: one word for how it feels to be at Week 12."

Two state checks. The first word is their present state. The second is their relationship to the ending. Let both land.

"The Weekly Review — how did the last one go? And looking at your Evidence Log across the whole programme — what does the account look like compared to when we started?"

Let them hear the difference themselves. Don't summarise for them.

The before/after comparison

Pull up the Baseline Check-in trend chart on their dashboard — 12 bars of dimension data. Then put the original Baseline Index score alongside the current one.

"Where did the most movement happen? What produced it?"
"Where was there least movement? What does that tell you?"
"Which dimension feels most different — not in score, but in how you experience it day to day?"

OS finalisation

"Let's go through the OS together one final time. Not to polish — to make sure it's honest and usable."

Focus on the Recovery Protocol and Drift Warning Signs — these are the sections they'll need most.

Closing the relationship

"Before we close — what do you know about yourself now that you couldn't have written twelve weeks ago?"
"Which single practice, if you kept only one, would protect the most of what you've built?"
"What do you want to say about the work you've done here — not for my benefit, for yours?"

That last question often produces the most honest thing said in twelve sessions. Stay with whatever comes.

NLP in this phase
Identity-Level Reframe

"I am someone who..." shifts from behaviour-level change (I do X) to identity-level change (I am someone who X). Far more durable.

Evidence Anchoring

The before/after comparison makes subjective change objective. Change that felt gradual becomes visible as something concrete.

Future Pace

The Drift Warning Signs protocol is a future pace — rehearsing return before drift happens so the pattern is already installed when it's needed.

Integration + commitment (45–60 min)

"Two or more Drift Warning Signs appearing at the same time — that's the signal. What's your first move?"

Establish the sequence: see the signs → open OS at Drift Warning Signs page → do the Weekly Review → contact Sam for a check-in if needed.

After the session — within 48 hours

  • Send before/after Baseline Index comparison (from admin panel)
  • Remind them to export their OS as PDF from the OS Print page in the portal
  • Ask for a testimonial — now, while the result is still felt
  • Offer optional 30/60/90-day check-in
  • Portal access stays active for post-programme reference