How to Use Threads in Your Coaching Practice

What Threads is

Threads is one page in Another Session that reads across your whole client list and surfaces the small things still moving between sessions. Not alerts. Not notifications. A quiet page you open when you choose to.

The seven threads, and what each one means

Threads surfaces seven kinds of signal. Each one is built from your own sessions and notes. No outside data, no guessing. Here is what they look like and why they appear.

• Note still open

  A client is back today or tomorrow, and the last session has no note. The thread appears because the next session will land better if you catch the thread while it is still warm. The action is to open the session and write four lines.

• Quietly away

  A client has not been on the schedule for three weeks or more, and nothing is booked next. The thread appears with a line from the last note, giving you a gentle reason to check in. The action is to send a short message or suggest a time.

• Since last summary

  Four or more sessions have happened since the last progress note or monthly summary. Enough has happened to write something that feels personal and specific. The action is to draft the update from your notes.

• Parent update

  For junior clients, six or more sessions since the last summary. The parent has not had a proper update in a while, and there is enough recent context to write one with care.

• Recurring theme

  The same significant word or idea has appeared in at least three of the last six session notes. You meant to build a block around it. The thread reminds you to pick it up deliberately.

• Milestone

  A client has reached their fifth, tenth, twenty-fifth, fiftieth, or hundredth session with you. The thread appears within a week of the milestone session, suggesting a moment to mark what has changed.

• Same focus

  A client's focus line has held for two months or more with at least four sessions in that window. The thread asks whether the focus still feels true, or whether something has quietly shifted.

How to read a thread card

Each thread card is designed to be read in about ten seconds. The structure is the same every time, so the scan stays fast even when the roster is full.

• The kind label

  A small tag at the top left that tells you what kind of signal this is. Note still open, quietly away, recurring theme. One glance and you know what you are looking at.

• The client name

  Always in Fraunces, always prominent. The card is about one person, not a category.

• The reason line

  One sentence in the Another Session voice, explaining why the thread appeared. Written to be read quickly, not to be comprehensive.

• The context lines

  Two or three wrapping lines below the reason. When you last saw them, when they are next in, a short memory from a recent note. The context that makes the thread actionable.

• The action

  A single button or link at the bottom of the card. Write the note, book a check-in, draft the update. One tap and you are in the right place.

When to open Threads

The page works best as a weekly ritual, not a daily habit. Once a week, ten minutes, with a coffee.

• Sunday evening or Monday morning

  Before the week starts, when you still have a clear view of the week behind you. The scan sets the small actions that keep the roster warm.

• Not between sessions

  Threads is not a todo list. It is a read. Opening it between sessions turns it into a source of stress. Open it when you have time to think, not when you have three minutes before the next client.

• Not every day

  The threads update slowly. A note still open will still be open tomorrow. A client quietly away for two weeks is still quietly away on Wednesday. The weekly cadence is enough.

How to act on what you see

The scan is only half the job. The other half is doing one or two small things before you close the page.

• Pick one thread to act on

  Not five. Not ten. One. The client whose note is most urgent to write, the check-in message that will land best, the summary that a parent is waiting for. One action per scan is enough to keep the roster warm.

• Dismiss what you choose not to act on

  Threads does not have a dismiss button because the signals are real. But you can mark a thread seen by tapping through to the action and then closing it. The thread will not reappear for seven days, which keeps the page from becoming a wall of guilt.

• Write the note first, then send the message

  If a thread points to an unwritten note, write the note before you send any check-in. The note gives you the specific detail that makes the message feel personal. "Still thinking about that volley drill from Tuesday" lands better than "Haven't seen you in a while."

How Threads fits with the rest of your workflow

Threads is not a separate feature. It reads from the same client list, sessions, and notes that the rest of the product uses.

• Notes feed Threads

  The more consistent your session notes, the richer the threads become. A note with a specific worked-on line becomes a recurring theme. A note with a parent mention becomes the context for a parent update.

• The schedule sets the cadence

  Quietly-away threads appear because the schedule shows no upcoming session. Note-still-open threads appear because the schedule shows a client coming back soon. Threads and the schedule share the same data.

• Summaries close threads

  When you send a monthly summary, the since-last-summary thread for that client disappears. The summary is both a client communication and a way to keep the Threads page clean.