A missed notice deadline cascaded through three layers of contracts

The situation

Vartan's first question to our office was blunt: ‘If we missed a deadline we did not even know existed, is there anything left to do?’ The honest answer, at that first meeting, was that it depended on which deadline, how far past it the company already was, and whether anything else in the chain of contracts was still salvageable. It was not the answer he wanted, but it was the one that mattered.

Vartan's family had built a chain of clinics across the Vaughan area over two decades, starting as a single walk-in clinic his parents had run and growing, under Vartan's management, into a company with somewhere between twenty and sixty million dollars in annual revenue and locations across the region. His sister Lusine, a surgeon by training, had moved into a co-owner role several years earlier, handling clinical standards and staffing while Vartan ran the business side. The two made major decisions jointly, and the expansion project was the largest capital commitment the company had made in years.

The company was mid-expansion, building out three new clinic locations at once, and had hired a general contractor to manage the construction rather than negotiate separately with electricians, plumbers, and finishing trades. The general contractor, in turn, subcontracted the mechanical and electrical work on all three sites to a specialty firm it had used before. That firm ran into financial trouble partway through the second location's build-out and simply stopped showing up. Wiring sat exposed behind unfinished walls, and permits that depended on inspection sign-offs could not move forward. The general contractor's principal, Duc, called Vartan directly to say the subcontractor was in default and that his firm was ‘handling it.’

What nobody at the clinic company had realized was that the prime contract between the company and the general contractor contained flow-down language: obligations and notice requirements that ran down through the subcontract chain and, less obviously, ran back up too. Buried in that language was a requirement that the clinic company itself give formal written notice within a set window once it became aware of a default anywhere in the chain, in order to preserve its own right to claim against holdback funds and against a payment bond tied to the project. That window had already closed by the time Vartan called our office, roughly three weeks after the subcontractor stopped work and about a week after the deadline had quietly, invisibly passed.

The exposure was not abstract. Delay costs on the stalled second location were mounting weekly, and a meaningful portion of the holdback the company could claim for finishing the abandoned work was tied to the missed step. The company also had no clear internal record of who had known what, and when, which made it hard to assess how bad the position was before we started.

The gap nobody had noticed

The core problem was not that anyone at the clinic company had been careless. It was that the flow-down notice clause lived three layers deep in a contract nobody had reread since signing, written in language that, on a first pass, seemed to describe an obligation running the other direction — something the general contractor owed the clinic company, not the reverse.

Flow-down terms are common in construction and larger subcontracting arrangements, and for good reason. They exist so that obligations at the top of a chain — warranty standards, insurance requirements, dispute procedures, notice deadlines — are mirrored down through each subcontract, so that a general contractor cannot promise something to the owner that its own subcontractors are not equally bound to deliver, and so that a default anywhere in the chain triggers a consistent, predictable response instead of a scramble. The tradeoff, and the part owners rarely notice until it costs them something, is that the party at the top of the chain often inherits obligations of its own: notify us within a fixed number of days once you learn of a default anywhere below you, or your right to claim against certain protective funds is affected, sometimes permanently.

In Vartan's contract, that clause sat inside a general dispute-notice section rather than one labelled for subcontractor defaults specifically, which is part of why nobody flagged it during the original signing. It used the term ‘adverse event’ rather than ‘default,’ and it defined the notice window as running from when the company ‘knew or ought reasonably to have known’ of the event — not from the moment Duc formally called to explain what had happened. That distinction turned out to matter enormously. Our review of the company's own email records found a message from the site supervisor, sent to Lusine three days before Duc's phone call, that already described the subcontractor as ‘basically gone, no one on site in over a week.’ That email, not the later phone call, was the more defensible starting point for the clock under the contract's own wording, and it meant the missed window was missed by a wider margin than anyone at the company had assumed going in.

This is the gap that catches otherwise well-run companies, not careless ones. A notice obligation flows down from a contract signed once, years or months earlier, and sits dormant until a default anywhere below it wakes it up — with a clock that starts on knowledge, however informal, rather than on any formal notification the business is used to waiting for. Nobody at Vartan's company had flagged the clause before, simply because nobody had ever needed to.

