GM594 Unit 9 Ethics Case Analysis Example

Fully Operational by November 30: A Unit 9 Ethics Case Analysis on a Grant Completion Date

[Student Name]

Purdue University Global

GM594: Project Closing, Ethics, and Professional Responsibilities

Unit 9 Ethics Case Analysis

[Instructor Name]

[Date]

The emergency communications district, its staff, the grant and every figure are composite and illustrative; the code and research cited are real.

The Facts

The Ridgeline Emergency Communications District received a $1.2 million state 911 grant toward its backup power and cooling upgrade. The grant agreement sets an end date of November 30 and holds back 10 percent, $120,000, until the district files a final report certifying that the funded system was fully operational by the end date.

The project reached substantial completion on November 20, when the new generator first carried the building and the architect certified the work as usable. But the first transfer test had failed, at 14 seconds against a 10-second requirement, and the alarm escalation to a second contact had never been configured. The transfer passed on retest on December 2, and the alarm escalation passed on December 9, which the district recorded as its acceptance date.

The executive director, preparing the report with the projects manager, asked her to write November 20 as the date the system became fully operational. The executive director's reasoning, as the case gives it: "The generator was running and carrying the building on the twentieth. Everything after that was fine-tuning. We are not going to lose $120,000 over a text message setting."

The Code

The projects manager is a certified project management professional and has agreed, as a condition of that certification, to follow PMI's ethics code. The code sets out four values, responsibility, respect, fairness and honesty, each with aspirational standards that practitioners strive for and mandatory standards they must follow (Project Management Institute, 2006). The mandatory honesty standards prohibit behavior meant to deceive, including making false or misleading statements, stating half-truths, giving information out of context, and withholding information that would make a statement misleading.

Testing November 20 Against the Code

Writing November 20 is not a plain falsehood. The generator did carry the building that day. But the grant asks when the system was fully operational, and on November 20 the system did not meet two of its own acceptance criteria. Writing November 20, with no explanation, would invite the grant program to believe the system met its criteria by the end date. That is a half-truth under the code: each word can be defended, but the statement as a whole is meant to leave a false impression.

November 20 is a true date put to a misleading use, which is exactly what the code means by a half-truth.

The executive director's framing matters too. Calling the alarm escalation a text message setting makes it sound minor. For a 911 center, an alarm that reaches one phone and stops is a real gap: an overnight generator fault could go unanswered. The acceptance criteria existed because the district decided at approval that the gap mattered.

Max Bazerman and Ann Tenbrunsel describe how people under pressure redefine a decision so that its ethical dimension fades, often by focusing on the business stakes and describing the troubling part in smaller terms (Bazerman & Tenbrunsel, 2011). Calling the criterion fine-tuning is an example.

Who Is Affected

Four groups have a stake in the date. The state grant program relies on final reports to decide whether public money bought what it was meant to buy, and other districts compete for the same funds. The county's residents depend on the center's backup power working as designed, including the alarm that would summon a technician at night. The district's board is responsible for the reserve that would cover a lost holdback and for the district's reputation with the state. And the projects manager's own professional standing rests on the reports she signs. The Project Management Institute frames project decisions as affecting stakeholders well beyond the project team, and asks practitioners to weigh those interests openly (Project Management Institute, 2021). Only the executive director's framing treats the date as a matter between the district and the grant program alone.

Three Options

Write November 20. Secures the $120,000 if the grant program does not inquire. Violates the mandatory honesty standard. If the program later reviews the acceptance record, which is a public document, the district risks repayment of more than the holdback and damage to its standing for future grants.

Write December 9 and accept the consequence. Honest. Risks losing the $120,000, which the district would have to cover from its reserve, already drawn down for the overrun.

Write December 9 with a full chronology, and ask the program in advance for a decision. Honest. Before filing, the projects manager calls the grant manager, explains that the system carried the building from November 20 and met all criteria on December 9, and asks whether the program will release the holdback, grant a short extension or release part of it. The report then states the facts and whatever the program decides.

The Decision

The projects manager should choose the third option. She should first tell the executive director, in person, that she cannot sign a report giving November 20 as the date the system was fully operational, and explain why with the code's words. She should then propose the call to the grant manager, offering to make it with the executive director. If the executive director refuses and asks someone else to sign, the code's responsibility standard requires the projects manager to raise the matter with the board chair.

She should keep a written record of each conversation, with dates, so that the sequence of her decisions can be shown later if the report is ever questioned. The costs are real. The district may lose some or all of the $120,000. The projects manager's relationship with the executive director may suffer. Against that, the district keeps its credibility with the grant program, avoids a statement that could later require repayment, and keeps the acceptance criteria meaningful for the next project.

Why Asking First Matters

The third option is not only the honest one; it is often the effective one. Grant programs frequently allow extensions when a project is substantially complete and the delay is documented. Asking before filing gives the program a chance to say yes, and it shows the district treating the grant's terms as a commitment rather than a hurdle. If the program refuses, the district has lost money but nothing else, and it can make a stronger case in its next application by pointing to a record of accurate reporting.

References

Bazerman, M. H., & Tenbrunsel, A. E. (2011). Blind spots: Why we fail to do what's right and what to do about it. Princeton University Press.

Project Management Institute. (2006). PMI code of ethics and professional conduct.

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