I've spent a lot of the past year talking with psychologists about the parts of their week they wish they could get back. Almost every assessment-focused clinician lands on the same thing: report writing. Not the testing, not the scoring — the writing. One psychologist told me a single report runs 10 to 15 hours. Another described 14 hours of writing for every 5 hours of actual testing. Most of it happens at night, on weekends, and off the clock.
I'm not a clinician, so I won't pretend to tell you how to write your reports. But I do get to hear the same frustration over and over, and the pattern is clear enough that it's worth writing down — partly so other clinicians know they aren't the slow one, and partly because it shapes what we build.

One report is a stack of tasks, not a single one.
Why does one report take 10 to 15 hours?
Because it isn't one task — it's a stack of them. Reviewing the file and history, interpreting results, reconciling findings across measures, writing each section so it's clear and defensible, and tailoring recommendations to a real person. Every step is judgment-heavy, and none of it is fast.
The time also shows up in the research. A survey of 93 health-service psychologists found they spend a median of about 5 hours a week — roughly 7 on average — on non-billable clinical work, and more than half (51.6%) named that administrative load as a significant source of work-related stress. Assessment reports sit at the heavy end of that load: not weekly minutes, but multi-hour blocks per report.
What actually eats the time?
The clinicians I talk to are clear that the testing is the part they trained for and largely enjoy. The drain is the blank document afterward — translating scores and observations into prose that a parent, a school, or a referring physician can act on, and that will hold up if anyone ever questions it.
One clinician put it simply: "a big part of the unpaid work is the prep before and after." A report is exactly that, magnified — hours of skilled work that happen outside the billable session and rarely get counted.

Every report starts from the same blank page.
Is it slow writing, or is it the process?
In almost every conversation, it's the process — not the writer. Every report tends to start from a blank page even though much of the structure repeats from one report to the next. The same section headers, the same framing language, the same scaffolding get rebuilt by hand each time, and then the unique findings get poured in on top.
That's a strange way to spend expert time. The repeatable 60–70% — the structure and the connective tissue — is the part that doesn't need a psychologist's judgment. The findings and interpretation are the part that does. When those two get blended into one long manual task, the judgment work ends up competing with clerical work for the same late-night hours. It's the mechanical assembly, not the thinking, that drives the report-writing problem in private practice — and it's also why a better template alone doesn't solve it.

Separate the assembly from the thinking, and the hours come back.
What actually helps clinicians get report time back?
Two things come up again and again. First, not starting from a blank page. Second — and this is the non-negotiable one — keeping their own voice and judgment. No one wants a generic template that flattens their clinical reasoning into something that doesn't sound like them.
That gap is the reason we built Soma's report drafting the way we did. You complete the assessment; Soma assembles the repeatable structure and the connective tissue; you review, edit, and sign every section. Your interpretation, phrasing, and conclusions stay yours. It's software for clinicians, not a stand-in for one — the judgment never leaves your hands. (More on the reports side on our product page.)
Does faster reporting mean lower quality?
The clinicians I speak with are protective here, and they should be. Faster only matters if the report still reads like theirs and still holds up. The point was never to hand judgment to a machine — it's to take the mechanical assembly off the plate so the thinking, which is the part that actually matters, gets the clinician's full attention instead of their leftover energy at 11pm.
If anything, the clinicians who've reclaimed those hours tell me the reports got more consistent, not less — because the structure stops drifting when you're tired, and the time goes back into the interpretation.
The short version
Assessment report writing takes 10 to 15 hours because skilled clinicians are doing clerical assembly and clinical interpretation in the same exhausting block, usually unpaid and after hours. The interpretation is irreplaceable. The assembly isn't. Separate the two and most of the hours come back — without the report ever stopping sounding like yours.
If you write assessment reports, I'd genuinely like to hear how long they take you and where the time actually goes — it shapes what we build. The goal is a simple one: a report that reads like yours, in a fraction of the hours — see how Soma drafts a report you review and sign.
— Ian
