Skip forward into hiring notes
RosterAcorn

Age and family exemptions: 5 Minnesota and Michigan rules

Minnesota and Michigan exemptions have specific limits: replacement hiring, retirement policies, age-based benefits, a state summer program, and employment by relatives require separate checks.

Key takeaways

  • Identify the exact provision before relying on an exemption.
  • Confirm the employer, relationship, or program involved.
  • Keep benefit questions separate from hiring decisions.
  • Record job-related reasons and send close calls to counsel.

This guide covers five exemptions in the official text of Minnesota and Michigan law. For each one, we explain what the text says, what it does not say, and where it stops. We are not lawyers, and nothing here is legal advice. Treat the list as questions to bring to your employment counsel before you place an applicant.

Before you read the exemptions

Two points will help. First, an exemption is a carve-out from a general rule in the same statute. If a situation does not fit the exact words of the exemption, the general rule still governs it. Second, words like "shall not apply," "does not apply," and "may be established" do real work. Skipping past them can lead a recruiter to apply an exception to a case it was never meant to cover.

Each quote below links to the official statute page for Minnesota or Michigan, so you can read the full text yourself.

1. Replacement hiring

The Minnesota statute says: "The provisions of section 363A.08 do not apply to the employment of one person in place of another, standing by itself, shall not be evidence of an unfair discriminatory practice." Under this sentence, the fact that one person was hired in place of another is not, on its own, evidence of an unfair discriminatory practice.

The wording is narrow. It does not say replacement hiring is always lawful, and it does not say a replacement can be chosen because of age. The phrase "standing by itself" is the key limit. The sentence addresses only the replacement fact, and other evidence is a separate question.

This matters when a client asks you to fill a role recently vacated by a worker of a particular age. The exemption does not give the client or your team a reason to screen by age. Your records should show that the applicant was selected on job-related grounds, stated in plain language.

Source: Minnesota Statutes section 363A.20.

2. Published mandatory retirement age

The Minnesota text says that "[b]y law or published retirement policy, a mandatory retirement age may be established without being a violation of this chapter if it is established consistent with section 181.81." Two conditions appear in that sentence. The age must come from law or a published retirement policy, and it must be set consistent with section 181.81.

Recruiters often assume too much here. A mandatory retirement age is not a general license to avoid older applicants. If a client says its workforce has a retirement age, ask where that age is written. A verbal understanding or a hiring manager's habit is not a published policy. Confirm the requirements of section 181.81 before relying on a retirement age in a placement.

Source: Minnesota Statutes section 363A.20.

3. Age-based differential treatment

The Minnesota text says that "[n]othing in this chapter shall be construed to prohibit the establishment of differential privileges, benefits, services, or facilities for persons of designated ages if (1) such differential treatment is provided pursuant to statute, or (2) the designated age is greater than 59 years or less than 21 years."

The sentence has two paths. The first is differential treatment that a statute itself provides. The second is a designated age greater than 59 or less than 21. Both paths concern "privileges, benefits, services, or facilities," which is not the same as a rule for who gets hired.

The statute then sets a limit: "Clause (1) does not apply to hiring, tenure, compensation, upgrading, or conditions of employment." The first path does not reach the decisions that matter most to a recruiter. A client may run a benefit built around an age group, and the statute may allow it. In practice, that benefit can exist without changing who is interviewed, offered a role, or paid. It does not mean the same age line can decide those outcomes.

The second path is also not a general hiring license. If a client asks you to screen applicants by whether they are over 59 or under 21, you are in a different situation from a benefit program. Take that request to counsel before acting on it.

Source: Minnesota Statutes section 363A.20.

4. The state summer youth employment program

The Minnesota text says that "[t]he provisions of section 363A.08 with regard to age shall not apply to the state summer youth employment program administered by the commissioner of employment and economic development."

The sentence names one state program and the official who administers it. This exemption concerns that program, rather than private summer jobs, a client's seasonal hiring, or youth hiring in general. If you place young workers into summer roles, you cannot cite this exemption unless the role is actually part of that state program. Ask the client to show whether the role belongs to the state program. If it does not, the ordinary age rules still apply.

Source: Minnesota Statutes section 363A.20.

5. Employment by a parent, spouse, or child

The Michigan text, in section 37.1202 of the Michigan Compiled Laws, says: "(3) This section shall not apply to the employment of an individual by his or her parent, spouse, or child."

