HR Compliance & QA Framework

Internal Governance Deck — HR Department & Compliance Officers | August 2026

Phase 1

Onboarding & File Compliance

Phase 2

Attendance Auditing Standards

Phase 3

Progressive Discipline Workflows

All documentation must be dual-signed, digitally logged, and filed under the standardized naming convention before any corrective action is considered legally defensible.

Framework at a Glance: Three Compliance Phases

This framework governs the full employee lifecycle from onboarding through progressive discipline. Each phase is supported by standardized forms, manager sign-off protocols, and a digital employee file architecture designed for audit readiness and legal defensibility.

1

Phase 1 — Onboarding & File Compliance

  • Week 1 check-in protocol and assignment completion audits
  • Medical accommodation documentation
  • Policy 5.04 accountability logging
2

Phase 2 — Attendance Auditing Standards

  • 90-day rolling lookback grid
  • Daily time & attendance records
  • Variance classification: Late / Call-In / NCNS
  • Digital file architecture
3

Phase 3 — Progressive Discipline Workflows

  • Tiered corrective action thresholds
  • Formal written warning protocol (Policy 7.03)
  • Schedule modification directives
  • Termination criteria

Phase 1

Onboarding & File Compliance

Week 1 check-in protocol · Assignment completion audits · Medical accommodation documentation · Policy 5.04 accountability logging

Scope

All Tier 1 and Tier 2 employees from Day 1 through end of Week 2 onboarding cycle

Owner

Hiring Manager + General Manager co-sign all Week 1 deliverables

Output

Complete Digital Employee File — Sections 1 & 2 — closed before employee returns Week 2

Week 1 Check-In Protocol: Five-Point Accountability Structure

Manager Deliverable: Written summary of engagement level, technical hurdles, and medical status confirmation filed in the Digital Employee File by end of Week 1.

Well-being & Restrictions Review — 15 min

Mandatory for employees with active medical accommodations. All requested modifications documented in the employee file same day. No accommodation request is considered acknowledged until it appears in the file.

Advancement Track Development Seed

Use employee background to assess operational awareness — security flow, register accuracy, and opening/closing intuition evaluated against Tier 2 readiness criteria.

Core Values Reflection

Structured discussion anchored to three foundational values, used across every new-hire check-in. Responses logged to connect individual development to organizational mission. Prompt: "Which of our core values did you find yourself leaning into the most this week when talking to customers?"

Assignment Completion Audit

Four mandatory Week 1 deliverables verified and uploaded to the Digital Employee File before end of shift Friday. Incomplete submissions are a compliance flag. 1.1 Signed Welcome Letter · 1.2 "Reflections on Service" prompt · 1.3 Leadership Team Contact Card · 1.4 Operational Flow Specialist Quiz (100% score required)

Week 2 Transition Prep

Classroom enrollment confirmed, weekend reader schedule reviewed, and Code of Conduct module (cell phone policy) briefed before employee departs Friday.

Policy 5.04 — Zero-Reminder Standard: Accountability Log

Compliance Objective

Tier 2 employees must demonstrate full self-reliance on personal device policy — zero management-issued reminders for the duration of Week 1. A single documented correction constitutes a policy failure.


Policy Requirement

Cell phones stored in personal locker; use permitted only during designated break times — no exceptions during active floor hours.


Weekly GM Audit

Punctuality status (Pass = 100% on-time) and policy adherence (Pass = zero reminders) reviewed by General Manager at close of Week 1.


Escalation Path

Any policy failure during Week 1 is documented in the employee file and referenced in the Week 2 onboarding review — repeat violations trigger Tier 1 corrective action.


Value Creation Requirement

One documented proactive self-correction and 2–3 logged high-value client interactions required to validate Tier 2 sales performance alongside compliance metrics.

Daily Accountability Log — Policy 5.04

Daily log fields must be completed and initialed by MOD at end of every shift. Unsigned rows are treated as missing records.

Phase 2

Attendance Auditing Standards

90-day rolling lookback grid · Daily time & attendance records · Variance classification: Late / Call-In / NCNS · Digital file architecture

Scope

All active employees — rolling 90-day cycle maintained continuously from date of hire

Owner

General Manager initiates audit; HR co-signs all formal corrective actions triggered by threshold breach

Output

Signed 90-day lookback grid filed in Section 3 — primary evidentiary record for all disciplinary proceedings

90-Day Audit Methodology: Data Capture & File Architecture

Audit Standard: Every attendance variance is captured in a rolling 90-day lookback grid — the primary evidentiary record for any corrective action or termination proceeding.

Grid Capture Fields

  • Date — cross-referenced against POS clock-in actuals
  • Scheduled start time vs. actual clock-in
  • Variance in minutes — logged to the minute
  • Occurrence type: Late / Call-In / NCNS
  • Manager notes — contextual notation only, not substitutes for formal entries

Weekly Time Record Fields

  • Daily clock-in/out with two lunch break windows
  • Total hours per shift
  • Employee initials on each row — provides shift-level granularity for disciplinary proceedings

Record of Conversation Template

Structured coaching log capturing: meeting purpose, employee input, manager decision, follow-up date, and dual signatures. The instrument that converts informal coaching into a formal corrective action on record.


