Exact Software North America, Inc. v. Infocon, Inc.

ORDER

This case began as a collection action by the plaintiff, Exact Software North America, Inc. [ESNA], against the defendant, Infocon, Inc. ESNA claimed that Infocon owed monies to ESNA that Infocon had received from its customers.

ESNA is a successor through merger to Macóla, Inc., a Marion, Ohio, producer of software.

Infocon, which had been a “reseller” [i.e., distributor] of software produced by Macóla, counterclaimed, alleging: 1) breach of contract; 2) fraud; and 3) intentional interference with contract.

Pending is Infocon’s Motion for Entry of Default Judgement Pursuant to Fed. R.Civ.P. 37(b) [Doc. 141] as to ESNA’s complaint and Infocon’s counterclaims. 1 Infocon bases its motion on ESNA’s persistent and protracted failures to comply with its discovery obligations and this court’s orders relating to those obligations.

For the reasons that follow, I conclude that, due to ESNA’s persistent and egregious noncompliance with a series of discovery orders, sanctions are fully warranted. But, as I cannot presently ascertain where the fault for that noncompliance lies as between ESNA and its now former counsel, 2 and thus on whom sanctions for noncompliance should be placed, ESNA will be granted leave to show cause why *704 the relief sought should not be imposed against it.

Background

During the years of its business relationship with Macóla, Infocon developed a customer base that generated income in two stages. First, Infocon would provide software to its customers; then it would enter into “maintenance” agreements with the customers. Under those agreements, the customers would prepay for periodic upgrades to the software and any maintenance and service that might be required during the term of the agreements.

Infocon, in turn, was contractually obligated to pay Macóla a portion of the fees it was receiving from its customers.

Continued availability from Macóla of software upgrades was crucial to Infocon’s ability to maintain its customer base and income.

ESNA is affiliated with a Dutch company, Exact Holding NY [Exact], which acquired Macóla [and transformed it into ESNA] through a “reverse merger.” According to Infocon’s countercomplaint, it received assurances that ESNA would continue to provide it with software upgrades, thereby enabling Infocon to continue to service its customers and generate income.

The complaint alleges that ESNA did not fulfill its obligations to provide products for Infocon to supply to its customers. For a period of time, Infocon continued, however, to receive advance maintenance fees from its customers.

Not having the upgrades it claims it had been promised, and thus not being able to perform on its obligations under the maintenance agreements with its customers, In-focon stopped collecting maintenance fees and otherwise ended its relations with its customers, at least insofar as those relations involved Macola/ESNA software. In addition to alleging fraud in ESNA’s original assurances that it would provide upgrades and breach of contract against ESNA, Infocon alleges that ESNA tor-tiously interfered with its contractual relations with its customers, and, as well, that ESNA ultimately took over Infocon’s former customers.

ESNA brought its collection action for unremitted maintenance fees in the Marion County, Ohio, Court of Common Pleas. Infocon removed the suit to this court. At a scheduling conference on July 28, 2003, the parties were given nine months to conduct discovery. Trial, which was to follow summary judgment motion practice, was set for October 5, 2004. 3

The scheduling order included the following boilerplate directive:

No motion to compel may be filed unless the parties, as required by Local Rule 37. 1, have undertaken in good faith to resolve discovery disputes, and, if unable to do so, have contacted the court with a request for judicial resolution.

[Doc. 21],

This mandate, which expands upon and implements the purpose of Fed.R.Civ.P. 37(a)(1)(A), 4 is designed to reduce, if not nearly eliminate the delays commonly resulting from discovery disputes.

*705 I have followed the practice of requiring the parties to contact me forthwith with discovery problems for about twenty-five years. In all but the most rare of instances, this method of informally resolving discovery disputes has successfully reduced delay, expense, inconvenience, and uncertainty for the parties. This method also has significantly reduced the judicial time and effort that otherwise would have been expended adjudicating formal motions to compel.

This approach did not work in this case, despite extensive effort on my part to see to it that it would. 5 For the reasons that follow, I find that the fault for its failure sits squarely in the lap of ESNA and/or its counsel. Before, however, granting Info-con’s motion for default, ESNA shall be granted the opportunity to show cause why it should not be held accountable for the nearly utter failure to comply with the series of discovery orders issued in this case. 6

Discussion

A. Infocon’s Allegations

Before turning to the discovery that In-focon sought, I ordered, and ESNA failed to provide, despite my orders, a summary of the allegations of the complaint will set the context in which the discovery dispute arose, conferences were conducted, and orders were issued.

