An accusation of reckless disaster, often linked to the collapse of a building, does not only concern those who were present when the event occurred. It can involve designers, site managers, executors, clients, directors, technical managers, or those with maintenance and control duties. The most immediate doubt is understandable: is a technical error, an omission, or an organizational decision really enough to incur criminal liability?
I want to help you distinguish the points that matter: when a structural failure assumes the relevance of a disaster, how the causal link between conduct and the event is proven, which roles entail a duty of protection, and which elements can support a concrete defense. The title indicated in a contract is important, but it does not replace the analysis of actual powers, available information, and the technical causes of the collapse.
When a structural collapse can constitute a reckless disaster
A collapse does not automatically equate to a reckless disaster. Article 449 of the Italian Criminal Code punishes anyone who causes through negligence a fire or another disaster provided for in the chapter dedicated to crimes against public safety. In the case of buildings, the reference is Article 434 of the Italian Criminal Code: the prosecution must therefore prove not only a material failure, but an event with characteristics capable of endangering the community. An official reference on Article 449 of the Italian Criminal Code recalls the penalty provided for reckless disasters and the structure of the offense.
The gravity of the event has a precise meaning. The Court of Cassation distinguishes reckless collapse from the misdemeanor of ruin of buildings by looking at the scale of the danger: for a disaster, the gravity and complexity of the incident are required, with a concrete exposure of the safety of an indeterminate number of persons. It is not necessary for the entire building to disintegrate, but a circumscribed damage devoid of that diffusiveness of danger is not enough either. The criterion is illustrated in the criminal review of the Court of Cassation of December 2025.
What matters is the danger created by the failure, not merely the economic value of the damage. A partial collapse can assume high criminal significance if it involves load-bearing structures, accessible areas, neighboring homes, or spaces where the effects propagate beyond the original point. Conversely, major damage for the owner may require a different classification if it remains confined and does not expose public safety in the terms required for a disaster.
Negligence must be identified with precision. In criminal law, negligence means the violation of rules of caution, diligence, skill, or technical and regulatory prescriptions, when the event was foreseeable and avoidable through demandable conduct. It is not sufficient to state, after the collapse, that someone should have done "more": it is necessary to indicate what precaution was due at that stage, for what reason the risk was knowable, and what intervention could have prevented its materialization.
The causal link: the central issue of the defense
A technical violation alone does not prove liability for the collapse. The prosecution must connect the contested conduct to the event: it must explain, with verifiable technical elements, why that design error, missed control, omitted maintenance, or executive choice caused the disaster. If multiple factors coexist, such as original defects, subsequent modifications, material degradation, weather events, or third-party conduct, each factor must be placed in the causal sequence.
Omissions require an additional step. When the allegation consists of not having done something, the question is not only whether the intervention was appropriate. It must be established whether the person had a legal obligation to intervene and whether the omitted action, performed in a timely manner and correctly, would have avoided the collapse or the danger that occurred. This is where the guarantee position and technical reconstruction meet.
The reconstruction must respect chronology. An anomaly detected after the failure may be a cause, a consequence, or merely a concurrent element. Therefore, the date of the works, previous reports, inspections, issued prescriptions, project modifications, and potential knowledge of instability symptoms assume relevance. The defense is not based on an abstract challenge of the expert report: it verifies whether the data used truly allows moving from the technical hypothesis to the proof of causality.
Foreseeability is not judged with hindsight. The Court of Cassation has recalled that sudden events, devoid of early warning signs, may require precautions that can only be adopted well in advance; the judgment on negligence must then focus on the measures that were concretely demandable before the event. The principle is recalled in Cassation judgment no. 9906, deposited on March 11, 2025. This distinction is decisive when the failure is described as sudden, but investigations hypothesize overlooked signs over time.
Guarantee position: role, powers, and real limits
Those who had the duty and power to prevent the risk are liable for omission. The guarantee position does not automatically derive from being a manager, owner, technician, or company employee. It can arise from the law, an assignment, the custody of an asset, or the effective governance of the source of danger. The point is to understand whether that subject could know the risk, decide on useful interventions, and have them executed.
In construction sites and companies, roles must be distinct, not overlapped by label. The employer and managers have prevention obligations connected to the duties and competencies conferred upon them; Article 18 of Legislative Decree no. 81/2008 recalls, among other things, the adoption and updating of safety measures. The current text of Article 18 helps identify the perimeter of these obligations, but does not allow attributing responsibility without further checks for any event that occurred within the organization.
The technical assignment entails duties connected to the functions exercised. The Court of Cassation stated, in a reckless disaster case, that the site manager can be held liable even if not physically present on site, when they omit the supervisory activity required by their assignment or fail to adopt the necessary technical precautions. The principle does not turn every absence into negligence: it is necessary to ascertain tasks, intervention powers, the necessary frequency of controls, and the incidence of the contested conduct. The case is summarized in the criminal review of the Court of Cassation of April 2024.
How I structure the defense in a reckless disaster charge
An effective defense starts from the exact charge. It is necessary to separate the allegation concerning the disaster from that concerning the personal role: the prosecution may attribute imprudent action, omitted control, a calculation error, a choice of materials, a failure to suspend works, or a lack of maintenance. Each hypothesis requires different facts and technical rules. A generic allegation makes it more difficult to identify the real evidentiary issue.
The technical consultancy must answer legally useful questions. It is not enough to propose an alternative explanation for the collapse. It is necessary to verify whether it is compatible with the findings, the chronology of the works, and the conditions of the structure. Design documents, authorizations, calculation reports, inspection minutes, dated photographs, maintenance logs, alarm communications, and service orders may be relevant. A document is useful if it helps establish who knew what, when they knew it, and what intervention they could realistically perform.
Concurrent causes do not automatically eliminate liability. An error by an executing company, an unauthorized modification, or a pre-existing defect may concur with the suspect's conduct. However, they can also interrupt or render insufficient the causal link attributed to a person if they result autonomous, unpredictable, or decisive in a way incompatible with the formulated charge. The difference depends on technical evidence and the concrete content of the assigned tasks.
Post-event conduct does not replace the verification of the fact. Securing the area, cooperating to reduce further dangers, and correctly preserving documentation may be necessary, but it does not prove or exclude by itself liability for the collapse that has already occurred. It is essential to avoid unverifiable post-facto reconstructions, document alterations, or interventions that make it impossible to understand the state of the places without adequate traceability.
Company and compliance model 231: what really changes
The organizational model does not replace the defense of the individual. A model adopted pursuant to Legislative Decree no. 231/2001 can describe procedures, controls, information flows, and internal responsibilities. It can therefore assume relevance as a documentary element to understand the concrete organization and the measures provided. However, it does not prove by itself that those measures were implemented, that they were adequate to the risk, or that the individual defendant did not have a personal obligation.
Reckless disaster does not entail entity liability ex Legislative Decree no. 231/2001 in itself. Entity liability requires a specific predicate offense provided by the law. In matters of workplace safety, Article 25-septies concerns negligent manslaughter and severe or extremely severe negligent personal injuries committed with violation of health and safety protection rules, as resulting from the text of Article 300 of Legislative Decree no. 81/2008. The charge under Article 449 of the Italian Criminal Code therefore requires autonomous verification, without automatically inferring a 231 allegation.
If entity liability is also contested, the model must be read in its concrete elements. Article 6 of Legislative Decree no. 231/2001 links the exclusion of entity liability, for crimes committed by senior management, to the adoption and effective preventive implementation of suitable models, in addition to the other requirements indicated by the rule. The current text of Article 6 clarifies that the mere formal possession of a document is not decisive: protocols, supervision, updating, and concrete application are what matter.
Frequently asked questions
Is a partial collapse always a reckless disaster?
No, not always. The decisive point is the concrete scale of the danger to public safety. Even the failure of part of a building can constitute the crime if it is serious, sudden, and capable of exposing an indeterminate number of people. If the damage remains circumscribed and lacks such characteristics, the legal classification may be different.
Does the site manager remain liable even if not present?
They can be liable, but absence is not enough to affirm it. It is necessary to establish what supervisory tasks derived from the assignment, whether the risk was knowable, and whether a demandable intervention would have avoided the event. Physical presence is not the sole criterion: functions, powers, received information, and the causal incidence of omitted control matter.
Does the violation of a safety rule automatically prove the causal link?
No. The violation can be an important element for assessing negligence, but it must be connected to the collapse through reliable technical reconstruction. It must be proven that the violated rule aimed to prevent precisely that risk and that compliance with it would have prevented or avoided the event under the concrete conditions of the case.
Does the 231 model protect the company from any challenge?
No, the model is not an automatic shield. For entity liability, it is first necessary that a specific predicate offense is configurable. Furthermore, when Article 6 of Legislative Decree no. 231/2001 is applicable, exhibiting the model is not enough: its suitability, effective implementation, and the functioning of controls assume relevance.
What documents can be useful for defense?
Documents that clarify causes, roles, and times are useful. Projects, technical reports, minutes, service orders, reports, maintenance records, photographs, and communications between the subjects involved can count. There is no standard file: the value of each act depends on whether it allows verifying the knowability of the risk and the actual power of intervention.
When it is useful to address technical points immediately
In these matters, the initial reconstruction can guide the entire proceeding. If you are under investigation, accused, or involved as a technician, manager, or company, it is useful to promptly identify the exact content of the charge, preserve relevant documentation, and distinguish your role from that of other subjects. To examine these aspects with reference to your case, you can contact me.