How to track client sessions without a spreadsheet
5 min read
Almost every independent practice starts in a spreadsheet. It is free, it is flexible, and for the first ten clients it genuinely works. The problem is not that spreadsheets are bad — it is that the thing you need changes shape as you grow, and a spreadsheet does not change with it.
Where the spreadsheet actually breaks
It is rarely a dramatic failure. It is a slow drift into not trusting your own file. Three things cause it, and they arrive in this order.
Logging moves off-site. You finish a session and the laptop is not open. You tell yourself you will fill it in tonight. Two or three nights of that and the file is a reconstruction rather than a record.
Payment state drifts out of sync. The session tab and the money tab are separate, and they only agree on the day you reconcile them. Between reconciliations you genuinely do not know who owes you.
Cancellations get flattened. A no-show, a cancellation with notice, and a session that simply did not happen all end up as a blank cell, so the pattern you most need to see is the one the file cannot show you.
If you have ever cross-checked your spreadsheet against your bank statement to work out whether someone paid, the file has already stopped being the source of truth.
What to look for in a replacement
The instinct is to look for more features. That is usually the wrong axis. A spreadsheet fails on friction and on structure, so the replacement has to win on exactly those two things — extra capability that raises logging friction makes the problem worse, not better.
Logging has to happen in the room, on a phone, in seconds. If it takes a form, it will get deferred, and deferred logging is how you ended up here.
Attendance outcomes need to be distinct. Completed, cancelled, and no-show are three different facts about your business and should never collapse into one.
Payment state belongs on the same record as the session. The moment money lives in a second place, the two drift.
The client, not the date, should be the organising unit. You look things up by person far more often than by day.
What you give up
Honesty matters here, because the switch is not free. A spreadsheet lets you invent a column at any moment. A purpose-built tracker does not — if it does not model the thing you want to record, you cannot bolt it on. For most practices that trade is worth it, because the columns people actually invent tend to be ones they stop filling in within a month. But if your record-keeping genuinely depends on a field nobody else would think of, keep the spreadsheet for that one thing.
You also give up bulk editing. Fixing forty rows at once is a spreadsheet superpower and no session tracker matches it. In practice this matters at migration time and almost never afterwards.
Moving across without losing the history
The mistake is trying to import three years of history on day one. It is slow, the old data is usually incomplete, and the effort tends to exhaust whatever enthusiasm was going to carry you through the first fortnight of a new habit.
Add your active clients only — the people you have actually seen in the last couple of months. Dormant clients can be added if they come back.
Start logging new sessions from today. Do not backfill.
Keep the old spreadsheet read-only for reference. Do not maintain both; running two systems is how both end up wrong.
After a month, check whether you have opened the spreadsheet at all. Most people have not.
The measure of success is not how complete the data is. It is whether you logged this week without thinking about it.
Blockday logs a session in two taps and keeps attendance and payment on the same record.
