Frankenstein’s Comp Plan: When a Salary Structure Redesign Can’t Wait

Open your grade file and count the pay systems inside it. If you find three sets of grades, a dozen “special” ranges, and titles nobody can define, you own a Frankenstein’s comp plan. Each piece made sense once. Together, however, the pieces form a creature that no one designed and no one can defend. A salary structure redesign is how you finally put it to rest.

This problem rarely starts with bad decisions. Instead, it grows from good decisions made in isolation. An acquisition brings its own grades. A hiring manager wins an exception for a hard-to-fill role. A legacy grade survives because nobody wants the fight. Over time, those stitches pile up. Meanwhile, new pay transparency laws ask you to explain every range you post.

This guide shows HR directors how to spot a stitched-together pay plan, decide whether to rebuild, and run the work in six steps.

Key Takeaways

• Most patchwork pay plans come from three sources: acquisitions, one-off exceptions, and legacy grades.
• Only 51.4% of organizations have a formal job architecture, according to an April 2026 survey of 525 employers.
• New 2026 pay transparency laws in Virginia, Maine, and Connecticut make unexplained ranges a legal exposure.
• Mapping old grades onto a new grid only relabels the problem. Instead, rebuild from job levels up.
• A salary structure redesign works best with a clear exception policy, a cost model, and trained managers.

Why Patchwork Pay Now Demands a Salary Structure Redesign

The case for change starts with data. In April 2026, Salary.com published its 2026 State of Pay and Compensation Practices Report. The survey covered 525 organizations across 23 industries. Its findings read like a parts list for a Frankenstein plan:

• Only 51.4% of organizations have a formal job architecture in place.
• 22% do not use job leveling to inform their pay grades.
• Nearly 21% rely mostly or entirely on manager discretion for pay decisions.
• Only 34.3% tell employees how the company sets pay.

Put simply, about half of employers set pay without a shared map of their jobs. As a result, each business unit, acquired company, or manager fills the gap with its own logic. That logic then hardens into grades.

The regulatory picture adds urgency. Virginia’s pay transparency law took effect July 1, 2026, and Maine’s followed on July 29, 2026. Connecticut moved to proactive range disclosure on October 1, 2026. In addition, the EU Pay Transparency Directive reached its June 2026 transposition deadline, which matters for any employer with EU staff. Every posted range now works like a public promise.

Here’s the core risk. A range you can’t explain is a range you can’t defend. For example, if a posted range traces back to a 2019 acquisition grid, a candidate or regulator may ask why. “That’s how their company did it” won’t satisfy anyone.

Still, compliance is only part of the story. Patchwork pay also slows every merit cycle, confuses managers, and fuels internal pay complaints. That’s why a salary structure redesign belongs on the 2027 agenda, not the someday list.

Stitch One: Acquisitions That Never Got a Pay Grade Overhaul

Acquisitions create the biggest seams. When one company buys another, leaders focus on revenue, systems, and culture. Pay grades often stay frozen, because changing them feels risky during integration. So the acquired team keeps its old grid “for now.”

Then “for now” becomes five years. Meanwhile, a second deal brings a third grid. Before long, you run parallel pay systems under one logo. Each one carries its own range spreads, its own midpoints, and its own title rules.

Consider a simple example. An analyst in the legacy business sits in Grade 7. An analyst from the acquired company sits in Band C. Both do similar work, yet their ranges differ by thousands of dollars. Neither employee can see why. Also, neither manager can explain it.

This gap causes three problems:

1. Hidden inconsistency: Similar jobs earn different pay for reasons nobody can document.
2. Mobility friction: Internal transfers stall because nobody knows how to map one grid to another.
3. Budget blind spots: Finance can’t compare cost across units when each unit uses different grades.

Integration teams also tend to leave behind “grandfathered” rates. Those rates protect employees in the short term, which is fair. However, without an end date, they quietly become permanent.

From MorganHR’s work with clients, the pattern holds across industries. The longer a company waits after a deal, the harder the merge becomes. Old habits settle in, and each year of separate merit cycles widens the gaps.

Therefore, treat pay integration as part of the deal, not an afterthought. If your last acquisition closed more than two years ago and its grid still stands alone, you have found your first stitch.

Stitch Two: One-Off Exceptions That Became Permanent

Exceptions start with good intent. A key engineer gets a competing offer. A sales leader insists on a custom range to land a star hire. HR approves the request because the business case looks strong. Then everyone moves on.

The trouble starts later. Nobody records why the exception happened. Nobody sets a date to review it. So the exception rate becomes the new normal for that job. Next, peers hear about it and ask for the same treatment. Eventually, the exception spreads across a whole job family.

