Ember

The Ember Codex

The own-words box: a prompt that quotes the client's commitment as they said it

The commitment belongs in your write-up in the client's own wording. One box prompt that quotes it out of the transcript, and the standard I set so a paraphrase does not pass.

Handy Gunawan · · about 3 min to read

Your client’s commitment belongs in the write-up in the words they used. In Ember Console, the session-report builder for coaches I build, that is one box: a prompt that takes the client’s sentence out of the transcript, and a standard it has to pass. Ember Console is in closed beta, and I call that box the own-words box.

One coach who sends a short recap after every session wrote in r/lifecoaching that the part making the biggest difference is “including their commitment in their own words”. Most answers under that question argue about whether to send one at all.

How do you write a client commitment in a session note?

Quote the client. The commitment box carries one sentence the client said in the recording, in their wording, with nothing the coach tidied afterwards.

Two published session frameworks already ask for it. Paperbell’s four-step framework ends on a Will Do in the client’s own words, and Real Balance’s session handout closes on what the client said they would commit to.

So the three lines I write into that box are short ones.

  1. Quote one sentence: the client’s commitment, their words.
  2. Keep the hedge if they hedged.
  3. Add nothing the client did not say out loud.

Each of those is an instruction, and that is all it is. A paraphrase breaks none of the three and still reads like a commitment, which is why the box system puts a second thing behind every section.

What makes an own-words eval fail a paraphrase?

An eval catches a paraphrase only when its test sends you back to the recording. The standard I set on this box is one sentence: the quoted line has to appear in the client’s own turn in the transcript. A smoother sentence fails it however well it reads, and writing that standard is the half of the work a prompt cannot do.

The Ember landing page puts the pair this way: “Ember learns from your edits and checks each result against your own criteria.” Each time an AI builds the report it gets every prompt and the eval system, and reworks a box until it passes the standard you set.

What this box costs you is a clumsy line in a tidy report. Keep the clumsiness, because a sentence your client would never say is a sentence they can argue with.

What is not stated yet?

Four questions about a box are still blank on my own fact sheet, and the answers are mine to publish.

  1. What a box is: a name, a prompt, an eval.
  2. Whether you can add, remove or reorder boxes.
  3. What an eval may check: length, wording, a fact, a rule you typed.
  4. How many reworks a failing box gets, and what you see.

Number three is the one this piece runs into. Until I answer it, the rule above stays a standard I write in plain English for an AI to meet.

Open the last write-up you sent and read its commitment line out loud. If it sounds better than your client talks, it is yours, not theirs.

Questions people ask next?

What is a coaching recap?

A short note the coach sends after a session. One r/lifecoaching poster keeps theirs to three items: what the client realised, what they committed to, and the obstacle they named. A summary of the whole session backfired, they found, because nobody reads it.

What if the client never said the commitment in one sentence?

Then the box has nothing to quote, and the line is yours to write. The report is editable in the Ember dashboard, so write it there and say whose words they are.

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