HD570 Unit 7 Supervision and Performance Case Example

Reviewed by Elspeth Marlowe, MSN, RN Health Education Leadership and Management Purdue University Global Free custom sample in 24 to 48h

Responding to a performance problem with data, dates and support rather than encouragement alone is the approach of the HD570 Unit 7 supervision and performance case. In this example a veteran educator struggles in a new role. Purdue Global HD 570 asks MS in Health Education students to work through a supervision scenario. At composite Ashcombe Health Plan, a health educator who taught community classes for fourteen years was moved to postpartum phone outreach when the classes were cut. Ten weeks later, 38 percent of the educator's calls lack the encounter code state reporting requires, and daily contacts lag the team. The case examines causes, sets three measurable expectations, adds coaching and splits the role between outreach and the remaining prenatal classes.

CourseHD570 Health Education Leadership and Management
UnitUnit 7
Paper typeSupervision and performance case
LengthAbout 1,100 words, 7 pages double-spaced
FormatAPA 7 student paper
SchoolPurdue University Global
ProgramMS in Health Education
UpdatedOctober 2026

Free sample paper for HD570 Unit 7

1

Thirty-Eight Percent Uncoded: A Unit 7 Supervision and Performance Case for a Veteran Health Educator Moved to Phone Outreach

[Student Name]

Purdue University Global

HD570: Health Education Leadership and Management

Unit 7 Supervision and Performance Case

[Instructor Name]

[Date]

Ashcombe Health Plan, the employee and every figure are composite; the feedback, goal setting and transition sources cited are real.

What this part is doingStating the gap and the kind of response in the lead tells the grader the case will be specific.
2

The Situation

Pat Delgado has worked in Health Education for fourteen years, nearly all of it teaching community classes on diabetes, nutrition and prenatal care. When the open-enrollment class series ended under the Unit 4 budget reduction, Delgado's hours moved to postpartum outreach calls. Ten weeks into the new assignment, the outreach system shows three problems.

Coding. Each completed outreach contact must carry an encounter code so that it is reported to the state and counted toward quality measures. Thirty-eight percent of Delgado's completed calls have no code, against a team rate of 4 percent. Uncoded calls do not count, so the work is invisible to the plan and the state.

Volume. Delgado completes an average of 13 contacts a day, against a team average of 21.

Notes. Call notes are thorough, often longer than colleagues', and members' feedback on Delgado's calls is the best on the team.

Understanding the Causes

Before meeting Delgado, I reviewed the call records and the training log. Delgado completed the outreach system's online module but did not attend the two hands-on coding sessions, which were held during class weeks. Calls are long because Delgado teaches during them, covering topics beyond the reason for the call. And the move was not Delgado's choice. Bridges (2009) describes transitions as a psychological process of letting go of an old role before a new one can be accepted. Fourteen years of teaching ended in a budget memo, and the outreach assignment was the result of that memo.

A performance problem that began the week an employee lost the work they had done for fourteen years is not only a problem of skill, and a response that treats it only as a coding error will fix the codes and lose the employee.

What this part is doingThe highlighted sentence explains why the case addresses the transition as well as the metric.
3

What I Considered First

My first instinct was to send Delgado back to the online coding module and set a deadline. That would have treated the problem as a gap in knowledge alone, ignored the transition and very likely produced resentment without much improvement. My second instinct was to move Delgado back to classes entirely. That was not possible, since the class series had been cut, and it would have left the outreach work short. The approach I chose combines expectations, support and a partial return to teaching.

Preparing for the Meeting

I set aside forty-five minutes, chose a private room rather than my office and prepared one page of data with the team figures beside Delgado's. I wrote down three things I wanted Delgado to leave the meeting knowing: what the problem was, why it mattered and what help would be offered. I also prepared to listen, since the causes I suspected were only guesses until Delgado spoke.

The Meeting

I met Delgado privately, with the data printed on one page. I began with what was going well: member feedback and the quality of call notes. Then I showed the coding rate and contact volume beside the team figures and explained what uncoded calls mean for state reporting and for the department's case to leadership. I asked what Delgado saw as the cause.

Delgado said the coding screen was confusing and that the system's prompts felt like reading a script to a new mother. Delgado also said, after a pause, that losing the classes had been hard.

Research on feedback suggests it improves performance more reliably when it directs attention to the task and to specific steps, rather than to the person (Kluger & DeNisi, 1996). The conversation stayed on the work and the conditions around it.

Expectations

We agreed on three expectations, each with a measure, a target and a date. Specific, challenging goals tend to produce better performance than vague ones (Locke & Latham, 2002).

Coding. Uncoded completed calls below 10 percent by the end of week four, and below 5 percent by the end of week eight, measured from the outreach system's weekly report.

Volume. An average of at least 17 completed contacts a day by week eight, rising to 20 by week twelve.

Call length. A median call length under twelve minutes by week eight, with longer calls allowed when a member asks for more.

Support

Delgado will attend the next hands-on coding session and spend two half-days shadowing the team's most accurate coder. A one-page coding guide will sit beside the phone. I will review ten of Delgado's calls each week for the first four weeks and meet for twenty minutes every Friday to go over the weekly report.

A Changed Assignment