The gravamen of Infocon’s counterclaims is that ESNA promised to provide contractually mandated upgrades to Macó-la software. 7 Infocon alleges, moreover, that ESNA’s misconduct went beyond simple nonperformance of its contractual obligations, and that ESNA’s assurances about the status of its work on upgrades constituted fraud. These and other actions had the effect, according to Infocon, *706 of destroying Infocon’s relationships with its customers.

The breach of contract claim is based on allegations of a deliberate breach of contractual commitments between Maco-la/ESNA and Infocon, whereby ESNA refused to provide software upgrades that were at the heart of Infocon’s business with its customers. [Doc. 37-1 ¶¶ 116— 123],

With regard to the assertions of fraud in the amended counter-complaint, Infocon alleges that, before its merger into ESNA, Macóla had notified its resellers, including Infocon, that an upgrade [“Version 8.0”] was being developed and would be made available. [Doc. 37-1 ¶ 73]. Infocon further alleges that ESNA specifically repeated that representation. [Id. ¶ 75], Despite these representations and assurances, ESNA, according to the amended counterclaim, secretly decided to terminate Version 8.0. [Id. ¶¶ 80, 81].

Infocon also contends that, when it asked ESNA’s parent, Exact, about rumors concerning a decision not to issue Version 8.0, Exact’s Chief Executive Officer responded with assurances that a version better than 8.0 would shortly be forthcoming. [Id. ¶ 84], When the announced deadline for delivery of this new software was not met, Exact, according to the amended counter-complaint, notified Info-eon that the upgraded version was already in place at Macola/ESNA. [Id. ¶ 96].

These assurances were false, Infocon claims, because ESNA had not renewed a licensing agreement with a third-party supplier of an integral component [namely, the “Micro-Focus compiler”] of the software. [Id ¶¶ 89, 90]. The fact of such nonrenewal, and, indeed, the fact that Ma-cóla and ESNA did not have sole proprietary interest in the entire software, had, Infocon claims, never been disclosed to Infocon. [Id. ¶ 93].

Because it was unaware of the true circumstances, Infocon continued to bill its customers for the anticipated upgrade, and, for a time remitted that portion of its receipts that it was required to remit to ESNA under its agreement with Macóla. [Id. ¶ 98],

Infocon’s allegations of fraud, accordingly, encompass both deliberate false misrepresentations and failure to disclose material facts.

As a consequence of the non-renewal of the Micro-Focus compiler license, according to the amended counter-complaint, In-focon can no longer serve its customers’ needs for service to their existing Macóla software. [Id. ¶ 105].

With regard to its claim of tortuous interference with its contractual relations with its customers, Infocon’s amended counter-complaint alleges that it was notified on September 26, 2003, that its “reseller agreement would be terminated.” [Id. ¶ 137]. No grounds existed for such termination, Infocon alleges. [Id. ¶¶ 135, 136],

Infocon also states that ESNA sent a letter to Infocon’s customers informing them that Infocon no longer represented ESNA, [Id. ¶ 139], a new representative would be assigned to them, and their accounts would be transferred by a certain date unless ESNA was notified otherwise. [Id. ¶ 140]. The foregoing actions, Infocon alleges, were in furtherance of an attempt by ESNA to supplant Infocon with its competitors. [Id. ¶ 143].

B. Discovery Sought by Infocon and Disputed by ESNA

1. Corporate Relationship Between Exact and ESNA

Infocon seeks information about the relationship between ESNA and its Dutch parent, Exact. On the one hand, this information may help Infocon [and the jury, *707 were trial to occur] know who was responsible for the alleged breach of contract, fraud, and interference with contractual relations. Exact may have played no role in any of the activities giving rise to this suit; it may have played some role; or it may have played a commanding role. Determination of what that role, if any, Exact might have played necessarily begins with an understanding of the corporate relationship between Exact and ESNA.

An understanding of inter-corporate relationships is also important to ascertaining the location of discoverable information about the transactions underlying the counter-complaint and the identity of potential witnesses.

Finally, and perhaps most important for Infocon, it understandably wants to be certain that, if it prevails, it can proceed to collect from a judgment-worthy defendant.

To facilitate and expedite ascertainment of Infocon’s efforts to find out what the E SNA/Exact relationship is, and ultimately, what role was played by whom in the events giving rise to this lawsuit, I suggested that a stipulation be prepared and filed. This rather simple request, which I can hardly believe could not have been easily accomplished, and which twice was encompassed in court orders [Docs. 104, 119], has only recently been fulfilled — and even then, contrary to those orders, in unverified form. 8

2. ESNA’s Sales

