ESST Guidance for Cannabis Business Attendance Policies
Table of Contents
- What is ESST
- The Part Most Operators Miss: Discipline
- Where Attendance Policies Break Down Under ESST
- The “No-Fault” Attendance Policy Problem
- What a Compliant Policy Actually Looks Like
- Documentation: Your Best Protection
- FAQ
Minnesota ESST: Attendance and Discipline Policies
Most Minnesota cannabis operators learned about Earned Sick and Safe Time (ESST) as a leave law. Employees accrue paid sick time. They can use it for illness or certain safety situations, and you have to let them. That part is fairly well understood at this point.
What is less understood is how ESST affects your attendance and discipline policies, even on days when no one calls in sick. That is where we see Minnesota cannabis businesses create real legal exposure, often without realizing it until a complaint surfaces.
This article walks through the specific ways ESST affects discipline and attendance management, where operators typically get tripped up, and what a compliant policy structure actually looks like.
What ESST Is (Quick Recap)
Minnesota’s Earned Sick and Safe Time law took effect January 1, 2024. It requires employers to provide eligible employees with at least one hour of paid leave for every 30 hours worked, up to 48 hours per year. Employees can carry over up to 80 hours.
ESST can be used for the employee’s own illness or medical care, care for a family member, and situations related to domestic abuse, harassment, or stalking, among other qualifying reasons.
That is the leave side of the law, but ESST gets more operationally complicated.
The Part Most Operators Miss: Discipline
Minnesota’s ESST statute includes explicit anti-retaliation protections. An employer cannot discipline, discharge, threaten, or otherwise penalize an employee for using ESST, requesting ESST, or even asking questions about their rights under the law.
That language sounds straightforward. In practice, it creates friction with the way most small dispensaries and operations run attendance management.
Here is a scenario we see regularly. An employee calls out on a Friday afternoon, the third time in six weeks. The manager, frustrated, issues a verbal warning and documents it as an attendance occurrence. The employee had a legitimate qualifying reason for each absence and used accrued ESST time every time. That written warning may constitute unlawful retaliation, even if it was issued without any intent to punish the employee for using sick time.
The problem is not bad intent. It’s a policy that doesn’t distinguish between protected absences and unprotected ones.
Where Attendance Policies Break Down Under ESST
The most common structural problem is the point-based or occurrence-based attendance policy. These are widely used in retail and hourly environments because they are easy to administer. An employee accumulates points for each absence or tardy, and enough points trigger progressive discipline.
Occurrence-based systems are not automatically illegal under ESST. But they become illegal the moment they apply to ESST-covered absences without carving them out. If your policy counts every unplanned absence as an occurrence, and an employee uses ESST for three of those absences, you have just assigned three disciplinary occurrences for legally protected activity.
That is the core of the problem. The policy is not malicious. It just wasn’t designed with ESST in mind.
Other common breakdowns include:
- Policies that require advance notice for absences without accommodating the unforeseeable nature of illness. Minnesota’s ESST law allows employers to set reasonable notice requirements, but only to the extent practicable when the need is unforeseeable.
- Attendance incentive programs that reward perfect attendance, effectively penalizing employees who use ESST by excluding them from bonuses or recognition.
- Policies that require a doctor’s note for any absence of one day or more. ESST limits when documentation can be required. Generally, it is permitted only after three or more consecutive days of absence.
The “No-Fault” Attendance Policy Problem
No-fault attendance policies are common in dispensaries because the environments often run lean. You need coverage, you value reliability, and you want a clear, consistent standard that treats everyone the same.
The intent is fair. The execution, under ESST, requires careful design.
A no-fault system that counts all absences equally, regardless of reason, will inadvertently discipline employees for using protected leave. Minnesota law does not require that you excuse unlimited absences. It does require that ESST-qualifying absences be distinguished from non-qualifying ones and treated accordingly.
In practice, this means your no-fault policy needs an explicit carve-out for ESST and any other protected leave. An absence covered by ESST should not generate an occurrence. An absence that is not covered, say, a no-call no-show with no stated reason and no ESST use, can still be addressed through your normal process.
The distinction sounds simple. Building it correctly into written policy language and then applying it consistently is where most operators struggle.
What a Compliant Policy Actually Looks Like
A compliant attendance and discipline policy under Minnesota ESST generally includes these elements.
First, a clear statement that absences covered by ESST will not count as occurrences or be used as the basis for discipline. This should appear in your employee handbook, under both the attendance policy and the ESST policy, so the connection is explicit.
Second, a defined notice procedure that accounts for unforeseeable absences. You can require employees to notify you as soon as reasonably possible, but your policy should not require advance notice for sudden illness or emergency situations.
Third, a documentation standard that aligns with ESST rules. You can ask for documentation after three or more consecutive missed days. You generally can’t require it for a single-day absence covered by ESST.
Fourth, an attendance incentive structure, if you have one, that doesn’t penalize ESST use. If you offer bonuses or recognition for perfect attendance, consider whether that program creates indirect pressure on employees not to use protected leave.
Fifth, a consistent application standard. If your policy carves out ESST absences but managers are still issuing verbal warnings for those absences in practice, the written policy does not protect you. Consistency between the written policy and day-to-day management decisions is what actually limits your exposure.
Documentation: Your Best Protection
When a discipline or termination decision gets challenged, the question is almost always whether the employer can show that the action was based on unprotected conduct and applied consistently. Documentation is how you demonstrate that.
For every disciplinary action related to attendance, document the specific absences or incidents that are the basis for the action, note which absences were ESST-covered and confirm they were excluded, and make clear what policy provision the employee violated.
For terminations, the record should show a pattern of non-ESST absences or conduct issues, and that the ESST-covered absences were not factored in.
This documentation discipline doesn’t need to be complicated. It needs to be consistent. A standardized form that prompts managers to identify the basis for each action, and to distinguish protected from unprotected absences, handles most of this automatically.
If you are building that documentation process from scratch, our Performance Management and Termination Documentation Toolkit is designed to create exactly that kind of consistent, defensible record. It is not Minnesota-specific, but the structure applies directly to the documentation discipline ESST requires. We will keep watch to see if Minnesota regulations change to require specific documentation templates.
For the policy side, our Minnesota Cannabis Employee Handbook template includes ESST-compliant leave and attendance policies that are already built with these carve-outs in place. Many operators use a pre-built template to avoid the risks that come from drafting these policies without a compliance background. If you’d rather not work through the statutory language yourself, this is a practical starting point.
FAQ
Can I still discipline employees for excessive absences if they used ESST?
You can address absences that are not covered by ESST through your normal process. What you can’t do is count ESST-covered absences as part of the disciplinary basis. If an employee has ten absences in a quarter and six of them were ESST-qualifying, your discipline should be based only on the four that weren’t covered.
Does ESST apply to part-time and seasonal employees in cannabis?
Generally yes. Minnesota’s ESST law applies to employees who work at least 80 hours in a year for the same employer. Many part-time and seasonal cannabis employees meet that threshold. Check the current Minnesota Department of Labor and Industry guidance for any updated thresholds.
What counts as retaliation under ESST?
Discipline, termination, demotion, schedule reduction, and threats are all covered. More subtly, excluding an employee from an attendance bonus because they used ESST, or subjecting them to increased scrutiny after a leave request, can also constitute retaliation. The standard is whether a reasonable employee would be discouraged from using their rights.
Are we required to have a written ESST policy?
Minnesota requires employers to notify employees of their ESST rights. A written policy included in your employee handbook is the most straightforward way to meet that requirement and to document that notice was given. Verbal communication alone is difficult to prove and leaves you exposed if a dispute arises.
Can our attendance policy still require call-ins before a shift?
Yes, with limits. You can require employees to notify you as soon as practicable before a scheduled shift if the absence is foreseeable. For unforeseeable illness or an emergency, the requirement has to flex. A policy that requires two hours advance notice for all absences without exception is probably too rigid to hold up under ESST.
