Kit

Consulting Practice

Every session prepped with a brief that remembers what the client said last time — and what they promised to do about it.

Nine clients, no assistant, and the thing that actually makes a session good is remembering what they said last time — and what they promised to do about it. The first run reads back through a year of your calendar and rebuilds the practice: every recurring one-to-one you hold with someone outside your own organisation, as an engagement with the sessions you have already run against it. Then you say what was contracted and on what terms, and from then on each weekday at seven Glade lays out the day's sessions and writes the brief for each — last session, what they committed to, what has come up with them since — as a document you can read on the way in. Say "just came out of Dana's session" afterwards and the note is written, filed under her, with what she committed to on its own row. Before a session, ask for an agenda built from what they committed to and what the last note left open, and walk it a point at a time in the room: what you write there goes into the note afterwards. Each client's outcomes are kept in their own words with where each stands as you say it, what you gave them is on record with what came back, and Glade can propose times for the next session from your calendar without booking anything. Your own supervision and training hours have a log of their own, with no client in it. On Fridays the review says where delivery stands against what you sold, which engagements have gone quiet, what looks worth invoicing, and the themes running across the practice — the pattern, never a client's name. Nothing here contacts a client: a follow-up, a recap or a note proposing times is drafted for you to send when you ask. And nothing you learn in one room is ever carried into another.

Try it free

1 agent, 2 routines, 1 dashboard, 6 datasets, 5 skills. Installing offers the first sweep on the same screen — connect, run it, and everything can be retimed or paused after.

The PracticeExample data
This week’s sessionsfrom the weekday morning run

Aisha — Adventure Works · Sales team workshops

in two days · 4th of 4 sessions · brief ready

Dana — Northwind Traders · Leadership coaching

in six days · 8th of 10 sessions · brief ready
Sessions still to run, by engagementcontracted, less what the log records as held
Operating model review12
Team offsite design4
Leadership coaching3
Founder coaching1
Sales team workshops1
Where the roster sitsfive engagements
5
  • Active3
  • Scoping1
  • Wrapping up1

one is scoping and one is wrapping up — the pipeline behind them is yours to watch

Every session, and what was committed toheld and still ahead
Dana — session 7Held · Northwind TradersBring the team charter to the next session
Marco — session 2Held · ContosoDraft the offsite agenda with his two leads
Tomas — session 7Held · LitwareShare the handover plan with his successor
Lena — session 1Scheduled · Fabrikambrief still to write

The crew

Glade

Holds the practice, writes the brief before every session, and never carries one room into another.

Steady, discreet, unhurried after a hard hour.

What else it installs

Practice rosterdataset

One row per engagement — who it is with, what was contracted, and how much of it you have delivered.

Session logdataset

One row per session — held or still ahead — with what they committed to and where the note lives.

Session agendadataset

What a session is for, one point at a time, with a note for what was said.

Client outcomesdataset

What each client says they want from the work, in their words, and where each one stands as you have said.

Client resourcesdataset

What you gave each client to do, read or use, when, and what you say came back.

Supervision logdataset

Your own supervision and training, as you mention it: when, what kind, how many hours, and what it was.

Session notesskill

"Just came out of Dana's session" — and the note is written, filed under her, with what she committed to on its own row.

Brief builderskill

"Brief me on Dana" — last session, what she committed to, and what has come up since, before you walk in.

Agenda and timesskill

"An agenda for Dana's next session", "when can I see Marco?" — an agenda from what is on the record, and a time from your calendar.

Outcomes and resourcesskill

"Dana wants her team to decide without her", "gave her the delegation grid" — a client's goals and what you gave them, kept.

Supervision and trainingskill

"Two hours of supervision this morning" — your own development, as a log of hours.

The Practicedashboard

The day's sessions with their briefs, what each client committed to, and how much of what you sold you have delivered.

Call plannerroutine

Each weekday at seven: today's sessions, and a brief written for every one that needs it.

Runs each weekday at 7am

Practice reviewroutine

Fridays: what is left to deliver against what you sold, what looks worth invoicing, and what the practice keeps circling.

Runs fridays at 4pm

How it works

