An HR inbox without triage is a compliance risk disguised as a service problem. When a harassment intake arrives at 9 a.m. and sits behind seventeen benefits enrollment questions because the queue is first-in-first-out, the ER case ages and the legal exposure compounds. By the time someone with the right authority picks it up, two weeks may have passed and the employee has already drawn a conclusion about whether HR is safe to use.
The reason this happens is structural, not personal. HR teams optimize for throughput. Clearing the queue feels like progress. Triage feels like overhead. But a team that closes two hundred low-stakes tickets while a Tier 3 item ages is not operating efficiently—it is creating a liability while generating the appearance of productivity.
#One Queue Blends Risk Categories That Should Never Coexist
The default state for most HR teams at under 150 employees is a shared inbox—Slack, email, or a ticketing tool configured to behave like email. Everything arrives together: a forgotten HRIS password, a question about FSA eligibility, a manager asking how to document a recurring attendance issue, and an employee reporting a hostile supervisor. Same queue, same priority logic, same visible response-time expectations.
The problem is not volume. It is that these requests represent fundamentally different risk profiles. A delayed FSA answer is a minor inconvenience. A delayed harassment intake that results in a second incident before HR even acknowledged the first is a legal matter with a paper trail that shows the organization's awareness. Triage is risk sorting, not customer-service optimization.
Most SMB HR teams resist implementing triage because they believe their size makes it unnecessary. The opposite is true. A team of three handling requests for 150 employees needs triage more urgently than a team of twenty—there is no slack in the system to absorb misallocation. A misallocated hour at that ratio is a day of delay on the cases that matter most.
#A Three-Tier Model That Fits SMB Scale
The design goal is the simplest structure that meaningfully separates risk levels.
Tier 1 — Documented answers, self-resolvable Any request with an existing documented answer in policy or a self-serve portal belongs here. The correct response is a link and a close, not a custom explanation.
SLA: Same-day acknowledgment; full resolution within one business day if the answer exists in the knowledge base.
Examples: Password resets, benefits enrollment windows, PTO policy questions, payroll calendar questions, standard leave policy inquiries.
Tier 2 — Manager coaching, complex policy, case-by-case judgment Requests that require HRBP professional judgment but do not involve legal risk or active misconduct allegations.
SLA: Acknowledge within four business hours; provide a substantive first response within 48 hours.
Examples: Manager asking how to address a performance plateau, an employee requesting a role change, accommodation discussions that are straightforward in scope.
Tier 3 — Employee relations, active investigations, legal-adjacent matters Any matter involving potential misconduct, accommodation complexity with legal exposure, termination preparation, or regulatory inquiry.
SLA: Same-day acknowledgment with a named investigator or senior HRBP assigned; active case management from acknowledgment forward. Compliance partner notified within 24 hours.
Examples: Harassment intake, hostile work environment reports, FMLA disputes with contested facts, retaliatory action claims.
Tip: The acknowledgment SLA is often more important than the resolution SLA. An employee who reported a serious concern and heard nothing for 72 hours has already formed a judgment about whether HR responds to risk or manages the appearance of it. "We received your report and [Name] will be your primary contact" costs 90 seconds and preserves the trust the investigation depends on.
#Staffing to the Tier, Not the Queue
| Tier | Staffing Logic |
|---|---|
| Tier 1 | HR coordinator or ops team; can be partially automated with a maintained knowledge base |
| Tier 2 | HRBP rotation; each HRBP owns Tier 2 for their client group |
| Tier 3 | Senior HRBP or ER specialist only; no concurrent Tier 1 or 2 assignment |
The structural mistake is assigning staff to the queue and allowing them to work items in arrival order. That model ensures your strongest investigators spend a third of their time on Tier 1 noise while Tier 3 cases age past the window where early intervention would have contained them.
Publish SLAs in a location managers can find—not buried in an internal wiki, but in the same channel or portal where they submit requests. Visible SLAs change behavior in both directions. Employees know what to expect. Managers know that Tier 3 items get same-day acknowledgment, which means they are less likely to sit on a complaint they heard secondhand before routing it through HR.
Measure misrouting rate monthly: what percentage of tickets entered as Tier 1 required escalation? Above 10% means the intake routing logic is not surfacing risk signals early enough. Recalibrate the intake form questions before the next review cycle.
Pair SLA tracking with input-driven performance metrics thinking: you are measuring whether the system produces timely truth, not just whether your team looks busy. Throughput numbers without a quality dimension miss the compliance exposure entirely.
The labor compliance for SMBs framework reinforces why structural accountability in HR operations matters: when the process is documented and consistently applied, the organization's response to risk is defensible. When it is ad hoc, the absence of a response policy becomes evidence.
#Related guides
Sources
- U.S. Equal Employment Opportunity Commission. Promising Practices for Preventing Harassment
- Society for Human Resource Management. Employee Relations and Investigations
This article is operational education only—not legal advice. Work with qualified counsel for compliance, compensation, and termination decisions in your jurisdiction.