Infocon has also sought to learn what ESNA sold and to whom, when those sales occurred, and how much they earned ESNA during a specified post-merger period.

Infocon seeks this information to determine the extent to which ESNA has transacted business directly with its customers [or now former customers], and the nature of that business.

The requested sales information is directly pertinent to establishing the merits of all of Infocon’s claims: i.e., that ESNA, by selling to others, breached its obligations under its contract with Infocon, dealt duplicitously with Infocon, and interfered with Infocon’s relations with its customers. 9

Information about ESNA’s sales is equally pertinent with regard to a determination of Infocon’s damages, in the event it prevails on any of its claims. 10

The subject of ESNA’s sales data was a repeated issue at several discovery confer- *708 enees. Initially, ESNA claimed that it did not have conventional [i.e., hard copy] price lists. Its pricing data, ESNA contended, was “virtual” and day-to-day data could not be retrieved retroactively. 11

I have previously expressed and continue to be of the view that the contention that ESNA cannot determine what it sold, when it was sold, to whom it was sold, and how much it was sold for to be utterly implausible. 12 It is inconceivable that a sophisticated company with a foreign parent would not retain and be able to retrieve information so basic to any commercial enterprise.

To be sure, there may well be no “price list” in the conventional sense of that term, and whatever data is available may be in digital, rather than paper form. But that does not matter. What matters is that all companies have to keep sales records to be able to conduct their operations, work with their customers, generate sales programs, and, most importantly, accounting activities, especially with their suppliers. The need to retain such information is also essential for tax purposes, and, as well, for accountability to shareholders.

Such data is crucial to Infocon’s case. Without it, it will be severely prejudiced. Failure to provide it can only be viewed as deliberate and contumacious. Even if discovery had otherwise been forthright and promptly forthcoming, withholding this information would, without more, call for stringent sanction.

3. Due Diligence Materials

Infocon seeks due diligence materials that may have been generated during negotiations between Exact and Macóla. Such materials, in Infocon’s view, could disclose the extent to which Exact became aware of Macola’s mode of doing business and its contracts and relations with its customers. Such insight may, Infocon *709 suggests, have fostered or furthered an intent on ESNA’s part to displace Info-con’s place and role as a distributor, and to deal with Infocon’s customers directly.

In the initial discovery conference discussions about this request, counsel for ESNA stated that the negotiations for the merger had occurred in two stages. The first had ended without success; to the extent that any sort of due diligence had occurred, ESNA’s counsel represented, 13 it would have occurred prior to the collapse of the first round of negotiations. Sometime thereafter the merger [via a stock acquisition] occurred on an expedited timetable.

ESNA repeatedly denied that any materials relating to due diligence continued to exist. In the face of those statements, counsel for Infocon contacted Hale & Dorr [now known as “Wilmer Hale”], former counsel for Exact during those negotiations. Wilmer Hale confirmed that due diligence had, indeed, been undertaken.

Once this became known, counsel for ESNA switched tracks, and contended that her client was not in possession of those materials, and thus could not be required to produce them. 14

At the very least, an attorney who was acting in good faith, and seeking to facilitate rather than impede discovery, could, would, and should have either obtained permission from ESNA’s parent, Exact, to have Wilmer Hale produce the documents, or, at the very least, informed counsel for Infocon that due diligence had been conducted by that firm. At that point, Info-Con could have undertaken to procure the due diligence documents from Wilmer Hale via Exact. This court could thereafter have dealt with any objection on the part of Exact in due course.

In my view, ESNA’s response to the request for due diligence materials manifested, at best, bad faith. At worst, it is indicative of an intent to mislead the court — at least to the extent that I and counsel for Infocon were repeatedly told no due diligence report existed. Even if technically true, that response concealed the due diligence work that had, in fact been done, and which should have been disclosed to Infocon. 15

4. Third-Party Contracts

Infocon also sought to obtain ESNA’s contracts with third parties, such as those *710 with whom it has licensing agreements. This information is pertinent to the fraud claim, as Infocon has learned that one reason for ESNA’s failure to produce the upgraded Version 8 is the loss of its license to incorporate an integral component in the software. Such contracts [or lack thereof] might reveal the date as of which ESNA was aware that Version 8 could not be produced, and thus, whether its assurances to Infocon that Version 8 was forthcoming were knowingly false. 16

5. Date[s] of Notice[s] of Termination of Relationship

Infocon has also asked ESNA to specify when and how it communicated its decision to terminate Infocon as a reseller. This information is clearly pertinent to Info-con’s claim of breach of contract. It may, as well, bear on Infocon’s claim of tortuous interference with its contractual relations with its customers.