The mechanics of this kit, plainly — what runs and when, where the data lands, and what you look at.

  • Call planner runs each weekday at 7am and keeps the The Practice dashboard fresh. Each weekday at seven: today's sessions, and a brief written for every one that needs it.
  • Practice review runs fridays at 4pm and keeps the The Practice dashboard fresh. Fridays: what is left to deliver against what you sold, what looks worth invoicing, and what the practice keeps circling.
  • What is captured lands in the Practice roster dataset, which lives at Data/Practice Roster in your vault — yours to open, search, and edit like any other file.
  • What is captured lands in the Session log dataset, which lives at Data/Session Log in your vault — yours to open, search, and edit like any other file.
  • What is captured lands in the Session agenda dataset, which lives at Data/Session Agenda in your vault — yours to open, search, and edit like any other file.
  • What is captured lands in the Client outcomes dataset, which lives at Data/Client Outcomes in your vault — yours to open, search, and edit like any other file.
  • What is captured lands in the Client resources dataset, which lives at Data/Client Resources in your vault — yours to open, search, and edit like any other file.
  • What is captured lands in the Supervision log dataset, which lives at Data/Supervision Log in your vault — yours to open, search, and edit like any other file.
  • The The Practice dashboard reads from the dataset and shows, at a glance: this week's sessions · briefs ready · agenda for the room · where the outcomes stand · engagements on the roster · where the engagements stand · sessions still to run, by engagement · the roster · every session, and what was committed to · themes across clients · how this board reads · sessions by client · your supervision and training, hours by kind.

The wiring, in one breath: Glade holds Session notes · Glade holds Brief builder · Session notes writes to Session log · Call planner writes to Session log · Session notes writes to Practice roster · Call planner writes to Practice roster · Practice roster shown by The Practice · Session log shown by The Practice · The Practice kept fresh by Call planner · The Practice kept fresh by Practice review · Call planner run by Glade · Practice review run by Glade · Glade holds Agenda and times · Glade holds Outcomes and resources · Glade holds Supervision and training · Agenda and times writes to Session agenda · Agenda and times writes to Session log · Outcomes and resources writes to Client outcomes · Outcomes and resources writes to Client resources · Supervision and training writes to Supervision log · Session agenda shown by The Practice · Client outcomes shown by The Practice · Supervision log shown by The Practice.

Getting the most from it

A kit earns its place when it changes what you look at and what you say, not when it is installed. This is the rhythm that makes it pay.

  • Read the morning card before the first session, not the board — that is the whole point of the seven o’clock run. It names the day’s sessions with their briefs, and the brief itself is a document in your vault you can open on the way in. The board is for Friday.
  • Say the session out loud the moment you come out of it: "just came out of Dana’s — we did the charter thing, she’s bringing it next time." Session notes writes the note, files it under her, puts what SHE committed to on its own row, and moves the engagement’s count. Thirty seconds then is worth an hour of trying to reconstruct it on a Sunday, and the commitments column is the thing the next brief opens with.
  • Be strict about what goes in "what they committed to". It is what the CLIENT said they would do — not what you agreed to send, and not what you think they should do. Anything you owe belongs in the notes. The column is only worth anything because it holds one kind of thing, and it is the single best question to open a session with.
  • Use Sessions still to run as the honest signal on Friday. It is the arithmetic — contracted, minus the sessions used — and the two figures behind every bar are in the roster table below it, so you can check the sum rather than trust it. Where the log records more sessions held than the roster counts, the log’s number is the one taken away. It is what tells you a client is about to run out of sessions while you are still planning the next one.
  • Ask Glade rather than searching: "where are we with Tomas?", "what did Marco commit to last time?", "who has gone quiet?" It reads the roster and the log and answers from what is written, and it will say plainly when something is not in the record rather than filling the gap.
  • Let the themes panel be about the practice, never about a person. It names what came up in more than one engagement and how many — which is where a talk, a post or a change to how you work comes from. It will never name a client in it, and Glade will not carry what one client said into another’s brief even if you ask.
  • Ask for an agenda the day before a session that needs one: “put an agenda together for Dana on Thursday.” Glade writes it from what she committed to last time, what the last note left open, an outcome still under way and anything you add, and each point says where it came from. Walk it from Agenda for the room on The Practice, a point at a time, with a tick and a note for what was said. What you wrote there goes into the note when you say the session is done.
  • Say what a client wants from the work in their words, once: “Dana wants her team to decide without checking with her.” It is kept as she put it. Where it stands is your word, never Glade’s: say “that’s under way” or “she’s got there” and the day goes beside it. Say what you gave her too (“gave her the delegation grid, she used it with two of her leads”), and the brief before the next session carries both.
  • Ask “when can I see Marco?” and Glade reads your calendar for the days his cadence points to and proposes up to three times. It books nothing and sends nothing: the booking is yours, and the note to Marco proposing the times is drafted for you to send when you ask.
  • Tell Glade about your own supervision and training as it happens, “two hours of supervision this morning”, and it goes on a log of hours that is yours alone. It leaves a client’s name off even where the session was about one, so what you took to your supervisor stays out of it.

