{"id":32225,"date":"2008-03-26T16:35:41","date_gmt":"2008-03-26T21:35:41","guid":{"rendered":"https:\/\/content.findlaw-admin.com\/ability-legal\/uncategorized\/the-year-2000-computer-challenge-to-the-insurance-industry.html"},"modified":"2008-03-26T16:35:41","modified_gmt":"2008-03-26T21:35:41","slug":"the-year-2000-computer-challenge-to-the-insurance-industry","status":"publish","type":"corporate","link":"https:\/\/corporate.findlaw.com\/corporate-governance\/the-year-2000-computer-challenge-to-the-insurance-industry.html","title":{"rendered":"The Year 2000 Computer Challenge to the Insurance Industry"},"content":{"rendered":"<section class=\"fl-gutenberg-byline\">\n    <div class=\"fl-gutenberg-byline-content\">\n                    <p><em>This article was edited and reviewed by <a href=\"https:\/\/www.findlaw.com\/company\/our-team.html\" rel=\"noopener\">FindLaw Attorney Writers<\/a><\/em><\/p>\n\n                | Last reviewed\n        <time>\n                            May 27, 2026\n                    <\/time>\n    <\/div>\n\n    \n    <details class=\"fl-gutenberg-byline-toggle fl-gutenberg-byline-legally-reviewed\">\n        <summary>\n            <i class=\"fl-gutenberg-byline-icon\" aria-hidden=\"true\"><\/i>\n            Legally Reviewed\n        <\/summary>\n\n        <div class=\"fl-gutenberg-byline-toggle-content\">\n            <p><em>This article has been written and reviewed for legal accuracy, clarity, and style by <a href=\"https:\/\/www.findlaw.com\/company\/our-team.html\" rel=\"noopener\">FindLaw\u2019s team of legal writers and attorneys<\/a> and in accordance with <a href=\"https:\/\/www.findlaw.com\/company\/company-history\/editorial-policy.html\" rel=\"noopener\">our editorial standards<\/a>.<\/em><\/p>\n\n        <\/div>\n    <\/details>\n\n    <details class=\"fl-gutenberg-byline-toggle fl-gutenberg-byline-fast-checked\">\n        <summary>\n            <i class=\"fl-gutenberg-byline-icon\" aria-hidden=\"true\"><\/i>\n            Fact-Checked\n        <\/summary>\n\n        <div class=\"fl-gutenberg-byline-toggle-content\">\n            <p><em>The last updated date refers to the last time this article was reviewed by FindLaw or one of our <a href=\"https:\/\/www.findlaw.com\/company\/our-team\/contributing-authors.html\" rel=\"noopener\">contributing authors<\/a>. We make every effort to keep our articles updated. For information regarding a specific legal issue affecting you, please <a href=\"https:\/\/lawyers.findlaw.com\/?fli=bylinelink\" rel=\"noopener\">contact an attorney in your area<\/a>.<\/em><\/p>\n\n        <\/div>\n    <\/details>\n<\/section>\n\n\n\n<div class=\"rxbodyfield\" xmlns:o=\"urn:www.microsoft.com\/office\" xmlns:st1=\"urn:www.microsoft.com\/smarttags\" xmlns:w=\"urn:www.microsoft.com\/word\" xmlns:x=\"urn:www.microsoft.com\/excel\">Most computer systems in use today can only record dates in a two-digit format, i.e., 98 for 1998. This format is very common in older systems and software that were designed when computer memory was expensive, but it also exists in contemporary systems and software applications. The two-digit date field threatens to cause computers to fail to operate properly when years after 1999 are used, because the year 2000 is indistinguishable from the year 1900.<p>While the problem is easy to rectify for a single line of programming code, if one multiplies the problem millions of times over for each time a date field appears, it is not hard to imagine why the tab for fixing this Year 2000 (&quot;Y2K&quot;) computer problem is placed as high as $75 billion in the United States and $600 billion worldwide. Moreover, this amount does not take into account associated litigation costs and damage awards. Such litigation costs are estimated at from $2 billion to $1 trillion while the costs of damages and punitive awards are being placed in the $100 billion range.<\/p><p>Given the huge amounts at stake, it is inevitable that businesses are searching for different ways to offset any anticipated expenditures related to the problem. Already, law firms that traditionally represent policyholders are pointing to insurers as likely &quot;deep pockets&quot; to foot the bill. Having previously recovered billions of dollars for asbestos and environmental problems, corporate policyholders and their counsel need little encouragement to see insurance as an untapped resource for funding an expensive Y2K fix. This all but guarantees that insurers again will face the prospect of massive, high-stakes litigation over the question of whom pays to correct an expensive, societal problem.<\/p><p>If anything, the Y2K problem may represent a more serious challenge to the insurance industry than the asbestos and environmental liability problems. While payments for asbestos and environmental claims fell almost entirely on liability insurers, carriers that underwrite property, directors and officers (&quot;D&#038;O&quot;) and errors and omissions (&quot;E&#038;O&quot;) policies are also expected to become targets of Y2K litigation. Thus, carriers writing such policies find themselves threatened with the same type of financial shocks from high-stakes litigation that liability carriers have become all too accustomed to facing in the recent past. Reinsurers ultimately are subject to similar problems; however, because their liability derives from that of their cedents, most appear to be taking a &quot;wait and see&quot; approach to this issue.<\/p><p>Anyone dependent on computers to produce a product or provide a service might seek coverage from their liability carriers when third parties make claims based on Y2K problems. Most such claims will seek a defense and indemnity for lawsuits based on Y2K problems such as the inability of a point of sale system to process post 1999 debit or credit cards. However, we cannot rule out the possibility of claims arising out of torts, i.e., when an airplane crashes or an elevator fails due to a Y2K problem.<\/p><p>Key issues associated with liability coverage will include: (1) whether the Y2K related damage is not covered because it was an expected or intended result of the failure to correct the Y2K problem earlier; (2) whether there is no coverage for Y2K related damage because the Y2K flaw constitutes a &quot;loss-in-progress;&quot; (3) whether delay in informing the insurer about a Y2K problem constitutes &quot;late notice&quot; of an occurrence; (4) whether the Y2K problem can be said to have caused nonrecoverable economic loss or recoverable damage to tangible property; and (5) whether the Y2K problem triggered a policy that was in force when the defective system or program was installed or when the Y2K problem manifested itself.<\/p><p>Claims-made coverage raises additional issues related to whether the claim was made and reported during the policy period. Thus, at least one policyholder&#39;s firm has advised its clients to provide notice under an existing claims-made policy of potential Y2K problems if a Y2K exclusion is being added to a policy on renewal.<\/p><p>In contrast to liability insurers, property carriers will be asked to reimburse the insured for in-house Y2K problems arising out of the insured&#39;s own systems. While property insurers will probably prevail against Y2K claims made under policies that only cover a named peril, they remain subject to the prospect of substantial liability under all risk policies. With respect to such policies, a key issue will be whether there is an exclusion that may apply, such as those for &quot;input, programming or processing errors.&quot;<\/p><p>Assuming there is coverage, property carriers may face additional claims for the cost of business interruption. Business interruption coverage typically compensates the insured for lost profits or earnings incurred due to a covered peril. Such coverage adds a costly dimension to the Y2K challenge confronting property carriers.<\/p><p>If a corporation&#39;s directors are sued because they allegedly failed to address the Y2K challenge, D&#038;O policies might be triggered unless it can be shown that the insured misrepresented the extent of his knowledge about potential liability for the Y2K problem. E&#038;O policies may also cover claims made against Y2K problem consultants if a Y2K fix goes awry. Because most contemporary E&#038;O policies are written on a claims-made basis, issues related to when the underlying claim was made and reported will be of critical importance in determining whether carriers assume liability under such policies.<\/p><p>What can insurance companies do now to help manage this potential Y2K liability? First, insurance companies should amend their underwriting guidelines to include specific inquiries concerning Y2K risks and, in appropriate cases, consider including Y2K exclusions at renewal. Second, insurers should ensure that claims handlers understand the Y2K problem as well as any applicable defenses. Third, insurers should review their book of business to attempt to assess their potential Y2K liability. This should include actively monitoring the growing number of Y2K lawsuits that have been filed against parties that use computers in products or services. Fourth, insurers should consider issuing bulletins to their insureds about the Y2K problem. Placing their insureds on notice about the problem now may help support a future occurrence, loss-in-progress or late notice defense. Finally, carriers should consider following the lead of companies that have already offered Y2K insurance. Providing such insurance eases the ability of a company to add Y2K exclusions to its policies.<\/p><p>In sum, the Y2K problem poses the greatest challenge to the insurance industry since the asbestos and environmental claims crises of the 1970&#39;s and 1980&#39;s. Given this challenge, the insurance industry cannot afford to merely await the Millennium. Rather, it must take a proactive approach to the prospect of Y2K inspired lawsuits.<\/p><\/div>","protected":false},"excerpt":{"rendered":"<p>Most computer systems in use today can only record dates in a two-digit format, i.e., 98 for 1998. This format is very common in older systems and software that were designed when computer memory was expensive, but it also exists in contemporary &#8230;<\/p>\n","protected":false},"template":"","meta":{"_acf_changed":false,"_stopmodifiedupdate":true,"_modified_date":"","_cloudinary_featured_overwrite":false},"corporate_categories":[6474,6476],"class_list":["post-32225","corporate","type-corporate","status-publish","hentry","corporate_categories-corporate-governance","corporate_categories-corporate-governance__insurance"],"acf":[],"_links":{"self":[{"href":"https:\/\/corporate.findlaw.com\/legal-api\/wp-json\/wp\/v2\/corporate\/32225","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/corporate.findlaw.com\/legal-api\/wp-json\/wp\/v2\/corporate"}],"about":[{"href":"https:\/\/corporate.findlaw.com\/legal-api\/wp-json\/wp\/v2\/types\/corporate"}],"wp:attachment":[{"href":"https:\/\/corporate.findlaw.com\/legal-api\/wp-json\/wp\/v2\/media?parent=32225"}],"wp:term":[{"taxonomy":"corporate_categories","embeddable":true,"href":"https:\/\/corporate.findlaw.com\/legal-api\/wp-json\/wp\/v2\/corporate_categories?post=32225"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}