Where psychologists lose the evening rewriting what the score tables already say
The score table is finished and correct. The observation narrative underneath it gets written, read back the next morning, and rewritten, because the first version read thin even though nothing about the administration was thin. It usually comes down to the structure: the first draft asks the narrative to do the score table’s job.
The narrative doesn’t need to re-report the scores
Describe what the table doesn’t show
A score table gives the number while the narrative exists to communicate what a number can’t: what the behavior looked like, in what context, and how consistent it was across the administration. A narrative that restates “the child scored in the moderate range of restricted and repetitive behaviors” repeats the table in sentence form. A narrative that describes the specific repetitive behavior, when it appeared, and whether it interfered with task engagement does what the table can’t.
The rewrite usually starts when the first draft defaults to restating scores instead of describing behavior. Fix that and the second pass gets shorter. The same split applies to any instrument that produces a score. A CARS-2 total and severity range sit in the table, and the narrative carries the behavior behind each rating.
Classification and diagnosis are two different sentences
The report has to show where the classification stops and the judgment starts
The ADOS-2 produces a classification. The DSM-5-TR diagnosis is a separate clinical judgment that draws on the classification along with developmental history, a parent interview such as the ADI-R, other standardized measures such as the CARS-2, and clinical observation across the full evaluation. A report that lets the classification read as the diagnosis invites a challenge. Picture an ADOS-2 classification sentence followed immediately by a diagnostic statement with no bridge between them. A due process hearing or a second opinion is built to find exactly that. Write the classification in one sentence and the diagnosis in another, with the reasoning that connects them in between.
Where the parent interview eats the evening
The transcript is a source. The report needs its own order.
A structured parent interview such as the ADI-R generates hours of material, and the temptation is to document by working through the transcript in the order it happened. That produces a narrative organized around what the parent said first. A reader needs the content sorted by domain first. With the ADI-R, organize the section around the algorithm domains: early development, social reciprocity, communication, restricted and repetitive behaviors, then pull the relevant history into each one.
Run this against your last three reports
A short audit that finds the pattern
Pull the observation narrative sections from your last three reports. Mark every sentence that restates a number instead of describing behavior. If most of the section does that, the first draft’s structure is causing your rewrites.
What a documentation system needs to preserve here
Speed that keeps the distinction intact
A system assembling this section has to keep the classification and the diagnosis as separate, attributable statements rather than merging them into one interpretive paragraph. It also has to draw the narrative from what the evaluator observed and entered. Plausible-sounding behavioral description with no source behind it fails that test.
Diagnosis Builder assembles the ADOS-2 and ADI-R sections from your entered observations and scores. The evaluator authors the classification and the diagnosis as separate statements and edits every interpretive sentence.
The evening goes to the paragraph that says what the table already said.
If the audit above turned up mostly restated numbers, a walkthrough of how Diagnosis Builder assembles the ADOS-2 and ADI-R sections will show you what a first draft built from observed behavior looks like.
