Why do write-ups I know are justified still get thrown out in arbitration?

An arbitrator usually voids a write-up not because the behavior didn't happen, but because the documentation can't answer three questions: when exactly it happened, who else saw it, and whether the response was proportionate to prior history. Roughly 40% of contested write-ups get voided or modified on review, and most of those are documentation failures rather than bad-faith arguments. Tightening the documentation captures the majority of that risk.

What has to be in a write-up for it to hold up under labor-law review?

There are 8 elements: date and time in store-local timezone, the specific behavior named (not 'attitude'), a witness or camera-plus-timestamp reference, prior incidents cited by date and write-up id (or a note that there is no prior), the rule violated by section, the employee's response, the manager's corrective action, and both signatures or a witnessed-and-timestamped refusal to sign. Every write-up should get a yes/no on each element before it is filed, and missing any one is grounds to fix it first. Refusal to sign does not void the write-up as long as the refusal is witnessed and timestamped.

When can I skip straight to termination instead of going through the warning steps?

Most operators run a 4-step ladder (verbal, written, final, termination), and skipping steps is the second-most-common reason write-ups get voided. Terminating offenses such as sale to a minor, theft, or violence can skip steps 1 through 3, but they require irrefutable documentation: video timestamp, witness, and audit-log entry, all three. A vague 'I think they sold to a minor' is not enough; a specific record naming the camera footage, transaction id, and manager-on-duty witness is.

← All guides

People-ops deep-dive

Manager write-ups that survive labor-law review

Cannabis retail has high turnover. That means cannabis retail also has high write-up volume — and a write-up that doesn't survive an arbitrator's review costs the operator a separation that should have been cleaner. Here's what a defensible write-up actually looks like, structured so the manager filling the form can't accidentally weaken it.

By CannAgentMay 6, 20268 min read

Why most write-ups get voided

An arbitrator throws out a write-up not because the underlying behavior didn't happen — but because the documentation can't answer one of three questions: WHEN exactly did this happen, WHO else saw it, and WAS the response proportionate to the prior history. If any of those three has gaps, the arbitrator strikes the write-up and the operator carries the cost.

The 8 elements every defensible write-up has

Print this list. Every write-up gets a yes/no on each element BEFORE it gets filed. Missing any one is grounds to fix the write-up before it goes in a personnel file.

Date and time, store-local timezone. Not 'last week' — the actual ISO date + time. If the incident bridges a shift change, name both shifts.
Specific behavior named. Not 'attitude' or 'unprofessional.' The actual action: 'failed to verify ID for a customer who appeared under 30 at 4:42pm', 'left the till drawer open while assisting a second customer at 2:17pm.'
Witness or video reference. Name the witness OR the camera + timestamp. Both is better than either. 'No one else was on shift' is a documentation gap — write that explicitly so it's not interpreted as withholding.
Prior incidents (if any) referenced by date + write-up id. A second-step write-up that doesn't cite the first-step is missing the proportionate-response anchor. If there's no prior, write 'No prior write-up on this issue.' Make the absence intentional.
Rule violated, by section. WAC 314-55-079 retailer privileges? Internal SOP §3.2 on cash handling? Cite it. 'Against company policy' isn't a citation.
Employee response. What the employee said when confronted. Verbatim if possible. If they refused to comment, write that.
Manager response / corrective action. The action being taken right now. 'Verbal warning' / 'Written warning, second step' / 'Final warning' / 'Termination effective 2026-05-06.' Plus what's expected to change.
Both signatures + the refusal-to-sign clause. Manager signs always. Employee signs OR the form notes 'employee declined to sign at 4:55pm with witness X present.' Refusal to sign doesn't void the write-up — but the refusal must be witnessed and timestamped.

The proportionate-response ladder

Most operators run a 4-step ladder. The ladder is not negotiable on a per-employee basis — that's how you end up in a wrongful-termination case. The ladder is consistent; the time-window between steps is what scales with severity.

