TREADSTONE LAW · ONTARIO · DIGITAL LEGAL SERVICES · EST. MMXXI ·TSL
Home/Case Studies/Corporate
№ 191 Case Study — Corporate

Two testing companies that had quietly become one on paper only

A Petawawa environmental testing company and a related lab run by a third shareholder had operated as a single business for years without ever formally combining, until a municipal review asked hard questions about who had actually done the work.

Corporate9 min readPetawawa, OntarioChoosing amalgamation over a purchase structure
All Corporate case studies
ClientMarek and Jacek, cousins and co-founders of a Petawawa testing company
The issueTwo related but legally separate companies had blended operations informally for years, raising questions when a municipality reviewed their contracts
ServiceStructuring an amalgamation instead of a purchase, and organizing years of records to respond to a municipal contract review
ResolutionThe companies combined and kept their contracts, though one municipality required a corrective plan before renewing

The situation

Marek and Jacek are cousins who grew up two streets apart in Petawawa and started their environmental and geotechnical testing company together twelve years ago, after Marek left a job as a municipal planner and Jacek left work as a court clerk. They split responsibilities the way cousins who trust each other tend to: Marek handled client relationships and contracts, Jacek handled compliance and the books, and neither one formalized much of it beyond a basic shareholders' agreement drafted in their first year and barely looked at since. The business grew steadily on the strength of that trust, taking on municipal and civilian contracts across the region without either of them ever feeling the need to bring in outside advice on how the company was structured.

A few years into the business, they met Indah, who ran a smaller materials testing lab with her own provincial licence and a handful of her own municipal contracts, built up over years of steady, careful work. The three of them started referring jobs to each other constantly, then sharing equipment when one side had a piece of gear idle, then sharing staff during busy seasons when one company had more work than hands, until it became genuinely difficult for anyone inside the business to say with confidence where Marek and Jacek's company ended and Indah's lab began. Indah eventually took a minority stake in the larger company as well, as a way of formalizing the partnership, without her original lab ever actually being folded into it. Two companies, one shared team in practice, and one set of increasingly loose habits that nobody had stopped to properly examine.

By the time revenue across both operations reached the low millions combined, everyone involved understood, at least in the back of their minds, that the arrangement was overdue for a proper structure. Contracts were sometimes invoiced through whichever company happened to have available capacity that particular month, not necessarily the one that had actually signed the agreement with the municipality in question. It was never intended as anything improper by any of the three of them. It was simply what happens, gradually and almost invisibly, when three people who trust each other completely stop keeping the underlying paperwork current with what is actually occurring on the ground.

They came to us wanting to finally combine the two businesses into one clean, properly structured company, before the informality caused a real problem down the line. The instinct itself turned out to be exactly right. What none of them expected was that the problem would arrive before the paperwork did, and from a direction none of them had been watching.

Where it went wrong

Midway through planning the combination, one of the municipalities that had contracted with Indah's lab directly launched a routine procurement review, the kind most vendors never notice happening and never think about until it lands on their desk. This one noticed a pattern that had built up quietly over several years: invoices for work under Indah's contract had, on a meaningful number of occasions, been issued instead by Marek and Jacek's company, a separate legal entity with no contract of its own with that particular municipality, and no obvious reason on paper to be involved in the file at all.

To a reviewer working from invoices alone, with none of the day-to-day context that made perfect sense to the three owners, this looked like exactly the kind of thing procurement rules exist to catch: a contract awarded to one vendor after a competitive process being quietly performed and billed by a different, unrelated vendor, potentially circumventing whatever selection criteria had chosen Indah's lab in the first place over other bidders. The municipality sent a formal letter requesting a written explanation and, pending one, paused further work under the contract entirely. For a business this size, losing even one steady municipal contract for an extended stretch was a genuine financial problem on its own, and the tone of the letter made unmistakably clear that the municipality was treating this as a compliance concern rather than a minor paperwork oversight to be waved through.

The honest explanation, that three trusted colleagues had shared staff and capacity informally for years without ever updating who technically invoiced what, was entirely true and also exactly the kind of explanation that sounds considerably worse the first time a stranger hears it than the second. Told badly, without supporting records, it sounds uncomfortably close to an admission of exactly what the reviewer suspected. Told with the underlying work properly documented, job by job, it looks like what it actually was: sloppy internal record-keeping between two closely related companies performing work that was, in every single instance, actually delivered by qualified staff to the standard the contract required, with the client never once shortchanged.

The stakes went well beyond the one paused contract sitting in front of the reviewer. If the municipality had concluded there had been a deliberate attempt to route work around a competitive award, it could have affected the company's standing across every other municipal contract it held in the region, and it would have made the eventual combination of the two businesses look, retroactively and unfairly, like it had been part of the original scheme all along rather than a genuine cleanup of something that had simply drifted over the years.

