How to say “Politely decline a task” professionally

Level 1: Thank you for considering me for this. My current commitments to [Project X] and [Project Y] are at a critical stage, making it challenging to dedicate the necessary focus to this new initiative without impacting existing timelines. Could we discuss prioritization or identify another team member with capacity?

Level 2: I appreciate you thinking of me for this. Given my existing bandwidth is fully allocated to [current priority], integrating this new task would necessitate a re-evaluation of current project timelines. Perhaps we could review the project roadmap to determine the most strategic placement for this request?

Level 3: Understood. As per our last sprint planning, my velocity is currently maximized by the initiatives already documented in [Project Management Tool Link]. Incorporating this new item would require a formal re-prioritization, presumably by adjusting the existing Q3 deliverables outlined in the strategic overview.

Level 4: I am unable to take on this task at this time. My current project load for [X] and [Y] is at capacity, and adding more would directly compromise the quality and deadlines of these critical deliverables. We need to either de-scope an existing project or reassign this new task.

Level 5: No.

Level 1: Thank you for this request. We've reviewed the scope, and this particular item falls outside our current Statement of Work. We can certainly provide a separate proposal to address this, or we can discuss how it might impact existing deliverables if integrated.

Level 2: We appreciate your proactive approach. This request introduces a new deliverable not explicitly outlined in our current project plan. To ensure we maintain the integrity of our agreed-upon timelines, we should formalize this as a change request to assess its impact and resource requirements.

Level 3: Acknowledged. As per the mutually agreed-upon contractual parameters detailed in Section 3.2.1 of the Master Service Agreement, this particular deliverable constitutes a scope deviation. A formal change order request, including revised budgetary allocations and timeline adjustments, will be initiated for your review.

Level 4: This task is not included in our current agreement. If you wish to proceed, we will need to initiate a change order, which will adjust the project scope, timeline, and budget accordingly. Please confirm how you would like to proceed.

Level 5: Not in the contract.

Level 1: Thanks for reaching out. Unfortunately, I'm currently focused on completing [my project/task] by [deadline], so I don't have the capacity to take this on right now. Have you checked with [another team member]?

Level 2: I appreciate you considering me for this. My current workload is quite tight with [specific commitment], and I wouldn't be able to give this the attention it deserves at the moment. Perhaps [another colleague] might have more bandwidth for this scope?

Level 3: Interesting initiative. My current OKRs are strictly aligned with [my team's specific objectives], as documented in our shared [Team Roadmap]. Taking on this ad-hoc request would introduce an unquantified variable into my sprint velocity, requiring formal stakeholder re-alignment.

Level 4: I cannot take on this task. My priorities are set for [my current project] and I need to ensure its timely completion. You're better off finding someone else who has the bandwidth and the direct responsibility.

Level 5: Ask someone else.