When a Security Guard's Memory Mattered More Than a Clause

The situation

Anjali read the draft purchase agreement twice before she flagged it. The representations and warranties clause said the sellers had no knowledge of any undisclosed liabilities, and knowledge was defined as anything the sellers 'knew or ought to have known.' On paper it looked protective. In practice, Anjali realized, it protected nobody. If something surfaced after closing, proving what a person 'ought to have known' would turn into a fight about reasonableness rather than a fight about facts, and her fund's investment committee did not want to buy a lawsuit along with a pharmacy chain.

The target was a three-location pharmacy business built by a family over two decades. Anjali's employer, a private equity-backed platform buyer already operating similar chains across the GTA, was acquiring it as a bolt-on to an existing regional network. The deal sat in the eight-to-fifteen-million-dollar range, small enough that neither side had deep M&A counsel on staff full time, which was part of the problem. The seller's first-draft agreement had clearly been adapted from a template used on an unrelated transaction, with the knowledge qualifier copied in without much thought about who actually knew what inside this particular business.

Anjali brought the draft to our office not because anything had gone wrong yet, but because she had learned, on an earlier deal at a different fund, what a vague qualifier can cost once a claim actually arises. She wanted the definition tied to real people this time, people whose knowledge could be checked and confirmed before the deal closed, not argued about after money had already changed hands.

The complication was that the family selling the business had strong feelings about who got singled out. The mother and son who owned the chain were proud of running it themselves, and the idea that two of their staff, rather than the owners, would be named as the people whose knowledge mattered felt to them like an accusation. Anjali's first attempt to raise it in a call had gone badly. The sellers' lawyer asked for a pause in negotiations the same afternoon, and for two days nobody on either side returned calls.

By the time Anjali came back to us with the stalled file, the deal had a closing date on the calendar and a financing commitment with its own expiry. There was no room to let the clause sit unresolved for long, but pushing harder on the same language that had already caused offence was clearly not going to work either.

The complication

The two employees Anjali wanted named were not executives. One was Prakash, a security guard who worked nights at the flagship location and had, over the years, been the person who actually saw the loading dock, the expired-stock disposal, and the after-hours deliveries that never made it onto anyone's paperwork. The other was Dov, a pharmacy technician who handled the day-to-day inventory system and would know, better than the owners themselves, whether the controlled-substance counts had ever come up short. Naming them in the knowledge definition was not about blame. It was about accuracy. These were the two people whose actual, first-hand knowledge would matter if anything about inventory or compliance ever became a dispute.

The owners heard it differently. To them, singling out a security guard and a technician by name in a legal document read as an accusation that something was wrong, or worse, as a signal that the buyer distrusted the family and was going around them to their own staff. One conversation escalated into raised voices on a call, with the son accusing Anjali's team of trying to build a case against his mother before the ink was dry. Deal fatigue was already setting in on both sides, and for a few days it looked like the whole negotiation might stall over a definitional clause neither party had originally thought would be contentious.

What made this harder than an ordinary drafting dispute was that the legal fix could not go first. Anjali could not simply insist on the language and expect the sellers to sign it once the logic was explained. The relationship needed to be repaired before the clause could be repaired, because a family that felt accused was not going to read the next draft in good faith no matter how carefully it was worded. Anyone pushing the technical argument at that moment, however correct, would have made the deal worse, not better.

There was also a real commercial risk sitting underneath the emotion. If the deal collapsed over this single clause, both sides lost months of work and legal spend, and the buyer would be back to searching for another acquisition target in a market where good bolt-on candidates were not easy to find. The financing commitment behind the deal had its own timeline, and letting the file drift while feelings cooled was not really an option. Anjali needed the precision the clause offered, but she needed the deal to survive long enough to get it, and those two goals were, for the moment, pulling against each other.

What we did

