Freelancer Contract Template Checklist: What to Include Before You Sign

1. Scope of Work

Scope disputes are the single most common source of freelance friction, and almost all of them trace back to a scope section that was too vague to settle anything.

• Define deliverables specifically. "A website" invites disagreement; "a 5-page responsive website built in [platform], including home, about, services, contact, and blog index pages" does not.
• List what's explicitly excluded. If you're not handling copywriting, hosting setup, or ongoing maintenance, say so in the same section — silence gets read as "included."
• Attach a project brief or spec sheet as an exhibit if the work is complex enough that a paragraph can't capture it.
• Include a change-order clause. State plainly that anything outside the listed scope is billed separately at your standard rate, so "can you also add..." has a built-in answer.

2. Payment Terms and Milestones

Payment terms are where a contract earns its keep — this is the clause you'll actually invoke if something goes wrong.

• Total project fee or hourly rate, stated as a specific number, not "to be discussed."
• Payment schedule — a deposit up front (typically 30–50%), followed by milestone payments tied to specific deliverables, with the final balance due at completion or before final file delivery.
• Invoice timing and due dates — net 15 or net 30, stated explicitly, so "late" has a fixed meaning.
• Accepted payment methods and who covers transaction fees on wire transfers or international payments.
• A currency clause if you work with international clients, so exchange-rate swings aren't a dispute later.

If milestone tracking and invoicing are the part that eats your time, our invoice template for freelancers with late payment reminders pairs directly with this section of the contract.

3. Revision Limits

• State a specific number of revision rounds included in the fee — two or three is standard for most creative and development work.
• Define what counts as a "round." A round is a single consolidated batch of feedback, not an open-ended stream of one-off change requests over several weeks.
• Set a price for additional rounds beyond the included limit, and state it now rather than negotiating it under pressure mid-project.
• Distinguish revisions from scope changes. "Make the logo bigger" is a revision; "add a whole new section" is a change order billed separately.

4. Kill Fee and Termination Clause

Projects sometimes end early — a client's business changes direction, budgets get cut, or the working relationship just isn't working. A termination clause decides what happens to the money and the work already done.

• Notice period. How many days' written notice either party must give to end the agreement early.
• Kill fee. A stated percentage (often 25–50%) of the remaining contract value owed if the client cancels after work has started, compensating you for the time already committed.
• Payment for completed work. Any milestone already delivered and approved is paid in full regardless of what happens after.
• Your right to terminate for non-payment or unresponsiveness, not just the client's right to walk away.

5. IP Ownership

• State when ownership transfers. The standard, client-protective approach is that IP transfers upon receipt of final payment — not upon delivery, and not automatically at project start.
• Carve out your own tools and frameworks. If you're reusing your own code libraries, design systems, or templates across clients, state explicitly that you retain ownership of those underlying assets while licensing their use in the deliverable.
• Address portfolio rights. Reserve the right to display the finished work in your portfolio unless the client has a specific confidentiality reason to restrict it.
• Cover third-party assets (stock photos, fonts, plugins) separately — you can't transfer ownership of something you licensed rather than created.

6. Confidentiality / NDA

• Mutual confidentiality — both parties agree not to share the other's confidential business information, not just a one-directional client protection.
• Define what counts as confidential (business plans, financials, unreleased products, client lists) so the clause isn't so broad it becomes unenforceable or so narrow it misses the point.
• Set a duration for the confidentiality obligation — commonly one to two years after the project ends, not "forever," which is harder to enforce and rarely necessary.
• Standalone NDA for sensitive work. If a client wants confidentiality terms before they'll even share a project brief, a separate signed NDA up front is more appropriate than folding it into the main contract.

7. Late Payment Penalties

• State a specific late fee — commonly 1.5–2% per month on the overdue balance, or a flat fee after a defined grace period.
• Define when work stops. Give yourself the explicit right to pause active work if an invoice goes more than a set number of days past due, rather than continuing to deliver while unpaid.
• Withhold final files until payment clears — state this plainly so it isn't a surprise if you ever need to invoke it.

8. Communication Expectations

• Response time commitments in both directions — how quickly you'll respond to client messages, and how quickly you need client feedback to keep the timeline on track.
• Approved channels. Naming email, a project tool, or scheduled calls as the official record prevents "I told you that on a text" disputes later.
• Meeting cadence for check-ins, especially on longer projects, so status updates aren't left to chance.
• Client responsiveness clause. State that delays caused by slow client feedback push the deadline back by the same number of days — this protects you from being blamed for a timeline the client themselves stalled.

9. Dispute Resolution

• Governing law and jurisdiction — which state or country's laws apply, and where any legal action would be filed.
• Escalation steps before legal action — many contracts require a good-faith negotiation period, then mediation, before either party can pursue litigation.
• Attorney's fees clause stating whether the losing party in a dispute covers the winning party's legal costs — this alone discourages frivolous disputes.

10. Build the Rest of Your Client System Around the Contract

A tight contract is the foundation, but it works best alongside the rest of your client management system — tracking which milestone you're on, when invoices are due, and where project files live. Our Automation Starter Kit and Notion Productivity & Client Management Template Pack are built for exactly this: the Starter Kit automates the repetitive admin around contracts and invoicing, while the Notion pack gives you a ready-made workspace to track scope, payment milestones, and deliverables against what you actually signed.

See the Automation Starter Kit & Notion Template Pack →

One-time purchase, instant digital delivery — no subscriptions.

Bringing It Together

This freelancer contract template checklist isn't about padding an agreement with legal language — it's about making sure the situations that come up in almost every project (scope changes, late payments, early termination, ownership questions) already have an answer before they happen. Run your next contract against this list, add whatever's missing, and you'll spend far less time negotiating disputes after the fact. For more on managing the client side of freelance work, see our guides on Notion templates for freelance contract and client management and invoice templates with late payment reminders, or browse the rest of the automation-edge.net blog.

Want More Automation Ideas?

The Automation Edge sends a new, plain-English automation tip every week — practical tools and workflows for small business owners, no coding required.

Subscribe for free tips →

No credit card needed. Unsubscribe anytime.