Duplicate documentation often arises where everyday support, goal work, service records, care, quality reviews and billing have to be documented in separate systems. This article explains why duplicate work happens and why the answer is not simply less documentation.
After the shift, a second shift often begins.
The group is settled and the handover is done, so it should be time to breathe for a moment or go home on time. Instead, a support professional sits down at the computer and transfers notes from the day, writes a progress entry, adds a service record, connects the situation to a participation goal and checks whether the same information also needs to go into another form.
Documentation is not the problem. In disability support, documentation is professionally necessary because it makes support traceable, protects quality and shows how participation is enabled in everyday life. The real problem is different: the same information often has to be captured, transferred and reformulated too many times.
That is where duplicate documentation begins.
What duplicate documentation means
Duplicate documentation does not simply mean writing something twice. In practice, the issue is usually more complex.
An everyday observation may first be written on paper, later entered into digital documentation, then used in a development report, then added to a service record and perhaps finally transferred into a template for a funding body. One situation becomes several documentation processes.
For example:
A person is practising how to take over individual steps while cooking together. The support professional notices that, for the first time, the person starts the next step without being reminded. Professionally, that matters because it relates to a participation goal. At the same time, the situation may be important for internal handover. For billing or reporting, it may also be necessary to document that a support service was provided. If care-related services are involved, another record may be required as well.
One everyday moment turns into several documentation logics.
The associations representing people with disabilities describe this tension clearly: service records often require detailed documentation, and processing them takes time away from direct support. They therefore call for digital and more standardised forms of documentation, including interfaces for approval and review. (Caritas)
A young person documenting a moment on a phone.
Why duplicate documentation arises so easily in disability support
Disability support in Germany has changed significantly since the Federal Participation Act (BTHG), the German Bundesteilhabegesetz, came into force. The reform is intended to strengthen participation and self-determination. Disability support is no longer part of the welfare assistance system, but part of participation law under SGB IX; support is meant to be oriented more strongly around individual needs rather than a specific housing form or institution. (BMAS)
That shift is professionally right and important. At the same time, it increases the need for traceability. It is no longer enough to document in general terms that support took place. Organisations need to show which goals were agreed, what support was provided in everyday life and how that support contributed to a person’s participation.
In addition, documentation rarely happens in one continuous system. Many organisations work with specialist software, paper notes, handover books, Excel lists, Word templates, emails and forms from funding bodies. In its Eingliederungshilfe 2026 study, Curacon describes that digitalisation has arrived, but major barriers remain: missing training, digital skills, financing for technical equipment, interface problems, as well as data protection and IT security. (Curacon)
Duplicate documentation is therefore rarely just an individual organisational problem within one team. It arises where requirements, systems and everyday work do not fit together.
Media breaks are the real time sink
A media break happens when information has to be transferred from one medium into another: from a note into software, from software into an Excel table, from the table into a report, from the report into another template.
That may sound trivial. In everyday work, it is a major part of the burden.
The Brüsseler Kreis study, reported by Reha-Recht, shows that three quarters of the surveyed facility leaders said administrative effort had increased or strongly increased since the BTHG reform. Staff in direct support spend an average of one and a half hours per working day on administrative tasks; for facility leaders, the average is 3.2 hours. Documentation and proof requirements were named especially often, including progress, daily and care documentation as well as participation and development reports. (DVFR Reha-Recht)
This is not a side issue. One and a half hours per working day is time that is missing from direct support. Not because professionals want to work less professionally. But because they are forced to translate professional work into different forms of proof after the fact.
When disability support and care meet
Duplicate documentation becomes especially visible where disability support and care come together.
Many people with disabilities and care needs receive services from several systems: disability support under SGB IX, long-term care insurance under SGB XI and, in some cases, social assistance for care under SGB XII. A statement by the Deutscher Verein für öffentliche und private Fürsorge points out that assigning which service belongs to which system was already difficult in the past; the BTHG has not fully resolved these boundary issues. (Deutscher Verein für öffentliche und private Fürsorge)
In everyday practice, this means that one activity can be pedagogically relevant, care-related and relevant for billing at the same time.
Cooking together can involve independence, safety, daily structure, motor support and social participation. For disability support, the key question may be whether the person gains more agency and participation. For care, the relevant point may be what concrete support was needed for an activity. For the organisation, it may also matter which professional support service was provided and how it was documented.
The activity is the same. The documentation requirements are different.
Shared activities can be relevant for support, care and documentation at the same time.
Less documentation is not automatically better documentation
Even with all justified criticism of bureaucracy, one distinction matters: the answer cannot be to reduce documentation across the board.
In disability support, documentation is a professional instrument. It protects people receiving services, makes support reviewable and helps teams follow development over time. In the context of the BTHG, Germany’s Federal Ministry of Labour and Social Affairs (BMAS) also describes stronger performance and quality controls: contract law created better options for economic-efficiency and quality reviews; in the case of significant deficiencies, payments can be reclaimed or service agreements terminated. (BMAS)
It would also be professionally wrong to reduce everything to a minimum. Special incidents, restrictive measures, medication records or regulatory requirements must be documented carefully. The associations representing people with disabilities therefore do not propose simply deleting documentation. They propose bringing documentation together and structuring it digitally so that repeated documentation of the same facts can be avoided. (Caritas)
The decisive point is therefore:
Not looking less closely.
But copying less often.
Conclusion: the problem is not documentation, but duplicate work
Duplicate documentation does not arise because support professionals lack structure. It arises where everyday life, goal work, proof of services, care, quality review and billing are organised according to different logics.
The solution therefore cannot be to reduce documentation across the board. Good documentation remains necessary. The real lever is to stop capturing the same information again and again, and instead record it where it happens so it can later be reused in a professionally meaningful way.
That is the topic of the second part: how everyday entries, goal links and better information flows can help reduce duplicate documentation.
Read next: How everyday entries can reduce duplicate documentation
