PMP 2026 | 92 | Ethics: Fairness and Honesty
Fairness and honesty complement responsibility and respect in the P M I Code of Ethics. Fairness calls for impartial decision processes and attention to conflicts. Honesty requires accurate communication without deceptive statements or omissions. Applying these values can support trust and reduce avoidable disputes, but it does not guarantee a favorable audit or universal agreement. The practical question is whether the decision and its explanation reflect the real evidence and the applicable process.
Welcome to Certified, the P M P prepcast. This is episode ninety two of season one. Today we are exploring fairness and honesty when project work comes under pressure.
Honesty starts with status reporting. On a healthy project, it may be easy to tell good news, but the real test of honesty comes when things go wrong. P M I expects you to report variance promptly, showing both the impact and the options, not simply excuses. That means saying, “We are five days behind; here are two paths forward,” rather than, “We’ll try to make it up.” Honest reporting also requires you to separate facts, assumptions, and opinions. When you conflate them, stakeholders cannot tell what is certain and what is conjecture. Honesty protects them from making decisions on flawed information.
One of the most damaging lapses of honesty in project environments is what some call “green shifting.” This is presenting a green status when the agreed criteria and material evidence do not support it, or concealing an issue that recipients need to understand. Open issues do not automatically make a project red; a green status can be honest when the criteria are met and the relevant issues remain visible. Sometimes this is done out of optimism, sometimes out of fear of reprisal, but either way it undermines trust. Stakeholders who discover later that “green” projects were in trouble will stop believing status reports altogether. P M I expects you to resist this temptation, reporting honestly even when it creates uncomfortable conversations. Painting over problems delays solutions and compounds risk.
Fairness is about the processes you use to make decisions, not just the outcomes themselves. For example, if you are managing procurement, fairness means publishing evaluation criteria in advance and applying them consistently. It means avoiding “moving the goalposts” by changing standards midstream once results are known. Fairness also means documenting the deliberations and rationales for decisions, so that stakeholders and auditors can see that choices were made transparently. Involving the right stakeholders, and no more than the right stakeholders, is another dimension of fairness. Playing favorites or stacking a committee with allies violates both process and trust.
Past supplier experience can be a valid consideration when it is included in the authorized evaluation approach. It should not become a hidden reason to override the criteria after proposals are scored. If a legitimate need requires criteria to change, use the procurement process that permits the change, communicates it fairly and addresses the treatment of existing proposals. Do not quietly move the goalposts to favor a preferred bidder. Consistency and an authorized transparent process matter more than defending a predetermined winner.
Use an original fictional supplier selection to examine fairness when the numbers are uncomfortable. The approved evaluation gives technical quality fifty percent of the weight, service capability thirty percent and cost twenty percent. Each criterion is scored on a scale of one hundred, with a higher cost score representing a more favorable evaluated cost. Supplier Alder scores ninety, eighty and sixty. Supplier Birch scores eighty, eighty-five and ninety. The evaluators must apply the agreed method rather than choose the proposal they prefer and adjust the method afterward.
Alder's weighted total is forty-five for technical quality, twenty-four for service and twelve for cost, producing eighty-one. Birch receives forty, twenty-five point five and eighteen, producing eighty-three point five. Birch leads by two point five points under the stated model. The calculation does not prove that every procurement must award solely on that total. It shows the result of this fictional authorized method, which must be interpreted with its actual eligibility, threshold and decision rules.
A manager who favors Alder proposes increasing the technical weight to sixty percent and reducing cost to ten percent after seeing the results. Under those revised weights, Alder receives fifty-four plus twenty-four plus six, totaling eighty-four. Birch receives forty-eight plus twenty-five point five plus nine, totaling eighty-two point five. The winner changes. The concern is not that technical quality should never have a larger weight. It is that the process is being altered after results are known to favor a particular outcome.
If the organization discovers a genuine missing requirement, use the procurement process that governs a material change to the evaluation. That may require an authorized revision, fair communication, further submissions or another appropriate step under the actual rules. Do not quietly recalculate the spreadsheet and present the new winner as though the original approach produced it. Preserve the history and explain why the authorized process changed. Fairness requires more than a mathematically correct total.
Now introduce a personal relationship. One evaluator has a close friendship with Alder's owner. A high technical score may still be supported by evidence, but the relationship creates a separate conflict question. Disclose it through the required channel and refrain from influencing the affected decision until the applicable process resolves involvement. An independent review can assess the scoring evidence without assuming either that the proposal is worthless or that the evaluator's confidence removes the conflict.
Confidentiality also protects the competition. An evaluator should not send Birch's pricing to Alder to help it improve its offer outside an authorized process. Nor should a broad project meeting receive private details of the evaluator's relationship when only designated recipients need them. Fair treatment does not mean unlimited disclosure. It means that relevant participants receive the information and opportunities required by the actual procedure, while protected information remains appropriately controlled.
Assess gifts, hospitality and personal interests through the applicable ethics and procurement policies. The rules may depend on the role, timing and jurisdiction, so a nominal-value label does not automatically make an offer acceptable. Disclose a real or potential conflict and refrain from influencing the affected decision until the required process resolves it. Decline or return an offer when that is required. Record the relevant facts through the proper channel instead of relying only on your belief that you can remain objective.
Consider a supplier offering event tickets during an active negotiation. Apply the actual gifts and conflict rules, disclose through the required channel and decline or return the offer where required. Do not assume that personal confidence in objectivity makes acceptance appropriate. The process should address actual and apparent improper influence, without promising that a disclosure or recusal will eliminate every suspicion.
Keep records faithful to what actually happened. Do not backdate an approval, invent a signature or conceal a failed result by replacing it with a later success. Use the recordkeeping and correction controls that apply to the system, including traceable amendments where required. Not every project log must be technically immutable, but a correction should not mislead readers about the history. Preserve relevant original evidence and distinguish an earlier event from a later update. Honest records support valid decisions.
When documentation lags, distinguish the date of the event from the date you are recording it. Authentic evidence may establish that an earlier approval occurred; describe that evidence accurately. If approval did not occur, a later approval must be recorded as later and must not be used to imply that earlier work was authorized. Follow the appropriate review of the gap and its consequences. A transparent correction helps readers understand what happened without manufacturing a cleaner past.
Fair decisions and accurate records provide a basis for explaining how an outcome was reached. They do not guarantee that a dispute or audit finding will disappear. Keep the evidence, authorized criteria and actual rationale visible to appropriate recipients. Where the record reveals a gap, address it honestly rather than treating the existence of paperwork as proof that the process was sound.
Credibility depends on repeated conduct and the quality of the evidence, not a promise that everyone will trust a dashboard. Make important assumptions clear, correct errors and apply the authorized process consistently. Stakeholders may still challenge a decision, and a fair challenge can improve it. Preserve the ability to review the facts rather than requiring people to accept the leader's assurance.
We have considered truthful reporting, impartial evaluation and accurate records. The next examples add personal relationships, changing forecasts and pressure to soften bad news. In each case, identify who needs the facts and what authority or restriction applies. Transparency should make a legitimate decision possible while preserving appropriate confidentiality. That is the standard to test as the pressure increases.
One of the most common tests of honesty comes when sponsors or executives apply pressure to soften bad news. Imagine a sponsor who asks you to downplay a risk in order to secure funding approval. The temptation is real: soften the language, present the project as less risky, and secure the money. But this is a violation of P M I’s expectation of honesty. Risks must be presented factually, with probabilities, ranges of impact, and potential mitigations clearly stated. The ethical action is to describe the risk accurately, show the mitigations you are pursuing, and document the decision. If the pressure persists, you escalate respectfully through policy channels.
The artifacts to update in such a situation include the risk register, which captures the risk factually with owners and triggers. You also update the decision log to record the conversation and the options presented. Finally, you ensure the communications plan reflects consistent, truthful messaging to stakeholders. Honesty here means telling the truth fast, even when it makes funding less certain. Protecting trust is more valuable than securing money on false pretenses. P M I wants you to recognize that long-term credibility always outweighs short-term expediency.
Suppose a friend's firm bids for a contract and scores strongly on technical criteria but has a higher price. Disclose the relationship and refrain from influencing the selection until the required conflict process is complete. Independent authorized evaluators should apply the approved criteria and document the decision. A strong proposal does not erase the conflict, and the relationship does not automatically disqualify the firm under every procurement process. Follow the actual rule on eligibility and mitigation rather than deciding either outcome yourself.
The procurement record should show the authorized criteria, the evidence used and how the conflict was handled. Keep confidential proposal information restricted to the appropriate participants. A completed disclosure form alone does not prove that improper influence was absent. The actual evaluation conduct and authorized safeguards matter. The record supports accountability when it accurately describes those actions, rather than serving as a cosmetic defense for a decision already made.
Report metrics according to what they measure and the quality of the evidence. Story points, when a team chooses to use them, are relative estimates rather than a universal unit of time or a promise of business value. Forecasts should make important assumptions and uncertainty clear, using ranges when appropriate. Earned-value measures, cycle time and benefit metrics answer different questions. Correct a misleading dashboard promptly for the recipients who relied on it, preserving the relevant history and explaining the material effect.
Examine honesty through an original fictional project dashboard. The approved measurement basis gives planned value of one hundred thousand dollars, earned value of eighty thousand and actual cost of ninety thousand. A manager proposes reporting that spending is ten thousand below plan and therefore the project is healthy. That statement compares actual cost with planned spending but omits how much work has been earned. Spending less than planned can coexist with unfavorable delivery and cost performance.
Cost variance is earned value minus actual cost, giving negative ten thousand dollars. Schedule variance in earned-value terms is earned value minus planned value, giving negative twenty thousand dollars. The cost performance index is eighty divided by ninety, approximately zero point eight nine. The schedule performance index is eighty divided by one hundred, or zero point eight. These measures describe the stated model. The schedule variance is expressed in value units, not a direct claim that the project is twenty days late.
An honest report explains both the measures and their limits. The team has earned less value than planned and spent more than the earned amount under this basis. The schedule network and remaining dependencies are still needed to forecast the actual finish date. Acceptance and business-value evidence may also reveal matters that these indices do not measure. Reporting the figures without their meaning can mislead even when each calculation is technically correct.
Suppose the approved budget at completion is two hundred thousand dollars. If the same cost efficiency is assumed to continue, dividing that budget by the cost performance index gives an illustrative estimate at completion of two hundred twenty-five thousand dollars. With ninety thousand already spent, the corresponding remaining estimate is one hundred thirty-five thousand. This is a conditional forecast, not an automatic entitlement to more funding. If the remaining work differs materially from past work, another estimating approach may be more appropriate.
The project manager should communicate the assumptions and a realistic response rather than quietly resetting the baseline to the new forecast. A baseline change requires its own authorized basis. The earlier baseline remains relevant to understanding performance history even after a legitimate revision. Updating the forecast promptly is honest reporting; changing the record to make variance disappear is not the same action. Stakeholders need to see which number is an approved commitment and which is the current expectation.
A later correction should reach the people who relied on the misleading dashboard. State the comparison that was incomplete, provide the corrected measures and explain the practical decision consequence. Preserve the earlier version according to the applicable record controls rather than pretending it never existed. The purpose is not to embarrass its author. It is to prevent a flawed picture from continuing to influence funding, scope or release decisions.
Consider an agile project where velocity drops due to staff turnover. The honest response is to report the drop, explain the cause, and adjust forecasts. The dishonest response is to maintain prior projections and “hope” performance recovers. P M I expects the first path, because it protects stakeholder decisions. By showing the real forecast, you allow sponsors to consider scope reduction, schedule adjustment, or staffing changes. Honesty in metrics prevents the compounding of disappointment later. The exam will test whether you present numbers accurately, even when they are not flattering.
Evaluate a proposed shortcut by its actual effect. Backdating an approval or hiding a known issue misrepresents the facts. A verbal authorization may be permitted under a particular emergency procedure, but the decision still needs to be captured accurately as that procedure requires. A later correction can be legitimate when it transparently fixes an error. Greater disclosure is not always appropriate for confidential information. Provide accurate, timely information to the recipients entitled or required to receive it.
If a case asks you to backdate an approval so earlier work appears authorized, reject that misrepresentation. Record the approval's actual date and the circumstances, preserve the evidence and communicate the consequence through the proper route. If a correction concerns personal or sensitive information, use the appropriate recipients and controls. Honesty and confidentiality operate together. The ethical goal is an accurate account for legitimate decisions, not the widest possible distribution of every detail.
A useful routine is to report material facts promptly, distinguish evidence from assumptions and explain the relevant consequences. Present options when a decision is needed, without delaying a mandatory report until every option is complete. Apply authorized evaluation criteria fairly and document the actual rationale. Use controlled records and traceable corrections appropriate to the project. Versions and reconstructed accounts can be legitimate when their sources and limitations are clear; they must not disguise the history or invent an approval.
Disclose real or potential conflicts and refrain from influencing the affected decision until the required process permits further involvement or assigns it elsewhere. Do not wait until you personally feel unable to be impartial. Keep the relevant disclosure in the authorized channel and avoid unnecessary exposure of private information. Correct reports when their evidence or interpretation changes materially. Fairness and honesty require consistent conduct as well as an accurate account of it.
Fairness also requires care when people need different ways to participate. In a fictional requirements workshop, one participant uses an approved accessibility arrangement that allows written input before the meeting. Another stakeholder objects that everyone should be treated exactly the same and only live comments should count. Equal respect does not require identical participation methods when those methods create avoidable barriers. Use the organization's applicable accessibility and decision procedures to make relevant input available without changing the substantive evaluation unfairly.
The facilitator can publish the same decision question and evidence requirements to all authorized participants, provide accessible ways to respond and document how input is considered. Do not assume the person needs a particular arrangement based on appearance or background; use the actual request and qualified support process. Also avoid giving a favored participant an undisclosed extra opportunity to change a proposal after the decision closes. An authorized accommodation and a hidden advantage are not the same thing.
Another fictional case concerns a late entry in a decision log. A valid approval occurred on Tuesday, supported by an authentic recorded message from the authorized owner, but the administrator entered it on Thursday. The record should distinguish the event date from the entry date and identify the supporting evidence. That is different from moving Thursday's first-ever approval back to Tuesday. Both records may look similar on a dashboard unless the chronology and evidence remain clear.
If the supporting message is ambiguous about what was approved, do not resolve the ambiguity by choosing the interpretation that makes the project look better. Ask the appropriate owner to clarify the current decision and assess the earlier action honestly. A new clarification may help determine what to do now without proving that every earlier action was authorized. Accurate records can contain uncertainty. A polished record that conceals uncertainty is less useful than an honest account with a defined follow-up.
Consistent reporting and impartial conduct can help establish clear expectations. Their effect should be assessed through actual behavior, including whether concerns receive a fair hearing and corrections reach the people affected. Do not assume that a truthful message guarantees trust or agreement. Follow-through and appropriate review remain necessary.
Use short reminders as questions rather than guarantees. Is a material fact missing, have the criteria been changed fairly, and does the record distinguish an event from a later correction? Test each question on a new example. The value of rehearsal is to improve attention to evidence, not to promise an automatic exam answer.
For a final review, distinguish unfavorable information from unfair treatment. A supplier may fairly lose under a consistently applied authorized method. A project may honestly report an unfavorable forecast even when the team worked diligently. A person may receive respectful corrective feedback when evidence shows a problem. The ethical requirement is not to make every outcome positive. It is to make the process and account defensible.
Ask whether a recipient could reasonably draw a materially false conclusion from the way information is presented. A true but selective statement, such as spending below plan, can still mislead when essential delivery context is omitted. Add the context needed for the actual decision and respect legitimate information restrictions. Honesty is more than avoiding an invented number; fairness is more than applying a formula after the desired result has been chosen.
An authorized review or appeal route is another safeguard in the supplier example. A bidder may identify a calculation error or unequal treatment without being entitled to see a competitor's protected proposal. The responsible procurement owner should handle the concern under the actual procedure, preserving the evidence and correcting an established error transparently. Defending the original result simply because it has already been announced would confuse consistency with unwillingness to learn.
If a calculation error changes the result, communicate that consequence through the authorized process rather than silently editing the total. If the review confirms the original result, explain the defensible basis to the extent disclosure is permitted. A fair process can reach the same outcome after scrutiny, but its credibility comes from the quality of that scrutiny, not from guaranteeing that the first answer will never change.
Ethical decisions can create discomfort, and they do not guarantee popularity or protection from every adverse reaction. Still, concealing a material fact or exercising improper influence undermines the basis for a legitimate decision. Use the required process, preserve the relevant evidence and seek appropriate support when pressure persists. The professional responsibility is to act fairly and report honestly within the role. The outcome cannot be controlled by reassuring language alone.
To close, remember that fairness and honesty are not about perfection. They are about transparency, consistency, and courage. Fairness means using impartial processes and treating all parties consistently. Honesty means telling the truth quickly, correcting errors, and ensuring records reflect reality. Together, they reduce disputes, protect against audit findings, and sustain trust. In the high-pressure environment of project delivery, shortcuts will always whisper their appeal. But fairness and honesty are the only sustainable path. They are what P M I expects of you as a professional, and they are what will carry you through both the exam and the ethical tests of your career.
For more certification study resources, books, and podcasts, visit Bare Metal Cyber dot com. Thank you for listening to Certified, the P M P prepcast.
