Columbus Adopts New Pay Transparency Ordinance


Job ads have played the salary game for years. You know the one: “Competitive pay,” “great opportunity,” “fast-paced environment,” and absolutely no clue whether the role pays enough to cover rent, groceries, and the emotional damage of a four-round interview process. Columbus, Ohio, has decided that little guessing game has run its course.

With its new pay transparency ordinance, Columbus is telling many employers to stop being mysterious and start being specific. The city’s updated law requires covered employers to include a reasonable salary range or pay scale in job postings, building on an earlier rule that already banned salary history questions during hiring. In plain English: employers cannot keep asking what you used to make and then act shocked when workers want a fair offer based on the actual job.

This matters for job seekers, HR teams, business owners, recruiters, and frankly anyone who has ever clicked on a posting, read “pay depends on experience,” and muttered, “That is not a number.” Columbus is joining a larger trend toward pay transparency, but the local version has its own rules, timeline, and practical consequences. Here is what the ordinance does, why it matters, and what employers and applicants should expect next.

What Columbus Actually Passed

Columbus City Council approved the measure in early November 2025, and Mayor Andrew Ginther signed it shortly afterward. The ordinance amended Chapter 2335 of the Columbus City Codes, which already dealt with salary history restrictions, and added a new pay transparency requirement for job postings.

The timeline is important. The ordinance itself took effect in December 2025, but the section requiring salary ranges in job postings is not scheduled to be enforced until January 1, 2027. That delay gives employers time to clean up hiring practices, review pay structures, retrain recruiters, and make sure every posting does not look like it was written by a witness protection program for compensation data.

In other words, Columbus did not just flip a switch and say, “Good luck, everybody.” It created a runway. Smart employers will use that runway now, not the night before takeoff.

Who the Ordinance Covers

The law applies to employers with 15 or more employees in the City of Columbus. That includes businesses and organizations operating for profit or not for profit, as well as job placement and referral agencies acting on behalf of covered employers. The law generally does not apply to other local, state, or federal government units, although the City of Columbus itself is included.

The ordinance is also broad in how it thinks about employment. It covers temporary work, seasonal work, part-time work, contingent work, commission-based work, and positions filled through staffing agencies. Independent contractor arrangements are excluded, which means businesses should be careful not to slap an “independent contractor” label on something that clearly walks and talks like employment.

And yes, this is where things get interesting for hybrid and remote work. If the job is to be performed within Columbus or the application is being processed or considered in Columbus, employers should review those postings carefully. Multistate hiring is already complicated enough. Columbus just added another reason to read the fine print before posting a role across six platforms in 30 seconds.

What Employers Must Put in Job Postings

The headline rule is simple: covered employers must provide a reasonable salary range or scale for potential employment in job postings.

That sounds straightforward until you ask what “reasonable” means. Columbus tried to answer that question directly. The ordinance says reasonableness should be based on factors specific to the position, including:

  • the employer’s budget flexibility,
  • the expected range of applicant experience,
  • variation in job responsibilities,
  • opportunities for growth in and beyond the role,
  • cost of living for work locations, and
  • market research on comparable jobs and salaries.

That is a big clue about what Columbus is trying to prevent. The city clearly does not want employers posting something ridiculous like “$1 to $1 million,” which technically contains numbers but tells applicants nothing useful. A compliant range should be grounded in the actual role, the actual market, and the actual pay strategy. Novel concept, right?

The definition of “employment posting” is also broad. It covers electronic and printed solicitations for a specific available position when the posting includes a description of the job or qualifications. So if your hiring team posts on your website, LinkedIn, Indeed, a recruiter portal, or even a printed notice, the law is likely interested.

How This Builds on Columbus’s Salary History Ban

The new ordinance did not appear out of thin air. It builds on Columbus’s earlier salary history ban, which took effect on March 1, 2024. That earlier law already prohibited covered employers from asking applicants about their prior pay, screening them based on past compensation, relying solely on salary history to set pay, or retaliating against applicants for refusing to disclose salary history.

That earlier law addressed one common way pay inequities can follow workers from job to job like glitter after a craft project: once a person is underpaid, every future employer can use that number as an anchor unless someone stops the cycle. Columbus tried to stop it by cutting off salary history questions.

