Building a Complaint Channel Before the Next Person Speaks Up

The situation

'What was I actually supposed to do about it?' That was the question Senthil brought to our first meeting, and it stayed the question through every meeting that followed. He had spent four years working as a gas station attendant in Collingwood while building a small appliance and small-engine repair business on evenings and weekends. What started as a handful of calls a month had grown into a company doing close to $100,000 a year, with two part-time technicians on the payroll and his cousin Anusha handling the books a few hours a week.

He had incorporated the business about eighteen months before we met him, mostly because a parts supplier asked for a corporate account and it seemed like the responsible thing to do. He named himself the sole director and never got around to much else. There was no employee handbook, no written policies, and no one but Senthil to bring a problem to. For a two-person operation running out of a rented bay, that had been good enough. It stopped being good enough the week one of his technicians, Yasmin, told him a supplier's delivery driver had been making comments to her that made her uncomfortable, twice a week, every time he dropped off parts.

Senthil told her he would deal with it. He meant it, and he did raise it, mentioning it to the supplier's office the next time he called in an order. Nothing changed. The driver kept coming. Yasmin raised the issue again about a month later, more pointed this time, asking what had actually been done about what she had told him. Senthil could not answer with any confidence, because there was nothing to point to - no note, no email, no record that the first conversation had ever happened, only his memory of a phone call he had made in passing.

Yasmin told him she was thinking about calling the Ministry of Labour to report that her employer had heard a harassment complaint and done nothing with it. That was the moment Senthil understood that the company he had built quietly around his own judgment had no way of proving it had exercised any judgment at all. He came to us not because he had been sued or even formally accused of anything, but because he needed to know, in plain terms, what a business his size actually owed a person who raised a concern - and how to show that it had been met, if it ever came to that.

What was actually at stake

What was actually at stake was bigger than a single supplier relationship, and bigger than one uncomfortable conversation about a delivery driver. A small corporation like Senthil's owes the people who work for it protection from reprisal, but that protection is not a blanket duty covering every workplace grievance - it attaches to specific protected activity: raising a health and safety matter, asserting an employment standards right, or making a harassment or human rights complaint. Within those areas, the protection exists whether or not the company has an HR department, a policy manual, or even more than one employee besides the owner. The size of the business does not change the obligation, only how formally it tends to get documented, and Senthil's company had documented nothing at all.

The immediate risk was a complaint to the Ministry of Labour, which could have opened an investigation into how the workplace had handled harassment raised by an employee. But the harder problem sat underneath that one. If Yasmin felt she had to escalate outside the company because nothing changed inside it, a regulator would be looking not just at what happened with the driver, but at whether Senthil's response - or lack of one - amounted to treating her worse for having spoken up in the first place. That is what a reprisal claim actually is: not the original complaint, but what happens to the person after they make it. Once Yasmin had raised the same concern twice and could point to no visible change, the company was exposed on exactly that ground.

There was also a quieter risk that mattered just as much to Senthil once he understood it. His company was growing, and growing companies eventually need to prove to a bank, a bigger supplier, or a future employee that they operate like a real business and not just a name on an incorporation certificate. A company with no way to receive, record, or resolve a complaint cannot show that its director exercised the kind of diligence directors are expected to exercise. That gap does not show up until someone tests it - a lender doing due diligence, an insurer asking about workplace policies, or, as happened here, an employee who simply wanted her concern taken seriously and kept notes of when she raised it and what happened next.

Anusha, doing the books, had unknowingly kept the only contemporaneous record that existed: a handful of dated invoice notes and a text exchange about scheduling changes around the weeks in question. That fragment mattered more than either of them realized at the time, because it was the closest thing to a paper trail the company had.

None of this meant Senthil had acted in bad faith. Small founders juggling a day job, a side business, and a growing crew rarely think about reporting channels until a complaint forces the question. What mattered from here was whether the company could still build the structure it should have had from the start, before the ministry called, before Yasmin decided the company was not listening, and while there was still a chance to show good faith through what happened next rather than argue about what should have happened before.