1. Separated the relationship problem from the drafting problem. Before touching the agreement again, we recommended a call devoted entirely to explaining the purpose of a knowledge qualifier, with no proposed language on the table at all. The goal was to let the owners hear, without a document sitting in front of them ready to be signed or refused, that naming specific employees is standard practice meant to make future claims provable, not an accusation aimed at any one person in the room.
2. Reframed the ask around protection for the sellers too. We pointed out that a knowledge qualifier tied to named individuals protects sellers as much as buyers, because it means the sellers cannot later be held responsible for what some unnamed junior staff member elsewhere in the business might have known. Once the owners understood the clause cut both ways rather than pointing only at them, the conversation noticeably stopped feeling one-sided and adversarial.
3. Proposed adding the owners to the named group rather than replacing them. Instead of the security guard and the technician standing alone as the knowledge group, we suggested naming all four individuals together: the two owners and the two employees whose operational knowledge actually mattered day to day. This let the family see themselves included in the clause rather than sidelined by it, while keeping the people with real hands-on knowledge in the definition as well.
4. Ran short, structured interviews with each named individual. With everyone's consent, and with the owners present for their own staff's interviews, we spent an afternoon confirming what each of the four people actually knew about inventory practices, controlled-substance handling, and any past incidents worth flagging. This gave both sides a shared factual baseline before the clause was finalized, rather than a guess about what naming someone might later expose.
5. Drafted the knowledge definition around the confirmed facts. The final clause limited 'sellers' knowledge' to the actual, personal knowledge of the four named individuals as of the closing date, with no constructive knowledge standard and no obligation on any of them to have investigated further before signing. This gave Anjali's fund a defined, checkable group to point to instead of an open-ended standard nobody could apply consistently.
6. Built in a survival period matched to the size of the deal. Because the transaction sat toward the lower end of the fund's typical range, we negotiated a survival period scaled to that size rather than importing the longer periods used on larger platform acquisitions. A survival period copied from a bigger deal template would have left the sellers exposed to claims far longer than a transaction this size usually justifies, keeping their exposure proportionate to the price actually paid rather than the fund's standard playbook.
7. Confirmed the final language with both sides before signing. We circulated a plain-language summary of what the clause meant for each named person, translating the drafting into everyday terms rather than assuming everyone could read legalese the same way a lawyer does. That step produced a shared, written understanding both the owners and Anjali's investment committee could point back to later, so neither side was relying on memory or legal phrasing alone at final sign-off.
8. Documented the interview notes and kept them with the closing file. The notes from the knowledge interviews were preserved alongside the signed agreement rather than discarded once the drafting was finished, because a knowledge qualifier is only as useful as the evidence behind it. That record meant if a question about someone's knowledge ever arose later, there would be a contemporaneous account to check rather than competing memories reconstructed months or years after the fact.

The outcome

The deal closed roughly six weeks after the disputed call, with the knowledge qualifier defined around the four named individuals rather than a vague standard borrowed from an unrelated template. The owners signed having heard, and accepted, why the clause existed, which in the end mattered more to how smoothly the closing went than the precise wording of the clause itself.

The value of the approach showed up about four months after closing, when a routine inventory audit under new ownership turned up a discrepancy in controlled-substance records dating from before the sale. Because the knowledge definition was specific, Anjali's team could go directly to the question that mattered, rather than arguing generalities: did any of the four named individuals actually know about the discrepancy before closing. The inventory system offered no answer, since it tracked only current counts. What resolved the question was Prakash's memory: he recalled a specific after-hours pickup of stock by one of the previous owners, on a date that matched the missing quantity, an event never logged because watching the loading dock was his job, not recording it. That recollection resolved what could otherwise have become a drawn-out dispute about reasonableness and constructive knowledge, the exact fight the original template language would have invited.

The indemnity claim was resolved directly between the parties within a few weeks, with the sellers covering the cost of the compliance correction, because the underlying facts were no longer in dispute once the knowledge group was checked. Nobody spent time arguing about what the sellers 'ought to have known.' The record already showed what they did know, and exactly who knew it, which cut the whole negotiation down from what could have been months to a matter of weeks.

Anjali later said the hardest part of the deal was not the legal drafting, it was getting everyone back to a room willing to talk about the clause calmly after the first attempt had gone so badly. The precision in the final agreement only ended up working because the relationship survived long enough to get there, and because nobody tried to force the technical fix through before the trust to accept it existed.

What you can learn from this