How to say “Refer to unpaid service” professionally

Level 1: Thank you for sharing this request. Based on our current project scope and resource allocation, this specific task appears to fall outside the agreed-upon deliverables for [Project Name]. Could we discuss how this aligns with our existing SOW or if it requires a separate budgetary consideration?

Level 2: I've reviewed the request, and it seems to extend beyond the parameters defined in our original Statement of Work for this engagement. To ensure we maintain project integrity and proper financial tracking, it would be prudent to clarify its funding and formal inclusion before proceeding.

Level 3: Understood. As per the documented `Statement of Work` (SOW) v1.2, this particular deliverable does not appear on the `RACI matrix` or within the `allocated budget`. Perhaps a `change request` would be the appropriate mechanism to formalize this `scope expansion`?

Level 4: This task falls outside the contracted scope of work. Proceeding without a formal amendment or additional budget allocation would expose the project to financial risk and delay existing deliverables. I require clear direction on how this will be funded and formally integrated.

Level 5: No budget, no work.

Level 1: Thank you for your request. This particular item represents an enhancement that falls outside the scope defined in our current Statement of Work. To move forward, we would need to initiate a change request and establish revised terms or a separate engagement.

Level 2: We appreciate your continued vision for this project. The functionality you've described goes beyond the deliverables outlined in our current agreement. We'd be happy to provide a proposal for this expanded scope, which would involve an updated project plan and adjusted pricing.

Level 3: We've logged your `feature enhancement request`. As per the signed `Master Service Agreement` (MSA) section 3.2.1 and `SOW` v1.0, this item is categorized as `additional functionality`. We can certainly provision a `change order document` outlining the `incremental resource allocation` and associated `cost implications`.

Level 4: This request is not covered by our existing contract. We cannot proceed with this work until a formal change order is signed and the additional services are appropriately budgeted. Please advise on how you wish to proceed.

Level 5: That'll be extra.

Level 1: Thanks for reaching out. My current workload is fully allocated to [Project A] and [Project B]. This task seems to fall under [Coworker's Area/Project]. Could you confirm if this is part of our shared responsibilities or if it requires a different team's bandwidth?

Level 2: I've reviewed your request. Given our respective project allocations, this particular item doesn't align with my current responsibilities for [Project Name]. It might be more appropriately handled by the team managing [Related Area], or perhaps it's an unallocated task that needs formal assignment.

Level 3: Appreciate you flagging this. Per the `team's established workflow` and our `individual contributor matrix`, this deliverable doesn't appear in my `active sprint backlog`. Have you cross-referenced it against the `unassigned tasks queue` or perhaps the `overlooked budget line item`?

Level 4: I cannot take on this task. It is not part of my assigned duties and has no associated budget or formal project allocation. You'll need to escalate this to management for proper assignment and resource planning.

Level 5: Not my problem.