Skip forward into hiring notes
RosterAcorn

Ohio pay complaint review: 3 statute facts for HR

Ohio Revised Code 4111.14 lets employees, people acting for them and interested parties file pay complaints, and lets the state investigate on its own. If a state pay complaint or a records request lands on your desk, the first few days shape everything that follows. Many staffing and HR leads have never answered a review of this kind, and the rules sit in two places: the Ohio Revised Code and the Ohio Constitution. This post walks through three facts from the statute that most affect how you respond. Each fact links to the official text so you can check the wording yourself.

The statute is section 4111.14 of the Ohio Revised Code. It covers complaints and investigations under Section 34a of Article II of the Ohio Constitution, and every quote below comes from that page. This is general information for planning, not legal advice. If you have an open matter, bring in employment counsel early, before you send anything to the state.

Key takeaways

  • A complaint can come from an employee, a person acting for employees, or any other interested party, so do not assume the affected worker filed it.
  • The state can open a review without any complaint, so check your pay practices and records before a letter arrives.
  • The employer must make related records and other required information available, so do not limit collection to the disputed item.
  • Name one contact, record the date and any deadline for each notice, and route state contact through that person and counsel.
  • Treat investigation records as confidential, and send any public-records request that touches a state investigation to counsel first.

Fact 1: Complaints can come from more than the affected employee, and the state can start its own review

Start with who can set a review in motion. The statute lets several people file a complaint. It says that an employee, a person acting on behalf of one or more employees, and any other interested party may file a complaint with the state for a violation of Section 34a of Article II, Ohio Constitution, or any law or regulation implementing its provisions ( Ohio Revised Code 4111.14).

That list is wider than many managers expect. The complaint does not have to come from the employee who believes they were underpaid, and it does not have to come from someone inside your company. A review may begin because someone acting for employees, or an outside party with a stake in the issue, raised a concern.

The second point is that the state does not need a complaint at all. The statute says that the state may, on its own initiative, investigate an employer's compliance with Section 34a and any law or regulation implementing it ( Ohio Revised Code 4111.14). For an HR lead, that means your pay practices can be examined without a single employee raising a concern. Do not assume a letter means a specific person has complained.

That has a practical consequence. Waiting for a complaint before you look at your records is a weak plan. Run a quiet review now. Confirm which roles are paid hourly and which are salaried, which records you keep on hours worked, who approves pay changes, and whether the written pay policies match what actually happens. Doing this before a letter arrives gives you time to decide, with counsel, how to correct any errors through proper channels. It also avoids rebuilding history under deadline pressure.

The third point concerns how the review runs. The statute says that the state shall investigate an employer's compliance with this section in accordance with the procedures described in section 4111.04 of the Revised Code ( Ohio Revised Code 4111.14). This post does not summarize section 4111.04, which is a separate section. Pull it up and read it with counsel. Its procedures govern how the investigation moves, so they should drive your internal timeline.

When a notice arrives, work through an intake checklist before anyone replies:

  • Write down the date you received the notice, who received it, and how it arrived.
  • Read the notice for any deadline and put it on the calendar. Do not rely on memory for dates.
  • Name one person as the single point of contact for the state. Route all state contact through that person and counsel.
  • Note whether the notice points to an employee complaint, a state-initiated review, or a records request. Say which one your response answers.
  • Tell managers about the review only on a need-to-know basis, and ask them to send any questions to the contact.

A good first response is short and factual. It identifies the person who will handle the matter, confirms that you received the notice, and asks for any clarification you need. It does not argue the merits in the first message. Arguments made before you know what the state has in hand tend to create new questions.

Before you draft anything substantive, collect the facts. Write down the pay decisions named in the complaint, the people who made them, the policy or pay structure that applied, and the dates of each change. Then write down what you do not know. Gaps stated plainly are easier to fix than gaps discovered after a response has gone out.

Fact 2: The employer must make records available, and the hours-worked definition has limits

The statute places a direct duty on the employer. It reads: "The employer shall make available to the state any records related to such investigation and other information required for enforcement of Section 34a of Article II, Ohio Constitution or any law or regulation implementing Section 34a of Article II, Ohio Constitution" ( Ohio Revised Code 4111.14).

Read the sentence slowly. The duty has two parts. It covers records related to the investigation, and it covers other information required for enforcement. The second part is wider than the complaint itself. A narrow complaint can lead to a request for records beyond the specific employee or pay decision it names. So do not limit your collection to the single item in dispute. Ask counsel to read the request and compare it with the statute before you decide what to produce.

The statute also defines part of what counts as "such information," and that definition has limits. It says: "Such information" does not include hours worked for each day worked by individuals for whom an employer is not required to keep that information under the Fair Labor Standards Act and its regulations or individuals who are not subject to the overtime pay requirements specified in section 4111.03 of the Revised Code ( Ohio Revised Code 4111.14).

In plain terms, the definition leaves out daily hours-worked data for two groups. The first is people for whom your company is not required to keep that daily information under the federal Fair Labor Standards Act and its regulations. The second is people who are not subject to the overtime requirements in section 4111.03. Two cautions apply. First, this is a definition of a term, not a blanket exemption from producing records. Second, sorting employees into those groups requires an accurate roster of who falls where and why. Build that roster carefully, document the basis for each entry, and confirm with counsel before you rely on the carve-out.

Staffing firms need one more check. If your workers are placed at client sites, confirm which entity is the employer for each worker before you start gathering records. A request may be directed to one company or to both, and the facts decide how the statute applies. Know who hired each worker, who paid them, who set their schedule, and who approved their pay before you respond.