A clear, definitive response to this request would appear to be a matter of utmost simplicity: namely, specification of one or more communications in which ESNA, in its view, terminated its relationship with Infocon.

ESNA’s responses to this most simple of questions have been inconsistent and not definitive. While suggesting a couple of different dates on different occasions as the date of notice, ESNA has, to my understanding, 17 never specified the precise communication.

This failure is incomprehensible. Although, as ESNA initially contended, Info-Con may have had the communications, that contention did not meet the request, which was for ESNA to specify which communication was intended to convey the particular message. ESNA alone knows what it meant to say and when it said it. But it did not do when this court ordered it to do so, and it has never explained its failure to comply with my orders that it do so far sooner.

6. End-User Sub-licensing Agreements

The other major category of discovery relates to end-user sub-licensing agreements. These are agreements between ESNA and its customers [including, Info-con believes, former customers that it once served]. This information is pertinent to Infocon’s claim of tortuous interference with contractual relations. Indeed, it is crucial to Infocon’s case against ESNA on that portion of its counterclaim. But nothing was forthcoming within the time frames set in my court orders. 18

C. Discovery Conferences and Orders: ESNA’s Failure to Comply

Infocon first became aware of obstructionism on the part of ESNA shortly after *711 ESNA’s motion to dismiss was overruled and discovery resumed. After receiving ESNA’s answer to the counterclaim, counsel for Infocon asked ESNA’s counsel in mid-2004 for the basis for ESNA’s denial in its answer of certain facts that, in the view of Infocon’s counsel, were indisputable. 19

Another indication that problems may have lain ahead arose when, during a deposition of ESNA’s in-house counsel, who had signed ESNA’s responses to Infocon’s initial discovery requests, Infocon learned that she did not have first-hand knowledge of the matters being disclosed. The attorney said that the responses had been prepared by retained counsel.

In October, 2004, new counsel [Ms. Grasso] appeared for ESNA. She assured Infocon’s counsel that revised discovery responses would be forthcoming. They were not.

In April, 2005, Infocon renewed its request for responses to the concerns it had expressed during the preceding year. The response by ESNA did not resolve those concerns, and Infocon submitted its Second Request for Discovery. The time for a response to that request passed without a response by ESNA.

This led to a discovery conference with the court on October 20, 2005. I ordered ESNA to respond to the requested discovery by October 24, 2005. During that conference, I first suggested that questions about the corporate interrelationships be resolved through a stipulation. In addition, I ordered ESNA to submit its tax returns by that date or show cause why it should not be sanctioned. [Doc. 73].

ESNA ignored that order. It filed nothing on the deadline date.

In the face of ESNA’s unresponsiveness to its discovery obligations and this court’s order to produce by October 24, 2005, In-focon’s attorney sent a memorandum of disputed discovery to ESNA’s attorney. She informed Infocon’s counsel that a response to that memorandum would be forthcoming on November 15, 2005.

That self-imposed deadline was not met.

Infocon requested another discovery conference with me. That conference was held on November 28, 2005. This led to my granting leave to Infocon to file a motion to compel [Doc. 78], which became decisional on December 15, 2005.

Thereafter on December 23, 2005, I entered a ten-page order discussing the parties’ positions as to each item of disputed discovery, granting in part and denying in part Infocon’s motion to compel, and explaining my reasons for allowing or denying the requested discovery. [Doc. 96]. 20

Among the items ESNA was to produce were:

*712 • documents relating to the putative notice of termination from ESNA to In-focon

• documents relating to Macola’s super-session of its promise to provide quarterly updates to certain parties

• the due diligence report obtained before the acquisition of Macóla

• documents relating to termination of “bug fixes”

• documents relating to the Brieve/Per-suasive platform used by Macola’s customers and ESNA’s termination of Brieve

Through oversight on my part, I neglected to set a date certain for compliance with the order of December 23, 2005. This led to an inquiry by Infocon’s counsel on January 10, 2006, for information from ESNA about its anticipated compliance with the December 23rd order.

Minimally partial response having been provided by ESNA by January 13, 2006, counsel for Infocon filed a motion for me to set a firm date for compliance. This led to a phone conference on January 26, 2006; ESNA’s attorney stated that she would comply with the order by January 30, 2006. That commitment was memorialized in yet another deadline-setting order. [Doc. 99].

That deadline passed unmet. ESNA’s attorney did not favor counsel for Infocon with further information as to when discovery might be afforded. Nor did she explain why she had again ignored a court-mandated deadline.

