HB 1308 and the Personnel File You Can’t Find

The request that starts a clock

It usually arrives as a one-line email: “Could you please send me a copy of my personnel file?”

Since July 27, 2025, that sentence starts a 21-calendar-day clock for most Washington employers. Calendar days, not business days. If the request lands on Monday, November 2, 2026, day 21 is Monday, November 23, 2026 (counting the day after receipt as day one; how you count is a question for your employment counsel).

Twenty-one days sounds like plenty until you try to answer the question honestly: where is all of this person’s file? Not the folder labeled with their name. All of it. The application in the recruiting inbox, the 2023 review a manager kept in their own OneDrive, the leave paperwork in the benefits portal, the payroll history that only exists at the payroll vendor.

Where I am coming from

I spent my first twelve years in legal working in accounting and finance, and the last fifteen in overall firm administration, HR included. I know how a “complete file” tends to get assembled when nobody planned for it: quickly, from memory, and with a quiet hope that nothing important lived anywhere else.

I have been building out a full plan for using Claude to do this work properly, from reading the statute to reorganizing the files to handling the next request. This article is the short version of that plan, plus enough of a starting point that you can begin on your own.

What the law requires

HB 1308 (Laws of 2025, chapter 273) amended RCW 49.12.240 and RCW 49.12.250 and added a new section, RCW 49.12.261. The short list:

• What counts as the personnel file. Six categories, “if the employer creates such records”: job application records, performance evaluations, nonactive or closed disciplinary records, leave and reasonable accommodation records, payroll records, and employment agreements.
• Who can ask. An employee, a former employee, or their designee. “Former employee” means someone who separated within three years of the request.
• How fast, and at what cost. A copy within 21 calendar days, at no cost to the person asking.
• A second document for former employees. On a former employee’s written request, a signed written statement of the effective date of discharge, whether the employer had a reason, and if so, the reasons. Also due within 21 calendar days.

The law does not require you to create records you never created, and it does not set a retention schedule. It does expect you to produce what you have, completely, on time. (Washington L&I’s summary page is a good plain-language companion to the statute.)

What it costs to miss

This is the part that changed. Before HB 1308 there was no private right of action. Now an employee or former employee can sue in superior court, and RCW 49.12.261 sets statutory damages for each violation:

• $250 if the complete file or the discharge statement is not provided within 21 calendar days;
• $500 if not provided within 28 calendar days;
• $1,000 if provided later than 35 calendar days; and
• $500 for any other violation.

Those numbers look manageable. The line I would pay attention to is the one above them: the employee “for each violation will be entitled to equitable relief, statutory damages, and reasonable attorneys’ fees and costs.” A $500 claim with the other side’s legal fees attached is not a $500 problem.

Two more details matter operationally. The employee must give a notice of intent to sue before filing, but that notice “may be provided to the employer with the initial request,” and suit can be filed five calendar days after it. So the first email may already carry the warning, and someone needs to read it that way on day one. And I found no small-employer exemption, cure period, or good-faith defense in the statute’s text. (How the tiers apply to a particular set of facts is a question for your counsel, not for me and not for an AI.)

Why this is hard in practice

The statute is two pages. The files are the problem.

To test my plan, I built a fictional small company with eight employee folders holding 149 files, and I planted the kinds of problems that show up in real businesses. Some of them:

• Form I-9s with passport copies sitting in the general personnel file.
• A doctor’s note with medical detail filed alongside performance reviews.
• Employees who received raises in 2022, 2024 and 2025 with no performance review on file after 2021.
• A written warning the employee never signed, with no note that they refused.
• An offer letter signed by the company only.
• Former employees’ folders mixed in with active ones, unmarked.
• Two owner-officers on the payroll with no personnel folder at all.
• An office manager’s checklist that instructs staff to file I-9s and doctor’s notes in the personnel file, which builds the misfiling into the process itself.

None of these is exotic. Every one of them turns a 21-day request into a scramble, and some of them (the medical record and the I-9 in particular) are things you do not want to hand to an employee’s attorney without someone deciding first whether they belong in the file at all.

Where Claude takes on the heavy lifting

The good news is that most of this work is reading, sorting, comparing and listing. That is exactly what Claude is good at, and it does it in hours instead of the weeks it takes a person working between other responsibilities.

The plan I built breaks the work into stages, each ending in a document a person reviews before the next stage starts:

