Why and How to Secure Records After an Incident or Claim
Ask any administrator whether their organization keeps records on staff and volunteers, and the answer is almost always yes. Ask that same administrator how quickly the organization can produce every record connected to one specific person, from every system. Their confidence usually drops. The problem is rarely that the records don’t exist. The more common problem is that nobody has ever pulled them into one place before an injury or allegation made them important.
That gap between having records and being able to produce them quickly is one place where organizations get hurt in litigation. When a concern surfaces about a staff member or volunteer, the questions that follow aren’t limited to what happened this one time. They’re about what the organization already knew. Had someone raised a prior concern about this person? Had they completed the training your policy requires? Did a supervisor ever document raising an issue with them before? Records you already have answer those questions. The difficult job can be finding them.
Old Records Can Matter More Than Recent Ones
There’s a reason to prioritize locating old records over polishing a new account of what just happened. A jury may treat contemporaneous records, made at or near the time something occurred, as more credible than anything your organization writes after a concern surfaces. A training completion log from last spring or a supervision note from six months ago can carry real weight, precisely because nobody wrote it with a lawsuit in mind. The most detailed, carefully worded account your organization produces this week may still look, fairly or not, like an attempt to change the facts.
There also can be a preservation problem, and it moves faster than most administrators expect. Once an organization has a specific, credible reason to anticipate a legal claim, most states impose a duty to preserve records connected to that claim. This duty covers records that already existed before the concern ever surfaced, not just new ones. Routine housekeeping doesn’t pause itself. Most HR systems clear out personnel files on schedule after someone leaves. Training platforms archive or delete old completion data automatically. Email systems auto-purge messages after a set retention period. None of these processes stop just because they should. Suppose a record disappears under a routine schedule after your organization had reason to expect a claim. A court can then instruct a jury to assume the missing record would have hurt you.
Where to Look for These Records
Most organizations don’t keep everything on one person in a single system. Departments, platforms, and individual inboxes each end up holding a different piece of the puzzle.
Personnel and Hiring Records
Start with HR software or physical personnel files, but don’t stop there. If your organization has changed HR platforms, changed executive directors, or merged with another program, confirm that historical files actually made the transition. Background check results are a frequent blind spot. Many organizations keep only a pass or fail notation in the internal file. The full report often sits in the screening vendor’s own portal instead. Reference check notes, if your organization keeps them, often sit in the hiring manager’s personal files rather than a central system. Look in all these places to be sure you have all the documents you need.
Training Records
If your organization uses a learning management system, that system usually holds completion records with reliable timestamps. In-person training often leaves only physical sign-in sheets, and those tend to end up in a binder in someone’s office rather than a shared file. Whoever coordinates volunteers, rather than HR, often tracks volunteer training records separately. Those records are the most likely to go missing entirely.
History with the Organization
This category rarely sits in one tidy place. Staff rarely log informal concerns the same way they log formal complaints. Check the direct supervisor’s email and personal notes, the program director’s files, any internal incident log your organization maintains, and board meeting minutes if someone ever reported a concern serious enough to reach the board. Don’t assume that nobody documented something just because it never became a formal complaint. It may exist as a throwaway line in an email nobody thought to flag.
Communications
Search email specifically for this person’s name, not just the organization’s shared drives or official files. The supervisor’s inbox and the inbox of whoever originally raised any concern are the two most likely places to find something relevant. Often nobody ever filed it anywhere else.
If you check a location where a record should exist and come up empty, don’t just move on quietly. Write down where you looked, when, and what you found instead. A gap you documented honestly reads very differently than a gap that surfaces for the first time when someone else goes looking.
Freeze Routine Destruction the Moment You Start Looking
The instant you begin pulling these records together, put a hold on any routine destruction schedule. Put the hold in writing and send it directly to whoever controls each individual system. The person who manages your HR software is often not the same person who manages your training platform or your email server. A single notice to one department will not cover everything. Loop in your attorney on how broad the hold should be and how long it needs to remain in place. A hold that’s too narrow leaves gaps. A hold nobody ever lifts becomes its own administrative burden.
Assign One Person to Own the Search
The single most common failure isn’t that these records don’t exist somewhere in your organization. It’s that no single person is responsible for finding all of them. Pieces sit scattered across HR, a supervisor’s inbox, a training platform, and a vendor portal while everyone assumes someone else has already pulled it together. Name one person, by title, not by department, whose job is to track down every category above and consolidate what they find. That person doesn’t need to interpret what any of it means. Their job is narrower: make sure that when someone asks what the organization knew and when, the answer exists in one place instead of four.
The Bottom Line
You cannot recreate a training log you never kept, or recover a supervision note a routine schedule cleared out two years ago. You can find out today exactly which records your organization actually has on any given staff member or volunteer, and whether anyone could produce all of them by the next discovery deadline. When you have an incident or claim, try to get ahead of the inevitable document requests by starting your search as soon as possible.
Want to go deeper? Our on-demand course, Responding to Serious Incidents & Allegations, covers how to organize and preserve these records before a real concern forces the question.
