Skip forward into hiring notes
RosterAcorn

Retaliation risks: 3 checks for records complaints

Handle records complaints by logging the request, reviewing decisions independently, and keeping penalties out of corrections; legal protection depends on the applicable law.

Key takeaways

  • Record verbal concerns instead of waiting for a written complaint.
  • Check the business reason before taking an adverse step near a dispute.
  • Give correction requests an owner, a reply date and a documented outcome.

A worker who says a file is wrong, disputes a rating, or asks for a note to be removed is doing something ordinary. The person who receives that request is often a recruiter, an HR partner or a hiring manager who wants the matter settled quickly. That speed is where the trouble starts. A reply that sounds routine can create retaliation risk if it punishes the worker for protected activity.

This post covers three risks. The first is acting against a worker before they have filed anything, because you expect them to. The second is brushing aside a complaint because it was spoken, informal or sent only to a manager. The third is handling a records correction in a way that quietly makes the worker pay for asking. For each risk I quote the official material I checked and link it, then describe what to do differently. Rules differ by statute and by state, so read this as a map of where problems usually start, not as advice on any one case. Where a source covers only one kind of claim or one state, I say so.

Can you act against a worker who has only hinted at a complaint?

Threatening a worker for an expected discrimination complaint can be retaliation under Title VII, even before a complaint is filed. The EEOC's enforcement guidance on retaliation cites a court decision holding that threatening to fire a plaintiff if she sued "would be a form of anticipatory retaliation, actionable as retaliation under Title VII."

That example comes from a discrimination case decided under Title VII, so whether a particular records dispute falls under that statute depends on the facts. The logic is still useful for anyone who handles files. Timing can raise questions about the reason for a decision. A worker mentions that they plan to ask HR to fix a performance note. A week later, a manager starts an extra review of their work or moves them off the account they were working on. Nobody may have meant to connect the two events. A reviewer who looks at the sequence may ask whether the decision would have happened without the worker's stated intention.

Hiring managers meet this risk in a few familiar forms. A new hire asks for an error in their onboarding file to be corrected, and the offer suddenly looks less certain. A current employee says they will contest a warning, and the manager starts documenting small problems. Each of these may have a legitimate reason behind it. The trouble is that the reason was not written down before the dispute, so the timing does the talking.

What to do differently is less dramatic than it sounds. Before taking any adverse step against a worker who has raised a records issue, write down the business reason and when you first had it. Then have someone outside the manager's chain review the decision. That reviewer should be someone who did not create the disputed record and who is not the person the worker is disputing with. If a manager makes a comment that sounds like a threat, even a light one, address it that week, in writing, and keep the note. A threat that sits unaddressed is harder to explain later than one that was corrected quickly.

It also helps to slow down on decisions that land near a dispute. The point is not to freeze the worker's career. The point is to make sure that any change has reasons you could explain to someone who was not in the room.

Is a verbal complaint about records protected?

Whether a records complaint is protected depends on the applicable statute or company policy; the cited oral-complaint decisions concern wage and equal pay laws.

The EEOC's enforcement guidance reviews several decisions under the Fair Labor Standards Act (FLSA) and the Equal Pay Act (EPA), and they point in the same direction. One decision it cites holds that a plaintiff's oral complaint to his manager was protected activity. Another concludes that the FLSA anti-retaliation provision, as incorporated into the EPA, prohibits retaliation against employees who orally complain to their employers. A third holds that intra-company complaints are protected activity under the FLSA, consistent with most of the courts of appeals that had addressed the issue.

The guidance also shows how the case law developed. An earlier decision found that oral complaints may be protected activity, but declined to decide whether internal complaints made to management were enough. The later decisions answered that question for internal complaints, consistent with most circuits. For a reader in HR, the practical lesson is that a complaint made to a supervisor is treated as a complaint for handling purposes, not as a casual comment.

A worker who says "this is wrong, please fix it" may not use the word "complaint," and may not name a statute or a policy. The question that matters for your handling is whether the worker is objecting to something and asking for a change. If the answer is yes, your process should treat it as a complaint, even if the person who received it would have called it a question.

A records dispute about a job title, a rating or a home address may fall under a different law, a company policy, or no statute at all. So the working rule should be broader than the narrowest legal minimum.

Language matters in the reply, too. Compare two responses to the same request. The first says, "We don't usually change reviews, so I'm not sure why you're raising this." The second says, "Thanks for raising this. I'm logging it today, I'll check the review against the source notes, and I'll reply in writing by the date I've given you." The first sounds like a warning. The second treats the complaint as a complaint, which is what it is.

Practical steps follow from that:

  • Write down verbal complaints the same day. Record the date, who raised it, what they said they wanted, and who you told.
  • Send the note to the person who handles complaints, not to the person who created the record. That keeps the decision away from the person whose work is in dispute.
  • Do not require the worker to put a concern in writing before you take it seriously. You can ask for a written summary afterward, but the complaint exists once it has been made.
  • Hiring managers should pass along what they hear in a hallway or a one-on-one. Telling a worker to "take it up with HR" without recording it leaves no trace that the complaint was ever made, and that gap can cause problems later.

