Make NY personnel-file requests a five-day routine before Nov. 8
Turn personnel files into a mapped, logged, notice-ready workflow before New York's Nov. 8, 2026 deadline, with a six-step checklist HR can run in a week.
A written request for a personnel file starts a clock. Starting November 8, 2026, New York employers must deliver reproductions of personnel files to present and former workers within five business days of receiving a written request, free of charge. The rule covers public and private employers alike, regardless of size.
Governor Hochul has said the state will work with lawmakers to clarify and narrow which records fall under the law, but the current text still controls until any change is signed into law. Build the process around the statute as it exists now.
The deadline is a workflow problem, not a filing problem
A file that is hard to assemble is a file that is hard to produce on time. The law requires the outcome; the workflow is what makes it repeatable. The process needs a route for written requests, a flag for entries that may hurt an employee, a hold after separation, and a packet for unresolved disputes. The New York Attorney General can enforce the law with civil penalties from $500 to $2,500.
The six-step checklist makes the deadline testable
The statute sets the duties; the checklist is the operational proof.
- Inventory covered records: choose one active file and one separated file, then list every document that belongs in the personnel record.
- Centralize a request log: make it possible to show where a written request was received, dated, assigned, and produced.
- Set a five-business-day, no-cost production process: run a sample request and confirm the copy can be delivered on time and without charge.
- Trigger 10-day negative-entry notices: when an entry is added that may affect the employee's job, promotion, transfer, extra compensation, or possible discipline, record the entry date and notice date so the gap is no more than 10 days.
- Set three-year post-separation no-deletion retention: keep the record for at least three years after separation, and make sure no deletion job runs before that date.
- Attach employee rebuttals to disputed information: if a dispute is not resolved, keep the employee's written statement with the disputed item so both travel together when the record goes to a third party.
The first two steps are inventory work. The last four are proof steps: they turn a legal duty into a date, a notice, a hold, or a packet.
The inventory step forces HR to separate the personnel record from the broader HR system. The log step forces HR to treat a request as a dated event, not a casual ask.
The log, notice, and rebuttal dates prove the process
A document outside the inventory is outside the file. A scattered folder can hide an entry that may hurt an employee. The request log ties the clock to the employee's ask, not to later recollection.
Begin with the employee's own file rather than the whole HR system. Include the documents that would follow the employee if the file were sent to a third party. The log should show when the request arrived, who asked, what was requested, when the file was produced, and how it was delivered.
A negative entry matters because it can affect the employee's standing. The notice duty starts when the entry is added, ahead of any later discovery by the employee. Put the notice date in the same system as the entry. If the dates live in separate emails or meetings, the file is harder to defend.
A manager can add a negative entry in one system and send the notice from another. The file should show both events as one sequence.
Separation starts the retention clock. Put the hold in the records system rather than in a person's memory. A deletion job that runs too early can erase documents the employer may need later. Make the retention setting visible in the file record, where a reviewer can check it without opening every document.
The retention hold is a control, not a cleanup task. It should survive staff turnover and system changes.
A dispute turns the file into a packet. Keep the employee's written statement with the disputed item, rather than in a separate email thread. When the file is produced, the two pieces should travel together. Before the deadline, run one mock request for a current employee and one for a former employee. Check that the log shows the start date, that the production can be made on time, and that any negative entry has a matching notice.