What is DS1140?

Load-bearing structures can't be allowed to fail. When something goes wrong here, the consequence is rarely cosmetic - it's a risk to people and to the building's lifespan. DS1140 exists to make sure control of exactly these structures is systematic and documented, not left to one tradesperson's memory or experience alone.

The standard sets out what control must be carried out, how thorough it needs to be, and how the result is documented, so a certified structural engineer can approve the building on a clear, traceable basis - not a gut feeling.

DS1140 documentation falls into three parts, each building directly on the last. The control plan (its formal name is B2) sets out what needs to be checked - every control point, with its control type, control level and control scope. The control report (B3) then documents that the control was actually carried out, with date, who did it, and the result for each point. The as-built documentation (A5) finally pulls it all together, including any deviations from the plan, when the building is handed over.

The control itself happens in two layers. Self-inspection is the ongoing control the contractor carries out as work progresses. From a certain structural class upward, it's supplemented by independent control, carried out by a person who did not carry out the work being checked, which verifies that the self-inspection can stand on its own.

The requirement depends on the building's structural class (KK1-KK4), set early in the project based on the consequence of a potential failure and the complexity of the structure. The higher the class, the more extensive the control required - and from a certain class upward, independent control becomes mandatory, not optional.

Most building owners and contractors first encounter the full scope of this when the certified structural engineer asks for documentation they don't have on file. That typically happens late in the process - often close to handover - where catching up is both more expensive and more disruptive than it would have been from the start.

If the control plan is missing, or too loosely described, the structural engineer will typically send it back before control work can even begin. If the B3 report isn't kept up to date, gaps appear that only surface when the engineer reviews the case close to handover - by which point the building is already well advanced. And if A5 is missing entirely, the building can't be handed over, no matter how well the actual work was done.

In practice, a weak DS1140 process rarely shows up as one big problem. It shows up as a series of smaller delays stacking on top of each other, until the building is finished on site but stuck waiting on paperwork.

The single most important first step is clarifying the building's structural class, because it governs how extensive the rest of the documentation needs to be. From there, the control plan (B2) is the starting gun for the whole process - it sets the frame that self-inspection, the B3 report and any independent control all work from.

If you already have a building under construction without a coherent DS1140 plan, it's still possible to catch up as you go, without necessarily stopping work on site while the documentation comes together.

When a disagreement arises between owner and contractor over whether work was done correctly, DS1140 documentation is often what settles it quickly. A well-documented control plan with ongoing B3 reporting shows exactly what was checked, when, and by whom - which makes it hard to disagree about the actual facts.

Where documentation is missing or incomplete, the case typically ends up needing several rounds of reports and explanations before the parties can agree on what actually happened. That's one of the strongest practical reasons to prioritise documentation from the start - not just for the engineer's approval, but to have a record if a dispute arises later.

A growing number of contractors now keep the control plan, the control report and the as-built file inside a single digital system rather than a folder of separate spreadsheets. The advantage isn't just tidiness - it's that a missing control point becomes visible immediately, rather than only surfacing when the structural engineer reviews the case close to handover.

That said, DS1140 itself doesn't require any particular tool or format. A well-kept paper trail in Word and Excel satisfies the standard just as well as a purpose-built app, provided the content is complete and consistent throughout.

In a straightforward project, the structural class is agreed early with the engineer, the control plan follows shortly after, and self-inspection then runs alongside construction as each phase is completed. The control report is updated as work progresses rather than reconstructed afterwards, and the as-built documentation is assembled in the final weeks from material that's already largely in place.

Projects that struggle with DS1140 rarely fail because the requirement itself is unclear. They struggle because the documentation is treated as a task for the end of the project, when in fact it needs to run in parallel with the physical work from day one.

There's no fixed page count or template that defines 'enough' documentation under DS1140 - what matters is that every control point named in the plan can be traced through to a dated, attributed result in the control report. A short, complete record beats a long one with gaps.

When in doubt about whether a particular detail needs its own control point, it makes sense to ask the structural engineer directly early on, rather than guessing and finding out the answer was wrong once the building is already up.

DS1140 documentation doesn't lose its relevance once the building is handed over - it remains the primary record of what was actually built and checked for as long as the building stands. It pays to have a fixed practice for where and how the documentation is stored, so it can be retrieved again in ten or twenty years if the need arises.

If your organisation has more than one DS1140 case running in parallel, it helps to keep a shared overview of where each one stands - which phase it's in, which control points are still open, and when the next engineer review is due. Without that overview, it's easy for a single case to quietly slip behind simply because attention naturally goes to whichever project feels most urgent that week.

For companies that also build outside Denmark, it helps to know that DS1140 is a Danish standard, without a direct one-to-one equivalent in other countries' control requirements - even though the underlying principle of documented control of load-bearing structures appears in many forms across Europe. If the same organisation needs to document to several countries' requirements at once, it's rarely possible to reuse one control plan directly - the structure can be reused, but the content has to be adapted to each country's specific requirements.

This matters most for contractors who work across borders on a regular basis, where a shared internal template gives a useful starting point even if the detail always needs local adaptation.