How do you correct a file without punishing the person who asked?

You do it by giving the worker a real route to a correction and by keeping every penalty out of the process. Massachusetts law sets out one version of this for personnel records. Under the Massachusetts General Laws, Chapter 149, Section 52C, "If there is a disagreement with any information contained in a personnel record, removal or correction of such information may be mutually agreed upon by the employer and the employee." If no agreement is reached, the employee gets a second route: "the employee may submit a written statement explaining the employee's position which shall thereupon be contained therein and shall become a part of such employee's personnel record."

That provision is specific to Massachusetts. If you recruit or employ people in other states, check the rules that apply there and your own company policy. Do not assume this text governs your files.

Even where no statute sets out a process, the same structure works well. Acknowledge the request in writing and say when you will respond. Check the disputed information against the source documents. For related file checks, see the recruiting records audit. If the record is wrong, correct it and tell the worker exactly what changed. If you disagree, explain why in plain words, and where your process allows, let the worker attach their own written response so the dispute is visible to the next reader rather than settled privately. The Massachusetts route above shows why that matters: the disagreement becomes part of the record instead of disappearing into an inbox.

Timing deserves its own attention. Once a correction request is logged, set a date for the reply and keep a record of each step: when the source documents were checked, who checked them, and when the file was updated. If a correction stalls, the worker is left with a file they believe is wrong and no sign that anyone is working on it. That gap can look like punishment even when the delay was caused by a busy calendar.

The retaliation risk sits in the details of how a correction is handled. Several patterns deserve review for possible punishment:

  • Adding a remark about the worker's attitude to the file because they asked for a correction.
  • Delaying a correction that affects pay, a background check, a promotion or a benefit while the request sits in someone's inbox.
  • Passing the request to a person who is known to be hostile to the worker, or who took part in the decision being disputed.
  • Treating a correction request as insubordination or as a performance issue.

If someone asks you to fix a detail in their file before they start, send the request to HR, record it, and answer it on the facts. Do not reply with comments about their tone or about how often they have raised issues. A reply that focuses on the fact in question keeps the conversation about the record, where it belongs.

Illustrative example: count requests before reviewing outcomes

Suppose an owner receives 5 verbal correction requests and 5 written requests. That makes 10 requests to log, rather than only the 5 that arrived in writing. For each request, the owner records what the worker wants changed and sets a reply date. If a manager proposes an adverse decision involving a worker in that log, an independent reviewer checks the reason before the decision reaches the worker. Counting requests helps expose missing intake records; it does not decide whether any complaint has legal protection.

Today, take a recent correction request and check that its record names an owner, a reply date and the next action. Use that review to identify a gap in your written process.

What should a complaint process look like on paper?

It should name one owner, log every request in the same place, and require a documented review before any adverse action affects a worker who has raised a dispute. These steps are general practice rather than a quoted legal requirement. They are useful in any state because they do not depend on which statute applies to a given complaint.

Write the process as a short document that managers can read in five minutes. Keep it to a few points:

  • Intake: anyone who receives a complaint, verbal or written, forwards it to the named owner within a time your company sets.
  • Log: the owner records the date, the worker's request, the record involved, and the people who were told.
  • Acknowledgement: the worker receives a written reply that confirms the request and the next step.
  • Review: any decision that touches the worker in the following months goes through a second reviewer who was not involved in the dispute.
  • Outcome: the worker hears the result, any correction is made, and the file shows what happened.
  • Training: managers learn what counts as a complaint and what to say when one comes up. The aim is calm, factual replies, not defensive ones.

For a related approach to recording decisions, see the hiring decision debrief.

Training works best when it uses real examples from your own company rather than abstract rules. For each one, ask the managers in the room what they would do next and what they would write down. The answers usually reveal where a manager would reach for a quick remark instead of a record, and that is the habit the process is meant to break.

The review step deserves more detail, because it is the point where a problem is easiest to catch before it reaches the worker. The reviewer should check four things: whether the reason for the decision existed before the dispute, whether the same decision would have been made for a worker who had not complained, whether the people involved had any stake in the disputed record, and whether the worker was told about the decision and given a way to respond. If any answer is unclear, the decision waits until it is clear.

When you speak with the worker, keep the message short and specific. Tell them what you received, what happens next, and when they will hear back. Avoid predicting how the dispute will end, and avoid commenting on whether you think they are right. Those comments can be repeated later, out of context, and they rarely help the file.

Retaliation can look like a decision made because a worker raised a protected concern. Most of the risks above come from ordinary workflow. A process that catches them early is far easier to run than an investigation that has to reconstruct them afterward.

Sources