Some discovery [described by Infocon’s counsel as “an unorganized document dump” [Doc. 141-2 at 16]] came forth on February 7, 2006. Infocon’s counsel, concluding that ESNA still had not complied with the December 23, 2005, order, filed a motion for sanctions on February 14, 2006.

This led to yet another discovery conference on February 27, 2006. I ordered the parties to file statements regarding the matters in dispute by March 6, 2006, and set a further conference for March 9, 2006. [Doc. 101]. This led to an order directing ESNA to comply with the following by March 31, 2006:

• pre-acquisition due diligence report

• sales data for the period of June 1, 2002, through March 31, 2003, including maintenance and support fees

• results of a search of Exact’s “E-synergy” database

• 2005 ESNA sales data for sales to customers claimed by Infocon to be its customers

• stipulation or other statement re. plaintiff and its or other related, potentially responsible entities; if stipulation not executed, defendant had leave to renew an earlier motion to compel.

[Doc. 104].

In addition to the foregoing, the order of March 10, 2006, required that the production be attested to by persons with knowledge, or on the basis of diligent inquiry as to the authenticity, accuracy, completeness, and truthfulness of responses to interrogatories and requests for production. This provision was necessary in view of uncertainties as to whether prior responses had, in fact, be submitted by an authorized person with knowledge.

Once again, the deadline was disregarded without request for extension, explanation, or excuse.

By mid-May, 2006, Infocon still had not received the price information that ESNA was to have produced by March 31 st. All that ESNA had provided was an unverified printout labeled “Exact Software, North America, Detail of Revenue June 2002, through March 31, 2003.” Rather than *713 telling Infocon what ESNA has sold to whom for how much, etc., this document simply listed figures from licenses, maintenance, and services.

Similarly, the search for documents via ESNA’s “e-Synergy” system was largely unproductive. ESNA’s counsel attributed the lack of success to defects in the keywords provided by Infocon. Here again, counsel seeking in good faith to provide the discovery it was required to provide would have worked with opposing counsel to ensure that production would be accomplished.

ESNA’s counsel has not suggested that she and her client did not know what was being sought. In seeking it, they relied on Infocon’s speculation about how the documents might be retrieved from their system.

Their attitude and approach were not appropriate. Just as a party asking for production of a paper document does not have to specify the room, cabinet, drawer, and file in which the document is to be found, a party calling for production of electronically created and kept information is not required to plot the search with exactitude. If the party from whom discovery is sought can comprehend with reasonable certainty what is being asked for, it is up to it to access its storage system to retrieve the document. If problems are encountered due to uncertainty about what is being sought, the party conducting the search of its own system and records is to ask for further clarification.

In one respect, ESNA undertook to comply with the order to produce: it submitted a stipulation relating to the corporate relationship between ESNA and Exact. That document was not, however, signed or otherwise authorized on its face or attested to by a duly empowered corporate official. The absence of a proper attestation was in direct contravention of the March 10th order. Such noncompliance has never been explained, much less justified.

With regard to specification of when and how ESNA terminated its relationship with Infocon as an ESNA distributor, ESNA produced a statement that placed the termination “on or about September 26, 2003.” That statement was not accompanied by copies of or reference to the documents or documents communicating notice of termination.

The statement was, moreover, inconsistent with an earlier sworn statement that termination had occurred in October, 2003.

How and why ESNA could neither specify when it terminated Infocon [if, such, in fact, occurred] nor produce the documents communicating such termination is inexplicable.

ESNA’s continuing failure to comply with discovery as ordered led the undersigned on May 24, 2006, to order ESNA to respond to Infocon’s pending motion for sanctions by May 31, 2006. ESNA’s counsel assured me and counsel for Infocon that the deadline would be met.

That deadline, was, like almost every deadline previously imposed by the undersigned, ignored. And it was ignored like the many other disregarded deadlines in this case, without explanation, a request for extension, or other gesture of acknowledgment that a court’s order was being disobeyed.

This, in turn, led to an order in which I sua sponte extended the deadline for ESNA’s response to the motion for sanctions to June 8, 2006. That order also stated:

Failure of the plaintiff to comply with this order shall result in an order granting, without restriction, the motion to compel. If that occurs, but nonetheless *714 fails to obtain by July 14, 2006, for defendant the complete discovery sought in its pending motion, the defendant shall have leave to file a motion for appropriate sanctions, including, inter alia, dismissal of plaintiffs complaint, striking of plaintiffs answer to the counter-complaint, entry of judgment by default against the plaintiff-counter-defendant, and the setting of further proceedings to determine the amount of damages to which the defendant may be entitled on its counter-complaint.

