How to say “Refer to romantic involvement” professionally

Level 1: To maintain strict professional impartiality, any discussions pertaining to personal relationships, particularly romantic involvement, should be handled outside of our work context. My focus remains on deliverables and upholding our team's operational integrity.

Level 2: Given the established guidelines for professional conduct, particularly regarding potential conflicts of interest, it's important to ensure all project considerations remain strictly within the defined scope. Personal relationships, including romantic involvement, are best addressed through the appropriate HR channels if they impact professional duties.

Level 3: While I appreciate the team-building initiative, our current sprint planning documentation does not allocate bandwidth for processing inputs related to individual romantic entanglements. Perhaps we can revisit this during the next QBR, post-performance review cycle, to determine if 'relationship management' warrants a new line item in our OKRs.

Level 4: My role and responsibilities are clearly defined by my job description and the project SOW. Discussions or decisions influenced by romantic involvement fall outside of my professional remit and could expose the company to unnecessary risk. I must insist we adhere strictly to professional parameters.

Level 5: HR's problem.

Level 1: Our engagement is strictly focused on achieving the outlined project objectives. Matters related to personal romantic involvement fall outside the scope of our professional agreement and are not something we can address.

Level 2: To ensure we deliver optimal results and maintain clear accountability, our team strictly adheres to the established project parameters. Discussions concerning personal relationships, including romantic involvement, are beyond our professional purview and are best handled internally by your organization.

Level 3: I'm certain the Statement of Work we meticulously developed outlines our deliverables, none of which include providing consultancy on your team's romantic dynamics. Should this represent a new, unbudgeted phase, we'd be happy to prepare an additional change order for 'Interpersonal Relations Management.'

Level 4: Our contractual obligations pertain exclusively to the project scope. Any attempt to introduce personal matters, such as romantic involvement, into this professional relationship is inappropriate and will not be entertained. We must remain focused on our agreed-upon objectives.

Level 5: Read the contract.

Level 1: I understand the situation, but my professional focus must remain on our shared project deliverables. Any personal matters, including romantic relationships, should be addressed privately and separate from our work.

Level 2: While I value our collaborative dynamic, it's essential to compartmentalize personal discussions to maintain our professional efficacy. If issues related to romantic involvement are impacting your work, perhaps a confidential discussion with HR would be more appropriate.

Level 3: I'm genuinely impressed by your ability to multitask between coding sprints and managing complex interpersonal narratives. However, my RACI chart for this quarter doesn't show me as 'Chief Relationship Officer.' Perhaps the 'water cooler talk' channel in Slack is more aligned with this specific domain expertise.

Level 4: This conversation is veering into territory that is not professionally relevant to our project. My priority is completing our tasks, and I cannot engage in discussions about romantic involvement during work hours. Please respect this boundary.

Level 5: TMI.