Wisconsin section 111.36 protects prospective employees who have testified, are about to testify, or have exercised a right under the section.
Key takeaways
- Both passages name prospective employees, so the protection does not begin on the day of hire.
- The protection can reach an applicant who is about to testify or who acted for another person.
- Send any disclosure of past testimony or rights to HR or counsel before a status decision.
- Set the job criteria in writing first, and apply them to every finalist.
- Document each step with dates, names, and reasons.
Why this matters at the hiring stage
Many employers think of retaliation protections as something that applies only to people already on the payroll. The Wisconsin language discussed below does not stop there. Both passages name the prospective employee directly. If an applicant has testified, is about to testify, or has exercised a right under the section, the protection can reach that applicant even though they have never worked for you.
This post is general information for recruiters and hiring managers. It is not legal advice, and it does not replace a conversation with your employment counsel. Its purpose is to help you spot the situation early, so that any status decision is deliberate, documented, and easy to explain later.
A status decision also outlives the people who made it. The file may be read months later by a new HR partner, an investigator, or a judge, none of whom were in the room. Write each decision as if that reader will have only the paper in front of them.
Recruiters often learn about an applicant's past activity by accident. A reference mentions a case. A background search turns up a filing. The applicant raises it during an interview. The moment you learn the information is the point where your process matters most. A short pause to check the facts and involve the right people is far better than a decision made on the spot.
The two protected activities
The Wisconsin Legislature publishes section 111.36 of the Wisconsin Statutes online. Two passages from that page describe the protected activities this post covers, and both name the same group: the employee or the prospective employee.
The first passage covers testimony. It describes an employee or prospective employee who "has testified or is about to testify in a proceeding under this section" ( Wisconsin Legislature, 111.36). Two details matter. The wording covers someone who has already testified, and it also covers someone who is about to testify. An applicant does not need to have finished a proceeding to fall within this language.
The second passage covers the exercise of rights. It describes an employee or prospective employee who, "on behalf of that employee, prospective employee or another person, has exercised any right under this section" ( Wisconsin Legislature, 111.36). This passage is broader in one respect. It reaches action taken on behalf of another person, not only action taken for oneself. An applicant who acted for someone else can fall within this wording.
Read each passage in its exact words. The quotes in this post are excerpts, and a paraphrase, including the one in this article, is no substitute for the statute itself.
Comparing the two passages
The table below sets the two passages side by side. Each cell comes from the wording of the passage, so you can check any row against the source.
| First passage: testimony | Second passage: exercising a right | |
|---|---|---|
| Who it names | The employee or prospective employee | The employee or prospective employee |
| What it covers | Has testified, or is about to testify, in a proceeding under this section | Has exercised any right under this section |
The table makes the difference plain. The first passage is about a proceeding. The second is about a right. An applicant can fall under either one, and a single applicant may have history under both. Treat any such history as something that needs review, not as a fact you can set aside.
When you brief HR or counsel, the table works as a quick screen. Ask two questions. Did the applicant testify, or are they about to testify, in a proceeding under this section? Did the applicant exercise a right under this section, either for themselves or for another person? A yes to either question does not by itself decide the outcome. It does mean the file needs a closer look before anyone moves it forward or out.
Practical steps for a status decision
When you learn that an applicant has done one of these things, the goal is a decision you can defend later. The steps below are general practice, not a legal checklist.
Note the information in the file. Record what you learned, when you learned it, and from whom. Do not rely on memory when the decision is made weeks later.
Bring in HR or counsel before deciding. Someone outside the hiring team should review the file before any status change. That person can check whether the applicant's history touches either passage and whether the process has been followed.
Set the job criteria first. Write down the job-related requirements before you look at this applicant's file again. Apply the same criteria to every finalist, and keep a copy of the criteria with the file. For a worked form, see Interview Scorecard Example for Consistent Hiring Teams.
Document each stage. Write the reasons for each advance, hold, or rejection, with dates and names. If a decision changes because of new facts, record that change too, along with what the new facts were.
Keep the circle small. Share protected-activity information only with people who need it to make or review the decision. The more people who discuss the applicant's history informally, the harder it is to show that the decision rested on the criteria you wrote down.
Watch the timing. A decision that follows closely after an applicant's protected activity will get a closer look. Have a clear, documented explanation ready for the sequence of events, including what happened before the applicant raised the matter.
Keep comments neutral. Words like "litigious," "difficult," or "trouble" will read badly later, even if they were said casually in a hallway. Keep notes factual: what the applicant said, what the criteria are, and how the applicant scored against them.
What belongs in the applicant file
A well-kept file tells the story of the decision without anyone needing to remember it. Keep these items together, in date order, so a reviewer can follow the sequence without interviewing the whole team:
- The job posting and criteria, with the date they were finalized and who approved them.
- A notice of the applicant's history, if one came up, with the date, the source, and the name of the person who received it.
- Interview notes and scores for every finalist, using the same form for each one.
- The referral to HR or counsel, including the date it was sent and what was asked.
- The decision memo, a short document that states the reasons in plain language and ties each reason to a criterion.
- Reviewer sign-off, showing that someone outside the hiring team read the memo before it was final.
- A log of applicant communications, including any conversation about the decision.
Do not add commentary to the file that you would not want read aloud. Keep opinions in a separate, clearly labeled note that goes to counsel, and keep the decision record limited to facts and criteria. For a structure you can reuse, see Hiring Decision Debrief: Notes to a Recorded Decision.
Illustrative example: warehouse supervisor
Suppose an applicant for a warehouse supervisor role mentions in an interview that she testified in a prior proceeding. The hiring manager feels uneasy and wants to pass on her. The example below shows one sensible sequence. It does not decide the outcome for any real case.
- The manager notes the disclosure in the file and tells HR the same day.
- HR asks the manager to restate the job criteria agreed before interviews began, and confirms they are in writing.
- HR asks counsel to review the applicant's situation under section 111.36, including the first passage on testimony.
- The interview panel scores the applicant against the agreed criteria, and each score is written down with a short reason.
- Any final decision includes a dated explanation tied to those criteria, reviewed by someone outside the hiring team before it goes out.
Talking with the applicant
Keep any message to an applicant about the decision and the stated criteria. Avoid discussing the applicant's past charge, testimony, or complaint unless counsel has approved what to say. A casual remark about a past case can turn an ordinary rejection email into evidence in a later dispute.
If an applicant raises their history on their own, listen, thank them, and say that the matter will go to the right people. Do not debate the merits, promise an outcome, or ask for details beyond what HR needs. Write a short note afterward recording what was said, when, and who was present.
Training your hiring team
Hiring managers often make the first call, so they need a simple rule they can follow without legal training. A one-page note can do much of the work. It should say three things: tell HR when an applicant mentions a past charge, testimony, or complaint; do not discuss that history with the applicant on your own; and keep interview notes factual and tied to the job criteria.
Run a short review before each hiring cycle. Walk through the note, ask who the team would call in each situation, and confirm that the criteria and scoring forms are current. A brief session once a cycle costs far less than a dispute over one undocumented decision.
Common mistakes to avoid
- Assuming the protection covers only current employees. Both passages name the prospective employee.
- Treating "about to testify" as outside the protection. The first passage covers that wording.
- Ignoring action taken for someone else. The second passage reaches action taken "on behalf of ... another person."
- Deciding from a summary. Excerpts and secondhand descriptions can drop conditions that matter, so read the statute itself.
- Writing reasons after a dispute starts. Notes written later look like justification. Notes made at the time are far more credible.
- Asking about past charges without checking first. Get advice on what you may ask and how to ask it before the subject comes up.
Your next step today
Pick one open job and write its criteria in a dated note before you review any applicant file. That note becomes the baseline every later decision is measured against.
Questions recruiters ask
Does the protection apply before anyone is hired? Yes. Both passages name prospective employees, which is the category an applicant is in during hiring.
Does an applicant have to win the earlier case? Outcomes are a legal question, so ask counsel rather than assume either way.
Should I tell an applicant why they were not chosen? Tell them the decision rested on the stated criteria, and leave out any mention of their past charge, testimony, or complaint. Counsel can approve the exact wording before it goes out.
Can I simply pass on an applicant who has a history like this? Put that question to counsel before any decision that turns on the applicant's past activity. Judge the applicant on the same job criteria you use for everyone else, and document how you did it.
When to get advice
This post can help you ask better questions, but it cannot tell you how a court would read a particular file. Bring three things to your counsel: the full text of section 111.36, the applicant's file with dates, and the job criteria you set before interviews began. Ask whether any part of the decision depends on the applicant's protected activity, and what process you should follow next. For filing timelines in the two states, see Ohio and Wisconsin discrimination deadlines.
Read the full statute
Start with the full section at Wisconsin Legislature, 111.36. Read the whole section, not only the two passages quoted here, before you make a status decision. Then confirm with counsel how it applies to your facts.