When a property developer's counsel in Kamloops, British Columbia opened a litigation file in early 2020 to assess the current posture of a construction lien dispute that had been commenced in 2017, the records revealed a troubling pattern: the last substantive step in the proceeding had occurred nearly 3 years earlier, and the file had accumulated no activity beyond routine administrative correspondence during that entire period. The underlying claim, brought by a building materials supplier seeking recovery of $24,000 for goods delivered to a residential development project, remained technically alive on the court's docket, yet the procedural record showed none of the hallmarks of active litigation. No examinations for discovery had been scheduled, no interlocutory motions had been brought, and no case planning conference had been requested by either party. The developer's counsel now faced a situation where the file's dormancy had transformed a defensible dispute into a potential dismissal proceeding, not because the merits had shifted, but because the machinery of litigation management had failed to generate the procedural momentum courts expect from parties who genuinely intend to prosecute or defend their claims.
The phenomenon of procedural dormancy occupies a distinct position within litigation file management because it creates risk that compounds silently over time. Unlike a missed limitation period, which produces an immediate and often irreversible bar to proceeding, dormancy accumulates incrementally until a threshold is crossed that triggers judicial scrutiny or opposing party action. The British Columbia Supreme Court Civil Rules establish mechanisms specifically designed to identify and dispose of proceedings that have stalled, and these mechanisms operate on timelines that punish inattention with increasing severity. A file that sits untouched for 1 year may require nothing more than a procedural step to restore momentum, but a file dormant for 3 years enters territory where the court's patience and the opposing party's tolerance have both been tested. The Kamloops lien dispute exemplified this progression: what began as a routine collection matter with clear documentation and a straightforward legal theory had become, through accumulated neglect, a file whose procedural vulnerabilities now overshadowed its substantive merits.
Understanding how dormancy endangers litigation requires attention to the specific procedural architecture that governs file activity in British Columbia. The Supreme Court Civil Rules empower registrars to issue notices requiring parties to show cause why proceedings should not be dismissed for want of prosecution, and these notices trigger response windows measured in days rather than months. Once such a notice issues, the defending party must demonstrate that the litigation remains viable and that delay has not prejudiced the opposing party to a degree that makes continuation unjust. The evidentiary burden on the party seeking to maintain the action includes explaining the reasons for delay, establishing that the claim retains merit, and satisfying the court that prejudice either has not occurred or can be remedied. For the developer's counsel reviewing the Kamloops file after 3 years of inactivity, each of these requirements presented challenges that would not have existed had the file received consistent procedural attention throughout its life.
The origins of the dormancy in this matter traced to a confluence of factors common to litigation file management failures. The building materials supplier's claim had been filed shortly before the expiry of the applicable limitation period, and the initial pleadings exchange had proceeded without incident. The developer's response raised defences relating to the quality of materials delivered and the conformity of the goods to the contract specifications, creating a dispute that would require documentary production and likely expert evidence to resolve. However, once the pleadings closed, neither party took steps to advance the matter to the discovery phase. The supplier may have been awaiting some indication of settlement interest before incurring the costs of production; the developer may have treated the relatively modest quantum as insufficiently urgent to warrant proactive case management. Whatever the motivations, the file entered a period where no diarized deadlines compelled action, and the absence of external pressure allowed months to accumulate into years.
Litigation file management systems are designed to prevent precisely this pattern, but their effectiveness depends on disciplined implementation and regular review. A properly maintained litigation file includes diarized entries that compel attention at intervals regardless of whether external deadlines exist. These internal triggers might include periodic reviews to assess settlement posture, reminders to initiate discovery steps, or alerts tied to the anniversary of the last procedural event. When these safeguards are absent or overridden, files drift toward the inactivity thresholds that expose them to dismissal risk. The developer's counsel, examining the file in 2020, could reconstruct this drift through the absence of diary entries: the file showed no scheduled reviews after the close of pleadings, no ticklers for production deadlines that had never been set, and no notation of a case management strategy. The file existed in a state of suspended animation, visible on the practice management system but generating no prompts for engagement.
The 3 years of inactivity that characterized this file placed it within the zone where registrar-initiated dismissal proceedings become probable rather than merely possible. British Columbia's civil procedure framework includes administrative review processes that identify dormant files and require parties to justify their continuation. These reviews are not triggered by any party's motion; they are initiated by the court's own administrative machinery as part of its mandate to manage its docket efficiently. When a file has shown no activity for an extended period, the registrar may issue a notice requiring the parties to appear and demonstrate that the proceeding should not be struck for want of prosecution. The notice typically provides a response window of 1 to 2 weeks, requiring the recipient to prepare and file materials that address the court's concerns on an accelerated timeline. For a file that has been dormant, this compressed timeline creates practical difficulties: counsel must locate the file materials, review the procedural history, assess the current merits, and prepare submissions, all within a period that assumes active familiarity with the matter.
The prejudice analysis that courts undertake when considering dismissal for delay operates on principles that disadvantage parties who have allowed dormancy to accumulate. Courts recognize that litigation delay impairs the opposing party's ability to defend itself or prosecute its claims because memories fade, witnesses become unavailable, and documents are lost or destroyed. Even when the dormant party can establish that its own case remains intact, the opposing party may be able to demonstrate that its position has been compromised by the passage of time. In the Kamloops lien dispute, the developer's counsel needed to consider whether 3 years of inactivity had affected the availability of evidence on either side. The building materials supplier presumably retained invoices and delivery records, but witnesses who could speak to the condition of goods upon delivery or the circumstances of any complaints might have moved, forgotten details, or become otherwise unavailable. The developer's own witnesses, including site supervisors and project managers, might face similar difficulties reconstructing events that had occurred 6 years prior to any anticipated trial date.
The distinction between plaintiff dormancy and defendant dormancy carries significant procedural implications that the developer's counsel needed to evaluate. The building materials supplier, as the claimant, bore the primary obligation to advance the proceeding toward resolution. A plaintiff who files a claim and then takes no steps to prosecute it violates the implicit bargain that underlies access to the courts: the right to commence litigation carries a corresponding duty to pursue it with reasonable diligence. Defendants, by contrast, have no obligation to assist plaintiffs in prosecuting claims against them, and a defendant's silence does not typically constitute the kind of delay that warrants sanction. However, this asymmetry does not mean defendants can ignore dormant files entirely. A defendant who wishes to be rid of a stale claim has procedural tools available, including the ability to bring a motion to dismiss for want of prosecution without waiting for a registrar-initiated review. The developer's counsel needed to consider whether bringing such a motion would serve the client's interests or whether it might provoke the supplier into renewed activity on a claim that might otherwise have been abandoned.
Strategic considerations in responding to dormancy create a complex decision matrix for litigation file managers. The option of allowing continued dormancy carries the hope that the opposing party will eventually abandon the claim or that any attempted revival will be met with a successful dismissal motion. This passive approach conserves resources in the short term but leaves the file open indefinitely and preserves the opponent's option to revive the proceeding. The option of seeking active dismissal forces a resolution but requires expenditure of resources on motion materials and potentially a contested hearing, with no guarantee of success. The option of initiating settlement discussions acknowledges the claim's existence and may signal weakness, but it offers a path to finality that neither continued dormancy nor contested dismissal provides. For a claim of $24,000, these strategic calculations are heavily influenced by proportionality: the cost of a contested dismissal motion might approach or exceed the value of the claim itself, making settlement the economically rational choice even if the defence has merit.
The file management failures that allowed this dormancy to accumulate illustrate systemic vulnerabilities that extend beyond any individual file. Litigation practices that rely on external deadlines to drive file activity will experience dormancy whenever the procedural calendar permits gaps in required action. The period between close of pleadings and commencement of discovery is particularly susceptible because it contains no court-imposed deadlines in most civil proceedings. Parties must self-initiate the next phase of litigation, and absent a case management order or a diligent opponent, this self-initiation may never occur. Practices that implement tickler systems keyed to time-from-last-activity rather than time-to-next-deadline can prevent this gap from opening, but such systems require consistent maintenance and attention. The developer's counsel, reviewing this file, would recognize that the dormancy resulted not from any conscious decision to delay but from the absence of systems that would have compelled periodic review and action.
The documentation within a dormant file often reveals the gradual decay of institutional knowledge that accompanies inactivity. Early correspondence shows familiarity with the file's details, specific references to documents and conversations, and clear articulation of strategic objectives. Later correspondence, if any exists, tends toward generality and uncertainty, reflecting the fading engagement of those responsible for the file. File reviews, when they occur, may be perfunctory notations that the matter is "pending" without analysis of what steps are required or why none have been taken. The Kamloops file exhibited this pattern: detailed attendance notes from the pleadings phase gave way to sparse entries as the file aged, culminating in a period of essentially no documented attention. Reconstructing the file's posture for purposes of responding to a dismissal notice would require not only reviewing existing documentation but also re-establishing the factual foundation that had been allowed to erode.
The timing considerations that govern dismissal motions create particular pressure points for defendants in dormant proceedings. Courts evaluating delay consider the entire history of the proceeding, not merely the recent period of inactivity, and they allocate responsibility for that history based on which party had the obligation to advance matters at each stage. A defendant who sat silently while the plaintiff delayed cannot claim prejudice from delay the defendant could have prevented by bringing a dismissal motion earlier. Conversely, a defendant who actively obstructed progress cannot complain that the plaintiff failed to overcome those obstructions. The developer's position in this dispute was ambiguous: no active obstruction had occurred, but neither had any effort to compel the plaintiff to prosecute or to seek dismissal for failure to do so. This passivity, while not legally culpable, reduced the equitable force of any prejudice argument the developer might advance.
The interplay between limitation periods and dismissal for delay creates a secondary layer of complexity for file management purposes. The building materials supplier's claim had been filed in 2017, and 6 years had elapsed since that original filing. Depending on the nature of the claim and the applicable limitation statute, the supplier might no longer be able to commence a new action if this one were dismissed. This consideration cuts in different directions for different purposes: it increases the supplier's motivation to resist dismissal vigorously, potentially resulting in contested proceedings that consume resources, but it also increases the finality value of any dismissal that is obtained. For the developer, the prospect of definitively extinguishing the claim might justify the expense of a dismissal motion that would otherwise seem disproportionate to the amount at stake. The limitation period analysis thus becomes an input to strategic decision-making about how to address the dormant file.
Rehabilitation of a dormant file, when a party chooses to revive rather than abandon or dismiss, requires systematic attention to the procedural steps that were never completed. In the Kamloops dispute, this would mean finally initiating the discovery process that had been deferred for 3 years: serving demands for production, scheduling examinations, and potentially retaining any expert witnesses needed to address the quality and conformity issues raised by the defence. The cost of completing these steps must be weighed against the value of the claim or the defence, and 3 years of dormancy will have affected some of the calculations. Witnesses may need to be located and re-interviewed; their recollections may be less reliable than they would have been had discovery proceeded promptly. Documents may have been archived, destroyed, or lost in ways that would not have occurred during an actively managed proceeding. The party seeking to rehabilitate the file bears these burdens, and they represent a form of self-inflicted prejudice that may not generate sympathy from the court.
The response windows of 1 to 2 weeks that characterize registrar-initiated dismissal processes impose acute pressure on file managers who have allowed dormancy to accumulate. These compressed timelines assume that counsel is familiar with the file and can quickly assemble the materials needed to respond. For a file that has been untouched for 3 years, this assumption fails. Counsel must effectively recreate the file from first principles: reviewing pleadings, assessing the current state of any limitations issues, evaluating the availability of evidence, and constructing an explanation for the delay that will satisfy the court. The administrative burden of this task is substantial, and the timeline permits little margin for error. A response that is incomplete, late, or unpersuasive may result in dismissal, transforming procedural neglect into permanent loss of the right to pursue or defend the claim.
File management disciplines that prevent dormancy must be implemented at the practice level, not merely the individual file level. A lawyer who maintains rigorous systems for one file while neglecting others creates inconsistent risk across the practice. Effective file management requires standardized protocols that apply to all matters, regular reviews that catch dormancy before it reaches critical thresholds, and escalation procedures that ensure problematic files receive attention from senior practitioners. The Kamloops file's 3 years of inactivity suggest that these protocols were either absent or not consistently applied. The review that occurred in 2020 may have been triggered by a billing inquiry, a client contact, or simply an accidental rediscovery of the file during other work. Whatever prompted the review, it came late enough that the file's procedural vulnerabilities had fully matured.
The professional responsibility dimensions of litigation file management add a further layer of concern for counsel handling dormant files. Lawyers have duties to their clients that include diligent prosecution or defence of their matters, and allowing a file to become dormant without the client's informed consent may constitute a breach of those duties. The developer's counsel needed to consider whether the dormancy had been communicated to the client, whether the client had been advised of the risks that dormancy created, and whether any failure in these communications might expose counsel to complaint or claim. These considerations operate independently of the outcome of the substantive dispute: even if the dormancy causes no ultimate prejudice to the client's position, the failure to maintain appropriate file management may itself be a breach of professional obligations. Documentation of communications with the client about file status and strategy becomes crucial evidence in any subsequent dispute about the adequacy of the representation.
The $24,000 quantum of this dispute illustrates a persistent challenge in litigation file management: proportionality pressures encourage minimal engagement with smaller matters, but the procedural consequences of inattention do not scale with the amount at stake. A registrar-initiated dismissal process treats a $24,000 claim identically to a $24 million claim; the response windows are the same, the prejudice analysis follows the same principles, and the potential consequences are equally severe. File managers who allocate attention based on quantum risk allowing smaller matters to drift toward dormancy while larger matters receive the engagement needed to prevent it. This allocation may be economically rational in the short term, but it creates exposure that can materialize unexpectedly when a dormant file suddenly demands urgent attention.
The Kamloops lien dispute, viewed through the lens of litigation file management, demonstrates how procedural neglect transforms substantive disputes into procedural crises. The underlying claim—a supplier seeking payment for building materials—raised factual and legal issues that were entirely capable of resolution on the merits. The developer's defences relating to quality and conformity were cognizable and potentially viable. Nothing about the substance of the dispute made it inherently difficult to manage or litigate. What endangered the proceeding was not the complexity of the issues but the absence of the procedural discipline needed to move them toward resolution. Three years of inactivity had created a file that now required immediate, resource-intensive attention to preserve options that would have remained available at no cost had the file been properly maintained throughout its life.