Look for these signs in your data:

• Employees paid well above their range maximum, often called red-circled pay.
• Custom ranges that apply to just one or two people.
• Titles created to justify a higher grade rather than to describe new work.
• Off-cycle increases that outnumber merit increases in some departments.

Each sign points to the same issue. Your official grades no longer reflect what you actually pay. In other words, the real pay plan lives in a spreadsheet of exceptions, not in your grade table.

The 2026 survey data supports this concern. Nearly 21% of organizations rely mostly or entirely on manager discretion. Discretion isn’t wrong on its own. Still, discretion without guardrails produces exceptions faster than HR can track them.

Exceptions also create a transparency problem. If you post a range but routinely pay above it, your posting tells candidates the wrong story. Likewise, current employees who learn about the gap may question every pay decision you make.

So the fix isn’t to ban exceptions. Markets move, and you need flexibility. Instead, the fix is to make every exception visible, priced, and temporary. We cover how to do that in the MorganHR view below.

Stitch Three: Legacy Grades Nobody Can Explain

Legacy grades are the oldest stitches. Someone built them years ago, often before the company had a compensation function. Back then, a simple grid made sense. Today, however, the business looks completely different.

You can usually spot a legacy grade by asking one question: “Why does this grade exist?” If the answer starts with “I think,” you have a problem. Common examples include:

• Grades with no employees in them.
• Grades that overlap so much they mean nothing.
• Ranges that haven’t moved with the market in several years.
• Grade names tied to old departments or retired job titles.

Legacy grades cause quiet damage. For instance, a range that hasn’t moved in years can push new hires above the midpoint on day one. That squeezes long-tenured employees and creates pay compression. Similarly, too many grades force tiny promotion steps, which frustrates employees and managers alike.

Too few grades cause the opposite problem. Broad bands can hide big pay gaps between jobs that look alike on paper. As a result, you lose the ability to explain why two people in the same band earn very different pay.

Legacy grades also block good data. When grades don’t match real job levels, market pricing gets messy. You end up comparing your jobs to survey jobs that don’t line up. Then your ranges drift further from reality.

Here’s the honest truth many leaders avoid. Nobody owns legacy grades, so nobody fixes them. Each new HR leader inherits the grid, patches what hurts, and passes it on.

That cycle ends only with a deliberate decision. Once you can name your acquisition seams, your exception pile, and your legacy grades, you have a full diagnosis. Next, you need a clear way to decide whether to patch or rebuild.

Five Warning Signs You Need a Salary Structure Redesign

Not every messy plan needs a full rebuild. Sometimes a targeted refresh does the job. So how do you know which path fits? Start with these five warning signs.

1. You run two or more grade systems. Parallel grids from acquisitions almost always need a full merge.
2. More than one in ten employees sit outside their range. Either above the maximum or below the minimum, this level signals ranges that no longer fit.
3. Managers can’t explain a range. If your managers can’t say why a job sits in its grade, neither can HR.
4. Exceptions outnumber rules. When custom ranges and special titles dominate, the official plan has stopped working.
5. You can’t post ranges with confidence. If posting ranges makes your team nervous, treat that nervousness as data.

HR Director decision test: Count how many of the five signs apply to you.

• Zero or one: Run a market refresh and clean up stray exceptions.
• Two or three: Plan a targeted rebuild of the most affected job families.
• Four or five: Schedule a full salary structure redesign for the next fiscal year.

The 10% threshold in sign two reflects MorganHR’s working rule, not an industry standard. In our experience, once out-of-range employees pass that level, patching ranges one at a time costs more than starting fresh.

Also, involve finance early. A rebuild changes pay costs, so your CFO needs a seat at the table from day one. Likewise, bring in legal counsel if you operate in states with new disclosure laws. Their input shapes how you post and document ranges.

Finally, be honest about timing. A full rebuild during a merger close or a major layoff can backfire. Instead, aim for a window when leaders can focus. For most organizations, that means starting six to nine months before the next merit cycle.

The MorganHR View: A Compensation Framework Rebuild Beats a Relabel

Here’s where we differ from much of the advice out there. Many firms recommend “harmonizing” grades. In that approach, you take each old grade and map it to the nearest new grade, often by midpoint. It looks efficient. However, in our view, it simply sews the old stitches into a new body.

Mapping keeps every flaw intact. If a legacy grade placed a job too high, the mapped grade keeps it too high. If an acquisition grid priced jobs oddly, those prices carry forward. So you get a cleaner table, but not a fairer plan.

Instead, MorganHR recommends rebuilding from the job up. That means three firm principles:

• Level jobs first, price them second. Define job families and levels before you look at current pay. Otherwise, today’s pay will bias tomorrow’s levels.
• Give every exception a ledger entry. Record the reason, the cost, the approver, and a review date. If an exception has no review date, it isn’t an exception. It’s a new rule.
• Sunset grandfathered rates. Protect people, not old grids. We suggest ending grandfathered rates within two merit cycles, with clear steps for each affected employee.

This approach takes more effort up front. Still, it pays off quickly. Clean levels make market pricing easier. Visible exceptions make budgets more honest. Clear ranges make pay transparency less stressful.

Rebuilding also gives you a story to tell employees. “We merged three systems into one, based on the work you do” lands far better than “We relabeled your grade.” People accept change more readily when they can see the logic behind it.

Notably, the 2026 pay practices report reached a similar conclusion. Its authors recommend building job architecture and consistent leveling first, before any push toward transparency. In short, you can’t explain a plan you haven’t truly built.

How to Run a Salary Structure Redesign in Six Steps

Once you commit to a rebuild, follow a clear sequence. Each step builds on the one before it, so resist the urge to skip ahead.

1. Inventory every pay system. List each grade table, range, and title set by legal entity and location. Include all exceptions, red-circled rates, and grandfathered agreements.
2. Build or refresh job architecture. Group roles into families, such as finance or operations. Then define levels by scope, impact, and skill. Write short level guides that managers can actually use.
3. Price benchmark jobs. Choose a set of well-matched jobs at each level. Price them against current, reputable survey data. Then confirm the results with your pay philosophy, such as targeting the market median.
4. Design the new grades. Decide how many grades you need, how wide each range should run, and how far midpoints should step apart. Typically, ranges widen at higher levels, where skills vary more.
5. Model cost and placement. Place every employee in the new framework. Then count who falls below the minimum and who sits above the maximum. Build a catch-up plan and a cost estimate before anyone sees a new grade.
6. Govern and communicate. Publish an exception policy, train managers, and set an annual review cycle. Then tell employees what changed and why.

Step five deserves extra care. It shows leaders the real price of the rebuild. For example, raising below-minimum employees to the new floor may require a phased budget over two cycles. Planning that early prevents surprise costs later.

Step six matters just as much. A new plan fails if managers can’t explain it. Therefore, budget time for manager training before launch, not after complaints start.

Quick Implementation Checklist for a Salary Structure Redesign

Use this checklist to keep the project on track. Most mid-size organizations can complete the work in four to six months with focused support. Larger or more complex employers may need longer, especially after several acquisitions. Before you start, share the plan with your executive sponsor so everyone agrees on scope. Because a salary structure redesign touches every employee, a shared timeline prevents surprises.

Months 1–2: Diagnose

• Gather every grade table, range, and title list across all entities.
• Log every exception, red-circled rate, and grandfathered agreement.
• Score your plan against the five warning signs.
• Secure an executive sponsor and a finance partner.

Months 2–3: Build

• Draft job families and level guides.
• Level every role before reviewing current pay.
• Select benchmark jobs and pull current survey data.

Months 3–4: Design and model

• Set grade count, range widths, and midpoint steps.
• Place all employees and flag out-of-range cases.
• Build a phased cost model and catch-up plan.
• Review the design with legal counsel for disclosure compliance.

Months 4–6: Launch

• Train managers on the new levels and ranges.
• Publish the exception policy with review dates.
• Communicate changes to employees.
• Load the new framework into your HRIS and planning tools.

After launch, schedule a check-in at 90 days. By then, you’ll see whether managers apply the new levels consistently. You’ll also learn which job families need fine-tuning. Then fold your findings into the first merit cycle under the new plan. Also, keep the exception ledger open, since it will tell you where the new ranges feel tight.

How a Compensation Framework Rebuild Changes by Company Size

The core steps stay the same at any size. However, scope, staffing, and risk differ a lot. Here’s how to adjust your approach.

Small organizations (under 250 employees)

Smaller employers usually face simpler seams. Often, the problem is a founder-era grid plus a handful of exceptions. In this case:

• Keep the grade count small, often eight to twelve grades total.
• Focus on clear level guides rather than complex job families.
• Use a consultant for market pricing if you lack in-house survey access.

Also, small firms can often finish the rebuild in one quarter. That speed is an advantage, so use it.

Mid-size organizations (250 to 2,500 employees)

Mid-size employers feel the Frankenstein problem most. They’ve often grown through one or two acquisitions, yet they lack a large compensation team. For these employers:

