The situation
Roughly nine thousand dollars. That was Pensri's rough estimate of what six weeks without her most senior stylist would cost her small Trenton salon in lost bookings, rebooking chaos, and the overtime she was paying two other stylists to cover the gap. It was not a number she had calculated formally. It was the number she wrote on a sticky note while trying to decide whether to push harder on the sick leave paperwork her longest-serving employee, Chelsea, had submitted, or to let it go and figure out the staffing some other way.
Pensri had incorporated her business four years earlier, after several years renting a single chair inside someone else's salon, and had built it into a shop with four stylists and steady, if modest, revenue. She had written the company's sick leave policy herself, using a template she found online and adjusting the wording without much thought for what the underlying rules actually required. The policy asked any employee out for more than three consecutive days to provide a doctor's note specifying the diagnosis, the expected duration of the condition, and confirmation of any ongoing treatment. It had never been tested until Chelsea, dealing with a health issue she preferred not to detail to her employer, submitted a note that gave only a return-to-work date and a general note that she was unfit for physical work involving standing.
Pensri pushed back, in writing, asking for the fuller detail the policy required. Chelsea's response, forwarded through a family member, was that she was not comfortable disclosing the specific diagnosis and did not believe the salon had a right to ask. The exchange escalated quickly from a scheduling problem into something closer to a dispute, and it landed on Pensri's desk at the worst possible moment: two other stylists were already covering extra shifts, a wedding party booking worth several thousand dollars was on the calendar in three weeks, and Pensri could not simply pause client bookings while she sorted out whether her own policy was even enforceable.
Chelsea's partner Bailey, an auto body technician with no connection to the salon, had reportedly told Chelsea the policy sounded illegal, which was not quite right but was not entirely wrong either. Pensri needed to know, quickly, what she could actually require, what she was risking by pushing further, and how to keep four chairs full while she found out.
The risk we had to size
The immediate financial exposure was modest in absolute terms but meaningful for a business of this size. A human rights complaint alleging that an employer had demanded medical detail beyond what was needed to assess fitness for work, tied to a request that touched on a possible disability, was the realistic worst case, and while damages in a case like that for a small employer tend to run in the low thousands rather than a life-changing figure, the legal costs of defending even a modest complaint, plus the staff time lost to it, could easily exceed the nine thousand dollars Pensri had scribbled on her sticky note.
The policy itself was the core problem. Ontario employment standards entitle employees to job-protected leave for illness and allow an employer to request evidence reasonable in the circumstances, but 'reasonable' has generally been understood to mean confirmation that the employee is unable to work and, where relevant, any restrictions on their return, not the underlying diagnosis. A policy that demands a named diagnosis as a matter of course, rather than only in situations where the specific condition bears on accommodation, sits well past what is defensible, and it creates exposure regardless of whether the employer ever intended to misuse the information.
There was a second layer of risk that had nothing to do with Chelsea specifically. If the policy was overbroad, every employee who had ever submitted a note under it, and every future one, was potentially affected, which meant the exposure was not really about one dispute but about a document sitting in the employee handbook that the whole business was operating under. Fixing it only for Chelsea and leaving the policy as written for the next employee would not close the risk.
The harder judgment call was timing. Pensri could not put client bookings on hold while the policy was rewritten, and pushing Chelsea for more detail mid-review risked making the complaint worse, not better. The risk had to be weighed against the business interruption a slower, more cautious process would cause.
There was also a reputational dimension that was hard to put a number on. Trenton's hairdressing community is small enough that a dispute between a salon owner and a longtime employee tends to travel, among clients and among the stylists Pensri might one day want to hire. That was not a legal risk in the strict sense, but it argued for a written, professional fix rather than a drawn-out back-and-forth that would leave both sides talking about the dispute long after it was settled.
What we did
- Reviewed the existing policy against what Ontario employment standards actually require, confirming that the diagnosis-specific language went well beyond a defensible request for evidence of inability to work, and that the exposure was real rather than theoretical, given Chelsea's note already touched on a possible disability. We walked Pensri through why 'evidence reasonable in the circumstances' is the actual legal bar, not a licence to ask for whatever detail feels useful to a scheduling problem.
- Advised Pensri to pause the written demand for further detail immediately, rather than waiting for a rewritten policy to be finalized, since continuing to press Chelsea under a policy we had already identified as overbroad would have compounded the risk with every further exchange. Every additional letter asking for the diagnosis, sent after we had flagged the problem, would have been harder to explain later as an oversight rather than a choice.
- Drafted a narrower sick leave policy that required only confirmation of inability to work, an expected return date where available, and any specific restrictions relevant to the job, dropping the requirement for a stated diagnosis except in the rare case where an employee sought a workplace accommodation and the condition itself was relevant to what accommodation might look like. Even there, the policy asks for functional limitations, not a diagnosis, wherever a note can supply one instead.
- Worked out a short-term staffing plan with Pensri that did not depend on resolving the dispute first, including a temporary shift-coverage arrangement among the remaining stylists and a plan for bringing in a contract stylist for the wedding party booking, so the business kept operating while the policy and the individual matter were both being sorted out in parallel. Pausing bookings, even briefly, would have cost more than any legal fee and drawn far more client attention to the dispute than either side wanted.
- Prepared a short, plain-language letter to Chelsea confirming that the earlier request for diagnosis detail was being withdrawn, that her original note was sufficient, and that the policy itself was being revised, which addressed the substance of her objection without requiring either side to concede the dispute had been mishandled from the start. Keeping the letter short and factual mattered as much as its content, since a defensive or over-explained version risked reading as an admission Pensri was not prepared to make.
- Reviewed the personnel files of the other three stylists to check whether any diagnosis-level detail had been collected under the old policy, and advised Pensri on securely removing that information from files where it was not needed, since simply having collected it created ongoing exposure even without any current dispute. Two of the three files did contain more than the business needed, a direct result of the same template language, and both were corrected the same week.
- Rolled out the revised policy to the whole team with a short explanation, framed around what the business needed to know to schedule staff safely rather than around the dispute that had prompted the change, so the update did not read as a concession aimed at one employee. We also gave Pensri a short verbal script for the rollout, since a policy update buried in an email tends to go unread until the next dispute forces someone to dig it out.
- Set a reminder for Pensri to review the policy annually alongside her other employment documents, since the underlying problem had been a policy adopted once and never revisited, and periodic review was the cheapest way to catch the next gap before it became a live dispute. We also flagged that any future template she borrows should be checked against Ontario requirements before adoption, not after it is tested by a real absence.
The outcome
Chelsea returned to work on the date in her original note, roughly five weeks after the exchange began, without ever providing the additional diagnosis detail Pensri had first requested. The relationship was strained through the process, and Pensri accepted, on our advice, that a full and comfortable resolution was unlikely given how the initial request had landed. That is the partial part of the outcome: the policy was fixed and the immediate dispute was defused, but the working relationship between Pensri and Chelsea did not fully recover to where it had been before, and Chelsea left the salon roughly eight months later for reasons that were only partly related to the incident.
The revised policy remained in place for the rest of the team, and no further disputes arose from it in the time since. The temporary staffing arrangement covered the wedding booking without disruption to the client, at a cost Pensri estimated at closer to four thousand dollars once the contract stylist's fee was included, well under her original worst-case estimate.
Pensri's biggest change was less about the document than about her own habits. She stopped using the online template she had started with for other parts of the employee handbook as well, after realizing the sick leave language was not the only section written for a jurisdiction and a business size that did not match her own. She now has the policy reviewed periodically rather than treating it as something written once and left alone.
Looking back, Pensri was candid that her first instinct, to push for the fuller detail her old policy technically allowed, would have been the wrong move even if it had felt justified at the time. The nine thousand dollars she had feared losing to a staffing gap never fully materialized, but the cost of the dispute, in strained trust and in the time spent untangling a policy she had barely read when she adopted it, was a reminder that the paperwork sitting quietly in a handbook can matter as much as the client-facing side of the business.
What you can learn from this
- A sick leave policy that asks for a specific diagnosis, rather than confirmation of inability to work, usually asks for more than the law requires and creates risk even before anyone objects to it.
- A policy that is wrong for one employee is wrong for everyone under it. Fixing a single dispute without revising the underlying document leaves the exposure open for the next person.
- When a dispute is live, pushing forward under a policy you already suspect is flawed tends to make things worse, even if pausing feels like giving ground.
- A business does not have to choose between fixing a legal problem and keeping the doors open. A short-term operational plan can run alongside the legal fix rather than waiting for it.
- Template policies pulled from generic sources are often written for a different jurisdiction or a different size of business. What looks like a shortcut can quietly become the source of the next dispute.
This is a corporate problem we handle
Start a file online — flat, published fees, reviewed by a licensed lawyer before a dollar is owed.