How to Track and Use Massachusetts Minimum Wage History
I used to spend my Tuesday afternoons digging through old statute amendments just to confirm what wage rate applied on a specific date back in 2012. It wasn't fun. The Massachusetts minimum wage has changed enough times, and in enough irregular increments, that you can't just guess your way through a payroll audit. You need the actual trajectory, and you need to know how the tipped employee exception and local ordinance interactions complicate things. The state minimum wage started at $2.25 per hour in 1968 when the minimum wage law was first adopted. It stayed at $3.35 during the federal floor years of the late 1970s and early 1980s. Then came the steady creep: $3.35 in 1980, $4.25 by 1990, $5.14 in 1996, $6.75 in 2004, $7.25 matching the federal floor in 2008, and $8.00 by 2014 after a series of ballot-initiative-driven increases. The Big One happened in 2018 when Question 4 passed, legislating a scheduled climb to $15.00 per hour by 2023. That rate took effect on January 1, 2023, and remains the current floor as of my last check. Here is the thing most people miss: Massachusetts does not have a single minimum wage. It has at least two, and sometimes three, depending on who you are paying. The standard rate applies to most workers. Tipped employees fall under a separate, lower cash wage requirement of $2.63 per hour as of 2023, but only if the employer can demonstrate that tips plus that cash wage meet or exceed the full minimum. If tips don't bridge the gap, the employer owes the difference. That tip credit reconciliation is where I have seen small employers get burned repeatedly. I once audited a restaurant's payroll from 2019 where the manager had simply paid the tipped minimum all year without tracking individual tip reports against the full $13.50 hourly floor. The back-wage liability came to roughly $18,000 across six employees. The fix was building a weekly tip-tracking spreadsheet that compared each server's actual tips to the pro-rated minimum, and issuing supplemental checks whenever the shortfall appeared.
The timeline gets messier when you factor in local ordinances. Some Massachusetts cities and towns have enacted their own minimum wage Ordinances that exceed the state floor. Boston, for example, has its own stepped increase schedule that ran parallel to but slightly ahead of the state timeline for certain periods. If you operate in multiple municipalities, you cannot apply a single rate across the board. You have to map each employee's primary work location to the applicable ordinance and use the higher of the two rates. I keep a running matrix in a shared spreadsheet that lists every municipality with an active local ordinance, the current rate, and the scheduled increase dates. It saves about forty-five minutes per payroll cycle compared to hunting down the latest city clerk update each time. One more counter-intuitive detail: the state minimum wage increases on July 1st of every year under the Question 4 schedule, but the tipped employee minimum does not automatically follow the same calendar. The tipped credit adjustment is tied to the full minimum wage increase, yet the calculation can create a scenario where the effective tipped floor jumps discontinuously. In practice this means you should recalculate the tip credit obligation every time the full minimum changes, rather than assuming a fixed dollar gap between the two rates. If you need the official records, the Massachusetts Department of Labor Standards maintains the historical wage tables on their website. The federal.gov archives also have the earlier state-level changes before the modern ballot-initiative era. Neither source is particularly friendly for date-range lookups, which is why I built my own lookup tool using the DOL's published tables as the source. It lets you enter a date and get the applicable rate for both the standard and tipped categories, plus a flag if a local ordinance in a given city would override the state rate. The tool runs locally on my machine and I share the file with any employer who asks. The whole process of verifying a historical rate that used to take me twenty minutes of cross-referencing now takes about thirty seconds.
The main limitation of tracking this by hand or even with a basic lookup is that local ordinances change without much fanfare. A town council vote can add or remove a local minimum on a date that has nothing to do with the state's July 1 cycle. I lost track once because a smaller municipality updated their ordinance in October without notifying the state DOL, and I applied the state rate to a worker whose entire shift distribution was within that town limits. The variance was small—about twelve cents per hour over a quarter—but it was still a compliance failure. The workaround is subscribing to the municipal code update feeds for any town where you have employees, or at minimum checking with the local labor office quarterly if you operate in a dozen or more municipalities.
Get the Full Details
