Document a Report That Contains Secondhand Information

Secondhand information shows up in almost every employee relations intake call. A caller reports something they heard from someone else, not something they witnessed themselves, and the specialist has to capture that report without turning it into a confirmed fact. Get the distinction wrong and the review that follows starts from a false premise. Get it right, and the reviewer who picks up the file can move straight to the right questions instead of untangling what actually happened.

Why This Call Goes Wrong

The pressure on this call comes from the caller, not from you. Someone brings you a report that troubles them, and they want to hear that you take it seriously. The easiest way to sound like you take it seriously is to repeat their words back with confidence, and that is exactly the trap. The moment you write "the supervisor threatened to cut shifts" as a plain statement in your notes, you have converted a secondhand account into something that reads like a finding. Nobody intended that. It happens because slowing down to ask who said what, and when, feels like you are doubting the caller.

There is a second pressure working against you. Callers often do not distinguish between what they saw and what they were told. They experienced the whole thing as one story, so they tell it as one story. Your job is to pull the story apart into its parts without making the caller feel cross examined. Skip that step and the reviewer inherits a note that treats a rumor as a documented event, which can waste time chasing a version of events nobody can actually confirm.

Prepare Before You Pick Up the Phone

Walk into the intake with a mental structure already in place, so you are not building it live while the caller talks. Three questions do most of the work.

1. What did the caller personally see or hear, with their own eyes or ears.
2. What did someone else tell the caller, and who was that person.
3. When did that conversation happen, and who else might have been present or might know more.

Decide in advance how you will label each piece of information in your notes. Most employee relations teams use some version of three labels, direct observation, reported by another person, and document provided. Keep those labels in front of you and apply one to every sentence you write. If a sentence does not clearly say who knew the information first, it is not ready to save.

Also plan for the moment the caller offers to send you something, a text message, an email, a note they wrote down afterward. Know your approved channel for receiving that material before you need it, so you are not improvising on the call.

What to Say During the Call

Employee Kai opened with, "I heard that our supervisor threatened to cut shifts." Specialist Ren did not write that down as a statement of fact. Ren asked, "Did you hear the supervisor say that yourself?" Kai answered, "No. Tessa told me about it after the team meeting." Ren replied, "That helps. I am noting that Tessa reported this to you, not that you heard it directly. Do you remember the date of that meeting, and was anyone else around when Tessa told you?" Kai gave the date and named two coworkers who were nearby.

Ren continued, "I am going to include those names and the date in my note, so the reviewer knows who else might have direct knowledge. I want to be clear with you that I cannot decide from this call what happened or what should happen next. That decision belongs to the reviewer, once they have talked to the people involved." Kai asked whether Tessa would get in trouble for talking. Ren answered plainly, "I cannot promise an outcome for Tessa or for anyone else. What I can promise is that your report and the details you gave me will reach the reviewer accurately."

Notice what Ren did not do. Ren did not ask Kai to guess why the supervisor might have said that, and did not ask Kai to rate whether Tessa seemed reliable. Those questions push the caller into territory they cannot actually speak to, and the answers would just be more secondhand guessing layered on top of the original report.

Mistakes That Undermine the Record

A few habits show up again and again in intake notes, and each one weakens the file.

1. Writing the caller's report as a plain statement of fact instead of attributing it to its source.
2. Asking the caller to characterize another person's motives or honesty, which invites speculation dressed up as information.
3. Promising a specific outcome or timeline before anyone has reviewed the facts.
4. Leaving out the date, the names of possible witnesses, or how the caller came to know what they know.
5. Not asking whether the caller has a message, email, or note they could provide, and if they do, not explaining how to submit it through the right channel.

Any one of these mistakes can send a reviewer down the wrong path or force a second call to fill in gaps that should have been covered the first time. Avoid them by reading your note back before you save it and asking, for every sentence, whether it says clearly who knew the information and how.

How to Practice and Score This Skill

This is a skill you build through repetition, not through reading a checklist once. Set up practice calls where a manager or a peer plays the reporting employee and deliberately blurs the line between what they saw and what they heard, the way real callers do. Your job in the practice run is the same as on a real call, pull apart the account, label the source of each piece, and resist any pressure to conclude something the caller cannot support.

Score each practice run against a short list. Did you ask directly whether the caller witnessed the event themselves. Did you capture the name of the original source when the caller named one. Did you avoid asking the caller to judge another person's character or motive. Did you end the call with a clear statement that you cannot determine the outcome. Did you explain how the caller can submit any supporting material they have.

DealSpeak's HR and Leadership practice conversations let you rehearse this exact scenario with an AI counterpart that plays the caller, so you can practice the attribution questions until they feel natural instead of scripted. If your team is also handling callers who ask to keep a serious concern off the record, the piece on how to Respond When an Employee Wants a Serious Concern Kept Off the Record covers a closely related situation worth rehearsing alongside this one. And if you are thinking about rolling structured intake training out to your wider team, the guidance on how to Select a Small Pilot Group Without Overstating Its Reach will help you scope that rollout honestly.

A clean intake note does not solve the underlying issue. It gives the reviewer a fair starting point, built on what the caller actually knows rather than what they assumed. That is the whole job on this kind of call, and it is a skill worth practicing until it holds up under pressure.