Log what happened, who was involved, who saw it and where — on any shift. AI checks every entry against California’s workplace-violence definition, and your team makes the call.
Watch it work
A guest at Table 7 loses a hand and shoves the dealer. Security logs it from the floor. Before anyone opens the entry again, the AI has checked it against Labor Code §6401.9.
Guest at Table 7 lost a hand, threatened the dealer and shoved him against the rail. Floor supervisor separated the guest; security escorted him out at 1:52 AM.
Flagged for review in the incident log. The AI’s reasoning is saved with the record.
The AI flags. Danielle Okafor reviews the entry and decides what happens next.
Example records · Redwood Crown Card Club is a fictional card room
What you get
Add as many employees as you need, mark each one Involved or Witness, and record who reported it.
Each incident is checked against the workplace-violence definition in Labor Code §6401.9 and tagged with an AI confidence score, so the ones that may qualify stand out.
Start with types built for your industry — misdeals and customer disputes for card rooms, failed ID checks for bars — then edit them any time.
Mark sensitive incidents private. Only people with permission can see them — and you can hide incidents about a person from that person’s own login.
When an incident matches your infraction list, AI pre-fills a point adjustment for a manager to review. Nothing is saved until they approve it.
Why: the incident says he did not report for his scheduled shift and did not call in.
A token-secured REST API lets outside systems create and read incidents. Workplace-violence detection runs on those too.
{
"employee_ids": [214],
"department_id": 3,
"incident_log_event_name": "Customer dispute",
"incident_log_entry_location_name": "Table 7",
"occurred_at": "2026-10-05T01:47:00-07:00",
"notes": "Guest shoved the dealer…"
}The receipt
The same label your managers see in the log. The AI’s reasoning is saved with the record; your team decides what happens next.
Just shipped
Say what happened, in English or Spanish. AI fills in who was involved, who saw it, the table and the incident type, then runs the workplace-violence check.
Learn moreWhen AI flags possible workplace violence, a follow-up checklist opens on the incident and ticks itself off as your team works it.
Learn moreExport flagged incidents for any date range with the fields Labor Code §6401.9 lists for a violent incident log, names left out, for your team to review.
Learn morePost a QR code in the break room. Staff report concerns anonymously; you get a logged, trackable incident.
Learn moreNo software can do that on its own. HR PaperTrail flags incidents that may meet the Labor Code §6401.9 workplace-violence definition so they’re easy to find and review. Your team decides, and your counsel confirms what your plan requires.
The incident’s narrative and details. It returns detected or not detected with a confidence score, and its reasoning is saved with flagged and borderline entries.
Only what their permissions allow. Department managers see their own departments, private entries need their own permission, and incidents about a person can be hidden from that person’s own login.
Yes. A token-secured REST API accepts incidents from outside systems, and the same workplace-violence check runs on them.
Same record, next module
Risk scores that cite the records behind them, workplace-violence flags, suggested point adjustments.
Shift reports, department checklists, time off and meetings with QR check-in.
Counselings with three-party e-signatures, PIPs, notes and onboarding documents.
Get started
Tell us a little about your operation. We’ll reach out within one business day to set you up — personally.