Why a simple spreadsheet mattered more than any single hearing

The situation

Soraya realized something was seriously wrong the week after she raised a formal complaint about how a promotion process had been handled within her policing organization, when her next scheduled shift rotation quietly changed, a peer review she had never had trouble with before flagged concerns that had never been raised in years of service, and a supervisor who had previously supported her file began responding to her emails with unusual formality. None of it, taken alone, proved anything. Together, over a period of weeks, it added up to a pattern Soraya believed was retaliation for having spoken up, and she brought a claim against her employer alleging just that, seeking damages in the range of three hundred fifty thousand to eight hundred thousand dollars to reflect the career and reputational harm involved.

Soraya's husband Farid, an air traffic controller, understood better than most people the value of a process that runs on a predictable schedule with clear checkpoints, and he was the one who first asked us directly what the case would actually cost and how long it would realistically take, rather than asking what the odds of winning looked like. That framing mattered. Soraya earned a solid income and could absorb legal costs that many clients could not, but she had no interest in an open-ended process that dragged on for years with unpredictable bills arriving at unpredictable intervals. Her main worry, from the very first meeting, was not whether she would win but whether the case would run in an orderly, foreseeable way.

The employer's side of the file was represented through Amrit, a human resources director who would become the key witness and the person responsible for producing internal documents during discovery. Early signs suggested the employer's records, spread across performance files, scheduling systems, and internal complaint logs, were not well organized, raising the risk of a discovery process that dragged on through repeated requests, partial answers, and missed follow-ups, exactly the kind of unpredictable slog Soraya had said she wanted to avoid.

We told Soraya plainly that we could not promise a particular outcome, but we could promise a disciplined process, and that keeping the case predictable would depend almost entirely on how tightly we tracked what each side owed the other once formal discovery began.

That conversation set the tone for how the file was staffed and run from the outset. Rather than treat discovery as a formality to move through quickly on the way to a hearing, we treated it as the stage where the case's timeline and its budget would actually be decided, since a discovery process that drags through repeated follow-ups and missed deadlines is very often the single biggest driver of unpredictable legal costs in a case of this size.

What the review found

From the first day of examinations for discovery, we built a single undertakings chart listing every question that had been taken under advisement by either side, who owed the answer, what document or information was promised, and the date by which it was due. It sounds like a simple administrative tool, and in one sense it is, but in a case with dozens of undertakings flowing in both directions over many months, a chart like that is often the difference between a case that stays on schedule and one that quietly drifts for a year while nobody notices which promises have gone unanswered.

Reviewing the chart on a regular schedule, rather than waiting for a crisis, surfaced a pattern early. Several of Amrit's undertakings, particularly those involving internal scheduling records and the peer review file that had unexpectedly flagged concerns about Soraya, were coming back late, incomplete, or accompanied by explanations that shifted from one follow-up to the next. On their own, late answers to discovery undertakings are common and rarely significant. But the specific pattern here, where the records most directly relevant to the retaliation allegation were the ones consistently delayed, was different, and the chart made that pattern visible in a way that would have been easy to miss if the undertakings had simply been tracked loosely in email threads and case notes.

Farid, without being a party to the case, had asked early on whether there was a way to see, at any given point, exactly where the file stood, and the chart doubled as that answer. Soraya could look at a single document and see which undertakings were outstanding, which had been satisfied, and what the next deadline was, which did more to manage her anxiety about cost and unpredictability than any single conversation about legal strategy could have.

The review also found that once we raised the pattern of delayed and incomplete answers formally, the employer's own counsel began pushing Amrit's office harder for compliance, which in itself signalled that the employer's side recognized the delays were becoming a liability rather than a routine administrative lag.

None of this proved retaliation on its own. A chart of missed deadlines is not evidence of what happened to Soraya at work; it is evidence of what happened during litigation. But it told us where to focus, and it meant that when the outstanding records finally arrived, we already knew precisely what to look for and why those particular documents mattered more than the dozens of other, less contentious undertakings that had been satisfied on time throughout the file.