What we did

1. Pulled and mapped the full contract chain — we assembled the prime contract, the general contractor's subcontract with the mechanical and electrical firm, and every side letter and change order attached to the project, because a single missed exhibit can hide a second, later notice window that changes the whole analysis. Confirming there was no such window was the first thing we needed to rule out before advising Vartan on anything else.
2. Fixed the actual date the clock started — by cross-referencing the site supervisor's email against the contract's ‘knew or ought reasonably to have known’ wording, we established the earliest defensible trigger date rather than accepting the company's own assumption that the clock started with Duc's phone call. This mattered directly: it determined how much, if any, of the notice window could still be argued as technically open.
3. Separated the recoverable claims from the lost one — close reading showed the missed deadline affected only the company's right to claim against the specific holdback tied to the second location's mechanical work. It did not touch separate rights under the general contract for delay costs across the whole project, which ran on a different, still-open notice clock that nobody had missed.
4. Sent notice immediately on every claim that remained live — rather than spend further time deliberating over the lost claim, we issued formal written notice on the delay-cost claim and two smaller warranty items that same week. Every day of additional analysis on the dead claim risked letting a live one run out too, so speed on the salvageable items came first.
5. Negotiated directly with the general contractor — we approached Duc's firm not as an adversary to sue but as a party with its own real exposure to the defaulting subcontractor, since Duc's company had also lost time and money. That shared interest let us propose a cost-sharing arrangement for the project delay that resolved the dispute without either side paying legal fees to litigate it out.
6. Documented the loss cleanly for the company's own records — the missed holdback claim was written up plainly for Vartan and Lusine, with the dollar amount, the specific reason it was foreclosed, and the date the window closed, so the company had a clear internal record instead of a vague, unsettled sense that something on the project had simply gone wrong.
7. Reviewed insurance and bonding coverage for any overlap — before closing the file, we pulled the company's commercial general liability policy and the project's own builder's risk coverage to check whether either might partially offset the lost holdback claim through a different route entirely, separate from the notice dispute. Neither policy responded to a purely contractual default of this kind, but confirming that in writing meant Vartan was not left wondering, months later, whether a second recovery path had simply been overlooked alongside the missed one.
8. Built a standing contract-review step for future projects — we set up an internal process, with a one-page checklist Vartan's office now runs against every material contract before signature, flagging any clause containing flow-down, notice, or default language and assigning it a calendared reminder tied to the relevant milestone rather than to memory. The checklist also requires a named person, not just a department, to confirm they read the notice provisions specifically, so responsibility for catching the next one does not sit with no one in particular.

The outcome

The holdback claim tied to the missed window was not recovered. That loss came to a low six-figure amount, a real cost the company absorbed rather than a rounding error, and we told Vartan and Lusine directly, early on, that no argument realistically available to us was likely to change that outcome once the notice period had already run before we were retained. We did not spend the company's money chasing an argument we believed would fail.

What was preserved mattered more in the long run than what was lost. The delay-cost claim, running on its own separate notice clock, was pursued successfully and recovered in full. The cost-sharing arrangement negotiated directly with Duc's firm covered a meaningful share of the schedule impact on the second location, and it resolved without either company engaging litigation counsel to fight over it formally. The third clinic location's build-out proceeded on a revised timeline afterward, without any further contract disputes arising on the project.

The larger result was the change in how the company operates now. Vartan's office flags flow-down and notice obligations at the point of signing on every material contract it enters, with calendared reminders tied to project milestones rather than relying on someone happening to notice a clause after a default has already occurred. Lusine, whose routine email had unknowingly started the clock the company later lost, now understands why an ordinary status update sent to a business partner can carry legal weight the sender never intended it to carry. The company's expansion continued, but its contract habits did not stay the same. Vartan later described the missed claim to us as the most expensive lesson the business had learned in a decade, and also the last time it would learn a lesson that way, since the review process now catches these clauses before a signature, not after a default.

What you can learn from this