| Course | HCA 465 Health Care Administration and Management |
|---|---|
| Topic | Topic 6 |
| Paper type | Performance management case |
| Length | About 1,020 words, 3 pages |
| Format | APA 7 student paper |
| School | Grand Canyon University (GCU) |
| Program | BS in Health Care Administration |
| Updated | September 2026 |
Free sample paper for HCA 465 Topic 6
Five Incomplete Cooling Logs in Three Weeks: A Performance Management Case Kept in Observable Terms, From First Conversation to Follow-Up
[Author Name]
College of Nursing and Health Care Professions, Grand Canyon University
HCA-465: Health Care Administration and Management
Topic 6 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.
Five Incomplete Cooling Logs in Three Weeks: A Performance Management Case Kept in Observable Terms, From First Conversation to Follow-Up
The Problem, Described as Behavior
Luis is a cook on the day shift in Mesa Grande Medical Center's production kitchen, with nine years in the department and good reviews until this year. His supervisor raised a concern that he had become careless about food safety. That description cannot be managed, because a manager cannot document carelessness or ask anyone to change an attitude. The manager therefore restated the concern as behavior, with dates. On March 4, 6, 11, 18 and 20, Luis cooked batches of soup, rice or cooked chicken for later service and recorded only the first temperature reading on the cooling log, leaving the second and third readings blank. On March 20, the evening cook found a pan of rice from Luis's batch at 58 degrees Fahrenheit seven hours after cooking, and it was discarded. In the same three weeks, Luis's other duties, recipe accuracy, portioning and cleanup, met standard according to the supervisor's checklist.
The Standard Being Missed
The standard was not invented for this conversation; it already existed in three places. The federal model food code, adopted by the state, requires cooked foods to be cooled from 135 to 70 degrees Fahrenheit within 2 hours and to 41 degrees or less within a total of 6 hours (U.S. Food and Drug Administration, 2022). The department's cooling procedure translates that rule into a log with three readings: at the start of cooling, at 2 hours and at 6 hours or when the food reaches 41 degrees, each initialed. Luis's job description lists "records temperatures on production and cooling logs as required by department procedure" as an essential function, and he signed an acknowledgment of the cooling procedure at his last annual competency review. Quoting the standard from these sources keeps the conversation about the job rather than about Luis.
The First Conversation
The manager met Luis privately on March 22 with his supervisor present. The union contract gives employees the right to a steward in any meeting that may lead to discipline, so the manager told Luis in advance that this was a coaching conversation, not an investigatory interview, and that he could bring a steward if he wished; he chose not to. The manager described the five dates and the rice, showed him the logs, and asked what had happened. Luis explained that since January, when the department cut a morning prep position, he had been assigned both the soup station and the hot line during the lunch rush, and the 2-hour cooling check fell in the middle of the rush. He admitted he had stopped setting the timer. The manager asked what would make the checks possible, and Luis suggested moving the batch cooking earlier so the 2-hour check would fall before 11 a.m.
Expectations, Support and Follow-Up
The manager wrote down what was agreed and gave Luis a copy. The expectation: every cooling log complete, with all three readings initialed, starting March 23. The support: batch cooking for items needing cooling moves to the 6:30 a.m. start, a kitchen timer is mounted at the soup station, and the supervisor will check the logs at 11 a.m. each day for two weeks. The follow-up: the manager and Luis will review the logs together on April 5 and again on April 19. The consequence: if logs remain incomplete after April 5, the next step is a documented verbal warning under the progressive discipline provisions of the contract. Feedback research suggests that feedback focused on the task and on specific ways to improve is more effective than feedback focused on the person (Kluger & DeNisi, 1996), which is why the written summary names the logs and the dates, not Luis's attitude.
What the Manager Chose Not to Do
Several easier responses were available and were deliberately set aside. The manager could have issued a written warning on March 20, when the rice was discarded, since the discarded food was a clear failure and the standard was documented. That would have satisfied the paperwork and left the cause untouched, because the same two duties would still have collided at the same hour for whoever held the station. The manager could have retrained Luis on the cooling procedure, but he already knew it; his competency record showed he had explained it correctly at his review. The manager could also have moved the logging duty to another cook, which would have hidden the problem rather than solved it and signaled to Luis that he was no longer trusted with a basic part of his job. Each of these choices would have looked decisive. None would have produced complete logs, and the discarded rice showed that the logs were not a formality: they are how the kitchen proves that food served to patients, some of them immunocompromised, was cooled safely.
What Happened
At the April 5 review, 18 of 19 cooling logs were complete; one had a missing 6-hour reading, which the evening cook had taken but not recorded. The manager treated that as a handoff problem rather than Luis's failure and changed the procedure so that the evening cook initials the final reading. At the April 19 review, all logs were complete. The manager recorded the outcome in Luis's file as a completed coaching plan with no discipline.
What the Case Teaches
The case shows why performance management starts with behavior and a standard rather than with a judgment of character. Described as carelessness, the problem would have led to a warning and a resentful employee. Described as five incomplete logs, it led to a cause, a staffing change in January that put two duties in the same hour, and a fix the employee proposed himself. Performance management is a continuous process of setting expectations, observing, giving feedback and supporting improvement, not a single annual event (Aguinis, 2019). The manager also learned something about the department: the January staffing cut had created food safety risk that no one had examined, and the same pattern should be checked at other stations.
References
Aguinis, H. (2019). Performance management (4th ed.). Chicago Business Press.
Kluger, A. N., & DeNisi, A. (1996). The effects of feedback interventions on performance: A historical review, a meta-analysis, and a preliminary feedback intervention theory. Psychological Bulletin, 119(2), 254-284. https://doi.org/10.1037/0033-2909.119.2.254
U.S. Food and Drug Administration. (2022). Food code 2022. U.S. Department of Health and Human Services.
Reading the GCU HCA 465 Topic 6 instructions
HCA-465 Topic 6 asks students to address an employee performance problem as a manager. Students typically describe the problem, identify the performance standard, plan and conduct a conversation with the employee, and set expectations, support and follow-up, considering relevant policies and employment rules. The assignment emphasizes describing performance in observable terms rather than judgments about attitude, and it rewards approaches that look for causes before choosing consequences. Students should apply performance management principles, respect any union or policy requirements and document the process clearly. Scholarly sources on feedback and performance management should support the approach and the outcome.
Inside the HCA 465 Topic 6 example
The finished case stays in observable terms throughout, which is the discipline the topic exists to teach. The problem is described as behavior with dates and instances rather than as an attitude, because a manager cannot document an attitude and cannot ask anybody to change one. The standard being missed is quoted from somewhere it already existed, whether a job description, a departmental expectation or a prior conversation. The meeting is drafted with the opening the manager will actually use, the evidence in the order it will be raised, and room for the employee's account, which sometimes changes the diagnosis entirely. The follow-up memo states what changes, by when, how it will be judged and what happens if it does not.
HCA 465 Topic 6 rubric: what Excellent looks like
GCU's rubric for the performance case rewards observable, fair and documented management. Excellent cases describe the problem as behavior with dates and instances and quote a standard that already existed. Credit goes to a private first conversation that asks about causes, respects employee rights under policy or contract, and leads to written expectations, support, follow-up dates and stated consequences. The rubric values evidence of the outcome and reflection on what the manager learned. The highest level explains alternative responses that were considered and rejected, and connects the approach to research on feedback and performance management.
Common HCA 465 Topic 6 mistakes, and how to avoid them
Marks concentrate on whether the record would hold up, and the common failures are all documentation failures. Describing the problem as a bad attitude or a lack of professionalism gives the employee nothing specific and gives a later reader nothing to verify. Records built entirely on what other people reported, with no instance the manager observed or confirmed, collapse the first time they are questioned. Cases that skip the standard leave the manager arguing about whether a rule existed. Meetings drafted as a speech, with no room for the employee to answer, fix the diagnosis before the door closes. Follow-ups without a measure or a date are conversations that will be repeated. Language a manager would not want read aloud later is the last reliable deduction.
Get an HCA-465 Topic 6 example written to your instructions
Send us the HCA-465 Topic 6 instructions, your section's rubric and the performance scenario you were assigned. We write a custom example to those criteria, with the pattern described in observable terms, the standard located, the meeting drafted with room for a response and a follow-up carrying a measure and a date, in 24 to 48 hours. The first one is free.
More HCA 465 papers and BS in Health Care Administration samples
- HCA 465 Topic 1: Management Role Analysis
- HCA 465 Topic 2: Delegation Decision Memo
- HCA 465 Topic 3: Departmental Budget Memo
- HCA 465 Topic 4: Interprofessional Conflict Case
- HCA 465 Topic 5: Authority Gap Discussion Post
- HCA 465 Topic 7: Decision Rationale Memo
- HCA 465 Topic 8: Management Philosophy Paper
- HCA 460 Topic 6: Risk Register
- HCA 240 Topic 6: Patient Responsibility Analysis
- HCA 450 Topic 6: Outcome Measurement Plan
- HCA 360 Topic 6: Systems Evaluation
HCA 465 Topic 6 questions, answered
Why does attitude not belong in the record?
Because nobody can verify it and nobody can act on it. An employee told to improve their attitude has been handed a verdict rather than an instruction, and a later reader has no way to check whether it was fair. Two missed handoffs on named dates can be confirmed, discussed and corrected, which is what a record is for.
What if the complaints came from other staff?
Then verify before you document. Reports from colleagues tell you where to look rather than what happened, and a record resting only on them puts the manager in the position of defending somebody else's account. Observing directly, checking a schedule or a log, or asking the employee first turns a complaint into evidence you can stand behind.
How specific does the follow-up have to be?
Specific enough that both people would agree afterward on whether it happened. That means a described change, a way of judging it that does not depend on impression, a date and a stated consequence. Follow-ups asking for sustained improvement leave both sides free to reach opposite conclusions at the review, which is how these cases end badly.
Where can I find a free HCA 465 Topic 6 sample paper?
This page holds the complete performance management case, with the behavior and dates, the quoted standard, the first conversation, the written plan, the outcome and the lessons. Send the case from your classroom and a matching model is written free.
Why restate carelessness as behavior in HCA 465 Topic 6?
Because a manager cannot document an attitude or ask someone to change one. Five dated incomplete logs and one discarded batch are facts that can be discussed, traced to a cause and corrected.