Records work is where small errors become large problems. A missing file, a quietly edited spreadsheet, or a summary that does not match its source can cost more credibility than the underlying pay question. Use these habits:

  • Build your collection list from the exact wording of the request, not from memory of what the payroll system contains.
  • Preserve what you have. Do not edit, backfill, or re-date existing records. If a record must be corrected, document the correction separately, date it, and get counsel's input first.
  • Suspend routine deletion for the payroll, timekeeping, and HR systems that touch the request. Ask your IT lead to confirm that backups are covered too.
  • Keep a production log that lists each document sent, the date, the recipient, and the version. Keep an identical copy of what left the building.
  • Separate responsive records from unrelated ones. If a record holds personal information about people outside the request, raise it with counsel before it goes out.
  • Ask in writing for clarification when a request is unclear, and keep the answer on file.

Build the file as if someone will check every line, because someone may.

Fact 3: Investigation records are confidential, and the minimum penalty covers only retaliation

The third fact cuts two ways. The statute says: "All records and information related to investigations by the state are confidential and are not a public record subject to section 149.43 of the Revised Code" ( Ohio Revised Code 4111.14).

For someone who handles records requests, this matters when a public-records request touches a state investigation. The statute treats records and information related to state investigations as confidential and says they are not public records under section 149.43. Do not assume that such a request can be answered the way you would answer an ordinary one. Route it to counsel first, because counsel decides what, if anything, to say to the requester. Nothing about the investigation should be disclosed until counsel has reviewed the request.

The sentence is about records and information related to investigations by the state. It does not say that your underlying pay records become confidential, so do not stretch it to cover them. Payroll files, job descriptions, and pay policies have their own handling rules, and your normal process should continue to govern them unless counsel tells you otherwise.

Then there is the penalty. The statute sets a minimum penalty and limits where it applies. It reads: "The "not less than one hundred fifty dollar" penalty specified in division (J) of this section shall be imposed only for violations of the anti-retaliation provision in Section 34a of Article II, Ohio Constitution" ( Ohio Revised Code 4111.14).

Read that carefully. The minimum penalty in division (J) is tied to violations of the anti-retaliation provision. The quoted sentence does not describe it as a minimum for every violation of the statute. That is a narrow reading of a narrow sentence, and it does not make other violations low-stakes. Retaliation is the risk most within your control, so manage it first. Every manager who might learn of a complaint or an investigation should know that the statute refers to an anti-retaliation provision in Section 34a, and that the penalty discussed above is tied to violations of it. Make sure they know to send any question about an employee's treatment after a pay concern to the point of contact. For more on this, read retaliation risks when workers complain.

When a records request arrives, a workable sequence is general and simple. Confirm exactly what is being asked. Check whether any part of it touches a state investigation, and if so, route that part to counsel. Respond to the rest on the schedule the request sets, and keep notes of every call and email. The scope always comes from the request itself, so read it before you assume anything.

The table below sets out the statute's rules side by side, using only the wording quoted above.

TopicWhat the statute saysSource
Who may file a complaintAn employee, a person acting on behalf of one or more employees, or any other interested party Section 4111.14
State review without a complaint The state may investigate an employer's compliance on its own initiativeSection 4111.14
Employer recordsThe employer shall make available related records and other information required for enforcement Section 4111.14
Investigation procedure The state investigates under the procedures described in section 4111.04Section 4111.14
Hours-worked definition"Such information" excludes daily hours for two groups of individuals Section 4111.14
Investigation records Confidential, and not a public record subject to section 149.43Section 4111.14
Minimum penaltyThe "not less than one hundred fifty dollar" penalty in division (J) applies only to anti-retaliation violations Section 4111.14

Preparing before the next letter

The three facts point to one habit: know your records and your people before a letter arrives. Preparation does not require a crisis. It requires a few standing practices that any HR or staffing team can set up in an afternoon, and then keep current.

Start with a single owner. Decide who receives state correspondence and who has authority to pull records. If that person is out, someone else should know where the notice and the contact list are kept. A review that stalls because nobody knew who was in charge creates its own problems.

Next, keep a current inventory of pay-related records. For each pay system, note what it holds, who administers it, how long records are kept under your own policy, and whether it can produce a clean export. An inventory turns a frantic search into a checklist. It also makes it easier to see gaps, such as hours data kept in one place and pay approvals kept in another. For a related checklist of what to keep, see discrimination complaint files.

Keep your pay roster accurate. Know which roles are hourly, which are salaried, and which individuals fall into the groups the hours-worked definition addresses. Record the reason for each classification and update the file when roles change. This work is tedious, but it is exactly what you will need if a request turns on who is in which group.

Train managers on two things: how to route an inquiry, and what retaliation looks like. Managers do not need to understand the statute in depth. They do need to know that a question about pay goes to the point of contact, and that no one should treat an employee differently because the employee raised a concern or spoke with the state.

Finally, check the notice you received. Any deadline and the specific records requested come from that notice, and the statute text tells you what kinds of records and information are in scope, so read both rather than relying on this post. When you reach out to counsel, bring the notice, the statute text, and your inventory. Those three items let counsel answer your questions quickly, and they keep your first response accurate.

Next step today: name the one person who will receive state correspondence, and write that name at the top of your pay-records inventory.

Frequently asked questions

Can a pay review start without an employee complaint?

Yes. As Fact 1 explains, the state may investigate an employer's compliance on its own initiative.

Who can file a pay complaint under the statute?

An employee, a person acting on behalf of one or more employees, or any other interested party can file, as Fact 1 explains.

Can a records request about a state investigation be answered like any other?

No. Route it to counsel first, because investigation records are confidential under Fact 3.

Sources