[Doc. 114].

Infocon’s motion to compel thereafter became decisional. On review of the parties’ contentions, the bumpy course of discovery to that point, reasons for the problems, and reasonableness of the discovery being sought, I ordered that by July 31, 2006, ESNA was to: “completely produce, as requested by Infocon, and do so in verified form as required herein:”

A. Sales information;

B. Data and information from the e-Synergy searches;

C. Due diligence reports;

D. Third Party Contracts;

E. A Verified Stipulation;

F. Documents relating to termination of its reseller status; and

G. End User Sub-License Agreements

[Doc. 119].

In addition to specifying the discovery to be provided, that order repeated my earlier warning to ESNA about the likelihood of sanctions, including judgment in favor of Infocon by default, if compliance was not timely and complete:

If these expectations are not met, and substantial cause for the failure to meet these expectations is not shown, further sanctions, including, inter alia, exclusion of evidence and entry of judgment by default, shall be considered.

[Id]

Rather than providing the discovery that was required of it, ESNA filed a supplemental brief. That brief, was, in essence, a motion for reconsideration of the order granting the motion to compel. ESNA contended that the documents covered by the order did not exist or it could not be required to create them or the data called for. ESNA sought, in essence, leave to conduct a computer search, or to have one conducted by experts to be obtained by Infocon [and paid for by ESNA] to see just what could be provided.

That response to the motion to compel was completely unsatisfactory. What was required was compliance, not further equivocation.

The June 26th order had also ordered ESNA to show cause by July 14, 2006, why the fees and costs incurred by Infocon in procuring that order and accomplishing the discovery ordered therein should not be borne by ESNA. ESNA ignored the deadline for showing cause [just as it was to ignore the July 31st deadline for providing discovery]. Ten days past the deadline for showing cause with regard to the shifting of fees and costs, ESNA filed a brief in response to the show cause order.

In addition to failing to acknowledge, much less explain the tardiness of its filing, ESNA’s brief in response to the show cause order failed utterly to show cause why fee shifting should not occur. While it repeated earlier assertions about the nonexistence of items it was to produce [contentions that I had previously found and still find] to be implausible, ESNA also offered nothing to support its contentions except the conclusory contentions of its counsel. Because the brief in response to the show cause portion of the June 26th order was both untimely and insufficient, *715 fees and costs were awarded to Infocon. [Doc. 131]. 21

D. Failure to Retain Data

Added to its noncompliance with a series of court orders is the failure of Exact and/or ESNA to have retained backup tapes for the period covered by Infocon’s request for discovery.

As I understand ESNA’s representations [made by counsel, rather than by a knowledgeable corporate official under oath], Exact has developed, both for its own internal use and as a product for sale to the commercial public, its “e-Synergy” system for document storage and retrieval. Some, if not many of the documents being sought by Infocon would, apparently, have been maintained and thus have been accessible via this system.

Many of the discovery conferences involved discussion of the e-Synergy system and its potential as a source for otherwise unavailable documents. It was not, however, until July 24, 2006, that ESNA’s counsel suggested to counsel that the backup tapes no longer exist for the period covered by Infocon’s discovery requests. That circumstance was first called to my attention, and confirmed by ESNA’s counsel on August 4, 2006.

That data pertinent to this litigation was not preserved, and appears to have been destroyed not only during the pendency of this lawsuit, but, quite possibly, after discovery requests had been submitted by Infocon, is neither comprehensible nor acceptable.

Most importantly, with regard to the pending motion for default, ESNA has offered no affidavit or other evidence about how and why the data was destroyed. Did destruction occur without actual notice of the need to preserve; if so, why was Exact not on notice of the need to preserve the data; was destruction in accordance with an established protocol or timetable; if not, why were established procedures not followed?

Rather than giving sworn answers to these and other possible questions about what happened to the data and why, ESNA has failed completely to respond to the allegations of deliberate spoliation. In this instance, and under the circumstances, its silence must be viewed as acceptance of the worst of the adverse inferences that can be drawn about its conduct. 22

*716 Following the disclosure about the destruction of the backup tapes, and in light of the failure of ESNA to have complied with prior orders regarding discovery despite warnings in those orders as to the consequences of noncompliance, this court granted leave to Infocon to file the instant motion for entry of judgment by default as to all claims and counterclaims in its favor and against ESNA.

E. ESNA’s Response to Infocon’s Motion for Judgment by Default

