| Course | HS460 Project Design and Management for Health Care |
|---|---|
| Unit | Unit 4 |
| Paper type | Work breakdown structure |
| Length | About 840 words, 6 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | BS in Health Science |
| Updated | October 2026 |
Free sample paper for HS460 Unit 4
Twenty-Two Packages, Each With a Role Beside It: A Unit 4 Work Breakdown Structure for Opening a Saturday Walk-In Session
[Student Name]
Purdue University Global
HS460: Project Design and Management for Health Care
Unit 4 Work Breakdown Structure
[Instructor Name]
[Date]
Tillford Family Health, its roles, packages and every estimate are composite; the sources cited are real.
How the Tree Is Built
The tree is organized by deliverable, matching the five deliverables in the scope statement, plus a thin project management branch for status meetings, the budget and reporting. Each package is written as a result, such as "signed transfer procedure," rather than an activity, such as "work on transfer procedure," so that it is clear when the package is done. Packages stop at the level where one role can own the work and complete it in a realistic number of hours beside ordinary clinic duties, which in a small practice is usually under sixteen hours per package. Project management guidance recommends decomposing work until each package can be estimated, assigned and verified (Project Management Institute [PMI], 2021).
The Tree
1.0 Staffing 1.1 Weekend medical assistant position approved, with job description. Role: practice manager. 1.2 Weekend medical assistant hired and oriented. Role: practice manager. 1.3 Saturday pay differential approved by partners. Role: managing partner. 1.4 Nurse practitioner Saturday rotation agreed and signed. Role: operations coordinator. 1.5 Twelve-week rota published with named backups. Role: operations coordinator.
2.0 Clinical Protocols 2.1 Triage sheet for medical assistants. Role: lead nurse practitioner. 2.2 Minor illness protocols for sore throat, urinary symptoms, ear pain, rash and simple wounds. Role: lead nurse practitioner. 2.3 Transfer procedure for patients needing emergency care, agreed with the regional emergency department. Role: managing partner. 2.4 Physician on-call arrangement for Saturday consultation. Role: managing partner. 2.5 Protocols signed by all four partners. Role: operations coordinator.
3.0 Site and Supplies 3.1 Weekend heat and building access agreed with landlord. Role: practice manager. 3.2 Point-of-care test kits ordered and quality control documented. Role: medical assistant lead. 3.3 Wound care and dispensing supplies stocked. Role: medical assistant lead. 3.4 Emergency cart checked and signed for Saturday use. Role: lead nurse practitioner. 3.5 Pre-opening walk-through completed. Role: operations coordinator.
4.0 Patient Access 4.1 Phone message and after-hours line updated. Role: front desk supervisor. 4.2 Website notice published. Role: practice manager. 4.3 Mailed notice sent to patient households. Role: front desk supervisor. 4.4 Exterior signage installed. Role: practice manager.
5.0 Launch and Handover 5.1 Six consecutive Saturdays operated with full staffing. Role: operations coordinator. 5.2 Saturday operating checklist handed to the practice manager. Role: operations coordinator. 5.3 Handover signed by the practice manager and the managing partner. Role: operations coordinator.
6.0 Project Management Status meetings every two weeks, budget tracking and the status note to the sponsor. Role: operations coordinator.
Every package ends in something a person could hand over or point to, which is how the tree prevents work from being declared done by opinion.
Roles, Not Names
The role column lists roles rather than names. Staff change, and a role-based tree stays correct when someone leaves or a new medical assistant is hired. The responsibility matrix built from this tree will add names for the current team.
Workload Check
Because every role also works full weekday duties, each package was checked against the role's available hours. The operations coordinator carries eight packages, the most of any role, but several are short coordination tasks such as publishing the rota. The lead nurse practitioner carries four packages that together need about thirty hours of protocol writing; that work is spread across five weeks, and two afternoons a month are protected on the schedule. The medical assistant lead carries two packages that depend on vendor delivery times rather than her own hours.
What the Tree Leaves Out
The tree contains only work the scope statement includes. Sports physicals, Sunday hours and the Stanwick branch, all excluded in the scope, have no packages. A request to add any of them would first change the scope statement, then add packages here.
How the Tree Feeds Later Documents
Every package code carries into the schedule in Unit 6, where activities are sequenced, and into the budget in Unit 7, where each package is priced. The risk register in Unit 8 refers to packages where a risk would strike, such as 1.2 for hiring delays. Project management texts treat the breakdown as the foundation that later planning documents share, which is why codes must be stable once the tree is approved (Kerzner, 2017).
Why Depth Stops Where It Does
A deeper tree, splitting the minor illness protocols into five separate packages, would add tracking work without helping anyone. A shallower one, with "clinical protocols" as a single package, would hide the transfer procedure inside a larger item and risk it being finished last. The level chosen here, five branches and twenty-two packages, keeps the transfer procedure visible because its failure would matter most to patients. Risk management guidance encourages planners to make high-consequence work visible early in the plan (Hillson, 2002).
References
Hillson, D. (2002). Extending the risk process to manage opportunities. International Journal of Project Management, 20(3), 235-240. https://doi.org/10.1016/S0263-7863(01)00074-6
Kerzner, H. (2017). Project management: A systems approach to planning, scheduling, and controlling (12th ed.). Wiley.
Project Management Institute. (2021). A guide to the project management body of knowledge (PMBOK guide) (7th ed.). Project Management Institute.
Reading the HS 460 Unit 4 instructions
In the fourth unit the scope becomes a tree of work, drawn once as boxes and again as a coded outline. Expect level-one branches, work packages, assigned roles and a short explanation of how the tree was built. Organize by deliverable rather than by phase or department so the tree mirrors your scope. Write each package as a result that can be checked. Decompose until a package can be estimated, assigned and verified, but not further. Assign roles rather than names so the tree survives staff changes. Check that each role's packages fit the time available. Leave out anything the scope excludes, and keep codes stable because later documents will use them.
Inside the HS460 Unit 4 example
A section explains the deliverable-based structure and the stopping rule, citing project management guidance. The tree lists five branches, staffing, protocols, site and supplies, patient access, and launch and handover, plus project management, with twenty-two coded packages and roles. The highlighted sentence explains why packages end in something checkable. A section explains roles rather than names. A workload check shows each role's packages against weekday duties. Sections on what the tree leaves out and how codes feed the schedule, budget and risk register follow, and a closing section explains why depth stops where it does, citing risk management writing. Package codes stay fixed so every later document can cite them.
Reading the HS460 Unit 4 grading rubric
Work breakdown structures are commonly scored on alignment with scope, appropriate decomposition, clarity of packages, assignment of responsibility and usability for later planning. Alignment and decomposition often weigh most: graders check that every branch matches a deliverable and that packages are small enough to estimate but not trivial. Packages written as results rather than activities earn credit. Role assignment is valued when it reflects real capacity. Stable codes that later documents can use add points. A clear tree and outline complete the grade. Trees organized by month, or packages written as vague activities, tend to lose points. A workload check against each role's real hours is often what separates a strong small-practice breakdown from an average one.
Common HS460 Unit 4 mistakes, and how to avoid them
A frequent problem is a tree organized by time or department, which lets work fall between branches. Another is packages written as activities, such as review supplies, that never clearly finish. Some students decompose too far, listing every phone call, or too little, leaving one giant package. Roles are often missing or overloaded without comment. Excluded work sometimes appears anyway. Codes may change between documents, breaking traceability. If your project has different deliverables, perhaps training or equipment installation, share your scope statement and we will build the tree from its deliverables. Check that the project management branch is present but thin; it should not swallow clinical work.
Get an HS460 Unit 4 example written to your instructions
Include the scope statement from Unit 3 if your section built one, the Unit 4 prompt and the rubric. Your free first sample, delivered within 24-48h, decomposes that deliverable into packages that each carry a role, laid out as a tree and an outline in whatever format the prompt names. 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 HS460 papers and BS in Health Science samples
- HS460 Unit 1: Project Charter
- HS460 Unit 2: Discussion Board Post
- HS460 Unit 3: Scope Statement
- HS460 Unit 5: Stakeholder Register
- HS460 Unit 6: Schedule and Milestone Plan
- HS460 Unit 7: Budget Worksheet
- HS460 Unit 8: Risk Register
- HS460 Unit 9: Seminar Reflection
- HS460 Unit 10: Project Closeout Report
- HS450 Unit 4: Mission and Vision Critique
HS460 Unit 4 questions, answered
Should the tree be organized by phase or by deliverable?
Most HS460 prompts favor deliverables, and the example uses them because each branch then traces straight to the scope statement. A phase-based tree can work for some projects, but it tends to mix timing into scope and makes later scheduling harder. If the instructions name a format, follow it and mention why it fits.
How small should a work package be?
Small enough for one role to hold and for its hours to be guessed within reason. In the example, the transfer procedure is a single package because the office manager and the nurse practitioner can finish it in a few meetings. Where a package needs several roles and several decisions, splitting it usually makes estimates and assignments clearer.
Do names or roles belong in the role column?
Roles are usually better, because people leave and the structure should survive them. The example lists positions such as weekend medical assistant, office manager and managing partner. Some prompts ask for names to show accountability; in that case, add names in a separate column so a staff change alters only one field.
Where can I find a free HS460 Unit 4 sample paper?
The full Unit 4 work breakdown structure is on this page, twenty-two coded packages under five branches with a role beside each.
How small should a work package be in a small practice?
Small enough that one role can finish it beside normal duties, often under sixteen hours, and large enough that tracking it is worthwhile.