The department still runs a prenatal class series, about 600 hours a year, which needs a lead teacher. From next month, Delgado will teach that series half-time and do postpartum outreach the other half, calling members who attended prenatal classes. Those members already know Delgado, which suits a teaching style on the phone, and the arrangement keeps fourteen years of class experience in use.

If It Does Not Improve

If coding is not below 10 percent by week four, I will consult the human resources business partner about a formal performance improvement plan, which would set the same targets in writing with a defined review period. I told Delgado this plainly at the first meeting, so that no later step comes as a surprise.

Documentation

After the meeting I wrote a short summary of what was discussed and agreed, including the targets and dates, and sent it to Delgado the same day with an invitation to correct anything. A copy went into the supervision file. Each Friday meeting adds a few lines. If a formal plan becomes necessary, this record shows that expectations were clear and support was offered from the start.

Reflection on the Approach

The approach rests on separating three things that could easily blur: the data, which are not in dispute; the causes, which include training gaps and a difficult transition; and the response, which combines clear targets with support and a better-fitting role. Each piece has a date someone will check. If the targets are met, Delgado's success will be recognized in the next performance review, and the split assignment will continue as long as the class series runs, since it uses Delgado's strengths in a way the outreach role alone did not.

What this part is doingSummarizing how the response is structured shows the case was planned rather than improvised.
4

References

Bridges, W. (2009). Managing transitions: Making the most of change (3rd ed.). Da Capo 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

Locke, E. A., & Latham, G. P. (2002). Building a practically useful theory of goal setting and task motivation: A 35-year odyssey. American Psychologist, 57(9), 705-717. https://doi.org/10.1037/0003-066X.57.9.705

The Purdue Global HD570 Unit 7 instructions

The seventh unit usually presents or asks for a supervision scenario and expects a plan for addressing performance. Prompts often ask how you would prepare, conduct a conversation, set expectations, offer support and decide next steps. Review the data before the meeting and consider causes beyond skill, such as training gaps or a difficult transition. Begin the conversation with what is going well, then present the facts. Give each expectation a number to hit and a day by which to hit it. Offer specific support. Consider whether a change in assignment would use the person's strengths. Say when a formal process would begin and who in human resources is involved. Document what was agreed. Many sections expect five to eight pages.

How this HD570 Unit 7 example is built

The case opens with the educator's history and three findings from the outreach system: uncoded calls, low volume and excellent member feedback. A section on causes points to missed coding training, a teaching style on the phone and a transition the educator did not choose. The highlighted sentence explains why the transition matters. The supervisor considers and rejects two first instincts, prepares a one-page summary and holds the meeting in private. Three expectations follow with dates, then coaching, a split assignment that returns the educator to the prenatal class series half-time, the threshold for a formal plan, documentation and reflection.

HD570 Unit 7 rubric: what earns full points

Supervision cases are typically assessed on preparation, fairness, clarity of expectations, quality of support, use of management or behavioral research and appropriate escalation. Preparation earns credit when data and possible causes are reviewed before the meeting. Fairness shows in listening and in recognizing strengths. Expectations score well when a third party could tell whether each was met. Support should be specific and scheduled. Research on feedback or goal setting strengthens the case when applied to the conversation. Escalation should be named in advance without being the first step. Clear writing and APA citations complete the assessment. Cases that use the employee's strengths in a revised assignment often show the most thoughtful management.

Common HD570 Unit 7 mistakes, and how to avoid them

The most common weakness is a vague plan, such as encouraging the employee to improve, with no measures or dates. Another is moving straight to formal discipline without support. Some cases treat a performance problem purely as a skill gap and ignore circumstances such as a role change. Others offer support but never say what happens if it fails. Separating the data, the causes and the response, as the example does, keeps the plan fair and clear. If your supervision scenario differs, share the facts and the person's history, and a writer can help you draft expectations and a support plan. A same-day written summary of the meeting protects both the employee and the supervisor.

Get an HD570 Unit 7 example written to your instructions

A personnel case with no clean answer is where a free first custom sample earns its keep: it separates causes, admits what the organization contributed and sets expectations with numbers, support and dates, all within 24-48h. Paste the situation your HD570 scenario describes, any performance data it gives, and the Unit 7 prompt and rubric. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.

More HD570 papers and MS in Health Education samples

HD570 Unit 7 questions, answered

Should the case recommend firing the employee?

Rarely as a first step. Most scenarios expect support and a fair period to improve before any formal action, and a case that jumps to termination usually skips analysis the course wants to see. If the facts involve misconduct rather than performance, the answer changes, so say which kind of problem you think it is and why.

How specific should performance expectations be?

Specific enough that the employee and a third party would agree whether each was met: a measure, a target and a date. 'Improve documentation' fails that test; 'encounter codes on 95 percent of calls by day 30' passes it. Pair each expectation with the support the organization will provide, since expectations without support tend to read as a paper trail for dismissal.

Can the case mention human resources policy?

Yes, and it usually should, in general terms. Say where a formal improvement plan would begin, who in human resources is consulted, and what documentation the process requires. Avoid presenting legal conclusions or policy details your scenario does not supply. A manager who knows when to involve human resources is showing the judgment this unit assesses.

Where can I find a free HD570 Unit 7 sample paper?

This page carries a complete Unit 7 supervision and performance case for a health educator struggling after a move to phone outreach.

How specific should performance expectations be?

Specific enough that the employee and an outside observer would agree whether each was met, which usually means a number and a deadline.