Quick Start Guide
Wurk Cannabis Operations Quick Start
Basic setup guide for Wurk in cannabis operations. Covers employee profile basics, badge and location mapping, onboarding email flow, timekeeping approvals, and payroll-close readiness.
Compliance Note
Treat employee, labor, and payroll data as controlled operational records. If shifts, approvals, or profile mappings are wrong near payroll cutoff, correct the source record first instead of forcing a last-minute workaround.
1. Clean up the employee profile model first
A lot of Wurk issues start because profile fields are incomplete or stored in the wrong place.
- Decide which fields belong in work email, personal email, badge, location, department, and cost center before loading users in bulk.
- Use a single source of truth for employee IDs, facility locations, and labor reporting structure.
- Make sure managers know which fields employees can self-view versus which fields only admins should edit.
- Audit one employee profile from each location before onboarding everyone else.
2. Verify onboarding notifications and first-login flow
New-hire email problems are easier to solve before the first day than during live scheduling or payroll work.
- Confirm the account-created notification is enabled for the workflow you actually use.
- Check the employee’s work and personal email fields before resending invitations.
- Test one real onboarding flow end to end so the team knows what the first user experience looks like.
- Document who owns re-sends, bad-email cleanup, and first-login support.
3. Map badge, location, and labor buckets before timekeeping goes live
Clock-in issues and bad payroll reporting usually trace back to profile mapping, not the final approval screen.
- Confirm the employee is attached to the right location, department, and cost center before the first shift.
- If cannabis badges or facility-specific identifiers are used in operations, validate they are stored consistently and visible to the right admins.
- Test clock-in or scheduling against a small pilot group before opening it to the whole team.
- Treat any missing badge or location data as a same-day fix, not a payroll-close fix.
4. Build a payroll-close routine around approvals
A small repeatable review process keeps the timekeeping queue from becoming a last-minute emergency.
- Set a standard time for managers to review missed punches, time changes, and pending approvals before cutoff.
- Have payroll review the exception queue by location instead of relying only on one manager’s view.
- Use unresolved approval volume as an escalation trigger, not just a late reminder.
- Keep a final payroll-close checklist that confirms approvals, location mappings, and unusual adjustments are reviewed.
Official Source Links
Related Download Assets
Checklists • PDF
Wurk Shift-Close Compliance Checklist
Manager-facing closeout checklist for time approvals, missed punches, labor mapping, and payroll-readiness checks in cannabis retail and operations teams.
Templates • DOCX
Wurk Manager Closeout Record
Manager-facing end-of-shift record for approvals, missed punches, carried exceptions, labor mapping issues, and payroll-risk notes in cannabis retail operations.
Related Support Tickets
Wurk
Wurk New Hire Welcome Email Was Not Received
Restore Wurk onboarding when a cannabis retail or cultivation employee never receives the expected welcome email and cannot start HR or payroll setup.
Wurk
Wurk Cannabis Badge or Cost Center Is Missing from the Employee Profile
Correct missing profile details in Wurk when cannabis operators cannot clock in, route labor correctly, or keep payroll aligned to the right department or location.
Wurk
Wurk Timesheets Pending Approval Are Blocking Payroll Close
Clear Wurk approval bottlenecks before payroll close when cannabis operations teams still have open timesheets, missed punches, or unresolved manager review tasks.
Wurk
Wurk Shift-Close Attestation or Manager Review Is Incomplete
Resolve end-of-shift Wurk gaps before labor records, punch corrections, and manager signoff drift into the next day and create payroll or compliance risk.
Reviewed
Last reviewed on May 11, 2026 by Tamem J, IT Solutions Engineer.