HCS 412 Week 5 Project Reporting, Change Management and Closure Example

Reviewed by Lenora Whitcombe, MSN, RN · University of Phoenix · Updated

This HCS 412 Week 5 example covers the final stretch of a health care project, from status reporting and a formal change request to closure and lessons learned, and the whole APA 7 paper comes after the facts table. Week five of University of Phoenix HCS 412, a course the catalog numbers HCS/412, brings health administration students to the controls that keep a project honest near the end and to the handover that turns it into operations. The sample brings the composite hospital's sleep center to completion. It shows a status report at week 28, when the project turned yellow, works through a request to add a pediatric-capable room, explains how staff were prepared for the new service using a well-known model of organizational change and closes with acceptance, contract closeout, a handover to operations and a lessons learned review built for use.

CourseHCS 412 Project Management for Health Care Professionals (HCS/412)
Week5
Paper typeProject control and closure paper
Lengthabout 1,010 words, 4 double-spaced pages plus title page and references
FormatAPA 7 student paper
SchoolUniversity of Phoenix
ProgramBS in Health Administration
UpdatedSeptember 2026

Free sample paper for HCS 412 Week 5

1

Status Yellow, One Change Request and a Handover: Reporting, Controlling Change and Closing a Hospital Sleep Center Project

[Student Name]

University of Phoenix

HCS/412: Project Management for Health Care Professionals

Week 5 Assignment

[Instructor Name]

[Date]

The hospital, the project's status, the change request and the lessons are composites written for a model paper; research findings come from the sources listed.

What this part is doingThe title names the status color, the change and the handover, the three events this final paper must manage.
2

At week 28 of 39, the composite community hospital's six-bed sleep disorders center was behind. Crews found corroded pipes behind a wall during demolition, and replacing them cost two weeks. The project was still expected to open on time, but the buffer had shrunk. This paper follows the project through status reporting, a change request, preparation for the new service and closure.

The Status Report at Week 28

Overall status: yellow. Schedule: yellow; construction is two weeks behind, leaving 2.5 weeks of buffer against the 39-week date. Cost: green; $780,000 spent against $790,000 planned, with $48,000 of contingency used for the pipe replacement. Risks: recruitment closed, both technologists hired; credentialing on track with three of five payers approved; equipment delivery confirmed for week 32. Quality: all information system tests passed; policies approved. Decisions needed: approval to add weekend work for finishes.

What this part is doingThe report measures each area against the baseline, which lets the sponsor see exactly where the project stands and what is being asked.
3

Recovery Decision

The sponsor approved weekend work for four weekends at a cost of $18,000 from contingency, restoring a week of buffer. The project manager reports weekly instead of biweekly until construction is complete.

The Change Request

Pediatric pulmonologists asked that one room be made suitable for adolescents aged 13 to 17, with a sleeping space for a parent, child-appropriate sensors and a pediatric scoring protocol. The pediatric program had been excluded from scope.

Analyzing the Change

Scope: one room redesigned, pediatric sensors purchased, a scoring protocol and technologist training added. Schedule: redesign of a room already under construction would add two weeks to the critical path, consuming most of the buffer. Cost: about $32,000. Risk: technologists would need pediatric competency, and the accrediting body's pediatric standards would apply.

The Board's Decision

The change control board, which reviews any change to the approved baseline (Project Management Institute, 2021) and is made up of the sponsor, the medical director, the finance director and the project manager, deferred the change to a second phase six months after opening. It approved buying the pediatric sensors now, since they did not affect the schedule, and planning the room change without disrupting construction. Saying not now, with a date and a plan, protected the opening while taking the physicians' request seriously, which is the balance change control exists to strike.

Preparing People for the Change

Kotter (1995) argued that transformation efforts often fail when leaders do not establish urgency, communicate the vision widely or anchor changes in the culture. A new service is a change for the people around it. The medical director met referring practices to explain the new referral process and home testing criteria. Emergency and inpatient nurses were briefed on what to do if an overnight sleep patient needed help. The hospital operator learned where to route calls.

What this part is doingPeople-side change is treated as part of the project rather than an afterthought, since a finished center with no referrals would still fail.
4

Communicating the Status

Different audiences received the week 28 news differently. The sponsor received the full report and the decision request. Team members heard it at the weekly meeting, with the pipe problem explained and the weekend plan described. Referring physicians were told only that the opening month was unchanged, which was true, and that home testing devices would be available from the first week.

Change Control for Smaller Items

Not every change needs the board. The team set a threshold: changes under $5,000 that do not touch the critical path may be approved by the project manager and logged. A request to move an electrical outlet in the monitoring station was handled this way in a day. Larger or schedule-affecting changes go to the board.

Final Weeks

Construction finished in week 32, equipment was installed and tested in weeks 32 and 33, and the mock patient night in week 35 found two issues, a missing emergency call cord and a scheduling template error, both fixed before opening.

Opening

The first patient was studied in week 38, a week before the committed date.

Acceptance

The sponsor and medical director signed acceptance against the criteria set in Week 4: rooms passed inspection, all systems recorded test studies, both technologists passed competency validation and the mock night ran without critical errors after fixes.

Contract Closeout

The construction contract closed after the punch list was complete and the final lien waiver received. Equipment warranties and service contracts were transferred to biomedical engineering.

