Ember

The Ember Codex

Coaching session structure in Ember Console: the fixed template and the boxes that flex with each session

A coaching session structure splits in two: the sections and the standard behind each one stay fixed, and what fills them comes from the session you just had.

Handy Gunawan · · about 3 min to read

Split a coaching session structure in two. The order of the sections, and the standard each one has to meet, stay fixed. What fills them comes from the session you just had. A rigid order protects the step you skip when a call runs hot, and flexing follows the client.

I build Ember Console, a session-report builder for coaches, and it is in closed beta. A template there is that split written down.

How do you structure a coaching session?

Run the same six sections every time, goal setting near the front, commitments near the end.

  1. Check in on last session’s commitments.
  2. Agree the one thing today is for.
  3. Explore where the client is now.
  4. Draw out options in the client’s words.
  5. Write down what the client commits to.
  6. Read the commitments back before closing.

The six-step guide at icacoach.com walks the same session, and Develop The Edge has the coachee set the goals.

A template in Ember Console has your letterhead and the boxes you set. Each box has a prompt and a test it must pass, called an eval, and the AI you already use reworks the box until it passes the standard you wrote.

Box in your templateWhat its prompt draws from this session
Check-inwhat came back from last session
Focusthe one thing named today
Explorewhere the client says they are
Optionsthe options the client found
Commitmentswhat was agreed
Closethe next step and its date

The left column is set once, and the right one is written again after every call.

When is a rigid coaching session structure better than a flexible one?

Keep the order rigid while the craft is new, and flex when a client arrives with something your boxes have no room for. The cost of rigid is a session that serves the form instead of the person. The cost of flexible is write-ups that do not line up.

Coaches argue about the order because it is the half anyone can see during the call. The standard each section has to meet turns up later, in the write-up, with nobody else in the room to check it. One r/lifecoaching poster answers a new coach with GROW, whose four stages settle the order. The standard is left where it was.

The Ember landing page says the box system “learns from your edits and checks each result against your own criteria.” Those criteria are yours, and you write them once. The box system goes through one prompt and one eval, and Life coaching templates in Ember Console covers the letterhead they go under.

Set what each section has to prove. The words were always going to be new.

What is not stated yet?

Whether a box can be switched off for one session, when a client brought nothing for it, is not written down anywhere, and nor is whether the box order can change while the template stays as it is.

The letterhead fact sheet answers “not stated yet” to all three of its questions: how the letterhead is set, where language preference belongs, and whether one coach can keep several templates.

Questions people ask next?

Does every coaching session need the same structure?

The order can repeat without the session repeating. Keep the headings so two write-ups sit side by side, and let the answers under them come from the call you just had.

Which model should the fixed part follow?

Any model whose stages you can name out loud. GROW gives four: Goal, Reality, Options, Will. GROW coaching model questions as box prompts builds that one box by box.

Ember Console is a session-report builder for coaches, in closed beta: https://ember.anyeads.com/. There is nothing to sign up for yet.