A budtender clocks in for a Saturday closing shift smelling like the parking lot behind the building. The assistant manager sends her home. The store manager fires her Monday morning, citing the shop's zero-tolerance policy — the one every new hire hears about at orientation, the one that comes up in every staff meeting, the one that has never once been written down anywhere an employee signed.

Two months later, a demand letter arrives from an employment lawyer.

Not because firing someone for showing up impaired is illegal. Minnesota is explicit that it isn't. Because the store never had a policy. It had a habit, and Minnesota's cannabis-testing statute treats those as two very different things.

Start with the good news, because operators rarely hear it stated this plainly. Minn. Stat. 181.952, subd. 3, para. (a) says an employer "is not required to permit or accommodate" cannabis flower, cannabis product, lower-potency hemp edible, or hemp-derived consumer product use, possession, impairment, sale, or transfer "while an employee is working or while an employee is on the employer's premises or operating the employer's vehicle, machinery, or equipment." That default exists on its own. You don't need a policy, a lawyer, or a filing to have the right to keep your shift and your premises clean.

That's a different question from the one this newsletter covered in "Off the Clock in a Minnesota Cannabis Job" — Minn. Stat. 181.938 protects what an employee does off duty and off premises. Subdivision 3(a) is the mirror image, aimed at on-shift and on-premises conduct, and the two statutes don't compete. Both can be true at once: you can't touch what an employee does on their own time, and you don't have to tolerate it on yours.

Here's the sentence that actually does the work in this statute, and it sits one paragraph below the one everyone quotes. Subd. 3, para. (b): "An employer may only enact and enforce written work rules prohibiting" the same conduct listed above "in a written policy that contains the minimum information required by this section."

Read that again slowly, because the two paragraphs of subdivision 3 are doing different jobs. Paragraph (a) tells you what you're allowed to prohibit. Paragraph (b) tells you the only way you're allowed to actually enforce a written rule prohibiting it — and the only way is a compliant written policy. Not a handbook sentence. Not something said out loud at onboarding and left there. A policy, in writing, that hits every item on a specific six-part list.

This is a restriction on the employer's power, not a grant of it. A "may only" clause narrows what's legally available; it doesn't describe a ceiling you're free to build past with something less formal.

Student feedback

Subdivision 1 lists exactly six things a compliant policy has to contain, and it's worth naming all six, because a policy that covers four of them isn't a compliant policy — it's four-sixths of one.

Who's covered. The policy has to name which employees or job applicants are actually subject to testing under it. A rule that applies to "the team" without saying who that means doesn't meet the bar.

When testing can happen. The circumstances under which drug, alcohol, or cannabis testing may be requested or required — random, reasonable suspicion, post-incident, whatever your program actually uses — have to be spelled out, not left to a manager's judgment in the moment.

The right to refuse, and what refusing costs. An employee or applicant has to be told, in the policy itself, that they can refuse testing, and exactly what happens if they do.

What discipline follows a confirmed positive. Any adverse action tied to a confirmatory test that verifies an initial positive result has to be named in advance — not decided after the fact.

The right to a second look. Employees and applicants have to be told they can explain a positive confirmatory result, or request and pay for a confirmatory retest.

How to appeal. Any other appeal procedure available to a tested employee or applicant has to be in the document.

Notice what that list actually describes: it's the anatomy of a testing program, not a one-line conduct rule. That looks like a trap for an employer who never runs a single test but wants a written rule they can point to when firing someone for showing up impaired — on one reading, subdivision 3(b) offers no lighter-weight path for a no-test, conduct-only rule, so that employer would still have to write a policy shaped like a testing program to satisfy subdivision 1. We want to flag right away that this reading is ours, not a settled one — the section below on what we're not sure about explains why, and it matters for a lot of small operators who don't test at all.

Subdivision 2 adds a second layer most small operators miss entirely, because it isn't only about writing the policy — it's about proving you handed it out. An employer has to give written notice of the policy to every affected employee when it's adopted, to any previously unaffected employee the moment they transfer into a covered position, and to a job applicant at hire and before any testing, if the offer is contingent on passing it.

Then there's a requirement that has nothing to do with paperwork in a drawer: the employer has to post notice in an appropriate and conspicuous location on the premises stating that a drug, alcohol, and cannabis testing policy exists and that copies are available for inspection during business hours. That's a physical sign, not a metaphor for one. A compliant policy sitting in a shared drive that nobody has posted or handed out in writing is not a policy this statute recognizes as validly enacted, whatever it says on the page.

Here's the reversal, and it's the reason this gap is worth an operator's attention even though it sounds like a paperwork technicality. When this newsletter covered off-duty rights, the operative remedy statute was 181.938, subd. 4 — damages capped at lost wages and benefits, a civil action as the sole remedy, two-way mandatory fee-shifting that can cut against either side.

A violation of 181.952 runs through a different door entirely. Minn. Stat. 181.956 governs remedies for a violation of "sections 181.950 to 181.954" — and 181.952 sits inside that range. That statute is not capped the same way. Subdivision 2 makes an employer who violates 181.950 through 181.954 liable "for any damages allowable at law," a broader measure than a wage-and-benefits ceiling, with attorney fees available to the employee — one-way, not two-way — if the court finds the employer acted knowingly or recklessly. Subdivision 4 lets a court order the equitable remedy operators fear most: reinstatement with back pay. Subdivision 5 bars retaliating against an employee for asserting these rights at all. And subdivision 3 gives standing to sue for injunctive relief not just to the employee or job applicant, but to a state, county, or city attorney, or a collective bargaining agent representing the affected class — which means the exposure isn't only as large as one worker's willingness to bring a claim, and it isn't limited to people who already got the job.

