Give a Process Update Without Sharing Another Person's Information

An employee who raised a concern wants to know what is happening, and they deserve an answer. The honest answer often includes details about another person's interview, discipline history, or the outcome of a review that is still underway. As an employee relations specialist, you have to give a real update without turning the call into a report on someone else's personnel file. That balance is the whole job here, and getting it wrong in either direction costs you something, either the employee's trust or the fairness of a process that is not finished yet.

Why This Conversation Goes Wrong

Most specialists do not get this wrong because they want to overshare. They get it wrong because silence feels like the bigger risk. Three weeks pass without contact, and the employee assumes the worst, that no one is looking into it or that the process forgot them. You pick up the phone wanting to reassure them, and reassurance without content feels hollow, so you start filling gaps you should leave empty. A hint about what the manager said. A guess about how long discipline usually takes in a case like this. None of that comes from bad intent. It comes from wanting the person on the other end of the line to feel heard.

The pressure gets worse when the employee is frustrated and asking direct questions. A frustrated person asks pointed questions, and pointed questions create an urge to answer them directly instead of answering what you are actually allowed to answer. That urge to resolve tension fast is worth naming on its own. Help a Leader Notice When Urgency Prevents Reflection covers the same instinct in a different setting, when the push to act quickly crowds out the pause a decision actually needs. The same pause matters here, before you speak, not just before you decide.

How to Prepare Before You Call

Walk into the call with three things settled, not guessed at. First, know exactly what the assigned reviewer has authorized you to share, in specific language, not a general sense of the case. Second, confirm there is no active safety issue that changes what you say, because a safety concern can change the shape of the whole update. Third, have a real date for the next contact, not a vague promise of soon.

Write the update down before you dial. A sentence or two, in plain language, naming the current stage without naming a person or a specific fact from an interview. If you cannot summarize your own update in two sentences, you are not ready to make the call.

Decide in advance how you will answer the two questions almost every employee asks, whether the other person admitted anything, and whether they will learn the outcome. Have your answer to each one ready, worded the same way every time you say it, so you are not improvising different phrasing to different people. Improvised phrasing is where the leaks usually happen.

What to Say

Rafael called Celia after three weeks without word. He said, "It has been three weeks since I raised this, and I still do not know anything. Did my manager admit to what happened."

Celia answered, "I understand the wait is hard, and I want to be direct with you. The review is still active. I cannot share what anyone said in an interview, or any part of another person's employment record. What I can tell you is that the reviewer is finishing the remaining conversations now and plans to contact you by next Wednesday with an update on where things stand."

Rafael pushed further. "Will I actually find out what happens to him."

Celia said, "You will get the information the process allows us to share once a decision is made. That is not everything, and I will not pretend otherwise. I will also let the reviewer know you are concerned about how long this has taken. You should not have to chase this for basic contact."

Notice what Celia did not do. She did not soften the limit by hinting at what the manager admitted or denied. She did not promise an outcome she cannot control. She gave a specific day, not soon or shortly, and she named a concrete next step, finishing the remaining conversations, instead of a vague reference to the process moving forward. Specific beats reassuring every time in this kind of call.

Mistakes to Avoid

A few habits break trust fast in these calls. Guessing to fill silence hurts you even when the guess turns out right, because you have now trained the employee to expect an inside line to the case, and to ask for more of it next time. Promising a date you are not sure you can hit hurts you too, since a missed date reads as being forgotten all over again, only worse the second time around. Comparing this case to another one, even to reassure someone that most cases resolve within a certain window, exposes information about other cases that is not yours to share. Answering a direct question with a non answer that dodges instead of naming the limit out loud leaves the employee guessing about why you will not answer, and people usually guess the worst reason.

The other mistake runs the opposite direction. Some specialists get so careful about privacy that they stop giving any real information at all, repeating a script instead of a status. An employee who hears only We are still working on it three times in a row stops believing there is a process at all. The goal is not silence dressed up as policy. The goal is a real answer inside a real boundary, every time.

How to Practice and Score It

This conversation is hard to get right on the first try, because the pull to overshare or undershare is strongest exactly when you are also managing someone's frustration in real time. Practicing it before you are on a real call with a real employee changes how the call actually goes.

Run the scenario with a partner playing the frustrated employee, and give them permission to push back the way Rafael did, twice or three times, on the same question. Score yourself on three things after each run. Did you name the wait and its effect on the person before you defended the process. Did you state a limit as a limit, out loud, rather than deflecting around it. Did you leave the call with a specific date and a named next step instead of a vague reassurance.

DealSpeak is built for exactly this kind of rehearsal. It lets you run the same tense exchange against an AI counterpart that pushes back the way a real employee would, and it scores your answers against the same criteria a case lead would use. You can find more scenarios built around this skill at HR and Leadership practice conversationsand if rushing past a needed pause is a pattern in your calls more broadly, Check Understanding When Every Task Feels Urgent is worth a look too.

A manager reviewing your calls should listen for the same three things. A specific date, a named limit, and an acknowledgment of the wait, in that order. If any one of those is missing, the update was not really an update.

In Short

An update earns trust when it is specific about contact and honest about its limits, not when it tries to sound complete. Keep a simple log of the last contact, what you were authorized to say, the promised date, and who owns the next step, and review it weekly with the case lead. If a date is going to slip, call before it does and give the employee the new one. That single habit protects more trust than any script ever will.