How to Track Client Progress Without Adding Admin Hours

Almost every coach has tried to track client progress. A spreadsheet, a Notion database, a scoring rubric built one enthusiastic Sunday. Almost all of them abandon it within two months, and conclude that progress tracking is a nice idea that does not survive a real practice.

The systems fail for the same reason: they cost more time than they return. The fix is not more discipline. It is measuring less.

What Is Actually Worth Measuring

Three things. Not more.

• One outcome number. Where the client rates themselves on the thing they came for, 1 to 10. Same question, every time. Its absolute value is nearly meaningless; its direction over twelve weeks is the entire point.
• One capacity number. Energy, or how much control they feel over their time. This is your leading indicator — it moves before commitments start slipping.
• Commitment completion. Yes, partly, or no. Binary enough to scan, honest enough to be useful.

That is roughly thirty seconds of client effort and produces the only three lines you will ever actually look at.

What to Stop Measuring

• Session counts and attendance. Your calendar already knows.
• Detailed mood inventories. Rich, and nobody completes them past week three. Completion rate beats resolution, every time.
• Anything you would not change your behaviour over. The test for any metric: if this moved, what would I do differently? No answer means stop collecting it.

Why the Spreadsheet Always Dies

Three failure points, all fatal:

1. You are the collector. Any system where you transcribe what a client told you is a system that ends the first genuinely busy week.
2. Nothing chases. A form that does not send itself gets sent when you remember, which is not weekly.
3. It has to be read to be useful. Rows of numbers require you to go and look. You will, for a month.

Any workable system has to collect without you, chase without you, and surface the exception without you going to look.

The Cadence That Works

Weekly, for fortnightly sessions. Short enough that recall is intact, frequent enough to catch a bad week while it is still happening.

Send it on a fixed day, not relative to sessions — a fixed rhythm becomes habitual in a way a variable one never does. Mid-week beats Monday and Friday, both of which are distorted by the week's shape. And keep the questions identical: varying them feels more thoughtful and destroys comparability, which is the only reason you are collecting anything.

Using It Without Reading Everything

You should not be reading every response. You should be seeing exceptions:

• A capacity number down two weeks running.
• A commitment missed twice consecutively.
• A response that has become markedly shorter than that client's norm.
• Silence — a missed check-in from someone who always completes it.

Those four cover most of what precedes disengagement, as the week-three pattern describes. Everything else can wait for the session.

The Thirty Seconds That Make It Pay

Reference it at the top of the session. "I saw Wednesday was rough — start there?"

This is the whole return on the system. It saves the eight minutes of recap that opens most sessions, and it tells the client the check-in is being read — which is the only thing that keeps completion rates up. Collect responses and never mention them and you have taught your client it is admin; they will comply politely for a fortnight and then stop.

What It Buys You

Three things, in ascending order of value: sessions that start with substance instead of reconstruction; early warning on disengagement while it is still reversible; and — at renewal — a record showing exactly where someone started, which turns a conversation about price into a conversation about evidence.

That last one is why this is worth doing even in a practice of six clients. Doing it manually costs you an hour a week you will eventually stop spending. Interlude does the collecting, chasing and surfacing, so the cost is the thirty seconds where you mention it.