A psychoeducational report follows a predictable structure: reason for referral, background and history, assessment procedures, behavioural observations, results and interpretation, a summary or conclusions, and recommendations. The sections rarely change from one report to the next. What changes is the person inside them.
When psychologists ask me how to structure a psychoeducational report, they usually already know the sections. The question underneath is why the structure exists at all, and why it takes so long to fill in even when the outline is the same every time.
I'm not a clinician, so I won't tell you how to interpret a single finding. But I've spent the past year listening to psychologists talk through their reports, and the shape of a good one comes up again and again. It's worth writing down — partly so newer clinicians know the frame, and partly because it shapes what we build.
The outline repeats; the person inside it never does.
What sections does a psychoeducational report include?
Most psychoeducational reports move through the same seven parts, roughly in this order: reason for referral, background and history, assessment procedures, behavioural observations, results and interpretation, a summary or conclusions, and recommendations. Some clinicians fold observations into results, or add a separate identifying-information header, but the spine is consistent.
The order isn't arbitrary. It walks a reader from why are we here to what did we do to what did we find to what should happen next. As one Canadian review put it, to be of value "the report must be understandable and meaningful to its readers." That same paper notes that a psychological report has three purposes: to describe current functioning, to communicate recommendations, and to support improvement over time. The structure is just those three purposes laid out in sequence.
Why does the reason for referral shape everything else?
Because every later section is either answering the referral question or it's padding. The reason for referral states who asked for the assessment, what they wanted to understand, and the specific questions the report has to answer.
The clinicians I talk to are clear that a vague referral produces a vague report. The same review stresses that a report should "clearly identify the referral question(s), provide evidence that these questions have been queried, and report comprehensive answers to these referral questions." When the referral is sharp, the summary and recommendations almost write themselves. When it's fuzzy, the whole report drifts and the reader is left guessing what it was for.
So the reason for referral is doing quiet work far down the page. It's the yardstick every other section gets measured against.
How should background and assessment procedures be handled?
Background and history give the reader the context a set of scores can't: developmental, educational, and family history, prior assessments, and anything relevant to how the findings should be read. Assessment procedures then list what was actually done — the measures administered, interviews, observations, records reviewed, and the dates.
The instinct with both sections is to over-collect. The skill is deciding what's relevant to this referral question and leaving the rest out. Background isn't a biography; it's the subset of history that helps a reader interpret the results.
Assessment procedures matter for a different reason. They're where a report earns its credibility. A reader who can see exactly what was administered, from what sources, on what dates, can trust the interpretation that follows. It's the audit trail.
Background is the subset of history that helps a reader read the results.
What's the difference between results and interpretation?
Results are what the measures showed. Interpretation is what those results mean for this specific person. The most common report-writing problem in the literature is collapsing the two, or reporting results test by test without ever integrating them.
That same Canadian review describes generic interpretation — pasting in a stock sentence about a score without connecting it to the individual — as one of the biggest challenges for report writers. It also notes that test-by-test writing "is often reported to be difficult to understand" and "reduces the likelihood of the report being read in its entirety." Readers, especially parents and teachers, comprehend results better when they're organized by domain rather than by instrument.
This is the section that carries a psychologist's judgment. It's irreplaceable, and it's the part no template and no software should ever touch. The findings and their meaning are yours. The scaffolding around them is where the hours leak out — which is why report writing takes so long even when the outline is identical every time.
How do you write recommendations that actually get used?
Recommendations get used when they're specific, tied directly to a finding, and written for the person who has to act on them. A parent, a teacher, and a referring physician each need something they can do, not a paragraph they have to decode.
This is where the reason for referral closes the loop. Every recommendation should trace back to a question the referral raised and a result the report established. If a reader can't tell which finding a recommendation came from, it tends to get ignored.
The summary sits just above the recommendations and does one job: answer the referral questions in plain language, briefly, before the reader gets to the action list. Done well, someone should be able to read the summary and the recommendations alone and know what to do next.
Does the structure ever really change?
Not much, and that's the point. The sections are stable across nearly every psychoeducational report; what varies is the client, the findings, and the recommendations. That stability is exactly why so much of the report is mechanical.
Turning raw scores into the results-and-interpretation narrative is the genuinely hard, judgment-heavy part — I wrote a whole separate piece on going from raw scores to a report narrative. But the section headers, the framing language, the procedures list, the scaffolding that repeats from one report to the next? That's assembly, and it's what eats the late nights. In a survey of 93 health-service psychologists, most described working at or beyond capacity — 41% "at full capacity" and 39% "over-extended" — with non-billable clinical work among their most common sources of stress and workload tied to burnout. Assessment reports sit at the heavy end of that.
That's the gap we built around. You run the assessment and own every finding and conclusion; Soma assembles the repeatable structure so you're not rebuilding the same scaffold at 11pm. You review, edit, and sign every section, and the judgment never leaves your hands.
If you write these reports, I'd genuinely like to hear where your version of this structure gets slow — it shapes what we build. The goal is simple: a report that reads like yours, in a fraction of the hours. That's what Soma drafts for you to review and sign.
Thank you for reading, and for the care you put into getting these reports right.
— Ian