Put plainly: an employer who is completely within their rights under subdivision 3(a) — no duty to tolerate on-shift impairment, full stop — can still lose a wrongful-termination fight, not on the merits of the firing, but because the "work rule" behind it was never validly enacted under subdivision 3(b). The right was real. The enforcement of it wasn't, because the paperwork wasn't.

We want to be honest about where our own reading gets uncertain, rather than hand you a confident answer we can't back up. Subdivision 1's six required contents are written in the vocabulary of an active testing program — confirmatory tests, retests, screening results. A cannabis retailer that has never administered a single drug or cannabis test to anyone, and wants a written no-impairment-on-shift rule purely as a conduct standard, is being asked by subdivision 3(b) to write a policy shaped like a testing program it doesn't run.

We did not find case law, agency guidance, or practitioner commentary directly addressing whether a non-testing employer can satisfy subdivision 1 with a conduct-only policy, or whether subdivision 3(b) effectively requires adopting a full testing framework to get a written rule at all. One employment-law firm's public guidance on this area (Avisen Legal, cited below) confirms the general written-policy requirement exists but doesn't reach this specific question. Treat this as an open reading, not a settled one — and treat it as a reason to have actual employment counsel draft your policy rather than adapt a template, since the six-part list has to fit whatever your business actually does.

Individual gifts fund what program grants cannot: student access, the free statewide job board, and new program development. Give any time.

Drafting a compliant policy is not a certification-course investment measured in hundreds or thousands of dollars and thirty hours of coursework, the way the medical cannabis consultant certificate this newsletter covered in "The Second Lock" is. It's a document: six required elements, a notice process, a posted sign. For most operators, that's a modest, one-time cost in employment-counsel time against the alternative — a reinstatement-with-back-pay order, uncapped damages, and legal fees if a court finds the violation knowing or reckless.

But be precise about what the paperwork actually buys you, because overstating it is its own risk. A compliant subdivision 1 policy, properly noticed and posted, satisfies subdivision 3(b)'s gate for enforcing an on-shift, on-premises conduct rule. It does not touch 181.938's separate protection for off-duty, off-premises use — no policy, however well-written, lets you discipline someone for what they did on their own weekend. And it doesn't immunize a testing program that is itself run incorrectly — the wrong retest window, an appeal procedure that exists on paper but isn't actually honored, are their own violations regardless of how clean the policy document looks. Fix the paperwork gap this piece describes, and you've closed one door to liability, not all of them.

None of this is an argument against having a real, enforced no-impairment standard for your shift. It's an argument that the standard doesn't exist, in the way Minnesota law recognizes, until it's written down the way subdivision 1 requires, handed out the way subdivision 2 requires, and posted where subdivision 2 says it has to be posted.

Before your next disciplinary conversation about on-the-job cannabis use, don't check your memory of what was said at orientation. Check the document — the actual one, with all six items in it, that somebody signed for or that's posted on your wall right now. If you can't point to it, you don't have a policy. You have a habit, and a habit doesn't hold up when somebody asks you to prove it existed before the day you needed it.

And once you can point to it, remember what it does and doesn't cover. It's your ticket to enforce an on-shift, on-premises rule — nothing here changes what an employee does off the clock and off your property, and nothing here protects a testing program that's run sloppily even with a clean policy on the wall. If you don't test anyone at all and just want a written no-impairment rule, that's the specific case we found no settled answer for above — talk to employment counsel before you assume a conduct-only policy satisfies subdivision 1 on its own.

Minn. Stat. 181.952 (subdivisions 1, 2, and 3) and Minn. Stat. 181.956 (subdivisions 1 through 5) were fetched verbatim from the Revisor's office and quoted directly, with quotation marks preserved around every operative phrase. Minn. Stat. 181.955 was fetched to confirm it addresses only collective bargaining and professional-athlete carve-outs, not a general enforcement mechanism for 181.952. The 181.938 figures and framing referenced here (the wage-and-benefit damages cap, two-way fee-shifting) are reused from this newsletter's Sep 6 "Off the Clock" piece, already independently verified that run.

We did not assert that any Minnesota court or DLI enforcement action has actually applied subdivision 3(b)'s written-policy requirement against an employer. We searched for case law and practitioner commentary directly on point and found none — only general guidance confirming the written-policy requirement exists, not a test of what happens when it's missing. The exposure described here is what the statute's remedy structure makes available, not a confirmed litigation pattern.

We did not say whether a non-testing employer can satisfy subdivision 1 with a conduct-only policy. That reading is stated above as genuinely open, because it is — subdivision 1's six elements are written for an active testing program, and we found nothing resolving how they apply to an employer who never tests.

We did not invent a dollar figure for what a compliant policy costs to draft. Unlike the certified-consultant piece, where a specific training provider's price was directly sourced, no comparable public pricing exists for employment-counsel policy drafting, so we described the cost qualitatively rather than print a number we can't stand behind.

Say hello anytime: [email protected].

Minnesota Cannabis College is a Twin Cities-based 501(c)(3) nonprofit. Donations are tax-deductible as allowed by law. EIN 86-2319307.

Discover your next career in cannabis.

Keep showing up, keep cheering each other on — and as always, our mission is education as repair! 👨‍🎓

The MNCC Team

P.S.

New here? Check our Website and get matched with an MNCC program that is right for you!