HR has asked to meet with you. What to do in the next 48 hours.
The email usually arrives on a Tuesday. It is short, it is polite, and it says something like we need to meet with you Thursday to discuss a concern that has been raised. There is no detail. There is no indication of how serious it is. And there are now roughly forty-eight hours between you and a meeting you know nothing about.
What follows is what that meeting actually is, and what to do with the time.
First, what the meeting is not
It is not a disciplinary hearing. Those are a separate, later step in almost every organization's process, and they come with their own notice.
It is not a decision. In a properly run process nobody has concluded anything about you yet, and the people running it are not supposed to have.
And it is not, despite how it feels, a signal that someone believes you did something. Organizations are obliged to look into concerns that get raised. If a complaint arrives and nobody looks at it, the organization has a far bigger problem than an unfounded complaint. The fact that a meeting is happening tells you a concern exists. It tells you nothing about whether anyone credits it.
What it actually is
A fact-finding interview. Somebody has been asked to establish what happened, and they are gathering information from the people who were there. You are one of those people.
The person conducting it is usually not the person who decides the outcome. Their job is to produce a record — an account of events, tested against documents and against what other people say. Someone else reads that record and decides what, if anything, follows.
That distinction matters more than almost anything else you will read this week. You are being asked to describe events. You are not being asked to argue a case. Nearly all the damage people do to themselves in these meetings comes from confusing the two.
What has probably already happened
By the time someone asks to meet you, the quiet part is usually finished.
Most investigations gather documents before they gather accounts. Emails, calendar entries, approval records, access logs, expense claims, file histories — whatever the concern touches. It is unglamorous and it is thorough, and it typically happens without anyone telling you.
This has one enormous practical consequence: you are rarely telling them something they cannot check. Build your account around what the records will show, not around what you hope they show. If you remember a date differently than the system does, the system is going to win, and the graceful thing is to say so.
You are also, usually, interviewed late rather than early. Complainant first, witnesses next, you last — because the investigator wants to be able to put specific things to you rather than fish.
The one thing worth doing with forty-eight hours
Not rehearsing. Not preparing arguments. Not calling around to find out who complained.
Build a chronology.
A dated list of what happened, in order. One entry per event. For each one: the date, as precisely as you honestly can; who was present, including people who said nothing; what was actually said or done; and — this is the part people skip — whether anything outside your own memory supports it.
Set the boundaries wider than the concern. If it covers the second half of last year, start two months earlier and run two months later. Context sits outside the window people draw for themselves.
Do not rely on recall for anything you can check. Your own sent email, in date order, reconstructs a period faster than anything else you own. Calendar entries, including the cancelled ones. Message history. File modification dates. Expense submissions.
Access only what you would access in the ordinary course of your job, in the ordinary way. This matters enough to say twice. Downloading, forwarding to a personal account, or bulk-exporting company records because you are under investigation is treated extremely seriously by most employers, and it is one of the few things that can turn a survivable matter into a dismissal regardless of what started it. If a record would help you and you cannot properly reach it, ask for it in writing through the process. That request is itself worth having on the record.
Why chronology and not argument
Three reasons, and they compound.
It is checkable. Every entry that lines up with a calendar or an email is a piece of your account nobody has to take on trust. An argument about what you intended is unverifiable by its nature. A dated sequence of events is not.
It survives questioning. After you give your account you will be asked about it in detail, sometimes twice, sometimes with a document in front of you. Answers drawn from one fixed written record stay consistent. Answers reconstructed fresh each time under pressure do not.
It tells you what you actually remember. This is the one people don't expect. Halfway through building a timeline, most people discover that two events they were certain were connected happened four months apart. Far better to find that out at your kitchen table than in the room.
Questions worth asking before you walk in
Asking is normal. A well-run process expects it, and a process that resents being asked is telling you something.
- What specifically is the concern I am being asked to respond to? If you have not been told plainly, ask. You are entitled to know what you are answering.
- Who will be present, and what is each person's role?
- Is the meeting being recorded? Will I receive a copy?
- Who is taking notes, will I see them, and will I be asked to sign them?
- Roughly how long will it take?
- Am I able to bring someone with me? Whether you can, and who qualifies, depends on your employer, your contract and where you work — so ask them rather than assuming either way.
Things not to do
Do not discuss it with colleagues, particularly anyone who might be a witness. Even innocent conversation can later be characterised as influencing an account, and that characterisation is far harder to answer than the original concern.
Do not record the meeting covertly. Whatever the legal position where you live, covert recording of colleagues is treated as misconduct by many employers and can end a matter you would otherwise have survived. If you want it recorded, ask openly.
Do not go looking for who complained. It changes nothing you can act on and it looks exactly like what you would not want it to look like.
Do not write a long defensive statement before you have a timeline. If you are asked for something in writing, the chronology comes first and the explanation second. A written account that argues before it describes reads as avoidance of the facts.
When forty-eight hours is not the right plan
Some situations are past the point where preparing well on your own is the right move. Speak to an employment lawyer, before the meeting rather than after, if any of these apply:
- The matter has a criminal dimension of any kind
- A regulator is or could become involved
- Dismissal has been mentioned, or you have been suspended
- An external law firm is conducting the investigation
- You have been offered a settlement or severance agreement
- Your professional registration or licence could be affected
An hour of advice costs far less than the outcome it may change, and many employment lawyers offer a fixed-fee first consultation. If you go, bring your chronology — an hour spent explaining background from scratch is an hour of advice you did not get.
The short version
You have two days. Spend them building a dated account of what happened, checking it against your own records, and writing down the questions you want answered at the start of the meeting.
Do not spend them building an argument. The meeting is not for that, and the people in it are not the people who decide.
The First Account is a preparation tool for people in exactly this position — the process explained stage by stage, the interview walked through phase by phase, and a chronology builder that asks the right questions in the right order. Built by someone who spent thirty years running these investigations from the other side of the table.