This family exemption limits the application of section 37.1202. It names three relationships: parent, spouse, and child. It concerns who the employer is, not a family tie between an applicant and a staffing firm or client. A placement at a company a family member owns requires checking who actually employs the worker. A relative who works for the client is not necessarily the employer. A family connection on one side of a placement does not make the placement exempt. Both the employer and the relationship must match the words of the exemption.

Suppose a family-owned business asks your firm for a worker, and the owner is the applicant's parent. The question is whether the owner is the one employing the applicant. If your firm is the employer of record, or the placement runs through a different legal entity, the answer may change. Counsel should review those details before you rely on the exemption.

Do not assume this family exemption resolves an age-related hiring question.

Source: Michigan Legislature, MCL 37.1202.

Where the exemptions stop

Across the five, the same pattern appears. Each one has a clear boundary, and most mistakes happen at that boundary.

The first boundary is the decision being made. The limit on hiring, tenure, compensation, upgrading, and conditions of employment applies to clause (1), the path for treatment provided pursuant to statute. Many age-based exceptions concern programs and benefits, not placement.

The second boundary is the named relationship or program. When a situation is close to the named relationship or program but not identical, do not assume the exemption applies.

The third boundary is the source of the rule. A retirement age that exists only in conversation does not meet that test.

The fourth boundary is evidence. Age-based comments or instructions attached to a replacement hire raise a different question.

What this means for your hiring process

Most staffing teams do not need to memorize statutes. They need a process that flags cases where an exemption is tempting and sends those cases to someone who can answer them.

Start by listing the questions that come up most often. The usual question is not whether an exemption exists but whether it applies to this client, this role, and this applicant. Keep that list alongside the answers counsel has given you.

Next, ask clients to state the basis for any age or family-related request in writing. A client claiming a summer youth program should be able to name the program. A client requiring a certain age should identify the rule that requires it. A client pointing to a family relationship should identify the employer. If the answer is unclear, stop and ask counsel.

Third, separate benefit questions from hiring questions. Do not let a benefits rule drift into a screening rule. For related questions, review age discrimination in hiring and benefits.

Fourth, check the state where the work happens. The rules discussed here are Minnesota and Michigan rules. If your team places workers in several states, keep a table with each state, the exemption relied on, the source link, and the date you checked it. Statutes change, and a stale table is a risk in its own right.

Fifth, keep records showing job-related reasons for each choice. In a Minnesota replacement, the file should show the skills, availability, and requirements behind the selection. A file that rests on age, or on a vague sense that the client wants someone younger or older, creates trouble even when a general exemption exists. Use a hiring decision debrief to organize that reasoning.

Sixth, route close calls through one contact. When a single person decides which exemptions the firm relies on, the reasoning stays consistent across placements and is easier to review later.

Common mistakes to avoid

Treating an exemption as general permission is the first error. An exemption covers the situation its words describe and nothing more. A recruiter who hears that a state allows age-based differences in one setting should not conclude that age can be used in every setting.

Another mistake is assuming an exemption for one characteristic covers another. Review age and family questions separately rather than treating the Minnesota age provisions as an answer to family-status questions.

The fifth is relying on old assumptions. Check the statute pages at a regular interval and record the date of each check.

What this guide does not cover

The guide covers five exemptions: a Minnesota replacement-hiring sentence, a Minnesota mandatory retirement provision, a Minnesota differential-treatment provision, a Minnesota summer youth program provision, and a Michigan provision on employment by a parent, spouse, or child. It quotes the words each one relies on and links to the source page.

It does not cover every age or family rule in either state, federal law that may apply alongside state law, or the rules of any other state. It also does not predict how a court or agency would read these sentences in a particular case. Those questions belong to counsel.

Illustrative example: a replacement request

A recruiter reviews 10 applicants for a replacement role. The client asks for someone younger. The recruiter records the role's skills, availability, and requirements, then sends the age-related request to counsel before acting. The replacement itself and the client's screening instruction are separate questions; calling the role a replacement does not settle the instruction.

What to do today

Read the exact words of an exemption, identify the employer, program, or relationship it names, and ask whether the placement fits those words. If it does not fit cleanly, ask someone who can give a firm answer before you place the applicant. Keep a copy of each provision you rely on, along with the date you retrieved it.

Questions about applying the exemptions

What should a recruiter record before relying on an exemption?

Record the state, provision, source link, date checked, and placement details for counsel to review.

What should you do with an unclear client request?

Ask the client for its written basis and send the unresolved question to counsel before acting.

Sources