The contract does not slip because freelancers fail to understand contracts. It slips because raising it feels like distrust at exactly the moment both sides are enthusiastic. The fix is mechanical: keep the agreement short enough to read in four minutes, send it in the same message that confirms the start date, and treat the signature as the thing that begins the work rather than a formality trailing behind it.
Why it slips
A client says yes on a Thursday afternoon. You want to start Monday. Sending a six-page agreement into that conversation feels like changing its temperature, so you say you will send something over, and then you are two weeks into the work with nothing signed and no comfortable moment left in which to raise it.
Every part of that is social. None of it is legal. So the useful interventions are social too.
What the document has to contain
Short is not the same as thin. A one-page agreement covering these is worth more than a template full of clauses neither of you has read:
- Scope, in specifics. “A marketing site” is not scope. “Six page templates, two rounds of revisions, desktop and mobile” is. Most disputes in freelance work are scope disputes wearing another costume.
- Deliverables and dates. What lands, when, and what the client owes you in order for it to land on time.
- Fee and payment schedule. Amount, currency, deposit, invoice points, days to pay. A deposit is the single clause with the highest correlation to being paid at all.
- Revisions. How many are included and what an extra one costs. Without a number, “a couple of tweaks” is unbounded.
- Intellectual property. When ownership transfers and on what condition. Transfer on final payment is the common arrangement, and it is worth stating rather than assuming.
- Ending it early. What notice either side gives, and what is owed for work already done.
- Governing law. One sentence. It costs nothing to include and a great deal to argue about later.
If the client is a company, add who is authorised to approve work. “The founder loved it, the marketing lead did not” is a very expensive sentence.
Sending it
The mechanics matter more than they ought to:
- Send it inside the yes. Reply in the thread that confirmed the engagement, on the same day. “Great — here is the agreement, it is one page, and signing it puts you in my calendar for the 14th.”
- Give the signature a job. A signature that reserves capacity, locks a rate or triggers a start date is something your client wants to do. A signature that is “just for my records” is something they will do later.
- Sign it first. A document that arrives already signed by you is a decision, not a negotiation.
- Do not attach a PDF and ask them to print it. Print, sign, scan and return is four steps, and at least one of them needs a device your client may no longer own.
The number of unsigned freelance contracts in the world is not a measure of anybody’s professionalism. It is a measure of how many steps stood between yes and signed.
“Can you just start?”
Sometimes the answer is genuinely yes, and refusing costs you the work. If you do start unsigned, do the smallest version of the right thing: send a short email stating the scope, the fee and the start date, and ask them to reply confirming. That is a written record containing an agreement, and an exchange of emails has settled a great many disputes.
Then send the real agreement within the week, while everybody is still pleased with each other.
Keeping it
A signed agreement is only useful if you can still produce it in two years, and there is a statute behind that. ESIGN § 7001(d) treats an electronic record as satisfying a retention requirement when it accurately reflects the information, remains accessible to everyone entitled to it, and is in a form capable of being accurately reproduced.
In practice: download the completed PDF and its certificate of completion and put them somewhere you control, rather than relying on any vendor’s dashboard still existing in five years. Keep the file exactly as downloaded — re-saving it from a PDF viewer rewrites the bytes and breaks the hash you would otherwise use to show it has not changed.
What signing does not settle
A signed agreement records what the two of you agreed. It does not make terms enforceable that were not, it does not establish that the person signing had authority to bind their employer, and it is no substitute for invoicing on time. What it removes is the argument about what was agreed, which is the argument you were most likely to have.
Try it on a real document
Everything described here is what closeit.fast does on every envelope, including on the free tier. Send one and read the trail it produces.
Start signing free


