Writing a Development Report: Separating Observation, Interpretation, and Assessment

“Unmotivated”, “refused”, “lacks insight”: words like these are quickly entered into a report. They seem to sum up a situation in a single phrase. Yet they often combine three different things: what happened, the presumed intention behind it, and a judgement about the person.

In German disability support, the structure and terminology vary between development reports, progress reports, and goal reviews, depending on the federal state, funding body, and service area. Our article on the structure of development reports explains these differences. Whatever the form, one writing principle remains useful: observation, interpretation, and professional assessment should be recognisable as separate elements.

Otherwise, later readers may struggle to see where the record ends and the interpretation begins. Keeping the two apart helps colleagues understand how an assessment was reached. It also leaves room for the perspective of the person the report is about.

An observation records what could be seen or heard: What did the person do or say? In which situation? How often or for how long? What support was offered, and what happened next?

Interpretation comes one step later. It considers what might explain the observation. This makes it a professional hypothesis, not a fact. “The noise may have played a part” is different from “He stopped because of sensory overload.”

Only then does the professional assessment follow. What does the situation mean for the agreed goal? Which conditions helped or hindered? What should the team retain, change, or explore together? The assessment concerns the significance of the situation for future support, not the value of the person.

This gives a report a clear sequence:

1. Observation: What could actually be seen or heard?
2. Perspective: What does the person say or communicate about it?
3. Interpretation: What professional hypothesis can be drawn from this?
4. Next step: What does it mean for the goal or future support?

Research on behavioural observation distinguishes concrete descriptions from statements that already contain strong inferences. Visible actions are easier to examine together than labels such as “unmotivated” or “provocative” (Girard & Cohn, 2016). This research did not study development reports in German disability support. The methodological principle is still useful: describe first, interpret second.

A randomised vignette study in medicine illustrates how consequential wording can be. A stigmatising note in a medical record led to more negative attitudes and differences in a treatment decision (Goddu et al., 2018). These findings cannot simply be transferred to disability support. They do show, however, that later readers encounter a person through the language used in earlier records.

The same caution applies when a new observation is too quickly explained by a known diagnosis. Research on “diagnostic overshadowing” is inconsistent and the overall quality of the evidence is low (Dell’Armo & Tassé, 2024). It does not establish an automatic effect. For everyday writing, it still offers a sensible precaution: keep other explanations open.

All wording examples in this article are fictional. They do not describe real people or cases.

1. From “unmotivated” to an observable account

Generalised: “Mr S. was unmotivated and refused to work.”

More specific: “Mr S. sorted eight components between 9:10 and 9:25. When the machine at the neighbouring workstation was switched on, he put the materials aside and said, ‘I’m not carrying on today.’ When asked, he pointed to his headphones. After moving to a quieter area, he resumed the task at 9:40.”

Professional interpretation: “The sequence suggests that the noise may have contributed to him stopping the task. Together with Mr S., the team will explore whether a quieter workstation or earlier access to an agreed aid makes the activity easier.”

2. From “manipulative” to a question about the circumstances

Generalised: “Ms B. manipulates the team so that she can leave early.”

More specific: “Within 20 minutes, Ms B. asked three members of staff in succession whether she could end the activity early. After two staff members said no, she asked a third person. She explained, ‘Anna let me leave yesterday.’”

Professional interpretation: “It remains unclear whether the repeated questions reflected inconsistent agreements, a current wish for a break, or another reason. The team will agree on a consistent response and ask Ms B. how she would like to communicate a request to change the plan.”

3. From “lost control for no reason” to situation, perspective, and next step

Generalised: “Mr T. lost control at lunch for no reason.”

More specific: “During lunch, Mr T. shouted four times, pushed back his chair, and left the room. Immediately beforehand, another person had moved his cup. In the conversation afterwards, Mr T. selected the symbol for ‘break’. He did not provide any further information.”

Professional interpretation: “It remains unclear whether moving the cup, wanting a break, or another factor was decisive. Together with Mr T., the team will explore how he can indicate that he wants a break earlier in this situation.”

A report does not have to provide a definite cause when the cause is unknown. It may leave open what is still uncertain. What matters is that the observation, the person’s communication, and the team’s conclusion do not merge into an explanation that sounds more certain than the evidence allows.

Reports can easily blur the person’s statement, a professional’s observation, and the team’s shared assessment. A few words are often enough to identify the source:

• “Ms B. said during the conversation …”
• “Mr T. selected the symbol …”
• “The professional observed …”
• “The team currently assesses …”

Not everyone communicates through speech or extended writing. A person’s perspective may also be expressed through symbols, photos, audio, signs, or other communication aids. In one study, the visually supported Talking Mats method helped some adults with learning difficulties communicate their views more effectively. It did not suit everyone (Murphy & Cameron, 2008). The appropriate form of communication therefore depends on the individual.

For Germany’s overall planning procedure, Section 117 of Book IX of the Social Code requires the person entitled to support to be involved throughout the procedure and their wishes to be documented. The provision does not prescribe the format of every service provider’s development report. It does reinforce a basic principle: the person’s perspective should not disappear into the professional voice of the team.

Strengths-based writing does not mean glossing over difficulties. Yet the sentence “Ms K. can travel independently by bus” still falls short. It does not show the conditions under which this works:

“Ms K. completed the familiar bus journey independently on four of five days. She used the saved route and a picture sequence for the transfer. When the stop display was not working, she asked the driver for the correct stop.”

The fuller version records ability and initiative without hiding the conditions that helped. This reflects the ICF, which explicitly includes environmental factors (World Health Organization). It leads to a practical question for the report: What was the person able to do, and what needed to be in place?

At Stellwerk Papenburg, participants use the Independo Journal app to document daily routines and work. Professionals review and add to these entries in the Portal. They also create development goals there; on the tablets, participants can select goals and related activities.

The team reports that participants complete their entries more independently and have a better overview of the work they have done and the goals they are currently pursuing. Getting started did take time: the team first had to build a suitable collection of photos and goals. The Stellwerk Papenburg practice report describes one organisation’s experience. It is not a scientific effectiveness study.

What matters here is the division of roles. The person’s own documentation provides a possible source. Professionals review and add to it, connect entries with goals and activities, and provide the professional interpretation. This does not automatically produce a finished development report.

A short check before completing the report can help:

1. Is it clear what was directly observed or communicated?
2. Are the situation, period, frequency, and support described as precisely as necessary?
3. Is it clear who said, communicated, observed, or assessed each point?
4. Are intentions, feelings, and causes presented as hypotheses rather than facts?
5. Have plausible alternative explanations been considered or left open?
6. Are strengths recorded together with the conditions that make them usable?
7. Does the interpretation lead to a traceable conclusion for the goal or future support?

A development report has to condense everyday life. That is precisely why its sentences should not claim more than the observations support.

Concrete descriptions and clearly marked hypotheses do not weaken a professional assessment. They show how it was reached. Recording what was observed, whose perspective is represented, and where interpretation begins creates a more reliable basis for the next step.

In the Independo Portal, professionals can connect approved everyday entries with goal work and professional documentation.