Medical Note Protocol

Absence justification documents (e.g., jury duty) filed in Section 3. Medical notes maintained in a separate, restricted file per compliance protocol. Commingling medical and attendance records is a compliance violation.

Digital Employee File — Section Architecture

Illustrative Case: 90-Day Attendance Audit

Composite example for illustration — figures adjusted and do not represent an actual employee, business, or audit record.

Audit Outcome: Documented attendance pattern constitutes a chronic reliability failure — occurrence count exceeded the corrective-action threshold well beyond the trigger point, requiring mandatory formal action.

Attendance violations are overwhelmingly concentrated in late arrivals, confirming a chronic punctuality pattern rather than isolated or circumstantial absences — the data supports formal corrective action.

Verified Occurrence Totals

28+

Late Arrivals

Primary violation category, confirmed against POS clock-in actuals

6

Call-Ins

Unplanned absences requiring active coverage negotiations

1

Early Departure

Clocked out ahead of scheduled shift end


Occurrence Pattern (relative timeline)

Policy 7.03 Threshold: 5-instance limit in a rolling 90-day period. Total documented occurrences exceed threshold. Recurring midweek call-ins required active coverage negotiations — downstream staffing risk to operations confirmed.

Phase 3

Progressive Discipline Workflows

Tiered corrective action thresholds · Formal written warning protocol (Policy 7.03) · Schedule modification directives · Termination criteria

Verbal Warning

First documented threshold breach — logged in Section 4

Written Warning

Policy 7.03 formal action — dual-signed, schedule modification enacted

PIP / Schedule Change

Performance improvement plan with defined threshold and review date

Termination

Threshold breach post-warning — immediate, per Policy 7.03

Policy 7.03 — Corrective Action Plan: Written Warning Protocol

Directive: Formal written warning issued following 90-day audit findings. All corrective actions take effect immediately upon signature and are logged in the digital HR impact system.

1

Schedule Modification

Employee transitioned to Saturday/Sunday schedule only — effective immediately. Weekday operations (Tuesday intake, Thursday transfers) require 100% attendance reliability not demonstrated during the audit period. Business necessity documented in writing.

2

Break Protocol Enforcement

Shifts over 7 hours: mandatory 1-hour lunch break required. Shifts of 4–6 hours: mandatory 30-minute break required. Non-compliance logged as a separate, standalone policy violation — not bundled with attendance occurrences.

3

Digital Variance Logging

All further attendance variances logged in real-time via the digital HR impact system. No informal coaching notes accepted as substitutes for formal log entries from this point forward.

4

Termination Threshold

Any further unplanned absence or tardiness exceeding the 5-instance threshold in a rolling 90-day period triggers immediate termination per Policy 7.03. No additional warning step is afforded.

5

Conduct Zero-Tolerance Clause

Any further unprofessional conduct in front of guests results in immediate termination — no progressive warning step required. This clause is communicated verbally and documented in writing at the disciplinary meeting.

Disciplinary Meeting Strategy: The Cumulative Weight Method

Standard: All formal disciplinary meetings follow a four-step structured protocol to ensure objectivity, legal defensibility, and operational clarity. Deviation from this sequence is a compliance risk.

1

Lead with the Data

Open by presenting the verified 90-day audit totals — specific numbers, specific dates, no subjective language. Example: "You have had over 28 late arrivals and 6 unplanned absences in the last 90 days." The data speaks; the manager frames it. No emotional language, no character assessments — numbers and dates only at this stage.

2

Define the Operational Impact

Quantify the downstream effect on the team and business — coverage burden, schedule disruption, and risk to store operations. Keeps the conversation objective, not personal. Naming the operational consequence elevates the meeting from interpersonal conflict to a business performance conversation.

3

Deliver the Directive

State the corrective action clearly and without ambiguity — schedule modification, policy citation, and next-threshold consequence communicated in plain language. The employee must leave with no uncertainty about what changes, what the new standard is, and what happens next if it is not met.

4

Close on Conduct

Reinforce zero-tolerance conduct standards as a separate, non-negotiable clause — ensures the employee understands both attendance and behavioral expectations going forward. Conduct clause is documented distinctly from the attendance corrective action in the Record of Conversation.

Governance Standards: Audit Readiness & Legal Defensibility

Core Principle: Documentation is the only thing that stands between a tough management decision and a legal liability. Every informal coaching note must be converted to a formal corrective action the moment a policy threshold is crossed.

File Naming Convention

All disciplinary documents saved as:

YYYY-MM-DD_LASTNAME_F_DOCUMENTTYPE_FINAL.pdf

Example: YYYY-MM-DD_LASTNAME_F_WRITTEN_WARNING_FINAL.pdf — ensures readiness for external HR review, legal proceedings, or SHRM-CP portfolio submission.


Dual Signature Requirement

All Records of Conversation and formal warnings require manager and employee signatures before filing. Unsigned documents carry no legal weight and will not withstand external HR review or legal challenge.


Separation of Records

Medical documentation maintained in a restricted file separate from the standard employee file. Commingling medical and attendance records is a compliance violation — this separation is non-negotiable and applies to all employee tiers.

Ongoing QA Monitoring Cadence