How to say "Politically remind of prior communication" to your boss
Level 1: Regarding this new request, I wanted to circle back to our discussion on [Date/Meeting Name] where we previously aligned on [specific detail/decision]. My understanding was that [previous agreement]. Could you confirm if there's been an update to that decision?
Level 2: To ensure we maintain consistent messaging, it might be beneficial to revisit the parameters established during our [Previous Discussion/Meeting]. We had previously outlined [Key Point], and aligning this new direction with that original context would be prudent. This approach ensures we leverage the groundwork already completed.
Level 3: Per the official minutes from the [Project Kick-off/Steering Committee] meeting on [Date], and as documented in the [Project Charter/SOW], the agreed-upon strategy was [Previous Strategy]. I'm operating under the assumption that these foundational documents remain our guiding principles, unless a formal change request has been processed and approved through the standard governance framework.
Level 4: We previously discussed and agreed upon [Specific Decision] on [Date], which shaped the current project trajectory. Implementing this new direction without acknowledging that prior discussion could lead to significant rework and budget overruns. I need clarity on which directive takes precedence before proceeding.
Level 5: Read your own emails.
How to say "Politically remind of prior communication" to your client
Level 1: To ensure we're aligned on the project's foundational agreements, I wanted to refer back to our discussion on [Date/Meeting] where we jointly confirmed [Specific Scope/Deliverable]. My understanding is that [Previous Agreement] remains our guiding principle for this phase.
Level 2: With respect to the current request, it might be beneficial to cross-reference the original scope and parameters established during our [Kick-off Meeting/Contract Review]. We previously agreed upon [Key Term/Condition], and we want to ensure any new considerations are integrated in a way that respects those initial agreements.
Level 3: As per the mutually executed Statement of Work (SOW) dated [Date], and further detailed in the project brief approved on [Date], the deliverable for this phase explicitly includes/excludes [Specific Item]. Any deviation from this documented scope would necessitate a formal change request, impacting both the project timeline and budgetary allocation, as outlined in section 4.2 of our agreement.
Level 4: Our previous communication on [Date] clearly established [Specific Expectation/Constraint] as part of our agreement. Proceeding with this new request without addressing that prior understanding will directly impact [Deliverable/Timeline/Budget]. We need to formally adjust the scope if this new direction is to be adopted.
Level 5: It's in the contract.
How to say "Politically remind of prior communication" to your coworker
Level 1: Just wanted to reference our conversation on [Date/Channel] where we established [Key Detail/Task]. My current understanding is that [Action/Deliverable] was assigned to [Person/Team]. Is that still accurate?
Level 2: To ensure we're all operating from the same playbook, it's worth recalling our discussion regarding [Topic] on [Date]. We had previously determined that [Specific Responsibility] would fall under [Your/Their] purview. Let's confirm we're still aligned on that.
Level 3: Per the thread in the [Slack Channel Name/Email Subject Line] from [Date and Time], we collectively agreed that [Specific Item] was to be actioned by [Their Name]. I'm just cross-referencing against the established workflow to avoid any unnecessary duplication of effort or, worse, critical gaps.
Level 4: As confirmed in our prior communication on [Date], [Specific Task] was clearly designated to you to complete by [Deadline]. My ability to move forward with [Subsequent Task] is contingent on its completion. What is the current status?
Level 5: It's in the chat.
