| Course | NU 476 Nursing Capstone |
|---|---|
| Unit | Unit 3 |
| Paper type | Project plan with milestones |
| Length | About 540 words, 4 pages |
| Format | APA 7 student paper |
| School | Herzing University |
| Program | RN to BSN |
| Updated | October 2026 |
Free sample paper for NU 476 Unit 3
Project Plan With Dated Milestones: Teach-Back for Discharge Medication Education on a Cardiac Step-Down Unit
Student Name
Department of Nursing, Herzing University
NU 476: Nursing Capstone
Instructor Name
February 4, 2026
Project Plan With Dated Milestones: Teach-Back for Discharge Medication Education on a Cardiac Step-Down Unit
The Project in One Paragraph
The project will introduce teach-back, in which the nurse asks the patient to explain in his or her own words what each new or changed medication is for and how to take it, into discharge medication education on 6 North, a 24-bed cardiac step-down unit. The measure is the proportion of discharges with documented teach-back for all new or changed medications, and a secondary measure is the proportion of patients who can correctly state the purpose of each new medication in a follow-up phone call within 72 hours. Teach-back is a core practice for confirming understanding in health literacy guidance (Brega et al., 2015), and in patients with heart failure, discharge education using teach-back has been associated with fewer readmissions (Oh et al., 2023). The term runs from January 12 to April 24, 15 weeks.
Tasks, Dates, and Milestones
Every task carries a start and end date against the actual term calendar; milestones are events that either happened or did not.
| Week (dates) | Task | Owner | Depends on | Milestone |
|---|---|---|---|---|
| 1-2 (Jan 12-23) | Finalize proposal; meet manager and preceptor | Student | None | Proposal signed by manager, Jan 23 |
| 2-3 (Jan 19-30) | Quality office determination; practice council agenda | Student, preceptor | Signed proposal | Determination letter received, Jan 30 |
| 3-4 (Jan 30-Feb 3) | Baseline audit of 40 discharges; baseline calls to 20 patients | Student | Determination | Baseline report complete, Feb 3 |
| 4 (Feb 5) | Practice council approval of teach-back standard | Council chair | Baseline report | Approval recorded in council minutes, Feb 5 |
| 5 (Feb 9-13) | Build documentation field for teach-back with informatics | Informatics nurse | Council approval | Field live in test environment, Feb 13 |
| 5-6 (Feb 9-20) | Educate all 38 RNs: 15-minute huddle sessions, all shifts | Student, educator | Council approval | 90% of RNs trained, Feb 20 |
| 6 (Feb 16) | Documentation field live in production | Informatics nurse | Test field | Field live, Feb 16 |
| 7-12 (Feb 23-Apr 3) | Implementation; weekly audit of discharges; follow-up calls | Student, RNs | Training and field | Six weekly audits completed, Apr 3 |
| 9 (Mar 9-13) | Mid-point review with manager; adjust if under 50% | Student, manager | Three audits | Review meeting held, Mar 13 |
| 13 (Apr 6-10) | Analysis of outcome and process measures | Student | Final audit | Results summary drafted, Apr 10 |
| 14 (Apr 15) | Present results at staff meeting | Student | Results summary | Presentation delivered, Apr 15 |
| 15 (Apr 20-24) | Handover to unit champion; final paper | Student, champion | Presentation | Handover document signed, Apr 24 |
Dependencies and the Critical Path
Four steps must happen in order and cannot overlap: quality office determination before baseline data collection, baseline before council approval, council approval before education and the documentation build, and both of those before implementation. That sequence is the critical path; a delay in any of them delays implementation week for week. The council meets only on the first Thursday of each month, so missing the February 5 meeting would push approval to March 5 and cut implementation from six weeks to two. For that reason, the baseline audit starts the day the determination arrives and the report is due February 3, two days before the meeting, and the council chair has agreed to add it to the agenda on short notice.
How to Tell Whether the Project Is on Track
In week six, a reader can check three things without asking: whether the council minutes of February 5 record approval, whether at least 90% of nurses appear on the training sign-in sheets, and whether the documentation field is live. If any is missing, the project is behind. The mid-point review works like the study step of a small improvement cycle (Langley et al., 2009): at week 9, the project is on track if at least half of discharges in the preceding two weeks show documented teach-back; below that, the manager and I will look for the cause and adjust, for example by adding teach-back to the discharge checklist or by reteaching night shift.
Resources and Contingencies
Resources: my time, about 6 hours a week outside my shifts; the unit educator for two weeks of huddle teaching; the informatics nurse for about 8 hours; and a phone line for follow-up calls. If the documentation field is delayed beyond February 16, teach-back will be recorded on a paper checklist kept with the discharge packet for the first weeks, so that implementation can still begin on time. If staff turnover or census interrupts training, sessions will be repeated on the next two weekends. The plan also includes one week of slack, week 13, which can absorb a delay elsewhere without moving the presentation date.
References
Brega, A. G., Barnard, J., Mabachi, N. M., Weiss, B. D., DeWalt, D. A., Brach, C., Cifuentes, M., Albright, K., & West, D. R. (2015). AHRQ health literacy universal precautions toolkit (2nd ed.; AHRQ Publication No. 15-0023-EF). Agency for Healthcare Research and Quality.
Langley, G. J., Moen, R. D., Nolan, K. M., Nolan, T. W., Norman, C. L., & Provost, L. P. (2009). The improvement guide: A practical approach to enhancing organizational performance (2nd ed.). Jossey-Bass.
Oh, S., Choi, H., Oh, E. G., & Lee, J. Y. (2023). Effectiveness of discharge education using teach-back method on readmission among heart failure patients: A systematic review and meta-analysis. Patient Education and Counseling, 107, Article 107559. https://doi.org/10.1016/j.pec.2022.11.001
What the NU 476 Unit 3 instructions ask for
Unit 3 asks you to build a project plan with tasks, dates and milestones. Expect to summarize the project, list tasks with dates against the term calendar, identify milestones, show dependencies and the critical path, describe how progress can be checked and list resources and contingencies. Many versions ask what makes a milestone useful and how much slack to build in. Check whether your section expects a Gantt chart or table. A milestone should be an event that either happens or does not, such as council approval. Dependencies matter, because some steps cannot start until others finish. Plan what to cut if time runs short, since capstone timelines often slip when approvals take longer than expected.
How the NU 476 Unit 3 example is put together
The plan opens with the project in one paragraph so the tasks have context. The table lists tasks with start and end dates and marks milestones. The dependency section names four steps in strict order and explains why, which shows the critical path. The progress section describes three things a reader can check in week six, such as whether council minutes show approval. The resources section estimates hours and support from the unit educator. The contingencies section names what will be cut or delayed if a milestone slips. The plan is short but complete, and it reads as something that could be followed and checked by a manager or instructor without asking the student for explanations.
Reading the NU 476 Unit 3 rubric
Herzing's rubric for a project plan usually covers the project summary, tasks and dates, milestones, dependencies, progress tracking, resources and contingencies. Dates and dependencies are read together, since graders check that tasks fit the term and that ordered steps do not overlap. Milestone points reward events that can be verified. Tracking criteria look for ways to check progress without asking. Resource points go to realistic hours and support. Contingency earns credit for a plan to cut or delay. A readable table helps. Contingencies that name what will be cut, rather than promising to work harder, are usually credited. Brega's AHRQ health literacy toolkit and Oh and colleagues' teach-back review belong in the APA 7 list.
NU 476 Unit 3 help before you submit
Project plans in Unit 3 often slip by listing tasks without dates or with dates that ignore holidays and clinical schedules. Another frequent problem is milestones that are vague, such as make progress. Students often miss dependencies, planning to collect data before approval. Slack is absent. Resources are not estimated. No plan exists for what to cut. Progress cannot be checked from the plan alone. Finally, mark the critical path, because graders reward a plan that shows which delays would push the whole project back and which would not. Another gap is forgetting the time needed for staff teaching across all shifts, which often takes two weeks rather than one.
Get a NU 476 Unit 3 example written to your instructions
Send the Unit 3 instructions and the rubric from your NU 476 classroom, plus your term dates and site availability. We write a custom example with dated tasks, sequenced dependencies and checkable milestones, returned in 24 to 48 hours. The first custom sample is free.
More NU 476 papers and RN-to-BSN samples
- NU 476 Unit 1: Capstone topic proposal
- NU 476 Unit 2: Practice gap evidenced at the site
- NU 476 Unit 4: Stakeholder and approval map
- NU 476 Unit 5: Implementation record
- NU 476 Unit 6: Outcome measurement
- NU 476 Unit 7: Results presented to the site
- NU 476 Unit 8: Sustainability and handover plan
- NSG 323 Unit 3: Communicable disease investigation
- NSG 324 Unit 3: Point-of-care evidence search
- NU 305 Unit 3: Code of ethics applied to a situation
- NU 345 Unit 3: Genogram and family health history
NU 476 Unit 3 questions, answered
What makes a milestone useful?
That it is an event rather than a state. Baseline audit complete, approval received, training delivered to all staff on the unit, first cycle of data collected: each either happened by its date or did not. Milestones phrased as progress on implementation cannot be checked, and a plan built from them tells nobody anything in week six.
How much slack should I build in?
More than feels necessary. Approvals take longer than promised, staff are unavailable, and the week you planned to collect data turns out to be the week the unit is short. A plan with every task ending the day the next begins fails at the first delay, and there is always a first delay.
Should I plan what to cut?
Yes, and deciding now is much better than deciding in week ten. Name which element of the project would be reduced or dropped if the schedule slips, and what the minimum version looks like that still meets the program requirement. That decision made calmly protects the capstone; made under pressure it usually removes the wrong thing.
Where can I find a free NU 476 Unit 3 sample paper?
This page shows the whole NU 476 Unit 3 teach-back project plan for free, dated tasks, milestones, the critical path and contingencies. Ask for a version dated against your own term calendar.
What is a critical path in a nursing project plan?
It is the sequence of steps that must happen in order, where any delay pushes back the end date. In this sample, quality office review, baseline data, staff teaching and implementation form the critical path.