Writing a Development Report: Six Building Blocks for a Clear Structure

When professionals have to write a development report, they often start by looking for a template. A template promises orientation. In German disability support, however, there is no single development report with the same structure throughout the country.

The document may be called an Entwicklungsbericht (development report), Sozial- und Entwicklungsbericht (social and development report), Verlaufsbericht (progress report), or Zielauswertung (goal review), depending on the federal state, funding body, and service area. Sometimes the service provider writes a separate report. In other procedures, the professional documents directly in the needs-assessment instrument, which the responsible public body then reviews.

Four examples show the differences:

The comparison reveals recurring professional questions, but no uniform form logic. Before writing the first sentence, professionals therefore need to know which form applies to the specific procedure, which version is current, and who is responsible for the report or follow-up review.

Despite the regional differences, six recurring building blocks can be identified. They are not a replacement template. They are a way to organise the content professionally.

A development or progress report looks back at a defined period. To make the review understandable, it must be clear which goals are being assessed.

This becomes difficult when several plans or versions are in circulation. The relevant reference is not just any goal formulated in the past, but the goal plan on which the current service is based.

Lower Saxony’s B.E.Ni F5 LE form records the date of the underlying goal plan, the date of the goal review, the reason for the report, and the period covered. The Bavarian HEB-B forms consider development during the previous period in relation to the relevant goals. The KSV Saxony report also links its review to individual participation goals.

Three questions provide a useful starting point:

• Which period is being reviewed?
• Which goals apply to that period?
• Were there any changes that matter for the review?

Without this reference, it remains unclear how development or goal achievement is being assessed.

A goal describes an intended outcome. A support measure describes what is done to help achieve that outcome. The two are connected, but they are not the same.

Here is a simplified, fictional example:

Goal: Ms M. completes her weekly shopping with a prepared shopping list and the agreed support.

Support measure: A professional prepares the list together with Ms M., accompanies her when needed, and gradually reduces direct prompts.

The support measure is not simply the goal in different words. It shows what support actually took place.

Regional procedures record this in different ways. The Bavarian HEB-B forms review measures carried out and record planned measures for the next period. The B.E.Ni form asks about measures and methods that were used, including those that may not have been successful. In the KSV Saxony report, measures are linked to the relevant participation goals.

An approach that did not work as expected can still be professionally relevant. Future planning becomes more meaningful when the report shows what was tried.

“Achieved”, “partly achieved”, or “not achieved” is initially only a selection. It becomes professionally useful when the reason for the assessment is included.

Returning to the example:

Assessment: The goal was partly achieved.

Reason: Ms M. used the jointly prepared shopping list during four of six documented shopping trips. She needed fewer direct prompts when looking for products. She continued to need support at the checkout.

This explanation shows what the assessment is based on. It makes progress visible while also showing the remaining support need. A goal that has not been fully achieved does not become a personal failure. It provides information for the next planning period.

B.E.Ni uses a graded assessment with reasons. In the BEI_NRW 3.0 review, the person records their view of goal achievement and whether the goal remains relevant. The service provider adds a professional assessment. In the Bavarian HEB-B forms, the description of development is followed by a field for continuing the relevant goals.

Useful questions include:

• What was the person able to do during the period?
• What changed compared with the starting point?
• What support was still needed?
• What evidence supports the assessment?
• Do the person’s perspective and the professional assessment differ?

Development does not depend on the person alone. The environment, communication, assistive tools, available support, and organisational conditions can make participation easier or harder.

The B.E.Ni form explicitly asks about supporting and hindering factors and the resources used. BEI_NRW records contextual factors, including environmental facilitators and barriers, in a separate section. Its goal review also records supporting and hindering influences. The Bavarian HEB-B forms ask professionals to describe development while considering the person’s resources. The KSV Saxony report addresses resources, environment, and support needs in several places.

This means a development report should not only record the outcome. It should also record the conditions surrounding it.

During a shopping trip, a clear list and a familiar routine may have helped. A last-minute change of support person or a confusing environment may have made the activity more difficult. Recording these conditions prevents goal achievement from appearing to be a fixed characteristic of the person.

It also leads to the next professional question: Which conditions should be retained, adapted, or created?

Our article on ICF-oriented documentation in everyday practice explores how goals, activities, and context can be connected in ongoing documentation.

