Fourteen parties to a Saturday clinic launch, from partners to the landlord and the town pharmacy, are recorded by authority, interest and message in HS460's Unit 5 register. Searches like "hs 460 unit 5 assignment example", "hs460 unit 5 sample" and "hs460 unit 5 example" land here.
What a finished HS460 Unit 5 stakeholder register looks like
A wide table printed sideways across three pages with eight columns: party, role, authority, interest, attitude, message needed, frequency and messenger. Authority uses four set terms, approve, block, advise or none, defined in a key above the table. The four partners approve; the two nurse practitioners can effectively block, since Saturday shifts need their agreement under existing contracts; the landlord blocks by controlling building access and heating. Charge nurses at the regional emergency department hold no authority but need the transfer procedure before opening. The town pharmacy, open until one on Saturdays, needs an estimate of prescription volume. Patients, front desk staff, medical assistants, the billing contractor, the cleaning company and the county health department complete the list. A half-page note explains the two rows most likely to cause trouble.
How a HS460 Unit 5 example is structured
The key comes first because authority terms mean nothing unless they are fixed; block, for example, means the ability to prevent the launch, not merely to complain about it. Rows are grouped by authority so the parties who can stop the project appear at the top. Interest is written as a concrete gain or loss, such as Saturday pay or fewer weekend emergency calls, instead of a rating. Attitude is recorded separately from interest, since a party can benefit and still resist. The message column carries the register's real work: what this party must understand to act or cooperate, written as a sentence. Frequency and messenger follow, so each message has a rhythm and an owner. The closing note singles out the nurse practitioners and the landlord, whose authority is informal but decisive.
Four authority terms, defined
Approve, block, advise and none, each with a sentence of meaning so a row's authority cannot be read two ways.
Parties who can stop it, first
Partners, nurse practitioners and the landlord grouped at the top, because each could halt the launch in a different way.
Interest as gain or loss
Saturday pay, fewer weekend emergency calls or added cleaning hours written out, instead of a high or low rating.
What each party must hear
What each party must understand in order to act, such as expected prescription volume for the town pharmacy.
Two rows to watch
The nurse practitioners and the landlord, whose authority is informal but decisive, singled out in a closing note.
Where marks go in HS460 Unit 5
Titles and ratings alone, high interest or low power, with nothing about what a party wants or can do, cost an HS460 register heavily, because the unit asks for authority and interest as facts. Authority written loosely, influential or important, cannot be acted on. Leaving out parties beyond the practice walls, the landlord, the pharmacy, the emergency department, is a frequent gap in clinic projects, where outside cooperation often decides the opening date. A message column filled with keep informed or regular updates tells no one what to say. Frequencies that ignore the project's rhythm, monthly updates for a launch lasting barely two months, suggest the table was filled without the schedule in mind. Missing messengers, and attitude merged into interest, prompt the smaller comments.
Get a HS460 Unit 5 example written to your instructions
Every register is specific to the parties around one project, so send your scenario or charter, the Unit 5 prompt and your rubric, and note any columns the instructions require. A first sample comes free in 24-48h, recording authority, interest and a concrete message for each party your project involves.
HS460 Unit 5 questions, answered
How is a stakeholder register different from a stakeholder analysis?
A register records facts about each party in one table, while an analysis interprets them, often with a grid and a strategy. Many HS460 prompts ask for the register first and build the communication plan from it. The example stays a register, with one closing note, because the prompt asks what each party can do and needs to hear.
Should staff inside the practice be listed individually?
By role, unless one person holds unique authority. The example lists medical assistants and front desk staff as groups, but gives the two nurse practitioners a row of their own because their agreement to Saturday shifts is individually required. Listing every employee by name adds length without adding anything a reader could act on.
What if a stakeholder is likely to resist?
Record the attitude honestly and let the message column respond to it. In the example, the front desk staff are wary of Saturday rotations, so their message covers the rota rules, the pay differential and the right to swap shifts. Resistance hidden in the register tends to reappear later as a schedule problem.