How do I explain a recommendation that changed after new information arrived?
Quick answer
State the earlier recommendation and what it was based on, then identify the new information and the specific assumption or decision criterion it changes. Show how that leads to the revised recommendation, while making clear the earlier view was reasonable given what was then known. Separate confirmed details from remaining uncertainty, and say what would prompt another review.
The question, the details, the next step.
How can I explain the change without making it sound as if I’m covering up a mistake? I want readers to understand why I recommended one option before and a different one now.
Make the reasoning visible at both points in time. Briefly state what you recommended earlier and the information available then. Next, name what has arrived since and explain which part of the decision it affects. Then give the updated recommendation and its reason.
Avoid saying only “we changed our minds” or “new information came to light.” Those phrases do not let readers follow the connection. If the new information reveals an earlier error, describe that plainly rather than disguising it as a routine update. If the earlier recommendation was reasonable given what was then known, say so.
A useful shape is: “Based on [earlier information], we recommended [earlier option]. We have since learned [new information]. This changes [assumption, constraint, or priority], so we now recommend [revised option] because [reason].”
What should I include as the new information? For example, say I had recommended a full rollout, then learned that some teams need more time to prepare.
Be precise about what you know. “Some teams need more time” could mean a confirmed readiness gap or an early concern that still needs checking. Say what the information covers and whether it changes the recommendation itself or just its timing.
For instance: “Our earlier recommendation was a full rollout in [month], based on the preparation timeline we had at the time. We have since heard from [teams or roles] that they need additional preparation time. That changes our assumption that all participating teams can begin together. We now recommend a staged rollout, beginning with [group or phase], while the remaining teams prepare.”
Use placeholders until you can fill them with verified details. Don’t present an estimate, one person’s concern, or an unconfirmed report as settled fact. If the scope is uncertain, say so and explain how that affects the recommendation.
How do I show the reasoning rather than just announce the new answer? And how do I avoid making the earlier option sound bad?
Name the link between the new information and the decision. Say which working assumption, constraint, or priority changed and what consequence follows. Keep the earlier option’s original rationale intact if it still made sense under the earlier conditions.
For the rollout example: “A single start date was our preferred option because the preparation timeline appeared workable across teams. The new readiness information means a single start date may leave some teams insufficiently prepared. A staged start better fits the timeline now known. The full rollout remains a possible later goal; the change is to the sequence, not necessarily to that goal.”
Use “may” only when the consequence is uncertain. If you have not established that teams would be unprepared, describe it as a risk to check rather than a proven outcome. State what remains unchanged so readers do not mistake a narrow revision for a complete reversal.
Can you give me a reusable note that includes what happens next, without making promises about what the new information proves?
Use this copyable note and replace each bracket with confirmed details. Delete any line that does not apply:
“Recommendation update — [date or version]
Earlier recommendation: We recommended [option] based on [information and assumptions available then].
What changed: Since then, we learned [specific new information]. This is [confirmed information / an initial report / an estimate] from [source or group, if appropriate to name].
Why it matters: It changes our view of [assumption, constraint, or priority] because [brief reasoning]. [State what remains unchanged, if useful.]
Revised recommendation: We now recommend [option] because [reason tied to the new information].
What remains uncertain: We have not yet established [open question]. We will [next check or decision step] by [date or condition, if known]. We will review the recommendation if [specific new information or trigger].”
Before sending, check that readers can distinguish the old basis, the new information, and your interpretation. Choose a next step you can actually undertake; don’t imply it will prove the recommendation is right. If evidence is incomplete, make that limitation visible and say what decision can reasonably be made now.
A practical checklist
State the earlier recommendation and the information it relied on at the time.
Describe the new information specifically, including whether it is confirmed or uncertain.
Identify the assumption, constraint, or priority that the new information affects.
Explain the reasoning from that change to the revised recommendation.
Separate what changed from what remains the same, and name any open question.
Give a feasible next step or a clear condition for reviewing the recommendation again.
A few more useful answers
Should I apologize when my recommendation changes?
If you made an error, acknowledge it directly and explain the correction. If the earlier recommendation was reasonable based on what was then known, explain the update without implying fault.
What if the new information is not confirmed?
Label it as preliminary, an estimate, or an unverified report, as appropriate. Explain whether you are changing the recommendation now or waiting for a specific check before deciding.
How much detail should I include?
Include enough for readers to trace the change: the earlier basis, the new information, the affected reasoning, and the revised recommendation. Move supporting detail elsewhere if it obscures that sequence.