Mullins Salary Above The Law

A Practical Guide to Mullins Salary Above The Law

I keep meaning to write this down because every few months someone on a message board or a Discord server asks the same five questions about Mullins Salary Above The Law. It's a structured approach to salary calibration that prioritizes legal compliance as the baseline rather than the ceiling. Most people who hear about it assume it means paying above market rate just to stay ahead of potential litigation. That's not what it does. The methodology is more narrow and more annoying than that. The core idea comes from contract law principles applied to compensation management. You map every role against the minimum legal requirements across all jurisdictions your company operates in, then you build salary bands that exceed those floors by a calculated margin. The margin isn't arbitrary. It's derived from employment law precedent where courts have considered "good faith compensation" standards. Some states in the US, California in particular, have had cases where salary disclosure laws created new compliance obligations that weren't clearly addressed in older compensation models. Mullins Salary Above The Law exists to handle those gaps before they become problems.

Implementing Mullins Salary Above The Law

Here's how the actual implementation works, and it's not as fast as people hope. The first step is jurisdiction mapping. You list every location where employees are classified as W-2, contractor, or otherwise compensation-bound, and then you pull the relevant wage laws for each one. This includes minimum wage, overtime thresholds, pay transparency requirements, and any sector-specific regulations. The tricky part is that these laws change constantly. California updated its pay transparency rules in 2023 and again in 2024. New York City has its own separate requirements from New York State. London has different rules from Manchester when it comes to gender pay gap reporting, which intersects with salary banding in ways most HR platforms don't account for. Once you have the jurisdiction data, you build salary bands for each role level. The standard formula takes the legal minimum for that jurisdiction, adds a compliance buffer, then layers in market data. The buffer varies. In high-risk jurisdictions with active class action environments, the buffer is wider. In stable regulatory environments, it's narrower. A lot of teams skip this step and just apply a flat percentage increase across the board, which defeats the purpose and creates overspend in low-risk areas while still leaving exposure in high-risk ones. The second step is role classification. You can't calculate compliance margins without knowing exactly what each role entails and how it's classified across jurisdictions. A software engineer in Texas and the same software engineer in Illinois may fall under different classification rules depending on how their responsibilities are documented. Title inflation is a real problem here. I've seen companies list everyone as "Senior" to justify higher pay bands, which then creates internal equity issues that become discovery material in employment disputes.

The third step is documentation. This is where most people fail, and it's the part that matters most if you ever get audited or sued. Every salary decision under this framework needs a written rationale that references the specific jurisdiction, the applicable law, the market data source, and the calculated band. Not a generic justification. Specific citations. I learned this the hard way during a compliance audit at a company I consulted for a while back. They had implemented salary bands using a version of this methodology but hadn't documented the margin calculations for their New York office. When the DOL requested records, they couldn't produce the original analysis. The audit findings forced a retrospective recalculation that resulted in retroactive pay adjustments for forty-three employees and a settlement that cost roughly twice what the original compliance buffer would have cost to implement properly.

Common Pitfalls That Beginners Miss

The biggest mistake I see is treating Mullins Salary Above The Law as a one-time setup. It's not. Jurisdictions add new requirements, court decisions shift precedents, and your employee population moves. A salary band that was compliant in 2022 might not be in 2025. I recommend running the full audit quarterly at minimum, with monthly spot checks on any jurisdiction that recently changed its wage laws. The time investment is usually four to six hours per quarter for a mid-size company, compared to the crisis-mode work that follows a compliance failure, which can take three to four weeks and require external legal counsel at rates that make the quarterly audit look cheap. Another issue is the intersection with internal equity. When you calculate bands based on legal minimums plus jurisdiction-specific buffers, you can end up with situations where two employees doing identical work in different cities have significantly different pay because the legal environment differs. That's technically compliant but creates morale problems that lead to turnover, and turnover is expensive. I've worked around this by adding a secondary internal equity layer on top of the legal compliance layer. The base band satisfies the Mullins framework, then I adjust within a narrow band based on internal comparable roles. It adds maybe ten percent more work to the process but prevents the obvious inequities that cause problems later. There's also the contractor classification problem. Some companies try to apply Mullins Salary Above The Law to their W-2 staff while leaving contractors outside the framework entirely. That creates a two-tier system that looks like intentional misclassification if anyone examines the pay structure closely. The Fair Labor Standards Act and similar frameworks outside the US don't care about your internal categorization schemes when the actual work relationship matches employee criteria. If your contractors are doing the same work under the same supervision, the compliance gap becomes a legal exposure, not just a policy inconsistency.

What This Methodology Doesn't Solve

Mullins Salary Above The Law will not fix a company culture that systematically undervalues certain demographics. It won't close pay gaps that exist because of hiring practices, promotion patterns, or negotiation biases. It addresses the floor, not the ceiling. If your internal equity analysis shows significant disparities, this framework gives you a compliance structure but you still need to do the actual work of correcting the underlying issues. The documentation requirements help with that somewhat because you're forced to be explicit about every pay decision, but explicit documentation of biased decisions just makes the bias easier to find in litigation. It also doesn't handle salary history bans effectively on its own. Several jurisdictions have prohibited asking about or considering prior salary in compensation decisions. Companies that implement Mullins Salary Above The Law without updating their hiring workflows often still pull salary history during offers, which creates a compliance violation independent of the band structure. The two systems need to be integrated, not run in parallel. For smaller companies or startups with limited HR infrastructure, this methodology may not be practical as a standalone framework. The documentation overhead and audit requirements can consume resources that a lean team doesn't have. In those cases, I usually recommend starting with the jurisdiction mapping and basic band structure, then layering in documentation and audit processes as the company grows. Getting full compliance on day one is less important than building a system that scales properly.

The resources for implementing this are scattered. There's no single authoritative guide, and most of the frameworks online are either too simplified to be useful or too legalistic to be actionable. The best starting point is usually the EEOC guidance on pay equity combined with state-level wage and hour resources, then building your band formulas around those requirements rather than trying to find a ready-made template. I maintain a simple spreadsheet model that I use for my own reference, and I share it with teams who ask. It covers the core calculation logic without being jurisdiction-specific, which forces you to actually understand what you're implementing rather than filling in numbers blindly. If you're dealing with a specific jurisdiction and need the exact current requirements, I'd recommend pulling them directly from the relevant government agency rather than relying on third-party summaries. The summaries are usually correct but they don't always capture recent amendments, and the amendment is often the part that matters most.