Who Owns the Relationship When the Client Goes Around You
It starts innocently enough. The client wants to move fast, so they email the vendor directly — just a quick question, just to keep things on track. What actually happened is this: the one person managing both sides of the project just lost visibility into one of them. And whatever gets agreed to in that side conversation becomes the operator's problem the moment an invoice doesn't match what anyone expected.
What Actually Breaks When the Client Goes Direct
The moment a client makes direct contact with a vendor, three things happen simultaneously — and none of them are visible to the operator until the damage is done.
The operator loses visibility into scope
Every conversation between a client and a vendor is a potential scope event. A 'quick question' can become a verbal agreement to add something, change something, or remove something. None of that gets routed through the operator. None of it gets documented in the project record. It exists only in an email thread the operator wasn't copied on — until it surfaces as a discrepancy between what the vendor invoices and what the client expected to pay.
The vendor now has two masters
A vendor who receives direct instructions from a client is in an impossible position: they have a subcontractor agreement with the operator, and a direct communication from the client that may conflict with it. Most vendors will try to accommodate both. In doing so, they create a version of the project that no one has fully authorized — and the operator is accountable for the output regardless.
Cost and scope changes lose their paper trail
Any change agreed to in a direct client-vendor conversation lands on the operator's ledger with no documentation. If the client asks the vendor to add something, the vendor does it, and the operator's invoice to the client doesn't reflect it — the operator absorbs the cost. If the client tells the vendor to skip something, the vendor does, and the operator's deliverable to the client is now incomplete — the operator absorbs the dispute.
When a client contacts a vendor directly, it isn't a shortcut — it's a structural failure of the agreement that was supposed to route all communication through the operator. Vendor contact restriction is the clause that keeps the operator the single point of truth for scope, cost, and timeline on both sides.
What the Clause Actually Says
Vendor contact restriction appears in two places: the upflow agreement with the client, and the downflow agreement with the vendor. Both are necessary. One without the other leaves half the structure unprotected.
In the client agreement (upflow)
The clause establishes the operator as the sole point of contact for all project communications, including communications with any vendors, subcontractors, or third parties engaged to deliver the work. It specifies that the client agrees to route all questions, requests, and feedback through the operator rather than directly to any vendor.
A simple formulation: 'Client agrees that all communications regarding project scope, deliverables, timeline, or cost will be directed to [Operator] and not to any subcontractor or vendor engaged in delivery of the work. Any agreement made directly between Client and a subcontractor or vendor is outside the scope of this engagement and does not bind [Operator].'
In the subcontractor agreement (downflow)
The clause establishes that the vendor's relationship is with the operator, not with the client. It specifies that the vendor agrees not to accept direction from the client directly, and to route any client communications to the operator immediately.
A simple formulation: 'Subcontractor agrees to direct all client communications to [Operator] promptly and to refrain from accepting direction, making commitments, or agreeing to scope changes directly with Client without [Operator]'s written approval.'
Together, these two clauses close the loop. The client knows they're supposed to go through the operator. The vendor knows they're not supposed to accept direct client direction. When something breaks that pattern, both sides have a documented obligation that was violated — not just an informal expectation that wasn't honored.
This Isn't About Control. It's About Accuracy.
The objection operators sometimes anticipate: clients will find the clause overbearing. It implies distrust. It slows things down.
In practice, the clause rarely generates friction with clients who intend to work professionally. Most clients understand — when it's explained clearly — that routing communications through the operator is how the project stays accurate. The operator is the one with full context on both the client agreement and the vendor agreement. Direct client-vendor communication creates a version of the project that neither party has complete information about.
The clients who push back on vendor contact restriction are, again, providing information worth having before the project starts. A client who won't agree to route communications through the operator is a client who intends to manage around the operator — which is a fundamentally different engagement than the one being priced.
When It's Already Happened
If a client has already contacted a vendor directly and something was agreed to outside the operator's view, the immediate move is documentation. Get the vendor to confirm in writing what was discussed and agreed. Get the client to confirm the same. Establish the record before the project progresses further on the basis of an undocumented side conversation.
Then address it directly with the client — not accusatorially, but clearly: 'I need all project communications routed through me so I can maintain accurate records on both sides. If something was agreed to in that conversation, I need to know so I can update the project scope accordingly.'
That conversation is easier when the agreement already includes a vendor contact restriction clause, because it gives the operator a documented basis for the request rather than an improvised one.
Oblige structures both upflow and downflow agreements as parallel documents on every project — which means the vendor contact restriction clause lives in both layers simultaneously, and both parties are bound by it from the start. The operator stays the single point of truth because the structure requires it, not because everyone happens to remember the informal expectation.
Subscribe to Velvet Ledger. Vendor Contact Restriction Doctrine drops Friday.
