| Course | MGT 465 Employee Relations |
|---|---|
| Topic | Topic 3 |
| Paper type | Discipline file review |
| Length | About 980 words, 3 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | BS in Business Management |
| Updated | October 2026 |
Free sample paper for MGT 465 Topic 3
Could the Dismissal Be Justified, and Could This File Defend It? A Progressive Discipline Review for a 58-Year-Old Forklift Operator, Read as an Investigator Would
[Author Name]
Colangelo College of Business, Grand Canyon University
MGT-465: Employee Relations
Topic 3 Assignment
[Instructor Name]
[Date]
The organization, setting and figures below are a composite written as a model document. No real employer, client, colleague or patient is described.
Could the Dismissal Be Justified, and Could This File Defend It? A Progressive Discipline Review for a 58-Year-Old Forklift Operator, Read as an Investigator Would
The Request
The warehouse manager at Lakeview Distribution's non-union Kenosha site wants to dismiss a forklift operator, Ray Thibodeaux, aged 58, after a third safety incident in five months. Before approving, HR asked for the file to be reviewed the way an investigator from a fair employment agency would read it if Thibodeaux filed an age discrimination charge. This review lays the file out in date order, tests each document and separates two questions that are easy to confuse: whether dismissal could be justified on the conduct, and whether this file could defend it. All details are illustrative.
The File in Date Order
Table 1
The Discipline File for the Forklift Operator
| Date | Event | Document | Weakness |
|---|---|---|---|
| May 6 | Operator seen carrying forks raised about four feet while traveling | Supervisor's notebook entry: "Talked to Ray re forks" | No record given to the operator; no policy cited; no signature |
| July 22 | Operator did not sound horn at an aisle intersection; near collision with a picker | Written warning, signed by operator the same afternoon | Issued before the operator was asked what happened |
| September 30 | Rack strike while placing a pallet; $3,400 of product damaged | Incident report and supervisor's recommendation to dismiss | No interview with the operator recorded |
Table 1 lists every document in the file.
Read on its own, the file tells a simple story of three incidents and escalating discipline. Read as an investigator would, each document raises a question about how carefully the facts were gathered before discipline was imposed.
How an Investigator Would Read It
An investigator reviewing an age discrimination charge would ask whether the employer's stated reason is the real one. In cases built on circumstantial evidence, the employee first shows facts suggesting discrimination; the employer then states a legitimate reason; and the employee can try to show that the reason is a pretext (McDonnell Douglas Corp. v. Green, 1973). Federal age discrimination law covers workers from age 40 upward, so the operator, at 58, falls within it (Age Discrimination in Employment Act, 2018). Evidence that the employer's explanation is not credible can be enough for a finding of discrimination (Reeves v. Sanderson Plumbing Products, Inc., 2000). The investigator would therefore look hard at whether the file supports the safety reason.
Three weaknesses stand out. The first warning exists only in the supervisor's notebook. It cites no rule, was never given to the operator in writing and is not signed. An investigator would give it little weight. The second warning was signed the same afternoon as the incident, before anyone recorded the operator's account. That makes it look like a conclusion reached before the facts were gathered. The third incident report contains no interview with the operator at all.
The Comparator
The most serious problem is outside the file. The review checked how similar incidents were handled on other shifts. On the day shift, a forklift operator aged 31 had two rack strikes in the past year, one of which damaged about $2,800 of product. That operator received one written warning and no further discipline.
An investigator would compare the two directly. Both operated forklifts under the same safety rules. The older operator would be dismissed after one undocumented conversation, one hastily issued warning and one rack strike; the younger operator, with two rack strikes, received one warning. Unless Lakeview can explain the difference with something other than age, such as a difference in the severity of the incidents or a prior record the younger operator lacked, the comparison would strongly suggest that the safety reason is not the whole story.
Two Questions, Two Answers
Could dismissal be justified on the conduct? Possibly. Traveling with raised forks, failing to sound a horn at an intersection and striking a rack are real safety violations. Three in five months is a pattern, and forklift incidents can injure people. A well-run warehouse might reasonably decide that an operator with that record should not drive a forklift.
Could this file defend it? Not yet. The first incident is barely documented, the second warning looks rushed, the third incident lacks the operator's account and a younger operator with a similar record was treated more leniently. If Lakeview dismissed the operator on this file, it would be relying on its conclusion about the conduct while giving an investigator several reasons to doubt that conclusion.
Keeping the two questions apart matters because managers often treat them as one. A manager confident that the conduct was serious may assume the paperwork does not matter; an investigator, who did not see the conduct, will judge mainly from the paperwork.
What Lakeview Should Do
The review recommends against dismissal on the current file and sets out what would need to happen before a decision. First, interview the operator about the September 30 rack strike and record the account. Second, determine whether the day-shift comparator's incidents were treated leniently by mistake; if so, Lakeview must decide whether to apply the same standard to both operators going forward. Third, consider a final written warning for the September incident, with a clear statement that any further safety violation will lead to removal from forklift duty or dismissal, and offer refresher training.
If the operator has another incident after that, the file will show a documented history, a fair investigation and consistent treatment. That file could defend a dismissal. This one cannot. The review also recommends that Kenosha's supervisors receive guidance on documenting verbal warnings, interviewing employees before issuing discipline and checking how similar incidents were handled, since the weaknesses here are likely to appear in other files too.
None of these steps prevents Lakeview from acting on safety. If the operator's driving poses an immediate risk, Lakeview can remove him from forklift duty while the review is completed, a step that protects coworkers without prejudging the outcome.
References
Age Discrimination in Employment Act, 29 U.S.C. ยง 621 et seq. (2018).
McDonnell Douglas Corp. v. Green, 411 U.S. 792 (1973).
Reeves v. Sanderson Plumbing Products, Inc., 530 U.S. 133 (2000).
Reading the GCU MGT 465 Topic 3 instructions
MGT-465 Topic 3 asks students to evaluate whether a discipline file supports the action a manager wants to take. Judging only whether the employee deserves dismissal misses half the question. The prompt rewards a review that lays out the file in date order, tests each document for what an investigator would weigh, checks how comparable employees were treated and separates two questions: whether the conduct could justify the action and whether the file could defend it. Students should apply the relevant legal framework accurately and recommend specific steps that would make the file defensible, along with guidance for supervisors that prevents the same weaknesses elsewhere.
Inside the MGT 465 Topic 3 example
The review opens with the manager's request and the reason HR asked for an investigator's reading. Table 1 lists the three incidents with their documents and weaknesses. A section applies the burden-shifting framework from discrimination law and explains why each document would carry little weight. The comparator section shows a younger operator treated more leniently for similar conduct. Two short answers follow, one on the conduct and one on the file. The recommendation is to interview the operator, resolve the comparator issue, issue a final warning with training and give supervisors guidance on documenting discipline. The review also notes that the operator can be moved off forklift duty while the file is completed.
Where the marks sit in the MGT 465 Topic 3 rubric
Faculty grading the file review reward a reading that tests every document rather than accepting the file as complete. Strong reviews identify missing records, warnings issued before the employee was heard and inconsistent treatment of comparable employees. Credit goes to applying the legal framework accurately, including the role of pretext evidence. The rubric values separating whether conduct could justify dismissal from whether the file could defend it, since the two often diverge. The highest band recommends concrete steps that would make a future decision defensible and extends the lesson to other supervisors. Reviews that approve dismissal without checking comparators usually lose marks. Noting interim safety steps shows the review does not ignore the conduct.
Common MGT 465 Topic 3 mistakes, and how to avoid them
Discipline papers lose the most when the conclusion arrives before the evidence does. A review agreeing that three incidents justify dismissal, because three is a lot, has judged the conduct and never read the file. Papers that miss the comparator fail on the point where discipline decisions are most often challenged, and here the age gap turns an inconsistency into a possible discrimination claim. Treating an undocumented verbal warning as a completed step credits the employer with a record it does not have. Citing Daugherty's tests at an unrepresented site without explaining why they are used there misapplies an arbitral standard as though it were a statute. Recommendations stopping at yes or no, silent on what must happen first, leave the manager holding the same weak file.
Get an MGT-465 Topic 3 example written to your instructions
Send the MGT-465 Topic 3 instructions, your section's rubric and the discipline case or employee file the assignment describes. We write a custom example to those criteria, with incidents set in date order, notice and prior steps checked, the seven tests applied as a checklist, comparators examined and the next steps for the file stated, in 24 to 48 hours. The first one is free.
More MGT 465 papers and BS in Business Management samples
- MGT 465 Topic 1: Employment Relationship Analysis
- MGT 465 Topic 2: Grievance Step Record Analysis
- MGT 465 Topic 4: Concerted Activity Analysis
- MGT 465 Topic 5: Informal Resolution Dq Post
- MGT 465 Topic 6: Workplace Investigation Report
- MGT 465 Topic 7: Bargaining Preparation Brief
- MGT 465 Topic 8: Relations Climate Evidence Review
- MGT 460 Topic 3: Internal Supply Projection
- MGT 455 Topic 3: Bottleneck Capacity Calculation
- BUS 317 Topic 3: Cost Behavior Impact Memo
- MGT 440 Topic 3: Scope Statement and Change Log
MGT 465 Topic 3 questions, answered
What are Daugherty's seven tests?
A set of questions the arbitrator Carroll Daugherty used to judge just cause: whether the employee had notice of the rule, whether the rule was reasonable, whether the employer investigated before deciding, whether the investigation was fair, whether it produced substantial proof, whether rules and penalties were applied evenly, and whether the penalty fit the offense and the employee's record. Arbitrators still cite them widely.
Why use just cause tests where there is no union?
Because the questions they ask are the ones any reviewer will ask. An agency looking at a discrimination charge examines notice, investigation, evidence and consistency to judge whether the stated reason was the real one. Using the tests as a checklist at an at-will site does not create a just cause obligation, a point the example states plainly; it simply builds a file that answers those questions.
Does an undocumented warning count?
It may have happened, but a file that cannot show it happened gives little support when a decision is challenged. The operator may remember the conversation as advice rather than a warning. The example counts it as a gap, recommends that future warnings be recorded and signed by the employee, and does not treat the missing step as fatal, since the conduct itself is documented elsewhere.
Where can I find a free MGT 465 Topic 3 sample paper?
The forklift operator file review is above, from the request and the dated table to the investigator's reading, the comparator, the two answers and the recommendation. Send the file details you need reviewed, and a free review can be drafted.
Why can the file not defend dismissal in MGT 465 Topic 3?
The first warning is undocumented, the second was signed before the operator was heard, the third incident lacks the operator's account and a younger operator with similar incidents received only one warning.