The Handshake vs The Contract Decision Tree
Why this matters
You just shook on a deal. Now the question is whether a handshake is enough or whether this one needs to be in writing. Insist on a contract for a small favor between people who trust each other and you look like you do not, which can sour a good relationship. Settle for a handshake on a big, complex, or risky job and you have nothing to point to when memories drift and a dispute starts. Getting this wrong costs you either a relationship or a remedy. This tree decides which deals earn a signature and which are fine on your word.
Start here: a handshake is a real agreement
First, clear up a common mistake. A handshake deal is still a binding agreement in most everyday situations, it is just one that is hard to prove. The choice is not "binding versus not binding." It is "easy to enforce versus your word against theirs." So the real question this tree answers is: how much do you need to be able to prove what you agreed, if it ever comes to that?
Read the deal on four axes
Sort the deal on these, and the answer falls out.
- Size. The larger the deal relative to what you can afford to lose, the more it needs writing. A small job gone wrong is a bad day. A large one gone wrong is a real wound.
- Complexity. The more moving parts, milestones, conditions, and exceptions, the more you need them written down, because nobody remembers a complicated deal the same way two months later.
- Duration. The longer the deal runs, the more memories drift and people change. A same-week job is one thing. A months-long arrangement is another.
- Trust and track record. A long history of clean dealing with this person lowers the need for paper. A new or shaky relationship raises it.
The comparison
| Factor | Handshake fine | Get it in writing |
|---|---|---|
| Size | Small, easily absorbed | Large relative to your means |
| Complexity | Simple, one deliverable | Many parts, conditions, milestones |
| Duration | Short, done soon | Long-running |
| Relationship | Long, trusted history | New or strained |
| If it goes wrong | A manageable loss | A serious problem |
| Need to prove terms | Low | High |
Walk the branches
If the deal is small, simple, short, and with someone you trust, a handshake is fine, and demanding a contract may insult a good relationship. Note: even here, a quick text confirming what you agreed costs nothing and gives you a light record without the formality of a contract. The text is the middle ground, and it is almost always worth sending.
If the deal is large, or complex, or long-running, or with someone you do not yet trust, get it in writing, and do not apologize for it. The bigger or more involved the deal, the more a written agreement protects both sides, not just you. Frame it that way: "Let us put this in writing so we both know exactly what we agreed." A professional asking for clarity is not a professional showing distrust.
If it is mixed, for example a sizable job with someone you trust, lean toward writing, because trust does not protect you from a memory gap, an accident, or that person being unavailable when the question comes up. The relationship is not the only thing that can go wrong. Writing it down protects the deal from circumstance, not just from bad faith.
What "in writing" can be
Writing does not always mean a formal contract. The level should match the deal:
- A confirming text or email for small deals where you just want a record of what was said.
- A simple written scope and terms for ordinary jobs: what, when, how much, payment terms, signed or acknowledged by both.
- A formal contract for large, complex, or long-running work, ideally reviewed by someone qualified when the stakes justify it.
Match the formality to the risk. A confirming text is overkill for nothing and a formal contract is overkill for a small favor, but the wrong direction, no record on a big deal, is the one that hurts.
The recap
- Remember a handshake is still binding, just hard to prove.
- Read the deal on size, complexity, duration, and trust.
- Small, simple, short, trusted: handshake fine, and send a confirming text anyway.
- Large, complex, long, or untrusted: get it in writing, no apology.
- Mixed: lean toward writing, because circumstance can break a deal even between honest people.
- Match the formality, text to scope to contract, to the actual risk.
The judgment to bank: the question is never whether you trust them, it is whether you could prove the deal if you had to. Size, complexity, duration, and stakes decide that, and a confirming text is so cheap there is rarely a reason to skip it.
References
- See related: The Deal That's Too Good: What's the Catch Decision Tree
- See related: Negotiating a Payment Plan That Holds
- Trade-standard practice for service agreements and scope documentation
- U.S. Small Business Administration (SBA), contracts and written-agreement guidance