What we did

1. Reconstructed the timeline first, before drafting anything. Because Senthil had never written down the original conversation with Yasmin or his call to the supplier, we could not simply summarize the file - there was no file. We interviewed Senthil and Yasmin separately, pulled Anusha's dated invoice notes and the scheduling text thread, and cross-checked delivery dates against the supplier's own invoices to establish, as closely as the evidence allowed, when each conversation actually happened and what was said.
2. Documented the reconstructed record in a memo Senthil could stand behind. Rather than presenting guesswork as fact, we built a dated account that distinguished what was confirmed by two sources from what relied on memory alone. This mattered because if the company was ever asked to show what it had done, a careful and honest reconstruction carries more weight than a tidy story with no support behind it.
3. Advised Senthil to speak with Yasmin directly and acknowledge the gap. We recommended he tell her plainly that her concern had been raised, that his response had not been adequate, and that he was putting a real process in place - rather than letting her conclude on her own that nothing had changed. Acknowledging a shortfall honestly reduces the chance that a person feels ignored enough to escalate further.
4. Escalated the supplier issue formally, in writing this time. We drafted a letter to the supplier's management describing the conduct reported and requesting that the driver be reassigned from that delivery route, with a clear request for written confirmation once it was done. A documented request that produces a documented response is worth far more, if the matter is ever reviewed, than a verbal ask that goes nowhere.
5. Built a short, plain-language complaint policy sized to the company. We did not hand Senthil a large corporate policy manual he would never use. We wrote one page describing how to raise a concern, who receives it, what happens next, and the company's commitment not to penalize anyone for raising one in good faith - something he could actually hand to two employees and follow himself.
6. Set up a simple written intake so the next complaint would not disappear. A single shared document, dated entries, one line per concern and one line per response, gave the company something it had never had: a running record that did not depend on anyone's memory of a phone call weeks later. We showed Anusha how to maintain it alongside the bookkeeping she already did, so the habit would outlast the immediate problem rather than fading once the pressure passed.
7. Confirmed the supplier's response and closed the loop with Yasmin in writing. Once the driver was reassigned, we helped Senthil send Yasmin a short written summary of what had happened and what had changed, giving her something concrete rather than a verbal assurance, and giving the company a dated record that the concern had actually been resolved, which is the kind of record a regulator or a future employee would eventually want to see.

The outcome

Yasmin did not file a complaint with the Ministry of Labour. Once the supplier confirmed in writing that the driver had been reassigned, and once Senthil put the resolution to her in writing rather than as a verbal aside, she told him directly that she felt heard, which was the outcome that actually mattered more than avoiding a regulatory filing. The written record we built to reconstruct the past ended up doubling as proof that the present had been handled properly.

The complaint policy stayed in place well after the immediate issue closed. Six months later, when Senthil hired a third technician, he had something to hand the new employee on day one instead of explaining the company's approach to complaints from memory, the same gap that had caused the original problem. Anusha kept the intake log running as part of her regular bookkeeping hours, and by the time we checked back in, it held three entries - two scheduling disputes and one supplier billing question - each closed within a week and each with a written note showing how.

The cost to Senthil was mostly time: the reconstruction work, the letter to the supplier, and the afternoon spent building a one-page policy that fit a two-person crew rather than a large company. He did not need to restructure the business or bring in outside management to fix what had gone wrong. What he needed was a place for a concern to land that was not just his own memory, and a habit of writing down what happened once it did. That is what the file left him with, and it is the piece that carried forward once the original complaint was long resolved.

There was no finding against the company, no ministry file, and no reprisal claim, because the process that should have existed from the start finally did, even if it arrived a few weeks late. Senthil still talks about the file as the moment the business stopped being something he ran out of his head and started being something with a record he could point to. That distinction, more than any single fix, is what protected him the next time a concern came in.

What you can learn from this