Checklist: Defensible Discipline When the Employee Was Also Protected

You are about to discipline an employee who has also engaged in protected activity. Use two files: a misconduct file that states the conduct on its own terms, and a same-action file that documents timing, comparable incidents, and the stated reason.

In 2026, the NLRB, the labor board, brought back the General Motors Wright Line mixed-motive framework for evaluating discipline tied to protected activity. It overruled the 2023 precedent on Sept. 23.

Under that framework, the NLRB general counsel must establish that the employee engaged in Section 7 activity, the protected activity at issue, that the employer knew of it, and that the employer showed enough hostility toward it to connect the activity to the discipline. Once the general counsel establishes the Wright Line showing, the employer can defeat the case by demonstrating that it would have imposed the same discipline regardless of the protected activity.

The misconduct file must state the conduct

Start with the conduct, not the protected activity. The misconduct file should describe the offensive behavior on its own terms: what happened, who was involved, when it happened, and why it violated a workplace standard. If the employee cursed at a manager, capture the words, the audience, the disruption, and the policy or rule the conduct breached. If the handbook has an offensive language policy, tie the conduct to that policy. Note the protected activity separately, but do not let it shape the misconduct statement.

A manager who writes that the employee was disruptive during protected activity has combined the issues. A manager who writes that the employee used profanity in front of customers has stated the conduct in its own terms. Keep the misconduct statement free of protected-activity reference, because that is the question the same-action defense will later ask.

The same-action file must show the alternative

The same-action file is good practice to make that answer visible. It should contain the timing, comparable non-protected incidents, and the stated reason for the discipline. Show a similar outburst by another employee that produced the same write-up. For conduct during a picket line, show why the conduct itself, not the picket, determined the decision.

Timing shows the decision followed the conduct, not the protected activity. A decision made immediately after protected activity can look retaliatory even when the conduct was real. Comparators show the standard was applied consistently. The stated reason gives the decision a basis that does not depend on the protected activity.

The record must be complete before the meeting

The checklist below is the minimum. Each item should be answerable from the file in a minute. The first items build the misconduct file. The later items build the same-action file. Do not wait for the employee meeting to decide what the file should say. Complete the record before the conversation; the conversation can add facts, but it should not create the basis for discipline.

• Write the misconduct in a short paragraph: what happened, when, who saw it, and why it violated a workplace standard.
• Attach the policy or standard the conduct violated, without adding protected-activity context.
• State the discipline chosen and the reason for that level.
• List comparable non-protected incidents and the discipline given in those cases.
• Show the timing: when the conduct occurred, when you learned of it, and when you decided.
• State the reason for discipline in the same words you would use if no protected activity existed.
• Keep the protected activity in a separate note, not in the misconduct statement.
• Review the file for language that blames the protected activity rather than the conduct.

When an item fails, fix the record before the conversation. A missing comparator, a vague policy, or a reason that only makes sense because of the protected activity weakens the same-action defense.

The decision must match the conduct

The NLRB left room for future reconsideration, and it did not settle how setting-specific standards, which vary by workplace setting, apply outside this case. The file should not rely on a lone phrase or a lone incident. It should show a consistent standard, a documented reason, and a decision that could survive review.

Offensive but not severe conduct may support a warning. Conduct that threatened safety or disrupted operations may support a stronger step. The record should make that distinction clear. Do not issue the discipline until the file can show that.