The great majority of minimum wage increases take effect on 1 January, which makes them easy to anticipate and easy for payroll to handle. A handful arrive mid-year instead — Alaska and Oregon on 1 July, Florida on 30 September — and those are the ones that get missed, because nothing in the annual cycle prompts anybody to check. Around eighty-eight jurisdictions changed a rate during 2026 across state and local layers, and most local ordinances are indexed to rise automatically.
The January cluster, and why it is the easy part
If you look at when minimum wage rates actually change, the picture is strikingly lopsided. The overwhelming majority move on 1 January, which is convenient for everybody involved. Payroll systems are already being touched for the new tax year, the change is widely reported in advance, and an employer who updates once in early January has usually caught everything that applies to them. The timing does most of the compliance work by itself.
That convenience is exactly why January increases rarely produce underpayment. Somebody is already looking closely at the payroll that week for entirely unrelated reasons. The rate change arrives alongside a dozen other annual adjustments and gets processed as part of a routine that would have run whether or not the minimum wage moved at all.
Which means the interesting question is not what happens in January at all. It is what happens in the months when nothing else prompts a review of anybody’s pay. That is where a rate rises and a payslip quietly does not, and where the gap can run for months before anybody notices it.
The ones that do not follow the crowd
A small group of states set their increases mid-year, and they are worth knowing by name if you work in one. Alaska and Oregon both raise on 1 July. Florida raises on 30 September, which is the most isolated date of the lot and sits in a month when nobody is thinking about wage floors.
The reason these matter disproportionately is structural rather than about the size of the increase. A July rise lands in the middle of a quarter, outside any annual review cycle, at a point when the payroll calendar has nothing else demanding attention. An employer who genuinely intends to comply can still miss it simply because nothing arrived to remind them.
Local ordinances add their own dates on top of all this. Many city and county rates rise on 1 July rather than 1 January, which means a worker in one of those places can see two separate increases in a single year. The state one lands in January and the local one in July, with only the higher of the two actually binding at any given moment. Keeping track of which is currently operative is genuinely fiddly, and it is why the local layer is worth a calendar entry of its own.
Why these are worth putting in a calendar
The practical value of knowing your own date is that it converts a vague suspicion into a specific check. If you know your state raises on 1 July, you look at the first payslip issued after that date and compare the hourly rate against the new figure. Either it moved, in which case you are done in ten seconds, or you now have a precise question with a date attached. Precise questions get answered; general impressions get deflected.
That is a far better position than noticing six months later that something feels off. Wage claims run on limitation periods, so a shortfall discovered promptly is fully recoverable while one discovered a year on may have partly expired. The calendar entry costs thirty seconds and it is the cheapest protection available on this subject.
It also helps in the ordinary case where nothing has gone wrong at all. Knowing the rate rose and seeing that it rose on time is worth something in itself. It tells you the employer’s payroll is being actively maintained rather than left to drift, which is a reasonable thing to know about a place you work and a mildly reassuring one.
Indexing is why the figure keeps moving
Most jurisdictions that raised their minimum in the last decade attached an indexing mechanism at the same time. The rate then rises automatically each year with a measure of price growth rather than requiring a fresh legislative vote. That is why roughly eighty-eight jurisdictions changed a rate during 2026 without any of it being newsworthy anywhere. Indexing was designed precisely to take the annual argument out of it, and it has largely succeeded.
Indexing has an important consequence for how you should read anything written about minimum wage rates, including this article. A figure quoted in a piece written last year is not merely possibly out of date; in an indexed jurisdiction it is almost certainly wrong now, by a small amount that compounds. The mechanism is durable and the number is not, which is why it is worth learning where to look rather than what the rate currently is.
The states without indexing behave differently and are worth recognizing. Where a rate only moves when the legislature acts, it can sit unchanged for years and then jump substantially in one step. Both patterns exist and they produce very different experiences for anybody earning near the floor.
Multi-year schedules and what they let you plan
Several jurisdictions have legislated a series of increases stretching years ahead, with each step’s date and figure fixed in advance rather than left to indexing. Where one of those applies to you, the entire schedule is published and public. You can see exactly what the floor will be in two or three years’ time, which is a rare thing to be able to say about any aspect of future pay.
That is unusual and genuinely useful. Most questions about future pay are guesses; this one has an answer written down. If you are weighing a job near the minimum, or deciding whether a wage will keep pace with a rent increase you already know about, a published schedule turns an unanswerable question into arithmetic.
It also tells you something about the direction of the local market above the floor. Employers paying a few dollars above a rising minimum face compression each time it steps up, and they generally respond by moving the whole bottom of their range rather than letting it collapse. A scheduled increase is therefore a weak signal about pay slightly above the floor as well as at it.
What is not scheduled at all
The federal rate. It has been $7.25 since July 2009, there is no indexing mechanism attached to it, and nothing is currently scheduled to change it. That is the single most important scheduling fact in this whole area, because it explains why every other layer has had to move.
The tipped cash wage of $2.13 sits in the same position and has been fixed since 1991, which is longer still. Neither figure rises unless Congress acts, and no mechanism exists to move them otherwise. Both are worth treating as genuinely fixed points rather than as numbers that might quietly update while you are not watching, because they will not.
How to set this up for yourself in five minutes
Find your state’s increase date, and your city or county’s date if one applies to you, then put both in a calendar with a reminder a week beforehand. Note the incoming figure next to each where it has been published, since indexed rates are usually announced a few months in advance. That way the reminder arrives with the answer already attached and the check takes seconds rather than requiring fresh research.
Then, on the first payslip issued after each date, check the hourly rate against the new figure. If it did not move, raise it as a question rather than a complaint. A rate that failed to update is very often a payroll system nobody remembered to tell, and those get fixed quickly when somebody points at a specific date and a specific number. Framing it as an error to correct rather than a wrong to redress gets you there faster.
This is general information about how scheduling works rather than legal advice about your pay. Dates and figures change and local ordinances change most often, so your state or city labor office holds the current schedule and will answer a question without any obligation to file anything.
Common questions
When do most minimum wage increases happen?
On 1 January. That timing is convenient — payroll is already being touched for the new tax year — which is why January increases rarely produce underpayment.
Which states raise mid-year?
Alaska and Oregon on 1 July, and Florida on 30 September. Those dates sit outside any annual review cycle, which is exactly why they get missed.
Why do mid-year dates matter more?
Because nothing else prompts a payroll review then. An employer who genuinely intends to comply can still miss a July rise because nothing arrived to remind them.
Can I see two increases in one year?
Yes, where a local ordinance rises on a different date from the state rate. Only the higher of the two binds at any given moment.
Why does the rate change so often?
Most jurisdictions that raised their minimum in the last decade attached indexing, so rates rise automatically with prices. Around eighty-eight jurisdictions changed a rate during 2026.
Does that affect articles about rates?
Yes. In an indexed jurisdiction, a figure quoted last year is almost certainly wrong now. Learn where to look rather than what the rate currently is.
What is a multi-year schedule worth?
It turns an unanswerable question into arithmetic. Where one applies, you can see exactly what the floor will be in two or three years and plan against it.
What never gets scheduled?
The federal rate. $7.25 since July 2009 with no indexing, and the $2.13 tipped cash wage fixed since 1991. Neither rises unless Congress acts.