The grievance that lived in a mailbox: what an employee relations system has to hold

In September, a manager asked HR what had been decided about a complaint one of his team had raised in March. The complaint had been handled — properly, as far as anyone could tell — by an HR executive who had since left. The record of it was in her mailbox, which had been closed. There was a vague memory of a conversation and an outcome. There was nothing anyone could show the employee, who was now asking why the thing he had raised six months ago seemed to have been forgotten.

Nothing about the handling had been careless. The business simply had no place for a case to live that was not a person's inbox, and when the person went, the case went with her. That is the failure employee relations software exists to prevent, and it is a records problem before it is a workflow one.

NUMBER     assigned at logging; the only name the case has
TYPE       suggestion / grievance / conduct / safety / other
RAISED BY  or anonymous, recorded as such
OWNER      one person, by role, with a date they took it
STATUS     open / acknowledged / investigating / decided / closed
DUE        the stated response time, and whether it was met
TRAIL      every action, dated, by whom, retained
OUTCOME    what was decided and why, in writing

If it is not in the record, it did not happen.

The trail is the product. Everything else — forms, reminders, dashboards — is convenience. A case with a dated, retained trail can be explained to the employee, defended to anyone who asks and reviewed a year later by someone who was not there. A case without one is a memory, and memories leave when people do.

The word 'engagement' in the product name is where confusion starts. A suggestion about the canteen and an allegation of harassment are both things an employee raises, and they must not share a queue, a response time or an audience. The system has to route by type from the moment of logging: suggestions to the engagement loop with a five-day answer; grievances to the formal process with its own steps; conduct matters and safety concerns to their owners, immediately, with access restricted to those owners.

Configuring that routing is where a business discovers whether it has a grievance and disciplinary process at all. The system asks who owns a grievance, what the steps are and how long each takes, and a business that has never written those down will either delay the implementation or let the implementer guess. Guessing is how a harassment complaint ends up in the suggestions queue.

1. 1

   Who may log

   Everyone, for suggestions. Everyone, for grievances, including on behalf of someone else. Logging must be easier than not logging, or the mailbox returns.

2. 2

   Who may see

   By type and by role, and narrowly. A grievance is visible to its owner, the HR lead and nobody else until the outcome. A manager must not see a complaint about themselves before the process says so.

3. 3

   Who may act

   The owner, and whoever the process names at each step. Actions are logged as theirs. Nobody edits a trail; corrections are new entries.

4. 4

   Who may report

   Aggregates — volume by type, time to resolve, outcomes — go to leadership. Individual cases do not. The aggregate is what makes patterns visible without exposing people.

Getting the visibility rules wrong is worse than having no system. A grievance visible to the wrong manager, even briefly, is a breach the mailbox never risked. This is the part of the configuration that deserves the most care and usually gets the least, because it is invisible when it works.

The second thing the system produces, once cases have a home, is a picture the mailbox could never give: how many things are raised, of what kind, how long they take, and where they come from. Three grievances in a year from one team of nine is a management finding. Suggestions that stop arriving after a manager changes is another. Time to first acknowledgement creeping from three days to nine is the earliest sign the loop is breaking again.

None of that is available while cases live in inboxes, and all of it is the difference between an employee engagement process that is managed and one that is hoped for.

• Volume by type and team, monthly. The team with the most grievances or the fewest suggestions is the one to look at.
• Time to acknowledge and time to close, median and worst case. The worst case is what employees remember.
• Proportion closed with a written outcome. Cases that age out without one are the failure the system exists to prevent.
• Repeat raisers and repeat subjects. Both are patterns. Neither is visible from a mailbox.

How long a closed case is kept, who may see it afterwards, and what happens when someone asks for their own record — these are questions the mailbox never forced and the system does. Set the answers before go-live, by type: a suggestion needs no long memory; a grievance outcome may need to be producible years later; a conduct matter has its own rules. The system enforces whatever is configured, so an unconfigured retention setting is a decision made by default.

An anonymous route is worth having and it changes the record: there is no raiser to acknowledge, no one to tell the outcome, and no way to ask a clarifying question. The system should mark anonymous cases as such at logging, route them by type exactly as named ones, and close them with an outcome recorded against the case even though nobody will read it — because the aggregate still needs it, and because a pattern of anonymous complaints about one team is a finding whether or not any individual can be followed up. What the system must not do is let an anonymous case be quietly dropped for want of a raiser to chase.

Most growing businesses are better served by the employee relations module of their HRMS than by a standalone case tool, because the case has to reference an employee record, a manager and a team, and a separate tool re-creates the lookup that the mailbox did badly. The exception is where the HRMS module's access controls are too coarse to keep a grievance from the wrong eyes — in which case the standalone tool is the safer choice and the integration is worth the cost.

Sequence it after the employee record is clean and after the grievance process is written down. Configured on top of both, engagement and employee relations software gives every case a number, a home and a trail that outlives whoever handled it — which is precisely what the manager in September could not find. Configured before either, it gives the mailbox a new address.

The one test worth running before signing anything: log a fictional grievance against a fictional manager, and check what that manager can see. If the answer is anything other than nothing, keep looking. That single check on engagement and employee relations access rules will tell you more than any demonstration of the dashboard.