Infocon has submitted a detailed review of the problems it has encountered in securing discovery from ESNA and this court’s response to those problems. ESNA’s response to the motion does not meet the motion head-on. As noted in the discussion, supra, of the categories of information and documents sought, ESNA’s point-by-point response fails to explain why production did not occur when first requested and/or ordered by this court, or why deadlines were consistently disregarded. 23

Even where ESNA asserts that it has provided the discovery, its representation is conclusory, and fails to specify exactly what was produced, and, most importantly with regard to the pending motion for default, when production occurred.

To some extent, as noted variously above, ESNA attempts to shift the blame and responsibility for its nonperformance to Infocon. The time for doing so is long past, given the series of discovery conferences and order that preceded the motion for default.

ESNA’s response, moreover, is largely an attempt to challenge the merits of Info-con’s claims or have this court revisit issues that have previously been adjudicated in Infocon’s favor.

ESNA’s effort to defend its noncompliance with a series of discovery orders by claiming that Infocon cannot prevail on the merits is entirely off the mark. ESNA is not faced with a summary judgment motion. It is, rather, faced with being held accountable for consistently missing deadlines and consistently failing to perform obligations mandated by this court.

*717 Instead of claiming that Infocon cannot prevail on the merits, it is incumbent on ESNA to justify its failure to comply with its discovery obligations and this court’s orders mandating such compliance. Given the consistent and repetitious character of ESNA’s noncompliance, ESNA’s task is difficult and unenviable. Nonetheless, the burden is on it to explain why it did not do what it failed to do.

ESNA has not done so. Whether ESNA has chosen its alternate, misdirected path in the direction of the merits of Infocon’s claims out of ignorance of what is at issue, inability to explain itself, or with an intent to mislead this court is immaterial at this point. What matters is that ESNA’s response does not, in essence, address whether its misconduct should be sanctioned, and, if so, just how severe a sanction that misconduct deserves.

The only concession to the reality of its misconduct is to be found in the last paragraph of ESNA’s response to the motion for default: “Ultimately, it must be acknowledged that there are deficiencies in the discovery responses.”

To paraphrase Winston Churchill: Some deficiencies. Some acknowledgment.

F. The Basis for Sanction and the Need for a Show Cause Hearing

Rule 37(b)(2) of the Federal Rules of Civil Procedure authorizes entry of “ ‘such orders AAA as are just’ with regard to a party’s failure to ‘obey an order to provide or permit discovery, including an order made under [Rule 37(a), Motion for Order Compelling Discovery].’” Reg’l Refuse Sys., Inc. v. Inland Reclamation Co., 842 F.2d 150, 153 (6th Cir.1988). Permissible sanctions include “[a]n order striking out pleadings or parts thereof, or staying further proceedings until the order is obeyed, or dismissing the action or proceeding or any part thereof, or rendering a judgment by default against the disobedient party.” Fed.R.Civ.P. 37(b)(2).

Dismissal of a party’s complaint, especially when joined with entry of judgment by default against the party on a counterclaim, is a drastic sanction, and one that should be considered with caution and entered only in extreme cases. See, e.g., Reg’l Refuse, 842 F.2d at 154 (6th Cir.1988) (“the most severe in the spectrum of sanctions”); Patton v. Aerojet Ordnance Co., 765 F.2d 604, 607 (6th Cir.1985) (citing Societe Internationale v. Rogers, 357 U.S. 197, 78 S.Ct. 1087, 2 L.Ed.2d 1255 (1958)) (“Dismissal of an action for failure to cooperate in discovery is a sanction of last resort.”).

The cornerstone on which a default for noncompliance with discovery requirements and orders rests is “wilfulness, bad faith, or fault.” Patton, 765 F.2d at 607. Where such is found, and where the party had the ability to comply, but failed to do so, default is an appropriate response. See, e.g., Bank One of Cleveland, N.A. v. Abbe, 916 F.2d 1067, 1073 (6th Cir.1990) (dismissal “or entry of default judgment” not an abuse of discretion if a party has the ability to comply with discovery orders but fails to do so).

The Sixth Circuit has upheld default judgments for discovery abuses that were equally or less severe than ESNA’s. In In re Family Resorts of America, Inc., 1992 WL 174539, at *1 (6th Cir.1992), the court approved entry of default against a pro se defendant who requested various extensions for discovery deadlines, answered interrogatories in handwriting, and failed to produce documents responsive to two sets of document requests after the court had *718 ordered production. 24