The new transparency rule takes the next step. Instead of merely banning a problematic hiring habit, it requires employers to show more of their hand upfront. That shift matters because transparency changes the tone of the process. Applicants can evaluate a role before investing time. Employers can reduce mismatched interviews. Recruiters can stop pretending “compensation will be discussed later” is a thrilling plot twist.

Why Columbus Is Doing This

Supporters of the ordinance have framed it as a pay equity measure, and the logic is easy to follow. When compensation stays secret, workers with less bargaining power often end up negotiating in the dark. That can worsen disparities tied to gender, race, disability, and prior underpayment.

The national context helps explain why local governments keep moving in this direction. Federal labor data still shows a meaningful pay gap between women and men. At the same time, HR research has suggested that many applicants are more likely to trust and apply to jobs that include a pay range. Pay transparency is no longer a fringe workplace idea. It is increasingly treated as a recruiting practice, an equity strategy, and a compliance issue all rolled into one somewhat uncomfortable but necessary package.

Columbus also seems to be thinking competitively. City materials tied to the ordinance argued that transparency can make employers more attractive to job seekers, improve the efficiency of hiring, and keep Columbus aligned with other jurisdictions moving in the same direction. Translation: if neighboring places are making job ads clearer and your city still allows salary hide-and-seek, talent may notice.

Exceptions and Limits in the Law

Like most employment laws, this one comes with exceptions. The pay transparency requirement and salary history restrictions do not apply in every possible scenario.

For example, the ordinance excludes internal transfers and promotions. It also does not punish voluntary, unprompted salary disclosures by applicants. Employers may still discuss salary expectations, benefits, and other compensation issues with candidates. Positions covered by collective bargaining procedures are treated differently as well, and employers rehiring someone within three years may use certain existing compensation information they already lawfully possess.

There is also a practical nuance worth noting: a background check or verification process might incidentally reveal salary history. That alone is not automatically the problem. The problem comes when an employer improperly uses that information as the basis for compensation decisions.

So no, the law is not banning ordinary compensation conversations. It is targeting the use of old salary information and the absence of clear pay information in ways that can distort the hiring process.

What Happens If an Employer Violates the Ordinance

Applicants may file complaints with the Columbus Community Relations Commission. The enforcement framework ties into the city’s broader anti-discrimination procedures, and civil penalties can apply after an administrative finding of violation.

For employers, that means this is not just a polite municipal suggestion with a clipboard and a dream. Repeated violations can become expensive. Even more importantly, they can create reputational headaches, employee distrust, and the kind of public scrutiny that makes a routine hiring problem suddenly very non-routine.

In a labor market where employer branding matters, being known as the company that fought salary transparency is not exactly the warm-and-fuzzy image most organizations want on their careers page.

What Columbus Employers Should Do Now

Even with enforcement delayed, employers should not treat this like a future problem for future people. The best time to prepare is before your recruiters accidentally post a noncompliant listing in 12 places at once.

1. Audit compensation ranges

Figure out what the organization reasonably expects to pay for each role. If the answer is “it depends,” narrow down what it depends on and document those factors.

2. Review job posting templates

Every template should have a clear place for salary ranges or pay scales. If your applicant tracking system still treats compensation like an optional afterthought, fix that now.

3. Train recruiters and managers

People involved in hiring should understand both the salary history restrictions and the upcoming posting rules. One loose comment in an interview can undo a lot of policy work.

4. Revisit remote and multijurisdiction hiring

Employers operating across cities and states should review how Columbus fits with other transparency laws. Patchwork compliance is still compliance work.

5. Prepare for internal questions

Once salary ranges are public, current employees may compare notes. That is not a bug in the system. That is the system doing what transparency tends to do.

What Job Seekers in Columbus Should Expect

For applicants, the biggest benefit is obvious: more information earlier. A posted salary range helps people decide whether a role is worth pursuing, whether relocation makes sense, and whether an offer is landing where it should. It can also reduce the awkward late-stage moment when a candidate has invested hours in interviews only to discover the pay is nowhere near workable.