Make it yours

Nothing here is fixed. The pieces are ordinary agents, routines, datasets and dashboards, so anything you know about shaping those applies. Retire whatever earns nothing.

Things people usually change first

Say any of these in chat, or edit them on the kit’s page in the app.

  • When the morning card lands — weekdays at seven out of the box — and when the review runs, or pausing either and keeping the roster and the log as they are.
  • Whether every session gets a brief, or only the ones you ask for. Said once and remembered.
  • Which meeting series are never engagements, and your own organisation’s domain so internal meetings are never filed. One line each, and the run stops suggesting them.
  • What was contracted, the terms and the rate on any engagement — yours alone, written as you give them. Nothing estimates a rate, and a blank stays blank.
  • The phase an engagement is in. It moves only when you say so: running out of contracted sessions does not make something "wrapping up", and nothing is closed without your word.
  • Whether a recorder feeds the notes. Read AI or Plaud can be connected under Connectors if you want transcripts read into a session note; nothing reaches one until you do.
  • The hours you take sessions in, the days you keep clear and how long a session is. Said once and remembered, and used only when you ask for a time.
  • A number of supervision hours your professional body asks of you, if you want the log set against it. Glade writes the figure you give it and, if you name the body, can look up its own published page and say where it found it.

Your first run

Installing starts a short setup conversation — not a form. Answer roughly, correct later.

  1. Adding the Kit offers the first run right away: connect your calendar on the same screen, and your email on the Connectors screen if you want thin entries placed, start it with one tap, and Glade reads back through a year of your calendar for the meetings you hold again and again with someone outside your own organisation. Each becomes an engagement on the roster, with every session it can see you already held against it. Where a calendar entry is too thin to say who it was with, it reads the subject line of the mail that arranged it — for that fact and nothing else.
  2. Prefer not to connect? Say so and Glade builds the roster with you instead, one engagement at a time. It starts from what 1Presence already knows, in your memory and in any proposals or statements of work in your vault, and asks only for the gaps: the client, what the work is, what you contracted for, roughly how many sessions you have run. The Call planner sits on your Routines screen if you change your mind later.
  3. When the first run finishes, Glade leaves a short note saying what it filed and asks for twenty minutes on what a calendar cannot know: what was contracted for each engagement and on what terms, how many of those sessions you have actually used, which of these are really engagements (a standing internal meeting is not), and any engagement settled on a call that never reached your calendar. Glade starts from what it already knows and what is in your vault, writes your figures as you give them and never estimates a rate.
  4. Whatever is still blank waits on the Kit page with a way back to Glade, and Glade offers it once the next time you talk. Tell it a part does not apply to you, or that you have finished setting up, and it stops asking.
  5. From then on the Call planner runs each weekday at seven: it puts anything newly booked on the log, writes the brief for every session in the next two days that has not got one, redraws the week ahead, and leaves a card only when the day actually holds something. The Practice review runs on Fridays.
  6. Glade never contacts a client and never writes to your calendar; a follow-up, a recap or a note proposing times is drafted for you to send when you ask, from that client’s record alone, and nothing from one client’s sessions is carried into another’s brief.

Watch the first pass, then tell it what you would have done differently — that correction teaches it more than any setup could.

The essentials

Learning, preferences and run costs work the same in every kit — so they are covered once, in the Kits guide.

Living with a Kit — the Kits guide →

← All kits

Put the Consulting Practice kit to work.

Install it, run it once against something that already happened, and see whether what comes back sounds like you.

Try it free

Everything it installs can be retimed, paused, or removed.

Last reviewed