Check Washington's annual file-review right and former-worker rebuttal period, Pennsylvania's seven-day workweek, New Hampshire's six-month income tests, and Washington's January rate changes.
Key takeaways
- Log Washington file-review petitions and the action taken.
- Track former workers' rebuttal requests and confirm the applicable period.
- Record the selected Pennsylvania workweek start day.
- Check New Hampshire income tests and Washington rate changes against the official pages.
Why these dates matter
Hiring files and pay periods look like routine paperwork, but several of the rules that govern them run on a clock. A state may give an employee a yearly right to ask for a review of their file. It may give a former employee a fixed period in which to add a statement. It may define a workweek that your pay schedule has to fit around. Each of these is a date that is easy to miss, because nothing in the daily work of hiring and payroll reminds you it exists.
This post covers three time limits to check, plus two more dates that come up in the same states. It is written for HR leads and owners of small staffing teams who keep hiring files and set pay periods for workers in Washington, Pennsylvania and New Hampshire. Each rule links to its official page, so you can read the wording yourself rather than rely on a summary, including this one.
Treat this as general information, not legal advice. Laws change, and the quoted text here is what was checked when this post was written. Before you act on a rule that affects a real decision, reread the official page and talk with an employment attorney if the answer matters for your business.
Limit 1: Washington employees can ask for a yearly file review
Washington's rules on personnel files begin with the employee's right to ask. Under RCW 49.12.250, an employee may petition once a year that the employer review all information in the employee's personnel file. The statute describes which files are covered: those "regularly maintained by the employer as a part of the employer's business records or are subject to reference for information given to persons outside of the company."
Read that phrase slowly, because it sets the scope of the review. A record is in scope when it is kept as a regular business record. A record is also in scope when it is the kind of thing the company refers to when it gives information about a worker to people outside the company, such as a reference check from a prospective employer. That means the review is not limited to the one folder in your HR cabinet. Before you tell a worker their file has been reviewed, check the places where you keep records about them: the applicant tracking system, payroll notes, shared drives and any written reference responses you have sent. For related record checks, use the recruiting records audit.
Build a routine for handling petitions when they arrive. You can also schedule an internal accuracy check around the worker's start anniversary, so the date is already in the calendar. Another option is a company-wide review month. Keep that internal schedule separate from responding to an employee's petition, and record when the review happened and what came of it.
A simple log helps. For each Washington worker, record the date of each petition, the date you completed the review, what you changed or corrected, and what you left as it was. Keep this log with the hiring file or in the same system, so that if a worker asks what was reviewed last year, you can answer from records rather than memory.
One practical point: the employee's petition is what triggers the statute's right, but you do not need to wait for a petition to keep files accurate. Waiting makes the work reactive. A routine review that runs ahead of petitions gives you time to fix errors before a worker asks about them.
When a petition does arrive, answer it in writing and keep the reply with the log. The reply should say the date the petition was received, the date the review is scheduled or completed, and whether any changes were made. A short, dated reply gives the worker a clear record of what happened. If the review turns up a question you cannot answer from your own records, say so in the reply and note what you are checking next, rather than guessing.
Limit 2: Former employees keep a rebuttal right for up to two years
The second limit deals with disagreement. Under the same statute, RCW 49.12.250, an employee who does not agree with the employer's determination may ask to have a statement placed in the personnel file. The statute calls that statement one "containing the employee's rebuttal or correction." In plain terms, the worker can put their side of the story in the file alongside your decision.
For a current employee, the practice is straightforward. When someone disagrees with a decision about their file, record the decision and the date, record the worker's request, and place their statement in the file when it arrives. Keep their statement as written. Note the date you received it. If you are not sure whether a correction is accurate, say so in your reply instead of quietly changing the record.
Former employees are where the time limit appears. The same section says that "a former employee shall retain the right of rebuttal or correction for a period not to exceed two years." Before treating a request as late, confirm how the applicable period runs.
Before you set a date, read the full section and confirm the start point. Until you have confirmed it, record each departure date in the file, so you have what you need once you know how to count.
For a departing worker, a short checklist is useful. Record the last day worked. Note in the file that the worker may request a rebuttal or correction. Set a reminder based on the start point you confirmed. When the reminder comes up, check whether any request is still open and whether your records match what the worker might dispute.
This is where small teams get caught. A worker who leaves in a hurry may not return with a dispute for a long time, and by then the person who handled their file may have moved on. A written note made at departure preserves what the file said and when the record was closed.
Limit 3: Pennsylvania's workweek is seven consecutive days
Pennsylvania's rule is simple to state but easy to misapply. The regulation at 34 Pa. Code section 231.42 defines the term: "The term workweek shall mean a period of 7 consecutive days starting on any day selected by the employer."
That definition has three parts you need to keep in view. The period is seven days. The days run consecutively, with no gaps. And the start day is selected by the employer, which means the choice belongs to you. You do not have to start on a Monday. This definition does not require the same start day for every worker.
Here is how it plays out. Suppose you choose a Sunday start. Each workweek then runs Sunday through Saturday, and the next one begins the following Sunday. If your payroll runs every two weeks, or on the 15th and the last day of each month, the pay period and the workweek will not line up one-to-one. That gap is the reason to check your pay schedule against the workweek definition before you finalize it, not after the first payroll has run.
If you run more than one pay schedule, such as a weekly schedule for hourly temporary workers and a monthly one for office staff, each schedule needs to be checked against the same workweek definition. A note in your pay policy that names the workweek start day, and shows an example of how a pay period maps to it, prevents confusion when someone new takes over payroll. Review Pennsylvania pay records alongside that policy.
Here are the steps to take:
- Write the workweek start day into your Pennsylvania pay policy in one sentence, so the choice is on record.
- Check that timekeeping and payroll records reflect the selected start day for each worker.
- Map each pay schedule to the workweek with a short worked example, using one real week's dates.
- If you ever change the start day, note the date of the change and the reason, and reread the regulation before you make the change.
Two more dates for New Hampshire and Washington
The next two items are not about files or workweeks. They are a test and a fixed effective date that show up in pay rules. They are easy to overlook because they do not arrive every pay period.
New Hampshire's six-month income tests
New Hampshire's minimum hourly rate section, RSA 279:21, includes tests comparing business income across six-month periods.
Another requirement in the same section states that "the establishment in the previous year shall have received at least 75 percent of its income within 6 months." The section also clarifies that "the 6 months, however, need not be 6 consecutive months." Your comparison is therefore not limited to January through June.
These tests are requirements inside a specific part of the section. Read the full text before you rely on any of them. Your practical job is to decide whether the test could apply to any New Hampshire operation you run, and if it could, to pull the previous calendar year's income by month. Monthly figures make it possible to build the six-month comparisons the statute describes. If getting those figures takes weeks, start now, because the test looks at a specific prior year. Check the available records before attempting the comparison.
Washington's January 1 rate changes
Washington's minimum wage statute, RCW 49.46.020, sets a fixed effective date for adjusted rates. The text says: "Each adjusted minimum wage rate calculated under this subsection (2)(b) takes effect on the following January 1st."
Look up the current rate on the official page before you set pay for any new year, and do not carry last year's figure forward out of habit.
A yearly routine helps here. In the fall, check the official page for any adjusted rate calculated under that subsection. Update your pay tables, offer letters, job postings and any worker notices so the new rate is ready when it takes effect. Then check any pay period that spans January 1, so the change does not catch you partway through a period.
If your Washington workforce is spread across several pay schedules, give each schedule its own check. A rate change that lands in the middle of a two-week period needs a plan for the hours already worked, and that plan should be written down before the first affected pay run. Keep the written plan with the pay policy, so the next person who runs payroll can follow it without asking you.
Common mistakes to avoid
The most common mistake is treating each of these rules as a one-time setup task. Keep responsibility for checking requests, dates and pay schedules clear when someone new takes over.
A second mistake is relying on a summary instead of the official text. Summaries drop the qualifiers that matter. For personnel files, check reference responses as well as the main folder.
A third mistake is recording decisions informally. A note in an email or a verbal assurance that a file is "closed" can be difficult to find when a former worker returns with a rebuttal. Put the decision, the date, and any statement the worker submitted into the file itself.
A fourth mistake is assuming the clock started when you think it did. Confirm the start point and the measurement method in the full text before you set a reminder or pull a report.
A fifth mistake is letting one rule's date drive another rule's decisions without checking. The Washington rate date, the Pennsylvania workweek and the New Hampshire six-month window are separate rules with separate clocks. Keep a short table with a row for each state and a column for each rule, so you can see at a glance which dates are running and which are still waiting for a check against the official text.
A four-week checklist
If you want a place to start, this sequence covers the items in this post without overwhelming a small team:
- Week 1: List every Washington worker's personnel file, and mark each file's internal review date.
- Week 1: Write your Pennsylvania workweek start day into your pay policy.
- Week 2: Compare each Pennsylvania pay schedule to a seven-day workweek, and note any mismatch.
- Week 2: Set up a log for file petitions, file reviews, and rebuttal statements.
- Week 3: For each former employee on file, record the departure date and keep it visible.
- Week 3: Read the full text of RCW 49.12.250 to confirm when the two-year rebuttal period starts.
- Week 4: If the New Hampshire six-month test could apply, pull the previous calendar year's income by month.
- Ongoing: Put January 1 on the calendar every year, and check for any Washington rate adjustment calculated under RCW 49.46.020.
Illustrative example: Check a petition log
An illustrative team has 20 Washington workers and receives 10 file-review petitions. It checks that each petition has a received date, a review date and an outcome recorded. The other 10 workers have not petitioned in this example; an internal review schedule does not replace responding to requests when they arrive.
Where to check the rules
Each rule in this post links to its official page. Keep these four links in your compliance folder:
- RCW 49.12.250, for personnel file petitions and rebuttal statements in Washington.
- RCW 49.46.020, for Washington minimum wage adjustments and their January 1 effective date.
- 34 Pa. Code section 231.42, for the Pennsylvania workweek definition.
- RSA 279:21, for New Hampshire's minimum hourly rate section and its six-month test.
A practical next step
Today, open your Pennsylvania pay policy and check that it records the selected workweek start day for each worker. Compare that entry with the timekeeping records and note any mismatch to resolve.
Related guides: Wisconsin hiring discrimination back pay: 3 limits · Check 4 state limits before you answer a reference call · Hiring claim filing deadlines: 3 state clocks.
Common questions
Does Pennsylvania require the same start day for every worker?
The workweek definition lets the employer select a start day without requiring one shared day for every worker. Record the selected day clearly in your pay policy.
How should a team record a file-review petition?
Record when it arrived, when the review happened and what changed. Keep the reply with the review log so the record is easy to find.
What should a team check before setting a reminder?
Confirm the applicable rule's start point and how the period is counted. Read the linked official page before using the reminder for a real decision.