1. Intake. A short questionnaire for HR, counsel and IT: where records live, who your counsel is, who signs the discharge statement, and whether Claude may read document content or only file names.
2. Preliminary audit. Claude reads the law and audits about three employee files. This is the proof of concept, done where you can watch it.
3. Full audit. Every file classified into the six statutory categories, with an employee-by-category matrix, a gap report, and a separate list of items that may not belong in the general file at all (medical, I-9, investigations, privileged material). Every one of those goes to counsel.
4. New home. A clean folder structure built around the six categories, with former employees separated from active ones.
5. Rename and move. Claude proposes a uniform naming convention and a move list. A named person approves it, Claude runs it as a dry run first, and only then does anything move.
6. Post-move audit. Claude re-checks that everything landed where the approved list said it would.
7. Request drill. A rehearsal of an actual request, including the deadline tracker, the completeness checklist, and the discharge statement template, so the first real one is not the first time.

Throughout, Claude proposes and a human decides. It does not make legal calls, it does not send anything to anyone, and it treats instructions found inside documents as data.

Getting there took a lot of testing. I wrote an answer key for the fictional company so every pass could be scored against a known list of problems rather than against my impression of the output. Then I ran the audit, scored it, adjusted the instructions, and ran it again, round after round. Each round changed something real: what Claude is allowed to open and why, how it records what it opened, how it reports a gap without drawing a legal conclusion, and how it handles records that have to be read to be judged (you cannot tell that a warning is unsigned from its file name). That testing is also why the decision about whether Claude may read document content belongs to the client, in writing, at the start. It is the difference between a tidy folder and a complete file.

Getting started on your own

If you want to begin without outside help, here is a safe first pass. It works from file names only, which keeps the contents of your personnel files out of the conversation entirely.

1. Use the right account. Do this in a paid business plan whose data retention and training terms you have actually read, not a free or personal account. Personnel files are some of the most sensitive records your business holds.

2. Get a listing, not the files. Export a list of every file path in your HR folders. On a Mac, in Terminal from the HR folder: find . -type f > listing.txt. On Windows, in Command Prompt from the HR folder: dir /s /b > listing.txt. Add any other locations you know about (the recruiting inbox export, the benefits portal download).

3. Replace names with employee numbers. Before the listing goes anywhere, swap every employee name in folder and file names for the employee number from your payroll system. Keep the crosswalk to yourself. Then read the result once more for names that slipped through.

4. Ask Claude to map it. Something like:

Attached is a list of file paths from our HR folders. Employee names have been replaced with employee IDs. Using only the paths and file names, classify each file into one of the six personnel file categories in RCW 49.12.240(2), or mark it “not a personnel record,” “may need separate storage (medical, I-9, investigation, privileged): counsel to decide,” or “unknown.” Then build a table of employees by category, and list every gap as “none found, confirm whether one was created.” Do not draw legal conclusions. Where interpretation is needed, write the question for our counsel.

5. Read the gap list against what you know. Claude will be wrong in places, and it will sometimes fill a gap with an assumption without saying so. Correct it, ask where each conclusion came from, and keep the list of corrections. That list becomes the start of your procedure.

6. Build the request log before you need it. Ask Claude to draft a simple request tracker (received date, requester, day 21, 28 and 35, delivered date) and a one-page checklist for the person who handles requests. Have counsel review the discharge statement template and the checklist before you rely on them.

That gets you a map of what you have and what is missing. It will not tell you whether a warning is signed, whether a review is still a draft, or what is sitting in a manager’s mailbox. That is where the content-level work starts.

Where I come in

The starting point above is real, and plenty of employers can take it a long way. The harder parts are the ones that need judgment about systems and data handling, not just prompts:

• Setting up content reads safely: inside your own Microsoft 365 tenant and your own Claude organization, on a machine you control, with a written authorization, a confidentiality agreement, and a clean wipe at the end.
• Finding the records that are not in the HR folder: personal OneDrives, mailboxes, document management systems, and payroll vendor exports.
• Running the reorganization so that nothing moves without an approved list and a dry run.
• Handing your team a working request process, trained and rehearsed, with your counsel making every legal call.

I have laid out the full plan so Claude can implement it against your own needs, not a generic template. If you are a Washington employer looking at a set of personnel files you would not want to produce in 21 days, tell me where your records live today and I will tell you how I would approach it.

This article describes a business process. It is not legal advice, and I am not an attorney. Talk to your employment counsel about how HB 1308 applies to your business.

Richard L. Wood, MBA is principal at kapchur consulting, where he helps business leaders and professional services firms deploy operational and financial solutions through AI implementation. He can be reached through the contact page.