How to say “Refer to feedback” professionally

“Refer to feedback”

Say this insteadLV.1 Professional

“Thank you for raising this point. We did cover this during our last review on [Date/Meeting Name], and the feedback provided then was [brief summary or action]. Could you please re-consult those notes for the specific details?”

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

I already told you this, read your own damn notes, or stop asking me the same thing. My time is not infinite.

YOUR BOSS'S READ

Ah, they're just confirming my brilliant strategic foresight. Good to know they're aligned with my initial, albeit forgotten, guidance.

PM'S READ

Another instance of scope creep averted through effective `knowledge management`. My `risk mitigation` strategy is flawless.

HR'S READ

Proactive `knowledge sharing` and `interdepartmental synergy` demonstrated by referencing `archived strategic communications` for enhanced `operational clarity`.

How to say "Refer to feedback" to your boss

Level 1: Thank you for raising this point. We did cover this during our last review on [Date/Meeting Name], and the feedback provided then was [brief summary or action]. Could you please re-consult those notes for the specific details?

Level 2: I appreciate you revisiting this. As per our previous discussions, the established direction incorporated the feedback shared on [Date/Platform]. Re-engaging with that documented input would be beneficial for aligning our current efforts.

Level 3: Excellent query. To ensure optimal adherence to our established `project governance` and `resource allocation`, kindly reference the detailed feedback documented within the [Specific Document/Platform e.g., Confluence, Jira ticket, email thread ID] on [Date]. This will streamline our `operational efficiencies` moving forward.

Level 4: This specific item was addressed and finalized with your feedback on [Date/Platform]. Any deviation from that agreed-upon path at this stage will impact the project timeline and resource forecasts, requiring a formal change request.

Level 5: Check your inbox.

How to say "Refer to feedback" to your client

Level 1: Thank you for your inquiry. The specific details and rationale concerning this point were outlined within the feedback section of the [Project Proposal/SOW/Last Review Document] dated [Date]. Please review that document for complete clarity.

Level 2: We appreciate you seeking clarification. Our current approach reflects the comprehensive feedback provided and documented in the [Contract/Approval Document] on [Date]. Re-examining those agreed-upon parameters will ensure we remain aligned with the initial scope.

Level 3: We value your commitment to `iterative refinement`. To maintain `contractual fidelity` and `fiscal prudence`, kindly consult the `stakeholder feedback register` located within the [Specific Document/Platform e.g., Signed SOW, Change Request Log, Client Portal] from [Date]. This ensures all `deliverable parameters` are consistently met.

Level 4: The parameters for this deliverable were explicitly defined and approved based on your feedback provided on [Date] in [Document]. Any changes at this stage will trigger a formal change order, impacting both budget and timeline.

Level 5: Read the contract.

How to say "Refer to feedback" to your coworker

Level 1: Thanks for reaching out. The details regarding this were previously shared and incorporated based on the feedback provided in [Specific Document/Platform, e.g., the sprint review notes, the Slack thread dated XX]. Please consult those resources for the comprehensive context.

Level 2: Appreciate you circling back on this. The agreed-upon approach, reflecting the feedback we received during [Meeting Name/Date], is outlined in [Location]. Reviewing that might clarify the current state and next steps.

Level 3: Great initiative to ensure `cross-functional alignment`. As per our established `information architecture` and `data repository protocols`, all actionable feedback pertinent to this item is systematically cataloged within the [Specific Tool/Document e.g., Jira ticket, Confluence page, Teams channel history]. A quick review there should provide the necessary `contextual framework`.

Level 4: This specific area was addressed and finalized following the feedback documented on [Date/Platform]. Re-opening this discussion requires a formal re-evaluation of dependencies and could impact other commitments.

Level 5: It's in the notes.

The Decoder's Analysis

In professional environments, the need to reference previously provided feedback often arises when stakeholders re-litigate decisions or request information already communicated. This practice is crucial for reinforcing the agreed-upon scope of work, maintaining clear boundaries, and managing workload effectively. It's a fundamental aspect of professional communication, preventing the re-delegation of already completed tasks and ensuring project continuity without unnecessary friction.

When to use this

USEWhen a stakeholder is asking for a decision or information that was already documented and approved in a prior review or meeting.

USEWhen a project or task is veering off course because previous instructions or feedback have been overlooked or ignored.

USEWhen someone attempts to re-open a discussion or re-assign a task that has already been finalized based on given input.

AVOIDWhen the feedback provided was ambiguous, contradictory, not formally documented, or inaccessible to the person asking.

Related Deflections

→ How to say “Politically refer to physical characteristics” professionally → How to say “Refer to romantic involvement” professionally

Also searched as

professional way to say feedback