Should I Sign This? A Simple Framework for Any Contract

Step 1: Understand what you are actually getting

The first question is the simplest and the most often skipped: what does this contract give you? For a job offer, that is more than the salary — it is the role, the start date, the benefits, the equity, the time off, the bonus structure, and the working arrangement. For a freelance contract, it is the deliverables, the scope, the payment schedule, and any rights you receive. For a lease, it is the unit, the term, the use rights, and whatever amenities are included. Write down what you are getting in concrete terms; if you cannot summarize it in a paragraph, you do not yet understand it well enough to evaluate it.

A common trap is conflating what you are told with what is in the contract. The recruiter promised a fast promotion path; is that in writing? The landlord said the appliances would be replaced; does the lease say so? Verbal promises are usually unenforceable, and the contract controls. So step one is reading the document and noting what is actually committed to in writing versus what was discussed.

Step 2: Understand what you are giving up

The second question is what the contract takes from you. Money is the obvious part — fees, salary expectations on your side, deposits, rent — but it is rarely the most consequential. The other things you are giving up usually live in the restrictive covenants, IP assignments, confidentiality obligations, mandatory arbitration, and similar clauses that take rights or future flexibility. A job offer that pays well but contains a broad non-compete is a trade you might or might not want to make; the salary on its own does not tell you whether the trade is worth it.

For each "giving up" item, ask how broad it is and how long it lasts. A six-month non-solicit limited to your specific clients is a very different commitment than a two-year non-compete covering your entire industry. A confidentiality obligation tied to defined trade secrets is different from one covering everything you might learn. The substance of what you are giving up matters more than the label.

Step 3: Ask "what is the worst that could happen?"

For every clause that pauses you, run the worst-case scenario. Not what is likely; not what either side intends. What does the language actually permit at its outer edge? If the client could pay you nothing under this payment clause because they never "approve" the work, that is the worst case — and that is the case the contract will be enforced by if it ever gets to court. Contracts are read by their text, not by anyone’s good intentions, and the gap between "they would never do that" and "the contract lets them do that" is exactly where most contract pain lives.

The worst-case analysis is uncomfortable but clarifying. If the worst plausible outcome under a clause is something you could live with — financially, legally, professionally — sign and move on. If it is something that would meaningfully damage you, that is a clause to negotiate before signing, not after the bad outcome happens. Doing this systematically catches most of what you need to catch.

Step 4: Identify your exit

How do you get out of this contract? Every agreement should answer that question, and many people sign without ever asking. For a job, look at notice periods, severance, non-compete survival, and what happens to equity if you leave. For a freelance contract, look at termination rights for both sides, payment for work completed, and any obligations that survive. For a lease, look at the term, early-termination penalties, and subletting rights. For a SaaS subscription, look at the renewal mechanics, cancellation notice, and what happens to your data.

The risk pattern to watch for is asymmetric exits — they can leave easily or "for convenience," and you are locked in or face penalties. A balanced contract has roughly symmetric exit terms; a one-sided one tells you who the contract was drafted to protect. You do not always need to fix the asymmetry, but you should know it exists before you sign, so you can plan around it.

Step 5: Compare the verbal pitch to the written text

If anyone has told you something about the deal — a recruiter, a salesperson, a landlord, a future business partner — check that whatever they said actually appears in the contract the way they said it. The number of disputes that come down to "but they told me" is enormous, and the answer is almost always the same: the written contract controls. If the recruiter promised a signing bonus and the offer letter does not mention it, the bonus is not real. If the landlord said you could have a pet and the lease prohibits pets, you cannot have a pet. The contract is the deal.

When you find a gap between verbal and written, raise it before signing. Most legitimate counterparties will add the missing piece without resistance because they did intend to provide it. The ones who suddenly cannot find a way to write down what they verbally promised are showing you something useful about how the relationship will work once you have signed.

Step 6: Check the dispute mechanics

If something goes wrong, how is the disagreement resolved? Look at the governing-law clause (whose law applies), the venue clause (where any dispute must be filed), any mandatory-arbitration provision, and any class-action waiver. These determine not just who wins a dispute but whether you can practically pursue one. A clause sending all disputes to a forum across the country, or to arbitration with the company-paying for the arbitrator’s selection, can quietly make your protections unenforceable in practice even when they look fine on paper.

For most everyday agreements, the dispute clauses are unfortunately non-negotiable — companies treat them as boilerplate they will not modify. What matters is that you sign with awareness, not in surprise after a dispute arises. For larger agreements, the dispute mechanics are worth negotiating; for everyday ones, knowing what you have agreed to is the bar.

Step 7: Apply the "would I take this trade in writing" test

A useful single test: if the contract were stripped down to "I give X, I get Y, I am bound by Z, and I can exit if W happens," would I take that trade? Verbalize the deal in those terms — not legalese — and see whether your gut response is "yes," "no," or "I need to change something." That basic articulation often surfaces concerns that the dense contract language obscured. If you cannot summarize the deal in plain English clearly enough to apply the test, that is itself a problem: you do not yet understand the contract well enough to sign it.

When the answer is "I need to change something," that is your negotiation list. When the answer is "yes," sign. When the answer is "no," walk away. The trick is doing the summarization honestly rather than waving away parts you do not want to think about, which is the most common failure mode.

Pick your two or three priorities

Once you have identified the issues, do not try to negotiate everything. Most counterparties tune out a person who treats a contract as forty equal battles, and you burn credibility on items that do not really matter. Pick the two or three terms that genuinely have the most impact on your situation and concentrate there. Maybe it is the payment trigger and the kill fee for a freelance contract, the non-compete and the IP assignment for an employment offer, the auto-renewal and the data terms for a SaaS deal. A short, prioritized list is more persuasive than a long one and far more likely to get a yes on the items that count.

When to walk away

Sometimes the right answer is "no," and the framework should give you a clear signal when it is. The patterns we see most often justify walking away include: the other side refuses to put their verbal promises in writing; the worst-case scenario under a key clause is genuinely catastrophic and they will not narrow it; the dispute mechanics make your protections practically unenforceable; or the counterparty’s response to reasonable, polite negotiation requests is hostility rather than engagement. Each of those signals tells you something about both this contract and the relationship that will follow, and the right move is sometimes to find an alternative.

Walking away is hard psychologically — you have invested time, you may have turned down other options, you want the deal. But signing a clearly bad contract because you are tired of negotiating is one of the most expensive forms of fatigue in business. The right alternative is almost always to walk now, before you are bound, even if it means starting over.

The 20-minute version

If you only have twenty minutes for an everyday contract, here is the compressed version:

• Read the whole document once at normal speed, just for orientation (5 minutes).
• Find the money, the exit, and the dispute mechanics — the three places risk concentrates (5 minutes).
• For each clause that gives you pause, ask "worst case under this language" (5 minutes).
• Compare what you were told to what the document says (2 minutes).
• Pick your two or three priorities, write specific replacement language, and send a friendly note (3 minutes).

The bottom line

The "should I sign this?" question is answerable by anyone willing to ask a few specific questions in order: what am I getting, what am I giving up, what is the worst case under the risky clauses, how do I exit, what does the contract actually say versus what I was told, how is a dispute resolved, and would I take this trade if it were stated in plain English? Apply that framework, pick your two or three priorities, and negotiate before you sign. If you want the framework run for you, ClauseAudit reviews the contract in about a minute, flags every clause that matters by risk level, compares each to what is typical, and gives you the language to ask for — so the "should I sign this?" decision is made on actual information, not on feel.