How to say “Politely say no” professionally

Level 1: Thank you for considering me for this. My current project load, particularly with the critical [Project Name] deadline approaching, means I wouldn't be able to give this new task the attention it deserves without impacting existing priorities. Could we discuss how this new initiative aligns with our current roadmap?

Level 2: I appreciate the opportunity to contribute to this, but my capacity is currently fully allocated to deliverables directly supporting [Strategic Goal X]. To take this on, we'd need to formally reprioritize something already in my queue. Which existing commitment should I defer?

Level 3: Per our last sprint planning session and the approved resource allocation matrix, adding this to my current commitments would necessitate a formal change request and subsequent review of our OKRs. Have you initiated the necessary workflow for impact assessment, or should I log a ticket for that?

Level 4: I cannot take on this additional task. My current workload is at capacity, and accepting more would directly jeopardize the completion of [Project A] and [Project B] by their established deadlines. We need to re-evaluate my current assignments or delegate this elsewhere.

Level 5: Not my problem.

Level 1: We appreciate your vision for incorporating this new feature. To ensure we maintain the quality and timeline of our current deliverables, we'd need to evaluate the technical scope and potential impact. This would likely require a formal change request to our existing agreement.

Level 2: That's an interesting enhancement idea, and we're always keen to explore ways to further improve the project. Given our current agreed-upon scope and schedule, integrating this would require a review of our project plan and a potential adjustment to the overall timeline or budget.

Level 3: While that concept certainly aligns with the 'stretch goals' we discussed during our initial ideation phase, it does fall outside the parameters explicitly defined in the mutually executed Statement of Work (SOW) version 2.7. Are you initiating a new project brief for this phase two expansion?

Level 4: This request is outside the scope of our current contract. Implementing it would necessitate a new agreement, which will include additional costs and an adjusted timeline. We can provide a separate proposal if you wish to proceed.

Level 5: Not in contract.

Level 1: I appreciate you reaching out, but I'm currently fully focused on my own priority tasks and won't be able to assist with that specific request at this time. I hope you find a resolution quickly.

Level 2: I understand you're facing a tight deadline, and while I'd normally be happy to help, my current bandwidth is committed to [Project X]. Have you already tried [Alternative Solution/Person] for this? They might be able to offer immediate support.

Level 3: That particular task falls within the scope delineated in our team's established RACI matrix for [Project Name], where I believe [Another Coworker's Name] is listed as 'Accountable.' Perhaps checking that documentation would streamline your search for assistance?

Level 4: I cannot take that on. I have my own deadlines to meet, and my focus needs to remain on my assigned responsibilities. You'll need to find another solution for that task.

Level 5: Do it yourself.