Almost everyone tracks supervised hours in a spreadsheet, and almost everyone's spreadsheet has a quiet error in it. Usually the same handful of errors, discovered late, when reconstructing eighteen months of Tuesdays from a calendar and a vague sense of what happened.
Here's what tends to go wrong, and what a log needs to do to survive scrutiny.
Requirements differ by state, board, and track, and they change. Nothing here overrides your board's current handbook or your supervisor's guidance — check both.
The four failure modes
Categories collapse. Hours aren't one number. Boards distinguish direct client contact from supervision, individual supervision from group, and clinical work from non-clinical activity — and each has its own minimum, its own cap, or both. A single "hours" column can't answer the question the board is actually asking.
Caps get discovered at the end. Many categories are capped: only so many hours of a given type will count, no matter how many you log. If you're tracking raw totals, you find out about the cap when you submit, and a chunk of real work turns out not to count. The number you need visible is creditable hours, which is the smaller of what you did and what's allowed.
Pre-degree and post-degree get mixed. Practicum hours earned before your degree and hours earned after are governed by different rules and often different limits. Once they're combined in one column, separating them means going back through the dates.
The log stops matching reality. Sessions get cancelled, a placement ends early, a supervisor changes. If the ledger is a spreadsheet updated on Sundays when you remember, the gap between it and what happened widens quietly for months.
What a defensible log has
- Every entry categorized at the time it's created, not sorted out later.
- Both raw and creditable totals, so you can see when a cap is biting.
- Pre-degree and post-degree kept structurally separate.
- Supervisor and site attached to each entry — you will be asked, and remembering which supervisor signed which stretch two years later is genuinely hard.
- An export your board will accept, itemized rather than summarized.
- Progress against the requirement, not just an accumulating number. "412 hours" means nothing on its own; "412 of 1,750, with individual supervision at 78% of its minimum" is a status you can act on.
That last one is the difference between a record and a tool. A log that only accumulates tells you what you did. A log that measures against the requirement tells you what to do next month.
Why the arithmetic is easy to get wrong
One example, because it catches people. If a category is capped and you also have a separate minimum in a related category, the interaction isn't intuitive: hours can be simultaneously earned, not creditable toward one requirement, and still creditable toward another. Computing that correctly means encoding the board's actual rules, not summing a column.
How Flowers handles it
Flowers tracks hours toward licensure as a first-class feature rather than an add-on. California BBS requirements are built in for the LMFT track with the categories, caps, and deadlines encoded. For the LCSW and LPCC tracks, or any other state, generic tracking gives you a clean itemized ledger plus custom targets you define to match your board's handbook. Pre-degree and post-degree are separated structurally, creditable totals are computed against caps, and the whole log exports when it's time to submit.
It's free for up to 15 active clients, which covers most practicum caseloads, and it runs entirely on your own Mac — which matters more than usual when the records in question belong to a placement site with its own rules about where client data may live.