Other cases have likewise held that comparable or less severe discovery abuses than those in this case justify entry of a default judgment. See, e.g., Bass v. Jostens, Inc., 71 F.3d 237, 241 (6th Cir.1995) (dismissing complaint with prejudice where plaintiff “failed to comply with four discovery orders of the court, failed to appear for a properly noticed deposition, and never sought any type of protective order from the court”); Tech. Recycling Corp. v. City of Taylor, 2006 WL 1792413, at *6 (6th Cir.2006) (finding default judgment proper when party failed to comply with four court orders to produce discovery); Ndabishuriye v. Albert Schweitzer Soc’y, USA, Inc., 2005 WL 1386475, at *5 (6th Cir.2005) (finding default proper when party caused delay, failed to produce discovery after court orders and produced no financial information whatsoever); Bradbury v. Township of Plymouth, 1997 WL 76187, at *6 (6th Cir.1997) (upholding district court’s response to party’s failure “to properly answer the defendants’ interrogatories, failed to respond to the defendants’ motion to compel, failed to comply with the district court’s order to compel, failed to respond to the defendants’ motion to dismiss, and ... failed to appear at [a] dismissal hearing”); CSX Transp., Inc. v. May, 919 F.2d 738, 1990 WL 197834, at *1-2 (6th Cir.1990) (default proper for failing to provide complete answers to interrogatories and failing to file responsive briefs).

When evaluating the propriety of dismissal or default as a sanction, a court is to consider whether: 1) failure to cooperate in discovery is due to wilfulness, bad faith, or fault; 2) the party whose efforts to obtain proper discovery have been frustrated was prejudiced; 3) the sanctioned party was on notice that failure to cooperate could lead to default; and (4) less dramatic sanctions would be effective. See, e.g., Reg’l Refuse, 842 F.2d at 155. Similar factors are taken into account when striking a pleading under Fed. R.Civ.P. 37(b)(2)(c). See United States v. Reyes, 307 F.3d 451, 458 (6th Cir.2002) (affirming district court’s striking of complaint); Pauley v. United Operating Co., 606 F.Supp. 520, 528-530 (E.D.Mich.1985) (entering default against defendant on complaint and striking defendant’s counter-complaint).

A court must, moreover, not sanction a party where the fault lies with inattentive, inept, or incompetent counsel, which ensures that a party does not suffer for the ineptness or incompetence of its counsel. See, e.g., id.; see also Patterson v. Grand Blanc Twp., 760 F.2d 686, 688 (6th Cir.1985) (dismissal deprived plaintiff of his day in court due to the inept actions of counsel); Carter v. City of Memphis, 636 F.2d 159, 161 (6th Cir.1980) (“Dismissal is usually inappropriate where the neglect is solely the fault of the attorney.”).

I cannot, at this point, ascertain whether the extent to which misconduct so amply apparent in the record is due to willfulness or bad faith on the part of ESNA, its counsel, or both. 25 Before I can *719 sanction ESNA, I must determine whether it or its counsel is at fault for the noncompliance with my orders. To that end, I will set a hearing at which will have an opportunity to show cause why it should not be sanctioned. A principal objective of that hearing will be to determine the cause[s] and motive[s] for noncompliance with my orders, and where the consequences shall lie.

The prejudice to Infocon is palpable. For nearly two years its efforts to procure information crucial to its affirmative defenses and counter-claims have been as unsuccessful as they have been persistent. The information at issue is not ancillary to its ease; most of it goes to the heart of one or more of its claims. Without it, it would not have a fair chance of prevailing at trial, or, perhaps, even surviving summary judgment.

The time and sums expended in this effort have been substantial. In the meantime, the trial date ever recedes into the indeterminate future. The prejudice to Infocon in this case has been clear and substantial, not uncertain or insignificant.

Conclusion

For the foregoing reasons, it is hereby ORDERED THAT:

1. A hearing, at which ESNA shall show cause why its complaint should not be stricken and dismissed, with prejudice, and default entered against it as to Infocon’s counterclaims, is hereby set for Tuesday, February 27, 2007, commencing at 8:30 a.m. before the undersigned;

2. Discovery relating to said hearing to be completed by February 15, 2007;

3. Leave granted to the parties, if they desire, to submit brief prehearing statements of issues, witnesses, and evidence, and applicable law on or before February 23, 2007; and

4. ESNA to reimburse Infocon for all attorneys’ fees, costs, and expenses reasonably incurred by Infocon in preparing for and participating in the show cause hearing and related proceedings, including post-hearing briefing, if any; and

5. Pending further order, ESNA to reimburse Infocon for all attorneys’s fees, costs, and expenses relating to further discovery in this case; leave granted to Infocon to bill ESNA monthly for said reimbursement.

So ordered.