What we did

1. Built the undertakings chart on the first day of discovery, not after the fact. We started tracking every undertaking from either side the moment it was made, rather than reconstructing a record later from memory or scattered notes, which meant nothing had a chance to slip through the cracks before anyone noticed it was missing, and gave us a running record we could hand to Soraya at any point without needing to reconstruct it under time pressure.
2. Set a fixed schedule for chasing outstanding undertakings. Rather than follow up only when something became urgent, we reviewed the chart on a set weekly rhythm and sent polite, dated reminders for anything approaching its due date, which kept gentle, consistent pressure on the process without escalating prematurely into a dispute over every minor delay, and without leaving Soraya to wonder whether anyone was actually watching the file.
3. Flagged the pattern in delayed records to Soraya and to opposing counsel early. Once the chart showed that the specific records tied to the retaliation allegation were the ones consistently late, we raised it formally with opposing counsel rather than letting it accumulate quietly, giving the employer's side a fair chance to correct course before it became a bigger issue.
4. Gave Soraya a running cost and timeline estimate tied directly to the chart. Because the undertakings chart showed concretely what remained outstanding, we could give Soraya realistic, regularly updated estimates of what steps were left and roughly what they would cost, which addressed her and Farid's core worry about unpredictability more directly than any prediction about the ultimate result.
5. Brought a motion to compel only after direct requests had genuinely failed. When two of the most significant undertakings, covering the peer review file and internal scheduling records, remained outstanding well past a reasonable extension, we brought a focused motion to compel production, framed narrowly around those specific documents rather than the whole file, to keep costs contained and the issue clear for the court.
6. Prepared Soraya thoroughly for what the compelled records were likely to show. Before the outstanding documents finally arrived, we walked Soraya through the range of what they might contain, good or bad for her case, so that whatever surfaced would not blindside her and so her expectations, and Farid's, stayed grounded in the actual record rather than in hope or in the frustration of the wait.
7. Used the delayed records, once produced, to build a clear timeline of the retaliation allegation. Once the peer review file and scheduling records finally came in, we cross-referenced their dates against Soraya's complaint and the changes to her shift rotation, turning what had been a subjective sense that something was wrong into a documented, dated sequence of events an employer would have to answer for directly.

The outcome

The compelled records showed that the unfavourable peer review had been initiated within days of Soraya's internal complaint being escalated, and that the change to her shift rotation had been approved by the same supervisor who had, until that point, supported her file, a sequence that lined up closely with what Soraya had suspected from the outset but had never been able to prove on her own. Faced with that documented timeline once the compelled records were finally in hand, the employer conceded the core of the retaliation allegation at a scheduled pretrial conference rather than proceed to a full trial, and Soraya secured damages toward the higher end of the range she had claimed.

This was a clear win, but what stayed with Soraya and Farid afterward was not only the number. The case had moved on a schedule they could see coming, with costs that tracked closely to the estimates we had given along the way, rather than arriving as unpleasant surprises. The one significant deviation from the original timeline, the motion to compel, had been flagged well in advance and framed narrowly enough that it did not spiral into an open-ended cost the way discovery disputes sometimes do.

Soraya later said that predictability had mattered to her as much as the eventual result, and that a simple chart tracking who owed what, and by when, had done more to make the process bearable than any single piece of legal strategy. The employer's own delays, rather than derailing the case, ended up becoming part of the evidence that supported it, once a disciplined process existed to notice the pattern and act on it.

The predictability also extended past the settlement itself. Because the case had been documented so thoroughly along the way, closing out the file, confirming the final payment terms, and wrapping up the last administrative steps took only a few weeks rather than dragging on the way loose ends sometimes do at the end of a long file. For Soraya and Farid, that orderly finish mattered nearly as much as the number itself, since it meant the case actually ended when it was supposed to rather than lingering in the background of their lives.

What you can learn from this