Field Note · Legal decisions and counsel
A Contract Should Set Expectations Before Conflict Tests Them
Most contracts are treated as paperwork at the end of a business conversation. By then, the parties may have skipped the most valuable part: deciding what each side actually expects the relationship to produce and what happens when reality changes.
A thinking frame by Andrew Moss
The questions I get
Usually some version of these:
- Which protections should we put in the contract?
- Can counsel make this agreement standard?
- What should be decided before the first legal draft?
What a lot of people seem to think
The contract is mainly a defensive document for allocating blame and remedies if the relationship fails.
How I look at it
I think a contract does its best work before conflict exists. It is a forcing function for expectations: outcome, scope, ownership, decision rights, evidence, economics, communication, change, and exit. If those conversations are skipped, more legal language can make the ambiguity longer without making it clearer.
Why the decision matters
The cost is rarely confined to the line item.
If the sequence is wrong
The parties can sign the same words while expecting different deliverables, timing, authority, economics, or standards of success. Conflict then consumes trust, margin, time, and the underlying opportunity.
If the sequence is right
The contract reflects a relationship both sides understand, gives the operating team usable rules, and creates an orderly way to adapt or exit.
How reversible is it?
Moderate before performance begins; low after money, work, data, customers, and reputation are committed.
The short answer
Set expectations while both sides still want the relationship to work.
Begin with a plain-language deal brief. Define the result, deliverables, acceptance, owners, decision rights, dependencies, economics, communication, changes, escalation, and exit. Stress-test the relationship before asking counsel to turn the decisions into enforceable language.
A useful analogyA contract is both a blueprint and a load test.
The blueprint tells the teams what they are building. The load test asks what happens when timing slips, an assumption fails, or one side wants to change the plan.
Move fromPapering a relationship→Move towardAligning the relationship before stress
The order I would use
Take the right steps in the right order.
- 01
State the intended result
What should be true if the relationship works?
- 02
Define the work and evidence
Specify deliverables, exclusions, timing, dependencies, acceptance, and how performance will be assessed.
- 03
Assign ownership
Name decision makers, operating owners, approvers, and the authority each side retains.
- 04
Make assumptions and economics visible
Identify required access, staffing, third parties, pricing, expenses, incentives, and how changed scope changes cost.
- 05
Design change and escalation
State how requests change, disagreements surface, issues escalate, and urgent decisions are made.
- 06
Write the exit and test scenarios
Address termination, surviving duties, data, work product, payment, handoff, delay, underperformance, dependency failure, and early exit.
Questions worth answering
Before the next irreversible move:
- What does success look like in observable terms?
- Which party controls each dependency needed for performance?
- Who decides when the work, timing, or price changes?
- What must survive termination, and what must be handed back?
What not to do
Do not ask counsel to make an unresolved relationship standard.
Do not hide the hard commercial trade behind vague words. Do not define deliverables without dependencies or acceptance. Do not sign under urgency and assume the team will work it out later. Do not let the written agreement drift away from how the relationship actually operates.
Keep the perspective
The point is not to predict every failure.
It is to make the important expectations discussable before stress makes them expensive. The legal language matters, but the parties first have to decide what they mean.
The boundary
What still depends on the facts
Formation, enforceability, remedies, warranties, liability, employment, intellectual property, privacy, regulated services, and other contract terms depend on the transaction, governing law, and facts. A decision frame cannot replace qualified contract counsel.
Independent sources
Useful primary material
These sources support the public frame. They do not replace the private facts or the accountable professional.
Common follow-up questions
Should the business team or lawyer draft first?
The business principals should first clarify the intended result and major decisions. Qualified counsel should then test, translate, and document the bargain.
Can every contract use the same checklist?
No. The structure must fit the relationship, risk, governing law, data, people, economics, and consequences.
Why define acceptance and dependencies?
They prevent one side from promising an outcome while the other side controls information, access, approvals, or conditions needed to produce it.