Set scope, payment, revisions, deadlines, ownership, and termination terms clearly.
Key takeaways
- Identify both legal parties and the notices address.
- Attach observable deliverables and acceptance criteria.
- Tie deposits and milestones to dates or events.
Freelance contract foundations
A designer agrees to create a five-page website for $4,800. The useful contract does not stop at the price: it names the five pages, two revision rounds, client feedback deadlines, launch dependencies, ownership transfer after final payment, and what happens if the client pauses the project.
Run a contract-specific review
Before sending a first draft, build a one-page deal map with the legal names of both parties, the exact deliverables, the acceptance event, the payment schedule, and the person who can approve changes. Then compare every contract section with that map. A clause that does not support the agreed project should be removed or explained.
1. Identify the deal
Use the legal entity name, notices address, project owner, and signer authority rather than a brand nickname.
2. Define completion
List files, formats, dimensions, access credentials, handoff items, and an objective acceptance window.
3. Connect money to events
Tie the deposit, milestones, final payment, and any reimbursable expense to dated evidence.
4. Plan the exit
State what is payable if either party pauses or ends the project before final delivery.
Stress-test the difficult case
Stress-test the agreement against a project that stalls for reasons outside the freelancer's control. The client may deliver copy late, a third-party platform may change its API, or an authorized reviewer may disappear during the acceptance window. The contract should separate freelancer delay from client dependency delay, explain how dates move, and identify any standby or restart cost. It should also state whether an incomplete dependency changes the deliverable or merely postpones it. Without that distinction, both parties can reasonably believe the other side missed the deadline.
Verification pass before signing
Before signing, read the deal map and the contract side by side with the person responsible for delivery. Trace one ordinary milestone from request to evidence, approval, invoice, and handoff. Then trace one failed milestone through notice, cure, change control, and termination. Confirm that every referenced exhibit is attached and uses the same project name, dates, fees, and defined terms. Record unresolved assumptions in the agreement rather than leaving them in email, because a later reviewer should be able to reconstruct the bargain from the signed package alone.
Evidence to retain
Keep the proposal version, signed contract, deposit receipt, approved brief, milestone approvals, change orders, and final delivery record in one project folder.
Worked example
A five-page website is not complete merely because five URLs exist. Completion might require responsive layouts, tested forms, supplied copy, analytics access, and written acceptance within five business days.
What to verify
1. Scope
Identify both legal parties and the notices address.
2. Trigger
Attach observable deliverables and acceptance criteria.
3. Evidence
Tie deposits and milestones to dates or events.
4. Fallback
Separate pre-existing tools from client-owned final work.
Build the decision record
| Review item | Record before signing |
|---|---|
| Identify the deal | Use the legal entity name, notices address, project owner, and signer authority rather than a brand nickname. |
| Define completion | List files, formats, dimensions, access credentials, handoff items, and an objective acceptance window. |
| Connect money to events | Tie the deposit, milestones, final payment, and any reimbursable expense to dated evidence. |
| Plan the exit | State what is payable if either party pauses or ends the project before final delivery. |
Warning signs
- “Website design as needed” leaves scope open.
- “Payment on completion” does not define completion.
- Immediate IP transfer can remove leverage before payment.
Questions to resolve before signing
- What would prove that “identify the deal” is satisfied if the parties later disagree?
- What would prove that “define completion” is satisfied if the parties later disagree?
- What would prove that “connect money to events” is satisfied if the parties later disagree?
- What would prove that “plan the exit” is satisfied if the parties later disagree?
Sources and further reading
- IRS: Independent contractor status
- U.S. Copyright Office: Works made for hire
- FTC: Endorsements and testimonials
External sources explain general rules and terminology. Your signed agreement, current policy, jurisdiction, provider documents, and individual facts control the actual outcome.
Open the related ContractFixPro tool