Handover to Operations

The sleep center manager, reporting to the medical director, assumed responsibility for daily operations. The handover package included policies, the equipment inventory, vendor contacts, the quality measures and the phase two pediatric plan.

The Final Report

Final cost was $1.21 million, $30,000 under the $1.24 million approved. The schedule met the committed date. Quality acceptance criteria were met. Benefits will be reported at six months against the charter's target of waits under four weeks.

Lessons Learned

Williams (2008) found that organizations frequently identify lessons from projects but often fail to spread them or to change practice. The team therefore limited itself to three lessons, each with an owner. First, exploratory openings during design should include plumbing, not only ceilings; owner, facilities director, who updated the design checklist. Second, start payer credentialing paperwork before staff are hired, using provisional names; owner, revenue cycle director. Third, publish exclusions to physicians at the start, so requests like the pediatric room come early; owner, planning office.

Celebrating the Team

Closure also recognized the people who did the work. The sponsor thanked the facilities crew who worked four weekends, and the medical director invited the whole team to see the first patient's room before opening night. Recognition matters for the next project, since many of the same people will be asked to do it again.

Six-Month Benefits Review

At six months, the wait for testing was 19 days, down from five months, and the center had performed 910 studies, on pace for its first-year target.

Conclusion

Honest status reporting, disciplined change control, attention to the people around the new service and a complete closure turned a slipping project into a center that opened on time and under budget. Lessons with owners give the next project a better start.

5

References

Kotter, J. P. (1995). Leading change: Why transformation efforts fail. Harvard Business Review, 73(2), 59-67.

Project Management Institute. (2021). A guide to the project management body of knowledge (PMBOK guide) (7th ed.). Project Management Institute.

Williams, T. (2008). How do organizations learn lessons from projects-and do they? IEEE Transactions on Engineering Management, 55(2), 248-266. https://doi.org/10.1109/TEM.2007.912920

What the HCS 412 Week 5 instructions ask

HCS 412 Week 5 typically asks students to explain how projects are monitored, how changes are controlled and how projects are closed. Prompts may cover status reports, performance measures, change requests and change control boards, stakeholder communication, organizational change management, closure activities, final reports and lessons learned. Many sections ask students to finish the project developed over the course, sometimes with a presentation. Length varies with the format. Strong work shows a realistic status report with measures, a change evaluated for its effects on scope, schedule, cost and risk, a closure checklist and lessons that are specific and assigned for follow-up.

How this HCS 412 Week 5 example is built

The paper opens at week 28, with construction two weeks behind and the buffer shrinking. The status report is shown in words: overall yellow, schedule yellow, cost green, risks and quality measures. A section explains how the project manager and sponsor decided on recovery steps. The change request follows: pulmonologists asked to make one room suitable for adolescents. Its impact on scope, schedule, cost and risk is analyzed and the change control board's decision recorded. Organizational change management prepares staff and referring physicians. Closure covers acceptance against criteria, contract closeout, the handover to the operations manager, the final report and a lessons learned review, with research on why lessons are often not learned.

HCS 412 Week 5 grading rubric: where the points go

The final week is usually graded on control and completion. Faculty look for status reporting with measures, a disciplined change control process, attention to the people side of change, a complete closure process and meaningful lessons learned. Connecting reporting and changes to the baseline plan from earlier weeks shows command of the course. Evidence and recognized models strengthen the paper. Clear structure helps, especially where the paper moves from control to closure. Writing and APA formatting complete the grade. Papers that describe closure as a celebration, approve changes without analyzing their impact or list lessons such as communicate better usually earn less than papers that show a project ending under control and handing over cleanly.

HCS 412 Week 5 help: mistakes to avoid

A common weakness in HCS 412 Week 5 is a status report that only says on track. Show measures against the baseline: schedule variance, cost variance, risk status and quality progress. Another is approving a change because a physician asked; analyze its effects on scope, time, cost and risk and record the decision. Students also forget the people side; staff and referrers need preparation for the new service. Make closure concrete: acceptance against criteria, contracts closed, documents archived and a named operations owner. Write lessons that are specific and assign each one to someone who will change a process. Connect everything to the baseline plan. Finally, report benefits, since the project was approved for its results, not its completion.

Related HCS 412 sample papers

Other HCS 412 week samples

More BS in Health Administration sample papers

HCS 412 Week 5 questions, answered

What does HCS/412 Week 5 usually ask for?

Many sections ask students to explain project reporting, change control and closure, often by finishing the project from earlier weeks with a status report, a change request and a closure plan.

Where can I find a free HCS 412 Week 5 sample paper?

The sleep center reporting, change and closure paper above is free and annotated throughout. Your own project can be the basis of a no-charge first paper.

What is a change control board?

A group, often including the sponsor and key stakeholders, that reviews proposed changes to a project's baseline and approves, rejects or defers them.

What happens during project closure?

Deliverables are accepted, contracts are closed, the result is handed to operations, records are archived, a final report is prepared and lessons learned are captured.

Why are lessons learned often not used?

Research on project learning found that organizations often record lessons but fail to disseminate or act on them, so lessons need owners and a route into future practice.

Write yours, or have the desk draft it

This paper is an original model document written by our desk, not a submitted student paper and not an official University of Phoenix document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.