A practical guide to decision authority, honest reporting, conflicts of interest and responsible AI use—with worked project scenarios and a decision record you can reuse.
A project can meet its delivery date and still fail its responsibilities. A supplier may be selected unfairly, an unresolved defect may disappear from a status report, or sensitive information may be sent to an unapproved AI service. Good governance makes the decision route clear before pressure makes shortcuts attractive.
This guide helps you reason through those situations in project work and Coursya practice questions. The scenarios are original learning examples. They illustrate project-management principles; the authority and requirements for a real decision come from the arrangements applicable to that project.
Table of contents
Governance, compliance and ethicsA practical decision routeFour worked project scenariosResponsible AI decisionsA reusable decision recordPractise the reasoningFrequently asked questions
Governance, compliance and ethics answer different questions
| Concept | Question to answer | Project example |
|---|---|---|
| Governance | Who can decide, using what evidence and within which limits? | A project manager can approve a routine purchase within delegated authority; a larger funding change goes to the designated decision maker. |
| Compliance | Which requirements must this activity satisfy? | A release needs specified security checks and an authorized acceptance record before deployment. |
| Ethics | Is the conduct honest, fair, responsible and respectful of those affected? | A project manager discloses a personal connection to a bidder instead of quietly influencing the evaluation. |
These ideas overlap. An approval can be within someone’s financial authority while the proposed action still fails another requirement. A sponsor’s support does not automatically authorize every exception. Conversely, a project manager should not escalate every routine choice when the team already has clear authority to decide.
Start with the project’s purpose and boundaries. The Coursya book Project Charter, Project Plan, and Business Case explains how authorization, delivery planning and business justification fit together.
Use a practical decision route
- Identify what needs a decision. Separate the verified event from assumptions. “The test failed” is different from “the product is unsafe”; record the evidence and identify what remains unknown.
- Check for an immediate protection need. If people, sensitive information or operations face imminent harm, use the relevant containment and escalation procedure within your authority. Do not postpone urgent protection merely to complete routine paperwork.
- Locate the requirement and decision owner. Check the agreed approval limits, acceptance criteria and applicable procedures. Ask the responsible specialist when interpretation is outside your competence.
- Compare feasible options. Explain effects on value, scope, schedule, cost, quality, risk and affected people. Include the cost of delay, but do not treat it as permission to ignore an obligation.
- Act within authority or escalate a clear recommendation. Give the decision maker the facts, options, recommendation and deadline. An escalation should enable a decision rather than simply transfer an unexplained problem.
- Record and follow through. Capture the decision, owner, conditions and next check. Update relevant plans and communicate what changes for each affected group.
This route is a reasoning aid, not an inflexible exam formula. A question about a routine disagreement may call for investigation or collaboration first. A question describing an active serious hazard may require immediate protective action. The context determines the next appropriate step.
Four worked project scenarios
Scenario 1: “Make the report green”
Situation: A sponsor asks you to omit a confirmed two-week delay until after a funding meeting. The current forecast still shows the delay, and recovery options have not been approved.
Better response: Keep the report accurate. Explain the forecast, its assumptions, the impact and the available recovery options. Discuss how to communicate the problem constructively and use the established escalation route if pressure to misrepresent it continues.
Why: Optimism does not change the evidence. Hiding the delay prevents stakeholders from making an informed decision. Reporting a problem also does not require speculation, personal blame or broadcasting confidential details to everyone.
Scenario 2: A friend joins the supplier shortlist
Situation: A company owned by your close friend enters a procurement exercise. You believe it offers the strongest solution and you sit on the evaluation panel.
Better response: Disclose the relationship promptly to the designated procurement or ethics owner. Follow the conflict-handling procedure, including independent assessment or withdrawal from evaluation where required. Preserve the same evaluation criteria and evidence for all bidders.
Why: Personal confidence in your impartiality is insufficient. Disclosure allows the organization to manage the conflict transparently. Neither secretly favoring the bidder nor automatically disqualifying it without authority is an appropriate substitute.
For the commercial side of the decision, read Project Contract Types: Costs, Risks, and Responsibilities.
Scenario 3: An approval limit is exceeded
Situation: Your delegated spending limit is 10,000. A single necessary purchase is forecast at 14,000. A colleague suggests splitting it into two orders to avoid additional approval.
Better response: Prepare the combined cost, justification, alternatives and schedule impact for the authorized approver. Use an approved urgent route if one exists. Do not misrepresent one purchase as unrelated transactions to bypass the control.
Why: The decision is about the commitment being made, not how many forms are submitted. At the same time, a routine purchase genuinely within delegated authority should not need unnecessary escalation.
Scenario 4: A failed release check
Situation: A required security check fails just before a public launch. The sponsor wants the launch to proceed because the campaign is already paid for.
Better response: Apply the release and incident procedures, involve the responsible security and release owners, and establish the impact and authorized options. Hold the affected release if the required criteria have not been met and the procedure requires a hold. Do not invent an exception or accept risk on someone else’s behalf.
Why: Money already spent does not resolve the failed requirement. The relevant authority must evaluate any permitted exception. If there is active harm, immediate containment takes priority over the ordinary approval cycle.
Treat AI output as a proposal that needs checking
An AI assistant can draft a risk description, summarize meeting notes or suggest alternatives. It cannot assume your project’s approval authority. A fluent answer may contain unsupported facts, omit an affected group or recommend an action that conflicts with the project’s controls.
- Check the input: use an approved service and confirm which information is permitted. Removing a person’s name alone may leave a record identifiable through other details.
- Check the evidence: verify factual claims, calculations and cited material before using them in a decision or report.
- Check the effect: consider unfair treatment, missing stakeholder perspectives and consequences if the output is wrong.
- Keep a responsible owner: require the appropriate human review and authorization for consequential actions. Record important assumptions and changes to the proposed output.
Worked example: A team wants an unapproved AI tool to analyze customer support records. The useful objective is to identify recurring issues; uploading the original records is only one proposed method. Pause the proposed upload, check approved data-handling arrangements and evaluate an authorized alternative. Synthetic examples or appropriately prepared data may support a trial, but changing the data does not automatically make an unapproved service acceptable.
For a broader learning route, use Coursya’s free AI courses for project managers. Each recommendation opens its course page on Coursya.
Keep a short, useful decision record
A decision record should let someone understand what was decided and what still needs attention. Use these fields:
- Decision needed: the specific choice and its deadline.
- Facts and uncertainty: verified evidence, assumptions and unresolved questions.
- Authority and requirements: the decision owner, relevant limits and required checks.
- Options and recommendation: expected benefits, costs, risks and affected people.
- Decision and conditions: approval, rejection or deferral; any conditions and their owners.
- Follow-up: action owner, due date, communication and evidence that the action worked.
For the failed-release scenario, the record might say: “Release held pending verification of the access-control fix; security owner reviews test evidence tomorrow; release owner confirms authorization; project manager updates the launch forecast.” That is more actionable than “Security issue discussed.”
If a decision changes a controlled commitment, continue with How to Manage Change Requests and Stay in Control. Use the Practical Risk Register guide for remaining uncertainty and response ownership.
Practise the reasoning before memorizing an answer
For each scenario, identify the decision owner, the evidence, any immediate protection need and the limits of the project manager’s authority. Then explain why the tempting shortcut is weaker. This develops a more useful habit than memorizing rules such as “always escalate” or “always analyze first.”
Practise governance, ethics and compliance →
The topic starts with Foundation practice and provides explanations for every answer option. Return to the relevant section here when you miss a question, then try the reasoning again in a different situation.
Frequently asked questions
Should a project manager always escalate an ethical concern?
Respond through the appropriate process. Some issues require prompt formal reporting, specialist involvement or protective action; others can be resolved within delegated authority. Assess the nature of the concern, immediate risk and applicable reporting responsibilities. Do not conceal an issue or investigate beyond your authority.
Does sponsor approval override a mandatory requirement?
Do not assume it does. Check the sponsor’s actual authority and the applicable requirement. If an exception process exists, only the designated authority can use it within its limits. A project deadline alone does not create an exception.
Can AI approve a change or choose a supplier?
An AI tool can support analysis, but using it does not remove the organization’s decision responsibilities. Follow the approved process, check the output and obtain the required authorization. Do not give a tool additional authority merely because it produces a confident recommendation.
Are these official PMP questions or official PMI guidance?
No. This is an original Coursya learning guide, linked to independent practice questions. It is not an official question bank, endorsement or certification. Read how Coursya practice and scoring work for the learning approach.