An assessment looks tidy on a fee schedule: interview, testing, write-up, feedback. The week psychologists described to me doesn't look like that. Testing is the only block that behaves — it's scheduled, bounded, and it happens. Everything else gets pushed into the gaps between other people's calendars, and that fragmentation, not the total number of hours, is what makes the week hard.
I'm not a clinician and I've never run an assessment. What I have done is ask a lot of psychologists to walk me through an ordinary week, and the same shape kept appearing. This is that shape, assembled from their accounts rather than from a template.
Testing goes in the calendar. The rest of the assessment goes wherever it fits.
What does the week actually look like?
Roughly, and with a lot of variation between practices:
Testing sits in blocks. Half-days, usually, booked well ahead, and treated as immovable because a family has arranged their life around it. Published clinic schedules put testing at somewhere between six and nine hours for a full psychoeducational assessment, and that's the part that reliably happens when it's supposed to.
Interviews and collateral gathering scatter. An hour or two of clinical interview on paper, but the actual gathering — a call with a teacher, a form that hasn't come back, a follow-up question to a parent — arrives in fragments across days.
Scoring lands in between. Short, frequent, requiring focus, and hard to do well in a twenty-minute gap.
Writing gets whatever's left. This is the part everyone talked about. Published schedules allow four to six hours; the psychologists I ask directly describe ten to fifteen for a full write-up. Both numbers are real — one is what a practice can defensibly bill, the other is what the work takes.
Feedback is scheduled but preparation isn't. The meeting is in the calendar. Re-reading the file beforehand so you can talk about it fluently is not.
Why doesn't the week match the fee schedule?
Because a fee schedule describes billable units, and a week is made of available attention.
The four-block model is a fair description of the work. It's a poor description of the day, because it implies the blocks are interchangeable — that four hours of writing can go anywhere four hours exist. Every clinician I asked said the opposite. Writing an integration section needs a long uninterrupted run and a fresh head. Those two conditions rarely coincide with the gaps a clinical calendar actually leaves.
That's the real finding, and it isn't about speed. It's that the most cognitively demanding part of the job is systematically assigned to the worst hours of the week — the leftovers, the evenings, the weekend. I've written before about why report writing takes as long as it does; this is the scheduling version of the same problem.
What did clinicians say is hardest to schedule?
The write-up, consistently, and for a reason that surprised me the first time I heard it.
It's not that the writing is long. It's that it's interruption-sensitive in a way the other blocks aren't. Testing survives an interruption. Scoring survives an interruption. Reloading an entire case in your head so you can write a coherent interpretation does not — and if you're reloading it three times in a week because you never got a clear run, you're paying that cost three times.
Several people described a version of the same coping strategy: batch the writing, protect a block for it, and treat that block as being as unmovable as a testing appointment. The ones who'd managed it said it was the single biggest change they'd made. The ones who hadn't said the block kept getting eaten by something with a person attached to it.
The people who protected a writing block described it as the single biggest change they'd made.
What happens when a week slips?
It compounds, and this is the part I hadn't understood before people explained it.
A report that doesn't get written this week doesn't cost the same amount of time next week — it costs more, because the case has to be reloaded from notes rather than from memory. Two weeks later it costs more again. That's how a manageable queue becomes a backlog: not by adding work, but by making the existing work more expensive every week it waits.
And a backlog changes behaviour upstream. More than one practice told me they simply stop taking new assessments past a certain point in the term. Not because testing capacity is full — because the write-up queue is. That's a revenue ceiling set by a scheduling problem. The dollar version of this arithmetic is in what an assessment report actually costs a practice to produce.
What did the practices that fixed it change?
Three things came up repeatedly, and none of them is "work faster".
They separated the write-up in their own tracking. Most practices record assessment time as one lump. Splitting the write-up out makes the bottleneck visible and, more importantly, arguable in a staffing conversation.
They protected the block and defended it. Treated as a fixed appointment, not as flexible time.
They attacked the blank page rather than the structure. A better template reorganises work that was never the constraint — the hours are in the writing, not the headings.
That last one is where a drafting tool belongs, if one belongs at all: not to make the clinical thinking faster, but to make sure the protected block starts with something on the page instead of nothing. That's what ours is built to do, and it's deliberately the only part of the week it touches.
If you take one thing from this: the problem isn't the total. It's which hours the hardest work is getting.
— Ian