That said, transparency does not guarantee perfection. A posted range can still be wide. It can still reflect market pressures, internal inequities, or cautious employer budgeting. But it is still better than walking into a negotiation with nothing but vibes and an overcaffeinated sense of optimism.

Applicants should also remember that a range is just that: a range. Employers may still consider experience, skills, certifications, internal equity, and job scope. Transparency should improve the conversation, not eliminate the need for one.

The Bigger Picture for Ohio

Columbus is not acting in isolation. The city’s own legislative materials point to Cleveland, Cincinnati, and Toledo as Ohio cities that have already moved toward similar transparency or salary history restrictions. That growing cluster matters because it creates momentum. Once multiple cities in the same state adopt similar rules, employers start to treat transparency less like an odd local experiment and more like the cost of doing business in a modern labor market.

There is also a cultural shift happening underneath the legal one. Workers increasingly expect clarity. Employers increasingly market trust. Lawmakers increasingly see salary secrecy as a policy problem. When those three trends meet, ordinances like Columbus’s stop looking radical and start looking inevitable.

Real-World Experiences Related to the Columbus Pay Transparency Ordinance

If you want to understand why this ordinance matters, do not start with legal jargon. Start with the actual experience of applying for jobs. For many people, the hiring process has long felt like buying a plane ticket without seeing the price until the checkout page. You prepare a résumé, draft a cover letter, schedule interviews, research the company, maybe even take time off work, and only then learn the salary is well below what you need. Pay transparency changes that experience immediately. It may not make every job offer fair, but it stops wasting quite so much human energy.

Think about a mid-career project manager in Columbus who sees three openings that all sound similar. Under the old style of posting, each ad might promise “great benefits” and “competitive pay,” which is corporate poetry for “please guess.” Under a transparent system, that candidate can quickly tell which role is realistically aligned with experience and which one is a dead end dressed in business casual. That saves time, reduces frustration, and makes the search more strategic.

Now consider the employer side. Hiring teams often claim they need flexibility, and that concern is not fake. A company may genuinely be open to different experience levels or still be sorting out budget approvals. But transparency laws do not eliminate flexibility; they force discipline. Employers must think through what they are actually willing to pay, how that compares with the market, and whether internal employees are being paid consistently. That can be uncomfortable, but uncomfortable is not the same thing as unfair. Sometimes discomfort is just accountability wearing sensible shoes.

Recruiters may also find that transparency improves conversations. When the range is clear from the beginning, fewer candidates drop out late in the process. Fewer interviews are built on mismatched expectations. Hiring managers may still debate where a finalist belongs within the posted range, but at least everyone is debating from the same map instead of wandering through the woods with a flashlight and a wish.

There is also an emotional side to this issue that city leaders and advocates have talked about openly. Many workers, especially women and people from historically underpaid groups, can tell stories about learning they were paid less than peers for similar work or discovering only after the fact that a company had far more room in its budget than anyone admitted. Pay secrecy often creates more than confusion; it creates resentment. Once people feel tricked, trust is hard to rebuild. Transparency does not magically erase inequity, but it makes it harder for inequity to hide under a neat HR memo.

That is probably the most important lived experience behind Columbus’s ordinance. For applicants, transparency feels like respect. For employers, it feels like structure. For the labor market, it feels like fewer smoke machines and more actual lighting. And honestly, after years of compensation mystery theater, a little more lighting sounds pretty good.

Conclusion

Columbus’s new pay transparency ordinance is not just a local headline. It is a practical shift in how hiring is supposed to work. By requiring many employers to include reasonable salary ranges in job postings and building on the city’s earlier salary history ban, Columbus is pushing the hiring process toward more clarity, more accountability, and less compensation guesswork.

For employers, the message is simple: get your pay ranges in order, review your job ads, and stop treating salary details like a state secret. For job seekers, the ordinance should gradually make the market easier to navigate and a little less exhausting. Will it solve every pay equity problem? No. But it does make one thing much harder to defend: asking people to invest time, skill, and hope in a job opportunity while hiding one of the most important facts about it.

And that, in 2026, feels less like a radical idea and more like basic workplace manners.