This is information about a practice, not legal advice. It cannot tell you what applies to your matter, and the rules on what you may retain vary by agency and by the sensitivity of the material. If you are in an active dispute, ask your union representative or your own attorney before acting on any of it.
I Why contemporaneous beats accurate
A record written the same day is not necessarily more accurate than one written a year later. It is more credible, and in an adversarial proceeding that is the property that matters.
The reason is simple. A note made before a dispute existed had no reason to shade anything. A summary written after a dispute began was written by someone with an interest in the outcome. A fact-finder assessing two conflicting accounts weighs that difference heavily, and it is the single largest reason the habit is worth having.
The value of documentation is set entirely by when you started — which means the only version that works is the boring one you keep during the years when nothing is wrong.
The corollary is uncomfortable: beginning to document the day a problem starts produces a file that is visibly reactive. It is still better than nothing, but it does not carry the same weight, and opposing counsel will point out the start date.
II What a useful entry contains
Six elements. An entry with all six is worth more than a page of narrative without them.
| Element | Why it matters |
|---|---|
| Date and time | Establishes sequence, which is frequently the whole case |
| Who was present | Identifies corroborating witnesses while you still remember |
| Where | Office, call, video meeting — affects who else may have heard |
| What was said | As close to direct quotation as you can manage |
| What was done | Actions, assignments, decisions — not impressions of them |
| What you did in response | Shows you raised concerns, and when |
The same event, recorded two ways
Weak: "Had another bad meeting with my supervisor today. He's clearly setting me up to fail and everyone can see it."
Strong: "March 4, 2026, 2:15pm, conference room B. Present: me, [supervisor], [colleague]. [Supervisor] said the Henderson project would go to [colleague] instead of me. I asked why. He said 'you're not ready for that level.' I asked what specifically I needed to demonstrate. He said he would get back to me. I sent a follow-up email at 3:40pm asking the same question in writing."
III Conduct, not motive
This is the distinction that separates documentation which helps from documentation which hurts.
Record what happened. Leave conclusions about why to the people whose job it is to draw them.
| Write this | Not this |
|---|---|
| "He assigned the project to someone else and said I was not ready." | "He is trying to force me out." |
| "I was not included in the meeting invitation." | "They are deliberately excluding me." |
| "My rating dropped from Outstanding to Fully Successful." | "My rating was retaliation for the complaint." |
| "She said the schedule change applied only to me." | "She is singling me out because of my age." |
A record that reports reads as evidence. A record that argues reads as advocacy, and invites a fight about your credibility rather than about the facts. The irony is that the left column supports the inferences in the right column far better than stating them does — because a neutral reader draws the conclusion themselves, which is always more persuasive than being told.
If you want to capture your own impression, keep it clearly separated and labeled as such. Do not blend interpretation into the factual record.
IV The email habit
The highest-value documentation technique is also the most ordinary: confirm verbal exchanges in writing, at the time, as a normal professional courtesy.
After a meeting where something consequential was said, send a short email: "Thanks for the discussion today. To confirm my understanding: the Henderson project will go to [colleague], and you will let me know what I need to demonstrate for assignments at that level. Please let me know if I have that wrong."
That email does four things at once:
- It creates a dated record in a system neither party controls unilaterally.
- It gives the other person a chance to correct it — which is what makes it fair, and what makes silence meaningful.
- It reads as diligence, not as evidence-gathering.
- An unanswered confirmation is itself a fact a fact-finder can weigh.
Write it the way you would write any professional follow-up. The moment these emails start reading like they are building a case, the working relationship changes and the practice becomes hard to sustain. Neutral, brief, and genuinely useful to both parties is the register — and it is also the register that reads best a year later.
V What you may keep
Records about you, addressed to you, or generated by you are ordinarily appropriate to retain:
- SF-50s — every one, for your entire career. They document service, grade, step, and bargaining unit status, and reconstructing them later is difficult.
- Performance appraisals and mid-year reviews.
- Your position description.
- Awards, training records, and certifications.
- Correspondence addressed to you — assignment emails, feedback, counseling memoranda.
- Your own notes about your own experience.
- Leave and earnings statements, at least the ones showing changes.
SF-50s deserve emphasis. They are the documentary spine of a federal career, they matter for service computation and retirement decades later, and agencies lose them. Keep a personal copy of every single one — see Career & Pay Topic 12.
VI Documentation Entry Builder
Select the situation and what you have. The tool returns the elements a useful entry needs and flags what to avoid.
What should this record contain?
General practice guidance. Ask your representative how it applies to an active matter.
How Credibility Decays With Delay
Relative evidentiary weight of a record by when it was created, as a general illustration of why contemporaneous documentation is treated differently from later reconstruction. Not a measured statistic — an expression of how fact-finders weigh timing.
VII What you must never take
This section matters more than everything above it, because getting it wrong creates a problem worse than the one you were documenting.
Do not remove agency records you are not authorized to have. The prohibition is strict and the consequences are independent of whatever your underlying dispute was about.
| Never remove | Why |
|---|---|
| Classified information | Criminal exposure. No exception applies because you are in a dispute. |
| Privacy Act protected records | Information about other employees is protected by law |
| Procurement-sensitive material | Separate statutory restrictions |
| Other employees' personnel records | Not yours, regardless of relevance |
| Medical records of others | Protected, and taking them is its own offense |
| Bulk agency data or systems exports | Reads as exfiltration regardless of intent |
An employee with a legitimate complaint gathers "proof" that includes material they were not authorized to remove. The agency then has a clean, provable case against them that has nothing to do with the original dispute — and the original complaint becomes background. If you believe specific agency records are relevant, that is what discovery, a FOIA or Privacy Act request, or your representative is for. Do not self-help.
If you are unsure whether something is appropriate to retain, ask before you take it — your union representative, your own counsel, or in some cases your agency ethics official.
VIII Where to store it
Two rules, both about access.
Not on government equipment. Anything on a government system is agency property and is subject to monitoring. Personal notes about your own experience belong on personal devices and personal storage.
Not only where the agency controls access. Your agency email account disappears the moment you are separated, suspended, or placed on administrative leave — frequently the exact moment you need the record most.
If losing access tomorrow would destroy your record, the record is in the wrong place today. Forwarding appropriate correspondence addressed to you to personal storage is ordinarily reasonable; check your agency's policy on forwarding, and never forward anything from the "never remove" list above.
IX How it actually gets used
Four functions, and only the first is obvious.
1. Establishing a timeline. Sequence frequently matters more than any single event. In a reprisal claim the pivotal question is usually what the agency knew and when — specifically, whether the adverse action followed the protected activity. A dated record of when you raised a concern can be the whole case.
2. Credibility. Where accounts conflict, a contemporaneous record made before the dispute existed is weighed differently from a recollection formed afterward.
3. Preserving detail. Exact dates, who was present, precise wording. Memory loses these first and they are frequently what a case turns on.
4. Supporting your reply. If an action is proposed, the reply is your record and it carries into any appeal. Having dated material to draw on turns a defensive narrative into a documented one — see Topic 16.
The same file serves an MSPB appeal, an EEO complaint, an OSC filing, or a negotiated grievance. You do not have to know which forum you will end up in — see Topic 02 and Topic 03.
X The mistakes that backfire
| Mistake | What it does |
|---|---|
| Recording conclusions instead of conduct | Turns evidence into advocacy and invites a credibility fight |
| Starting only when trouble begins | The start date is visible and undercuts the weight |
| Removing unauthorized records | Creates a clean, provable case against you |
| Recording conversations covertly | Legality varies by jurisdiction and agency policy — ask first |
| Storing everything on agency systems | Access disappears exactly when you need it |
| Writing while angry | Tone survives in the record and reads badly later |
| Discussing your file with colleagues | Not privileged; they become witnesses |
| Documenting instead of raising the issue | A file is not a remedy and does not stop anything |
The last one deserves emphasis. Documentation supports a remedy; it is not one. An employee with two years of meticulous notes who never raised the concern through any channel has a well-documented account of a problem nobody was asked to fix — and in a reprisal framework, the absence of protected activity can be decisive.
Whether you may record a conversation depends on state law, agency policy, and where you are, and the rules differ meaningfully. Some jurisdictions require all-party consent; many agencies prohibit recording on their premises or systems regardless. Ask your representative or counsel before recording anything. Getting this wrong is its own misconduct issue.
XI Making it routine
The practice only works if it survives the long stretches when nothing is wrong. Keep it small.
- One file, chronological. Newest at the bottom. No categories to maintain.
- Two minutes, same day. If it takes longer you will stop.
- A recurring reminder — end of week, five minutes, catch anything you missed.
- Save SF-50s and appraisals as they arrive, not in an annual sweep.
- Confirm consequential verbal exchanges by email as ordinary practice.
- Do not review it often. Rereading a grievance file is corrosive. File it and move on.
That last point is genuine. The purpose is to have a record if you ever need one, not to maintain a running account of everything that has gone wrong. People who reread their file frequently tend to feel worse and see patterns that may not be there. Write it, save it, close it.
XII The playbook
| Situation | What to do |
|---|---|
| Nothing is wrong right now | This is when to start. Save SF-50s and appraisals; note anything consequential. |
| A significant verbal conversation | Send a brief, neutral confirming email the same day. |
| You received unexpected negative feedback | Record date, quotes, who was present, and what you asked in response. |
| You raised a concern to management | Document when and to whom. This is often the pivotal fact. |
| You think you know why it is happening | Record the conduct. Leave the conclusion out of the factual file. |
| You want records you cannot access | Discovery, FOIA, Privacy Act request, or your representative. Never self-help. |
| Considering recording a conversation | Ask first. Law and agency policy vary and getting it wrong is misconduct. |
| An action has been proposed | Your file feeds the reply, and the reply carries into any appeal. |
Set this up this week
- Create one chronological file on personal storage, not on government equipment.
- Save a personal copy of every SF-50 you have, and every one going forward.
- Save your performance appraisals, position description, awards, and training records.
- Set a weekly five-minute reminder to note anything consequential from that week.
- Record six elements each time: date and time, who was present, where, what was said, what was done, what you did.
- Write conduct, not motive — describe what happened and leave conclusions to the people who draw them.
- Confirm consequential verbal exchanges by brief, neutral email the same day.
- Never remove classified, Privacy Act protected, procurement-sensitive, or other employees' records.
- Ask your representative or counsel before recording any conversation.
- Remember that a file supports a remedy but is not one — raise concerns through an actual channel.
Frequently asked questions
Because federal proceedings move slowly. An MSPB appeal, an EEO complaint, or an investigation can reach a hearing a year or more after the events, and by then everyone's recollection has degraded and shifted toward their own interest. A record made at the time — dated, specific, and written before anyone knew there would be a dispute — carries weight that a reconstruction written afterward simply does not. The practice costs nothing and its entire value depends on having started before you needed it.
Date and time, who was present, where it happened, what was said or done in as close to direct quotation as you can manage, and what you did in response. Keep it factual and specific. The strongest entries read like a neutral observer's account rather than an argument, because the person reading it later will be a stranger evaluating credibility, and a record that argues its own conclusion reads as advocacy while a record that reports events reads as evidence.
Describe conduct, not motive. Write what was said and done; leave conclusions about why to the people whose job it is to draw them. A note reading "he assigned the project to someone else and told me I was not ready" is useful. A note reading "he is trying to force me out because he does not like me" is an inference that invites a credibility fight and can make your entire file look like a grievance narrative rather than a record. If you must capture your impression, keep it clearly separate and labeled.
Some, with real limits. Your own personnel records — SF-50s, performance appraisals, position description, training records, awards, and correspondence addressed to you — are ordinarily appropriate to retain. What you must not do is remove agency records you are not authorized to have, and that prohibition is strict for anything classified, anything protected under the Privacy Act, procurement-sensitive material, and information about other employees. Improper removal is its own offense and has ended careers independently of whatever the original dispute was about.
Not on government equipment, and not only in an agency email account you can lose access to on your last day. Personal notes about your own experience belong on personal devices and personal storage. Be aware that anything on a government system is subject to monitoring and is agency property, and that access disappears immediately on separation or suspension. The practical rule is that if losing access tomorrow would destroy your record, the record is in the wrong place today.
They can be. Records you create may become discoverable in litigation or an administrative proceeding, which is a reason to write them as though a neutral third party will read them — because one may. It is not a reason to avoid writing. The consistent experience of practitioners in this area is that the absence of contemporaneous records hurts employees far more often than their content does. Write carefully rather than not at all, and ask your representative or counsel how the rules apply to your matter.
In several ways. It establishes a timeline, which frequently matters more than any single event because patterns and sequence are what proceedings turn on. It supports or undermines credibility when accounts conflict. It preserves detail that memory loses — exact dates, who was present, precise wording. And it can demonstrate that you raised a concern at a particular time, which is often the pivotal fact in a reprisal claim where the question is what the agency knew and when.
No, and treating it that way is what stops people from starting. Documentation is ordinary professional practice — confirming a verbal assignment in an email, keeping your own record of feedback, saving your appraisals. Most of what you record will never matter. The point is that you cannot identify in advance which conversation will turn out to be the important one, and the value of the practice comes entirely from it being routine rather than something you begin the day a problem starts.