Each step's planned date sits beside its actual one in NU590's Unit 8 progress report, which prices every change against the objectives and leaves the activity log to the writer. Searches like "nu 590 unit 8 assignment example", "nu590 unit 8 sample" and "nu590 unit 8 example" land here.
Planned Against Actual: A Progress Report on the Revised Fasting Script, a Six-Day Slip and an Order Set Outside the Term
[Student Name]
Purdue University Global
NU590: Applying Principles of Advanced Nursing Practice - Clinical
Unit 8 Progress Report
[Instructor Name]
[Date]
The department is composite; dates, counts and variances are bracketed, and the writer's activity log is kept outside this paper.
Plan Versus Actual
The table below restates each step from the Unit 7 plan, its planned date, its actual date and the variance.
1. Chair approves script: planned [week 1, Friday], actual [week 2, Thursday], variance [+6] days. Cause: exception line rewritten.
2. Sheet reprinted: planned [week 2, Wednesday], actual [week 3, Tuesday], variance [+6]. Cause: waited on step 1.
3. Day huddle: planned [week 2, Thursday], actual [week 3, Wednesday], variance [+6]. Cause: waited on step 1.
4. Evening huddle: planned [week 2, Friday], actual [week 3, Thursday], variance [+6]. Cause: waited on step 1.
5. Calculator card: planned [week 2, Wednesday], actual [week 3, Tuesday], variance [+6]. Cause: waited on step 1.
6. Check-in question: planned [week 2, Friday], actual [week 3, Thursday], variance [+6]. Cause: waited on step 1.
7. Go-live: planned [week 3, Monday], actual [week 4, Monday], variance [+7]. Cause: kept on a Monday.
8. First audit: planned [week 3, Friday], actual [week 4, Friday], variance [+7]. Cause: follows go-live.
9. Office outreach: planned [week 4], actual [week 5], in progress. Cause: follows go-live.
10. Weekly audits: planned [weeks 4 to 8], actual [weeks 5 to 8], one audit lost.
11. Summary and informatics request: planned [week 8], on track.
One cause produced almost every variance, and it sat at the step the plan had already named as the dependency for all the rest.
The Six-Day Slip
The chair read the draft script and approved the main instruction at once but rewrote the exception line. The draft had routed patients with diabetes, gastroparesis or bowel obstruction to anesthesia. The chair added patients taking a GLP-1 receptor agonist, citing multisociety guidance that these patients may need a liquid diet the day before a procedure and individual review rather than a standard fast (Kindel et al., 2024). The revision was right, and it added a question to the call: "Do you take a weekly injection for diabetes or weight loss?" The slip was the cost of getting the exception line correct before print.
Because every later step waited on the wording, the slip carried forward unchanged. The plan had shown this dependency plainly, and it worked as intended: nothing launched on the old wording, and the perioperative director was told of the new date on the day it changed. Go-live moved seven days rather than six to keep the Monday start, so that a whole week of patients heard the new script from the first call.
Huddles and Make-Up Session
Both huddles ran as planned once rescheduled. [Six] of [seven] pre-admission nurses attended; the seventh was reached through a five-minute one-to-one session before their next shift, recorded on the sign-in sheet. Nurses practiced three calls each using the calculator card. Two questions came up often enough to add to the posted summary: whether sparkling water counts as a clear liquid (it does) and what to say to patients who ask about chewing gum, which the chair asked to be routed to the standard answer from the anesthesia policy.
The Order Set
The request to change the surgical order set default was never inside the nursing plan, and this report treats it differently from the other steps. The chair submitted it to the informatics committee in [week 5]. The committee's queue places it for review in [month], after the term ends. Until then, "NPO after midnight" still prints on every surgeon's orders, and pre-op nurses record the difference by note: "Patient instructed per anesthesia policy, clear liquids until [time]." That workaround is documented, agreed with the chair and consistent with the policy the order set was meant to express (American Society of Anesthesiologists Committee on Standards and Practice Parameters, 2017). It is untidy, and it leaves a contradiction in the record that a new staff member could misread.
The Early-Call Cases
Two patients had their arrival brought forward after the pre-admission call had already given them a last-drink time. In the first, a case ahead canceled and the patient was asked to come in [two] hours early; the charge nurse told the patient by phone to take nothing further, and the check-in question confirmed the patient had drunk water [1.5] hours before the new arrival time. Anesthesia reviewed and proceeded after a short wait. In the second, the patient had not drunk since the call and proceeded on time. Neither case was delayed by more than [twenty] minutes, and neither meets the review threshold.
These are reported as a test of the contingency, which worked. They were not near misses, and hiding them would have given the chair less reason to trust the audit.
Audit Findings So Far
Across [three] weekly audits of [20] call notes each, the revised script was documented on [51] of [60] calls. The nine without it were split between [one] nurse's early calls in week 5 and patients routed to anesthesia on the exception line, who correctly received an individual instruction instead. Fasting-related delays in the four weeks since go-live number [two], both patients who ate breakfast, none who drank before their stop time. Intake times are not yet reported, because three weeks of a field that mixes food and drink is too little to compare with the baseline.
What the Changes Cost the Objectives
Objective one, the revised script used on at least [80] percent of audited calls by [week 7]: on track, at [85] percent so far, with the original wording and date kept. Objective two, median intake time at check-in shorter than baseline by [week 9]: at risk, because the slip leaves one fewer week of data; the date is kept, and the Unit 10 summary will label the result as preliminary. Objective three, nurses rating the card as useful: met at the huddles, to be confirmed by a short survey in [week 8]. The balancing objective's threshold has not been reached. Each objective keeps its original wording, so that the reader can see what changed and what did not; a progress report that rewrote its objectives would lose the ability to show anything (Langley et al., 2009).
Next Steps Before Unit 10
Three actions remain. The office outreach note goes to the last [two] of [four] managers who have not yet replied, with a follow-up call from the chair's assistant. The nurse survey on the calculator card runs in [week 8]. The final audit week will add a separate count of patients who mention a conflicting instruction, so the summary can say how often the offices' old sheets are still reaching patients.
References
American Society of Anesthesiologists Committee on Standards and Practice Parameters. (2017). Practice guidelines for preoperative fasting and the use of pharmacologic agents to reduce the risk of pulmonary aspiration: Application to healthy patients undergoing elective procedures. Anesthesiology, 126(3), 376-393. https://doi.org/10.1097/ALN.0000000000001452
Kindel, T. L., Wang, A. Y., Wadhwa, A., Schulman, A. R., Sharaiha, R. Z., Kroh, M., Ghanem, O. M., Levy, S., Joshi, G. P., & LaMasters, T. L. (2024). Multisociety clinical practice guidance for the safe use of glucagon-like peptide-1 receptor agonists in the perioperative period. Surgery for Obesity and Related Diseases, 20(12), 1183-1186. https://doi.org/10.1016/j.soard.2024.08.033
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.
How this NU590 Unit 8 example is structured
Variance is the organizing idea, so each paragraph begins from a gap between planned and actual and works toward its consequence. Causes are located in process wherever the evidence allows: a wording revision, a queue, a scheduling practice. The order set is treated differently from the other delays because it was never the project's to deliver; the report states that plainly and records the workaround instead. The early-call cases are reported for what they show about the contingency, which worked, rather than hidden as near misses. The cost section is the report's center. It restates each objective, keeps the original wording, and marks whether the target date holds, moves or now depends on something outside the project. A short closing lists what the writer needs from the preceptor and faculty, including a decision on whether the audit start should move.
Get an NU590 Unit 8 example written to your instructions
Your log and site events are the raw material, and only you hold them. Send the implementation plan, a line on what happened to each step and the Unit 8 report instructions. Back in 24-48h, the report compares plan with actual and prices each change; the first custom sample is free, with log entries left bracketed. 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.
NU590 Unit 8 questions, answered
Should a progress report admit that the project is behind?
Yes, and it usually reads better for doing so. Faculty expect practicum projects to meet friction, and they generally grade how the writer explains and responds to a delay. State the gap, its cause and what it changes. The sample reports a six-day slip and an order set change moved beyond the term, each with its consequence for the objectives.
What goes in the report and what stays in the log?
The log records what you did and when: meetings, huddles, audits, hours. The report interprets those entries against the plan. Keep the log as your own record, completed as the work happens, and let the report draw on it. The sample shows log rows only as brackets, because an activity record is valid only when the person who did the work writes it.
Can an objective change after the proposal?
It can, if the change is explained rather than hidden. Keep the original wording visible, state the revision and give the reason, so faculty can follow the thread from proposal to final paper. The sample leaves each objective's text untouched and marks only whether its date holds, which keeps the evaluation in the next course comparable.