How to say “Politely assert non-negotiable condition” professionally

Level 1: Regarding this latest request, my current commitments are fully allocated to high-priority deliverables. To integrate this effectively, we would need to formally re-prioritize an existing project or re-evaluate current resource allocation.

Level 2: While I appreciate the strategic importance of this initiative, my capacity is entirely dedicated to [Project A] and [Project B], both of which are critical path items. Accommodating this new request would necessitate a formal adjustment to our Q3 objectives.

Level 3: Per the established Q3 OKRs and the documented RACI matrix for our team, this particular item falls outside my designated responsibilities. Perhaps we should consult the project charter to ensure alignment, or schedule a cross-functional meeting to clarify ownership and prevent future ambiguity.

Level 4: I need to be clear: this task is beyond my current bandwidth and the scope outlined for my role. Proceeding with it would compromise the quality and deadlines of my existing, high-priority projects, which I cannot allow.

Level 5: Not my problem.

Level 1: We appreciate your enthusiasm for this additional feature. However, this falls outside the parameters of our current Statement of Work. To incorporate it, we would need to initiate a formal change request process.

Level 2: That's a compelling enhancement idea. To ensure we maintain the quality and timeline of our existing deliverables, any adjustments to the current scope would require a review of our project plan and potentially an updated engagement agreement.

Level 3: Thank you for sharing your vision. As per Section 3.2, 'Scope of Services,' in our signed Master Service Agreement, this particular request is not included. We can, of course, explore a separate engagement for this, pending a revised proposal and budgetary allocation.

Level 4: To be direct, this new request fundamentally changes the scope we mutually agreed upon. We cannot proceed with it under the existing contract terms. A new agreement outlining revised timelines and costs will be necessary.

Level 5: Pay us more.

Level 1: I appreciate you thinking of me, however, my current workload is at capacity with [Project X]. I won't be able to take this on.

Level 2: That's an interesting challenge. Given my current sprint commitments, I'm unable to divert focus without impacting existing deliverables. Have you perhaps checked with [Team Member Y] who has expertise in that area?

Level 3: Thanks for the outreach. According to our team's documented workflow and resource allocation, this task is not within my purview. Perhaps the Kanban board or our last sprint planning document could offer clarity on ownership for this specific item.

Level 4: Let's be clear: this specific task is not part of my responsibilities or our agreed-upon division of labor. I cannot take it on, and I expect you to manage your own workload.

Level 5: Do it yourself.