Employee exits are routine—until they aren’t. A rushed termination meeting, an unclear “last day,” or a missed final-pay deadline can turn a simple separation into a wage claim, an unemployment dispute, or a personnel-file fight.

This guide is a practical, Minnesota-specific checklist for employers and employees navigating resignations, layoffs, and terminations—especially in smaller shops, job sites, and multi-location operations where HR tasks often land on a supervisor’s desk.

1) Start with one sentence: “What is the separation reason and the last day?”

Before you talk about keys, laptops, or uniforms, confirm two facts in writing:

  • Separation type: resignation, discharge/termination, layoff/lack of work, end of assignment, mutual separation.
  • Last day worked vs. separation date: these may differ (for example, paid administrative leave, or sending someone home mid-shift).

Why it matters: those two facts drive final pay timing, benefit cutoffs, unemployment eligibility arguments, and what you should (and shouldn’t) put in a reference response.

2) Final pay in Minnesota: know the two different clocks

Minnesota’s final pay rules depend heavily on whether the worker is discharged or quits/resigns.

If the employee is discharged (fired/terminated)

In Minnesota, wages and commissions “actually earned and unpaid” become due upon the employee’s demand, and the employer can be in default if not paid within 24 hours after demand. (revisor.mn.gov)

Practical takeaway for employers: decide in advance how your organization will handle a demand—who receives it, how it’s documented, and how payroll can cut an off-cycle check quickly.

Practical takeaway for employees: if final wages are missing, make the request clearly (and keep a copy). Minnesota DLI’s wage-claim resources explain the process and common timing issues. (dli.mn.gov)

If the employee quits or resigns

When a worker quits, Minnesota generally requires final wages to be paid no later than the first regularly scheduled payday after the final day of employment. If that payday is less than five calendar days after the last day, payment can be delayed until the second regularly scheduled payday, but not more than 20 calendar days after the final day. (revisor.mn.gov)

Policy tip: keep your separation checklist aligned with your normal pay cycle so supervisors don’t promise “you’ll be paid tomorrow” when the law—and payroll operations—say otherwise.

3) Don’t let “usual manner of payment” become a problem

Final pay problems often aren’t about the amount; they’re about the method:

  • direct deposit turned off too early
  • a check mailed when the worker expected pickup
  • commissions “processed later” even though they’re already earned

Minnesota DLI emphasizes that separation pay timing and wage-payment rules matter—and that employees can pursue wage claims when employers don’t comply. (dli.mn.gov)

Operational best practice: confirm (in writing) how the final wages will be delivered and who to contact if there’s an error.

4) Personnel files: you need a plan for requests (and disputes)

It’s common for a separation to be followed by a request to see the personnel file—especially if the employee is applying for unemployment or challenging the termination.

Minnesota’s personnel record law provides timelines: after a written request, the employer must comply within seven working days if the record is located in Minnesota, or 14 working days if located outside Minnesota. (revisor.mn.gov)

Other practical points:

  • Employers are not required to allow a current employee to review the file if they reviewed it in the prior six months (with an annual review right after separation as long as the record is maintained). (revisor.mn.gov)
  • Minnesota DLI notes that (as of July 1, 2024) Minnesota employees have the right to dispute the contents of their personnel record—another reason to keep documentation factual and consistent. (dli.mn.gov)

Documentation rule of thumb (for supervisors): write for the day a neutral third party reads it. Avoid speculation, sarcasm, or medical assumptions.

5) Unemployment: separation documentation is your “appeal insurance”

Unemployment disputes frequently turn on whether the employee quit, was discharged, or was discharged for employment misconduct.

Minnesota’s unemployment information for applicants highlights that:

  • quitting can still be eligible in certain situations (for example, “good reason caused by the employer”), and
  • being discharged for employment misconduct generally makes an applicant ineligible for benefit payments. (mn.gov)

For employers, the main risk isn’t just paying unemployment taxes—it’s losing control of the narrative because the file is thin.

Employer checklist for unemployment readiness:

  • a clear final incident summary (date, conduct, policy expectation)
  • prior warnings or coaching notes (if relevant)
  • attendance records, customer complaints, or safety reports (if applicable)
  • the separation notice given to the employee

Minnesota’s unemployment program also provides guidance to employers on when and how to “raise an issue” about a job separation. (ui.mn.gov)

6) References: keep it consistent with your file

Minnesota is an at-will employment state, but “at-will” doesn’t eliminate legal exposure from inconsistent explanations, discrimination, or retaliation claims. Minnesota DLI’s termination overview is a good reminder that the reason cannot be illegal (for example, based on protected characteristics). (dli.mn.gov)

Best practice: decide what your organization will verify (often: dates of employment and job title) and train managers not to freelance. If you do provide more detail, make sure it matches what’s documented.

7) Restrictive covenants: noncompetes are largely off the table for new agreements

If your separation process includes reminding employees about “post-employment restrictions,” make sure you’re using up-to-date agreements.

Minnesota law makes most new noncompete agreements void and unenforceable for agreements entered into on or after July 1, 2023 (with narrow exceptions such as sale of a business). (revisor.mn.gov)

That doesn’t mean employers can’t protect business interests—confidentiality, trade-secret protections, and carefully drafted non-solicitation provisions may still be in play—but they should be reviewed with counsel, especially for multi-state workforces.

A one-page separation checklist (Minnesota-focused)

For employers

  1. Confirm separation type and last day (write it down).
  2. Gather final hours, PTO/leave balances, commissions, and deductions.
  3. Trigger final pay timeline (discharge vs. quit). (revisor.mn.gov)
  4. Decide delivery method for final wages; document it.
  5. Provide benefit continuation info as required (coordinate with your plan administrator).
  6. Secure company property; document returns.
  7. Prepare an unemployment-ready summary and keep it consistent.
  8. Be ready for a personnel-file request within statutory timelines. (revisor.mn.gov)

For employees

  1. Ask for the separation reason and last day in writing.
  2. Confirm when and how final pay will be delivered.
  3. If something is missing, request correction promptly and keep records. (dli.mn.gov)
  4. If needed, submit a written request to review or obtain a copy of your personnel file. (dli.mn.gov)
  5. When applying for unemployment, be precise about whether you quit or were discharged and why. (mn.gov)

Bottom line

Most separation disputes aren’t caused by one big mistake—they’re caused by three small ones: unclear dates, inconsistent documentation, and missed deadlines. A Minnesota-specific checklist, used the same way every time, is one of the simplest risk-reduction tools an employer can adopt—and one of the clearest ways employees can protect themselves during a transition.