How to say “Politely remind of prior communication” professionally

“Politely remind of prior communication”

Say this insteadLV.1 Professional

“Just circling back on this. We had previously discussed this approach during our meeting on [Date] where we aligned on [Key Decision Point]. Could you clarify if there's new information that warrants a revisit?”

SafeUnhinged

The Anatomy

The chain of dysfunction that forced you to say this.

Tap to expand

The Multiverse

You said one thing. Everyone heard something different.

YOUR INTENT

We already talked about this. You're wasting my time and everyone else's by making me re-explain or redo something.

YOUR BOSS'S READ

Ah, a diligent employee confirming details. Excellent initiative to ensure thoroughness, even if it delays things slightly.

PM'S READ

Another instance of scope creep being efficiently managed by identifying redundant efforts. Clearly, my project management documentation is robust.

HR'S READ

An employee demonstrating proactivity in clarifying project parameters, fostering a culture of accountability and effective information exchange. Truly a testament to our transparent communication policies.

How to say "Politely remind of prior communication" to your boss

Level 1: Just circling back on this. We had previously discussed this approach during our meeting on [Date] where we aligned on [Key Decision Point]. Could you clarify if there's new information that warrants a revisit?

Level 2: I believe we touched upon this topic in our discussion on [Date], where we finalized [Outcome]. To ensure we're leveraging prior efforts efficiently, could you confirm if this new request aligns with that established direction?

Level 3: Referencing our previous communication on [Date] (ticket/email ID: [XXXX]), where the **RACI matrix** clearly designated [Team/Individual] as Responsible. My current **scope of work** does not reflect this overlap; please advise on the process for **re-scoping** if a divergent path is now required.

Level 4: As per our confirmed agreement on [Date], documented in [Email/Meeting Minutes], the decision was [Specific Decision]. Reopening this without a clear change management process could impact our current deadlines for [Project Name].

Level 5: Read the email.

How to say "Politely remind of prior communication" to your client

Level 1: Thank you for reaching out. We did cover this during our meeting on [Date], where we confirmed [Specific Detail]. I've attached the relevant meeting notes for your convenience.

Level 2: I appreciate you seeking clarity. Our previous communication on [Date] outlined [Key Decision/Deliverable]. To ensure we maintain alignment, please let me know if there's any new information that would alter that understanding.

Level 3: Per the signed **Statement of Work (SOW)** section [X.Y] and our documented client review on [Date], the deliverable [Specific Item] was accepted/finalized. Any request for modification at this stage would constitute a **change request** and be subject to the standard **re-scoping process**.

Level 4: We mutually agreed on [Specific Outcome] on [Date], as documented in [Contract/Minutes]. Proceeding with a different direction now would require a formal amendment and could impact project timeline and budget.

Level 5: It's in the contract.

How to say "Politely remind of prior communication" to your coworker

Level 1: Just wanted to bring this back to our previous discussion. We agreed on [Specific Action/Outcome] on [Date/Channel]. Could you confirm if that's still the plan?

Level 2: I recall us aligning on [Key Point] during our chat on [Date]. Before moving forward, I wanted to ensure we're both operating from that established understanding to avoid any missteps.

Level 3: As outlined in the [Team Sync Minutes/Slack Thread] from [Date], the decision point on [Topic] was resolved with [Specific Solution]. Is there a new **sprint retrospective** finding or **post-mortem analysis** that negates this prior consensus?

Level 4: We confirmed the approach for [Task] on [Date]. Deviating from that without prior discussion will require a formal re-evaluation and could impact [Dependent Task/Project].

Level 5: Check your inbox.

The Decoder's Analysis

In the modern corporate landscape, effectively reminding colleagues or superiors of prior communications is crucial for maintaining clear scope of work and establishing healthy boundaries. This skill is vital for preventing rework, managing workload management, and ensuring tasks are not double-assigned or overlooked due to a lack of professional communication. Mastering this allows for efficient delegation and protects individual productivity from unnecessary interruptions.

When to use this

USEWhen a superior assigns a task that has already been discussed or completed.

USEWhen a colleague requests information that was previously shared in a team communication.

USEWhen a client asks for a deliverable that has already been submitted or approved.

AVOIDWhen attempting to shame someone in a public forum or during a critical high-stakes meeting where maintaining harmony is paramount.

Related Deflections

→ How to say “Politely request clarification” professionally → How to say “Politely request understanding” professionally

Also searched as

how to politely say as previously mentionedhow to politely say as i said beforehow to politely say you already sent an emailhow to politely say like i saidhow to politely say you missed an emailhow to politely say per my last emailhow to politely say per my previous emailhow to politely say i already told youhow to politely say you already sent an email samplehow to politely say as mentioned beforeprofessional way to say as previously mentionedprofessional way to say per my last email