Insuralex

  • The Group
    • About us
    • Current Management
    • Past Presidents
    • Membership inquiries
    • Regulatory Information
  • Experience and Vision
  • Services
  • Members
  • News + Articles
  • Reports
  • Events
  • Contact Us
  • FAQ´s
Join

Construction Damages: Separate or Joint Liability

by Insuralex / Wednesday, 02 September 2015 / Published in News + Articles

Download in PDF

 

May 27, 2015

Construction Damages: Separate or Joint Liability

 

From the Insurance Law Department at the practice in Madrid and as lawyers with expertise in construction damages, we will analyse the liability of the different stakeholders intervening in the building process when defects exist in construction.

Law 39/1999 of 5 November on Building Regulations regulates on section two of article 17 regarding public liability of construction stakeholders.

“Article 17. Public liability of construction stakeholders.

2. Public liability shall be due personal and separate, both due to own acts or omissions, and due to acts or omissions by persons for whom, in accordance to this law, it is necessary to respond.

3. Nevertheless, when the cause of material damages cannot be separated or contributory fault is duly proved without specifying the degree of engagement of each stakeholder in such damages, the liability shall be considered joint. In all cases, the developer shall jointly respond with the rest of stakeholders before the possible recipients of material damages in the building arising from vices or defects of construction.”

There has not been a consistent case-law regarding the separate or joint liability of the stakeholders intervening on the construction process.

In the first place, case-law interpreted that construction stakeholders, i.e. the different intervening parties in construction of buildings (developer, builder, architect, contractor, etc…), are joint-liable parties and, therefore, if a claim were addressed to them due to construction defects, limitation were interrupted and it might be claimed later, impacting also the rest of stakeholders.

Afterwards, the High Court decided that Building Regulations, particularly on article 17, sets the joint liability when faults cannot be separated or it is proved that there is contributory fault in defects among the building stakeholders.

Thus, High Court Ruling of 14 March 2003 creates third-party liability that arises from the nature of the wrong or offence and from plurality of subjects intervening at the production and that arise when it is not possible to separate liabilities without applying joint liability rules to this kind of liability.

In short, case-law, instead of regulation, leads to joint sanction, which has its origin not in the nature of the liability perfectly separated but in the indeterminacy of the cause that makes impossible to attribute each stakeholder their part of responsibility.

This joint responsibility, with which many rulings have dealt, has been also clarified by the High Court Ruling of 16 January 2015, among others, where it is said that it is a third-party liability, i.e. joint liability does not emerge from Law or agreement but from court ruling.

Thus we may conclude that building stakeholders’ liability for vices and defects is generally separate depending on their part of fault on the construction of the building. Only when the latter cannot be determined, the joint sanction is applicable.

Therefore, General Liability insurances must consider this circumstance offering to cover each element of the construction chain for a possible joint liability or for an individualisation of fault that compels every stakeholder to respond if fault is determined in a legal process.

 
Belén Domínguez Jarque
José Garzón García
Insurance Law Department | Madrid (Spain)
Belzuz Abogados SLP
 
This article contains general information, which does constitute neither a professional opinion nor legal advice. © Belzuz Abogados, S.L.P. All rights reserved. It is prohibited to exploit, reproduce, distribute, communicate publicly and transform totally or partially this article, without due written authorisation of Belzuz Abogados, S.L.P.

 

 

 

OUR SPONSORS

  • The Group
  • Experience and Vision
  • Services
  • Members
  • News + Articles
  • Reports
  • Events
  • Contact Us
  • FAQ´s

Insuralex is not a law firm, does not practice law and does not provide legal advice or legal opinions. Insuralex members are not a partnership of law firms or lawyers and are not affiliated or in a relationship for the joint practice of law. Insuralex member firms are strictly independent firms.

Insuralex 2025    Cookie Policy | Conditions of use | Privacy Policy | FAQ's | Contact

TOP
Manage Consent
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behaviour or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Manage options Manage services Manage {vendor_count} vendors Read more about these purposes
View preferences
{title} {title} {title}