• Prioritize merging parallel grids from past deals.
• Build job families for your largest functions first.
• Invest in tools that track exceptions and model costs.

In addition, mid-size firms benefit most from outside support. A short, focused engagement can deliver architecture, grades, and pricing without overloading a small HR team.

Large enterprises (2,500+ employees)

Large employers face scale and geography. They may run separate grids by country, union status, or business line. For them:

• Set a global level framework, then allow local ranges by market.
• Phase the rollout by region or business unit.
• Align closely with legal teams on EU and U.S. state disclosure rules.

Large firms also need strong change management. Thousands of managers must learn the new levels, so training becomes a project of its own. Plan for it early.

Where HR Technology Supports Your Salary Structure Redesign

Spreadsheets often helped create the monster. Each acquired team, manager, and exception lived in its own file. So moving the new plan into one system matters as much as the design itself.

Technology helps in four practical ways:

• One source of truth. A planning platform holds one grade table for everyone, instead of scattered files.
• Outlier detection. Tools that flag disparities and outliers show you who sits outside range before managers ask.
• Multi-currency budgeting. Global employers can plan in local currencies while reporting in one.
• HRIS integration. Direct links to systems such as ADP or UKG keep job data and pay data in sync.

For example, SimplyMerit, MorganHR’s merit planning platform, includes disparity and outlier analysis with board-ready reports. It also supports multi-currency budgets and integrates with ADP, UKG, and other HRIS platforms. Those features make it easier to run your first merit cycle on the new framework. Whatever platform you choose, look for those same capabilities.

Technology alone won’t explain pay, though. Managers still carry the message. That’s why we pair system rollouts with manager training. MorganHR’s CompAware program, for instance, helps managers talk about ranges and levels with confidence.

If you want a broader view of how these pieces fit together for growing employers, read our guide to mid-market compensation essentials for 2026. It covers pay philosophy, internal consistency, and merit planning in more depth.

Finally, choose tools after you finish the design, not before. Otherwise, you risk shaping your new plan around a system’s limits. Design first, then automate.

Frequently Asked Questions About Salary Structure Redesign

What is a salary structure redesign?

It’s a rebuild of your grades, ranges, and job levels from the ground up. Unlike a market refresh, it changes how you organize jobs, not just how much ranges move.

How long does the process take?

Most mid-size employers finish in four to six months. Small firms often need one quarter. Large or multi-country employers may need nine to twelve months.

Should we map old grades to new ones?

In MorganHR’s view, no. Mapping carries old flaws forward. Instead, level each job fresh, then place employees in the new grades.

What happens to employees paid above the new range?

Typically, you keep their pay and limit future increases until the range catches up. Some employers use lump-sum awards in the meantime. Review each case with counsel, since some rules affect overtime-eligible staff.

How do pay transparency laws affect the rebuild?

They raise the stakes. In 2026, Virginia, Maine, and Connecticut added or expanded range disclosure rules. A rebuilt plan makes those postings easier to explain and defend.

How often should we review the new ranges?

Review ranges against the market every year. Then revisit the full framework every three to five years, or after any major acquisition.

Who should own the project internally?

Usually, the head of total rewards or the HR director leads it. However, finance should co-own the cost model. In addition, a small steering group of business leaders helps approve job levels and keeps the work moving.

Put Your Frankenstein’s Comp Plan to Rest

A stitched-together pay plan won’t fix itself. Each new deal, exception, and patch adds another seam. Meanwhile, transparency laws make every seam more visible to candidates, employees, and regulators.

The good news is that the path forward is clear. First, diagnose your acquisition grids, exception pile, and legacy grades. Next, score yourself against the five warning signs. Then, if the signs point to a rebuild, follow the six steps and the checklist above.

Above all, remember the MorganHR principle. Level the jobs first, price them second, and give every exception an end date. That single habit prevents the next monster from forming.

Whether you lead a 200-person firm or a global enterprise, the first move stays the same. Pull every grade table into one place and look at it honestly. If the seams outnumber the rules, a salary structure redesign will save you time, money, and credibility in every future merit cycle.

You don’t have to do this alone. MorganHR helps HR leaders merge parallel grids, build job architecture, and launch grades their managers can explain. Our focused engagements cover job levels, ranges, market pricing, and leadership-ready reporting. We can start with a quick diagnostic of your current grades. Then we’ll tell you honestly whether you need a full salary structure redesign or a lighter refresh.

This post is for informational purposes only and does not constitute legal advice. Consult qualified counsel for guidance specific to your organization’s compliance obligations.

Ready to retire your Frankenstein plan? Talk with a MorganHR compensation consultant about your rebuild today.