What we did

  1. Paused the combination work to deal with the review first. Structuring the amalgamation properly meant very little if one of the underlying contracts was at real risk of termination in the meantime, so we shifted immediate focus entirely to responding to the municipality before returning to the longer-term restructuring, treating the active review as the more urgent fire that had to be put out first regardless of the original timeline.
  2. Rebuilt a full timeline of which entity actually performed which piece of work. Using job sheets, staff schedules, and site logs rather than invoices alone, since the invoices were exactly what had created the confusion, we reconstructed, contract by contract and month by month, which company's staff and equipment had actually delivered the services billed. In a meaningful number of cases that differed from which company had technically issued the invoice for the job, and pinning down that distinction, case by case, was what let us tell the municipality precisely what had happened rather than offer a vague reassurance.
  3. Separated genuine subcontracting from simple invoicing errors. In most instances, Indah's lab had performed the work under its own contract and Marek and Jacek's company had mistakenly issued the invoice for it, or the reverse, a repeated clerical pattern rather than any deliberate substitution of one vendor for another to dodge a competitive process. We documented each individual instance plainly rather than blending them all into one vague general explanation that would have been harder to verify.
  4. Drafted a written response to the municipality with the supporting evidence attached. Rather than simply asserting there had been no wrongdoing and asking the municipality to take that on faith, we gave its staff the underlying job records so they could verify the explanation independently against their own files, which is generally far more persuasive to a cautious reviewer than a bare assurance with nothing tangible behind it. We organized the package by contract and by month so a reviewer working through it could match each disputed invoice to the record showing who had actually performed that specific piece of work.
  5. Recommended amalgamation over an asset purchase for the eventual combination. An asset purchase would have required formally assigning Indah's municipal contracts to the new entity, triggering fresh consent and possible re-tendering questions with every municipality involved, at exactly the worst possible moment given the active review. An amalgamation, where the two companies combine into one single continuing entity rather than one buying the other's assets, generally carries existing contracts forward without treating them as newly assigned property; licences are a separate question, since the regulator that issued one commonly wants notice before treating it as held by the new company, which mattered enormously here.
  6. Put a corrected invoicing and record-keeping protocol in place immediately. Regardless of how the review itself concluded, the underlying practice needed to stop immediately, so we set out clear, simple rules for which entity invoiced which contract going forward, closing the exact gap that had created the problem in the first place before it could recur on a future file. We put the protocol in writing and had both companies' bookkeeping staff confirm they understood it, rather than leaving it as an informal understanding between the owners the way the original arrangement had been.
  7. Negotiated directly with the municipality's procurement office on next steps. Once the evidence had been reviewed and the timeline accepted, we worked through, in person and in writing, what the municipality actually needed to feel comfortable continuing the relationship, rather than simply submitting the response and waiting passively for a decision to be handed down from someone we had never spoken to. That direct conversation is what ultimately produced a corrective action plan and a shorter renewal term instead of an outright non-renewal, which had been a real possibility earlier in the file.

The outcome

The municipality accepted, once it had reviewed the full timeline and the underlying job records, that the irregularities were the product of informal shared operations between two closely related companies rather than any deliberate attempt to route work around a competitive process. It lifted the pause on the contract and allowed work to resume. It did not, however, let the matter close without conditions attached. As part of resuming the relationship, it required a formal corrective action plan covering exactly how the company would invoice and report work for the next two contract cycles, along with a shorter renewal term than the company would otherwise have received, treating the file as resolved on paper but not entirely forgotten in practice.

The amalgamation itself went ahead once the review had concluded, combining Marek and Jacek's company with Indah's lab into a single continuing entity, structured and papered properly this time rather than left as an informal arrangement. Because the structure chosen was an amalgamation rather than a purchase, the combined company continued the two predecessor businesses rather than acquiring their assets, so every other municipal contract the two businesses held between them carried forward without being assigned, meaning the ordinary consent-to-assignment clauses in those contracts were never triggered, avoiding a repeat of exactly the same problem playing out across every other client relationship the businesses had built over the years. The provincial licence Indah's lab carried was a separate matter: rather than assume it simply came along, we confirmed with the regulator what notice the amalgamation required before it would treat the combined company as the licence holder.

The result was not a clean win, and nobody involved has ever described it that way. The shorter renewal term and the corrective action plan cost the company some standing with that one municipality, standing it had spent years building, and Marek has said plainly that the years of informal sharing were a mistake he wishes the three of them had corrected long before an outside reviewer noticed it for them. What the file did produce was a combined company with its full contract base intact, a documented internal process that simply did not exist before any of this happened, and a relationship with the reviewing municipality that survived the scrutiny, on stricter terms than the company would have preferred but on terms it can genuinely live with going forward.

What you can learn from this

  • Sharing staff, equipment, or invoicing informally between related but legally separate companies can look, to an outsider, like a deliberate attempt to circumvent a competitive process, even when nothing improper was ever intended by anyone involved. Keep the paperwork matching the reality as you go, not only after someone finally asks.
  • When combining two companies that each hold contracts with outside parties, an amalgamation can carry those contracts forward without triggering the consent or re-tendering questions a straightforward purchase of assets would almost certainly raise. Licences are a separate question: check whether the regulator that issued one needs notice, or approval, before it will treat the combined company as the holder.
  • A pattern that looks troubling in a spreadsheet can look very different once the underlying work is properly documented with job sheets and schedules. Organize the evidence carefully before you try to explain yourself, not the other way around.
  • A regulator or contracting party responding to an irregularity usually wants to see a corrected process going forward, not just a credible explanation for what already happened. Bring both to the table, not one.
  • A resolved problem is not always a clean one. Accepting a shorter renewal term or added reporting conditions can be the realistic, honest price of keeping a valuable relationship rather than losing it outright over old habits.
This case study is entirely fictional. It does not describe any real client, file, or matter handled by Treadstone Law, and it is not a real file with details changed. All names, people, properties, businesses, dollar amounts, dates, and events are invented, and any resemblance to a real person, business, or situation is coincidental. Fictional scenarios like this one illustrate the kinds of legal issues people in Ontario commonly face and how a lawyer can help. They are general information, not legal advice — no two matters unfold the same way, and nothing here predicts the outcome of any real case. Reading a case study does not create a lawyer-client relationship. If you are facing something similar, speak with a lawyer about your specific circumstances.

This is a corporate problem we handle

Start a file online — flat, published fees, reviewed by a licensed lawyer before a dollar is owed.

ContactStart a File →