The person’s perspective does not appear in the same place in every procedure.

The KSV Saxony report includes a dedicated section for the person’s own perspective. Both Bavarian HEB-B versions also include a field for the perspective of the person receiving support and a signature line. In Lower Saxony, the person’s assessment is recorded in a separate form.

In North Rhine-Westphalia, LWL and LVR provide forms or materials for the Persönliche Sicht, the person’s own perspective. At LWL, a separate review form also helps the person prepare their view of previous goals and whether those goals remain relevant. The information is transferred into BEI_NRW 3.0, where the service provider adds a professional assessment.

For Germany’s overall planning procedure, Section 117 of Book IX of the Social Code sets common standards: the person receiving support must be involved in every procedural step, and their wishes concerning the goals and type of services must be documented. How this participation appears in the specific report or procedure differs by region.

The person’s perspective does not have to take the form of written text. A person may communicate using symbols, photos, signs, a speech-generating device, or other forms of augmentative and alternative communication. The origin of each statement should remain clear:

• Did the person express it themselves?
• Was a communication aid used?
• Does the statement record a professional observation?
• Is it a professional interpretation?

This distinction prevents a team’s interpretation from being presented as the person’s own statement.

A development report does not end with the review. It provides a basis for the next planning period.

In the Bavarian HEB-B forms, the description of development is followed by fields for continuing the relevant goals and describing planned measures. The KSV Saxony report contains separate sections for future goals and measures. Lower Saxony reviews progress and goal achievement, while the next decision is made within the overall and participation planning procedure.

At LWL, there is no separate service-provider report. The professional documents the participation process and the follow-up conversation directly in BEI_NRW 3.0 through PerSEH. The service provider then submits the follow-up review to LWL, which reviews it and decides how to continue the overall plan.

Depending on the procedure, a goal may be continued, reformulated, or no longer pursued. The goal may still fit while the support needs to change. New priorities may have emerged. Or a measure that was previously necessary may no longer be needed.

The outlook should therefore follow directly from the review:

• Which goals remain relevant?
• What should change?
• What support will be needed in the future?
• Which enabling conditions should be retained?
• Which barriers need to be considered?
• What matters to the person in the next period?

German federal law does not impose a general SMART requirement. Section 117 of Book IX of the Social Code requires the overall planning procedure to be goal-oriented, among other criteria, but it does not prescribe a particular method for formulating goals.

Regional procedures use SMART differently. KSV Saxony recommends agreeing goals using the SMART method where possible. The B.E.Ni 3.1 F2 C form instructs professionals to formulate outcome goals using SMART criteria.

The Bavarian HEB-B forms themselves contain no SMART instruction. However, the 2009 guidance for the mental health version applies a SMART rule to its intermediate goals.

The distinction matters: SMART concerns the formulation of goals during planning. A development or progress report later looks back at those goals. Not every sentence in the report therefore needs to follow a SMART structure.

The practical rule is simple: check the specific procedure and do not present SMART as a uniform federal legal requirement.

The quality of a development report is not determined only when the wording is drafted. Its evidence base emerges in everyday life.

A person tries a new route. A form of support works better than expected. A communication aid enables a decision. The same barrier appears repeatedly in a particular situation. If these observations have to be reconstructed from memory weeks later, important details are easily lost.

A traceable process looks like this:

Everyday situation → documented observation → link to a goal → professional interpretation → report or follow-up review

This does not mean that every everyday situation needs a detailed account. Relevant information should, however, be recorded in a way that allows professionals to connect it with a goal and a reporting period later on.

In the Independo Portal, professionals can review shared everyday entries, place them in their professional context, and connect them with goals and activities. This does not replace the regional form or professional judgement. It creates a more organised foundation for the point at which a report or follow-up review is prepared.

A development report or follow-up review can be checked using six questions:

1. Are the period and underlying goals clear?
2. Is it clear what support actually took place?
3. Is the assessment of goal achievement explained?
4. Are supporting and hindering conditions considered?
5. Can the person’s perspective be distinguished from the professional assessment?
6. Does the review lead to a reasoned outlook?

These questions do not replace the official guidance. The applicable procedure determines the order, required fields, responsibilities, and rating scales. As a framework, however, they help maintain the central thread: What was agreed, what happened, how is it assessed, and what follows from it?