Every dual-layer project runs on two sets of terms.
The terms you have with your client — the scope they approved, the rate they agreed to, the milestones that trigger their payments. And the terms you have with your subcontractor — the deliverables they owe you, the rate you are paying them, the timeline they are working against.
These two sets of terms are related. They are not the same. And one of the most common structural errors in dual-layer project management is treating them as if they are — either by using one agreement for both relationships, or by sharing information across layers that was never meant to travel there.
What Each Party Actually Needs to See
Your client needs to see the upflow agreement. The scope. The milestones. The payment schedule. The deliverable standards you committed to. That is the full picture of your obligation to them — and it is the only layer of the project they need visibility into.
Your subcontractor needs to see the downflow agreement. Their specific deliverables. Their deadlines. Their payment terms. The scope of their lane. That is the full picture of their obligation to you — and it is the only layer they need visibility into.
The operator sees both. That is the job. Holding the full picture — client commitments above, subcontractor commitments below — while each party operates cleanly within their own layer.
What neither party needs, and what creates real problems when it travels, is the other side's terms.
Why Information Boundaries Matter
When a client can see what you are paying your subcontractor, they can calculate your margin. That calculation changes the conversation — about your rate, about the value of what you deliver, about whether they need you in the middle at all.
When a subcontractor can see your client agreement, they know your rate. They know your milestone structure. They know enough to approach your client directly — not necessarily with bad intent, but with information that was never theirs to have.
Neither of these outcomes requires anyone to act in bad faith. They require only that information traveled further than it should have. The structural protection is not about distrust. It is about building a project architecture where each party has exactly what they need and nothing more.
How Oblige Holds Both Layers
Oblige separates agreement layers inside a single project view.
The client sees the upflow agreement — scope, milestones, payment schedule — and nothing beneath it. The subcontractor sees the downflow agreement — their deliverables, their deadlines, their terms — and nothing above it. The operator sees the full picture: both layers, side by side, with milestones linked across them so a change on one side surfaces its impact on the other.
When scope expands on the client side, the operator can see immediately how that expansion lands on the subcontractor layer — without either party having visibility into the other's terms. When a subcontractor deadline shifts, the operator can see how that shift affects the client milestone it feeds — and address it before it becomes the client's problem.
The information boundary is structural, not manual. The operator does not have to manage what each party sees. The platform holds it.
The Walk-Away Signal
A client or subcontractor who resists putting terms in writing is not making an administrative preference. They are telling you something about how they intend to operate when things get complicated.
The operator who insists on written agreements — separate ones, structured for each relationship — is not being difficult. She is building the infrastructure that makes the project survivable when something shifts. And something always shifts.
Two agreements. One project. Each party sees what they need. The operator sees everything.
That is the structure Oblige is built for.