Step	When used	What it does
1. Verbal warning	First-time minor (running 1 min late, single-shift sloppiness)	Documented in audit log; no signed form yet
2. Written warning	Second occurrence within 90 days, OR first-time medium (cash variance >$10, missed required training)	Signed form, prior verbal cited
3. Final warning	Third occurrence, OR first-time major (failed compliance gate, gross misconduct that doesn't warrant immediate termination)	Signed form, both prior cited, defines termination trigger
4. Termination	Fourth occurrence, OR first-time terminating offense (sale to minor, theft, violence)	Signed form OR refusal-witnessed; termination paperwork separate

The trick: terminating offenses can skip steps 1-3, but they require IRREFUTABLE documentation — video timestamp, witness, audit log entry, all three. A 'I think they sold to a minor' is not enough; 'Camera footage at 8:42pm shows the budtender accepting an obviously-fake ID without scanning it; transaction id 47291 confirms the sale; manager-on-duty witnessed the interaction at 8:43pm' is.

Phrases that get write-ups thrown out

Some phrases consistently lose in arbitration. Train every manager to recognize and rewrite them.

'Attitude problem' / 'unprofessional behavior' / 'bad attitude.' These are conclusions, not behaviors. Replace with: the actual action + the actual words.
'Always' / 'never' / 'constantly.' Absolutes lose to a single counter-example. Replace with: 'three times in the past 30 days, on these dates: …'
'Made customers uncomfortable.' The arbitrator asks 'which customers, and how do you know they were uncomfortable.' If you can't name the customers and the specific moment, this fails.
'Not a culture fit.' Federally and in most state employment law, 'culture fit' is a documented losing argument. Replace with: a specific behavior + the rule it violates.
'Repeated issues we've discussed many times.' If they've been discussed, where's the prior write-up referencing them? Either it's documented (cite it) or it's not (admit it and start the ladder cleanly).

Cannabis-specific risks

WSLCB-related write-ups carry extra weight. WAC 314-55-110 (“licensee responsibilities”) is the section: licensees are “responsible for the operation of their licensed business in compliance with the cannabis laws and rules of the board”, and “licensees AND THEIR EMPLOYEES must conduct the business” in compliance with the listed laws. -110(2) routes penalties to WAC 314-55-509 through 314-55-525, which “outline aggravating and mitigating circumstances that may affect what penalty is applied if a licensee or employee does not comply” — so a documented compliance failure is an input to the penalty, not just a fact about the employee. WAC 314-55-035 (qualifying for a license, true parties of interest) and 314-55-079 (retailer licence privileges) bear on who may hold the licence and what the retailer may do. A write-up that captures a compliance failure (sale-to-minor attempt, surveillance gap, etc.) becomes part of the operator's compliance file — and an arbitrator throwing out the write-up doesn't undo the WSLCB exposure.

Sale-to-minor incidents require: video timestamp, ID-check log entry, surveillance retention proof, manager-on-duty signature, and the WSLCB incident report number if filed
On-property consumption requires: camera footage, witness, customer ID if known, escalation timeline showing security response within 5 minutes
Cash variance triggering a write-up requires: the till audit row from the close, the manager-on-duty review notes, the bookkeeper escalation timestamp
Surveillance gap (camera offline, footage not retained per WAC 314-55-083): immediate vendor escalation log, CEO/CO notification timestamp, remediation ETA

Build it into the form, not the manager's head

The single highest-leverage change you can make: stop relying on managers to remember the 8 elements. Build them into the write-up form itself — required fields, prefilled timestamps, video-clip linkage, prior-write-ups dropdown. The manager fills the form; the form enforces the structure.

Required fields, not 'recommended' fields. The form rejects submission if any of the 8 elements is empty
Camera-bridge integration so the timestamp picker auto-pulls the matching footage segment
Prior-write-ups dropdown auto-populated from this employee's history; required to either select one or write 'no prior'
Proportionate-response calculator: the form suggests step 1/2/3/4 based on severity + history, manager can override but the override creates an audit row
Risk-flag check: a draft is flagged for review by an admin before file if it contains any strike-list phrase or skips ladder steps

Takeaways

40% of contested write-ups get voided or modified — most are documentation failures, not bad-faith arguments
The 8 elements: timestamp / specific behavior / witness or video / prior incidents / rule cited / employee response / corrective action / signatures (or witnessed refusal)
Proportionate-response ladder is 4 steps (verbal → written → final → termination); skipping steps is the second-most-common void reason
Strike-list phrases lose in arbitration: 'attitude problem' / absolutes ('always' 'never') / 'culture fit' / 'made customers uncomfortable' without named customers
Build the 8 elements into the form, not the manager's head. Required fields beat recommended fields.

Frequently asked

Why do write-ups I know are justified still get thrown out in arbitration?: An arbitrator usually voids a write-up not because the behavior didn't happen, but because the documentation can't answer three questions: when exactly it happened, who else saw it, and whether the response was proportionate to prior history. Roughly 40% of contested write-ups get voided or modified on review, and most of those are documentation failures rather than bad-faith arguments. Tightening the documentation captures the majority of that risk.
What has to be in a write-up for it to hold up under labor-law review?: There are 8 elements: date and time in store-local timezone, the specific behavior named (not 'attitude'), a witness or camera-plus-timestamp reference, prior incidents cited by date and write-up id (or a note that there is no prior), the rule violated by section, the employee's response, the manager's corrective action, and both signatures or a witnessed-and-timestamped refusal to sign. Every write-up should get a yes/no on each element before it is filed, and missing any one is grounds to fix it first. Refusal to sign does not void the write-up as long as the refusal is witnessed and timestamped.
When can I skip straight to termination instead of going through the warning steps?: Most operators run a 4-step ladder (verbal, written, final, termination), and skipping steps is the second-most-common reason write-ups get voided. Terminating offenses such as sale to a minor, theft, or violence can skip steps 1 through 3, but they require irrefutable documentation: video timestamp, witness, and audit-log entry, all three. A vague 'I think they sold to a minor' is not enough; a specific record naming the camera footage, transaction id, and manager-on-duty witness is.

Related guides

People + hiring playbook

Ready to talk through your migration?

30-minute demo. We end by quoting the cutover from your current setup — fixed scope, no hourly games.

Request a demo →All guides