Does every freelancer need a contract?
A freelancer needs clear and provable terms rather than a needlessly long document. A short accepted proposal may work for a simple engagement, while higher-value and copyright-heavy work needs a more detailed contract.
The main purpose of a contract is to prevent disputes by defining the deliverable, timing, price, stages and feedback process.
Mandate, specific-work or B2B agreement?
The document title does not determine its legal nature. A specific-work agreement focuses on a defined result, while a mandate or service agreement focuses on diligent performance of activities.
B2B cooperation agreements often combine elements of several contract types. A random template should not be used without matching it to the real working model.
- a defined logo, website or text may be result-based
- ongoing marketing or technical support is usually service-based
- retainers need limits and unused-capacity rules
- seek advice when classification is unclear
1. Correct identification of the parties
The contract must identify who is legally responsible. B2B agreements usually include business name, address, tax and registry data and authorized representatives.
- full legal or business name
- registered or residential address
- tax and registry identifiers
- authorized signatory
- official email addresses
Verify that the person signing for the client is authorized to accept the price and bind the company.
2. Contract subject and deliverable
The subject clause must explain exactly what will be delivered. Terms such as “build a website” are usually too broad.
- deliverables
- formats, technology and parameters
- number of pages, screens, texts or hours
- languages and devices
- integrations and migrations
- excluded items
- client materials and access
The detailed scope may sit in an annex, proposal or brief, but the contract should identify the binding version and incorporate it.
3. Project goal and success criteria
Recording the business or user goal helps distinguish a defect from a later preference change.
Do not guarantee outcomes outside your control, such as sales, ranking or campaign performance, unless the assumptions and responsibilities are precisely defined.
4. Schedule and milestones
Set start date, stage deadlines and final delivery. Larger projects are safer when divided into milestones.
- discovery and materials
- concept or prototype
- main production
- testing and revisions
- final acceptance
- handover of files and access
State how client delays in materials, access or approvals move the schedule.
5. Client obligations
The client’s duties should be as precise as the freelancer’s. Missing content, decisions or access should not become the freelancer’s delay.
- complete and lawful materials
- required access
- one decision maker
- timely responses
- consolidated feedback
- verification of client-owned legal and factual data
6. Fee and pricing model
State net or gross amount, VAT, currency and settlement method. Hourly work needs reporting, limits and approval for additional time.
- fixed project fee
- milestone payments
- hourly or daily rate
- retainer with limits
- mixed model
Separate the base price from extra work so an out-of-scope request does not become a free obligation.
7. Advance, deposit and milestone payments
An advance is part-payment of the future fee. A legal deposit has different consequences and should not be used as a synonym.
- booking after payment
- next stage after prior settlement
- final files or rights after full payment
- suspension for overdue amounts
8. Payment dates and interest
Link booking, stages, final files and suspension rights to the agreed payments.
Define when the invoice is issued, the payment period and the bank account.
9. Acceptance procedure
B2B late-payment rules, commercial interest and recovery compensation may apply, but they should not be copied automatically into consumer contracts.
- delivery channel
- review deadline
- specific non-conformities
- effect of no response
- partial and final acceptance
- protocol, email or project-tool approval
Explain when delivery and acceptance occur. Without an acceptance procedure, a project may never formally finish.
10. Revisions and revision rounds
Any deemed-acceptance clause must be reasonable and compliant with consumer protection where relevant.
Define revision rounds, feedback deadlines and consolidated comments.
11. Scope-change procedure
- description of change
- price impact
- schedule impact
- impact on other work
- written approval
- updated annex or order
Distinguish corrections within the agreed outcome from a new feature, format or direction that changes scope.
12. Copyright transfer or licence?
A change request should record the requested change, impact on price and timing and written approval before work starts.
Do not begin additional work based only on a vague meeting comment.
13. Fields of exploitation
A client does not always need ownership of all copyright. A licence may fully cover the intended use.
- digital or print reproduction
- distribution of copies
- online and app publication
- public display and playback
- advertising use
- modification, translation and derivative works if agreed
14. Required form for copyright transfer
Copyright transfer is permanent on the listed fields of exploitation; a licence grants defined use while ownership remains with the creator.
List the actual ways in which the work may be used. A generic reference to all fields may be insufficient.
15. When rights transfer
A copyright transfer agreement requires written form or an equivalent qualified electronic signature.
Ordinary email approval may document many business terms but does not satisfy the required form for copyright transfer.
16. Third-party assets and AI tools
It is usually safer to make copyright transfer conditional on full payment.
- third-party component list
- licence type
- client licence purchase
- redistribution limits
- AI and confidential-data rules
- responsibility for client materials
17. Portfolio rights
A limited review or testing licence may apply before the final transfer.
Fonts, stock assets, plugins, open-source components and AI-generated elements may carry separate licences. The freelancer cannot transfer more rights than they hold.
18. Confidentiality and NDA
Document third-party licences, client-supplied materials and rules for using confidential information in AI tools.
- customer and employee data
- strategy, pricing and plans
- source code and technical documents
- credentials and configurations
- unpublished materials
- information marked or reasonably understood as confidential
If the freelancer wants to show the project, the contract should grant portfolio rights and state any embargo or confidentiality limits.
19. Personal data and processing agreement
Specify whether the company name, logo, screenshots, process and business outcomes may be used.
Confidentiality should identify protected categories, permitted use, duration and exceptions.
20. Security and access
- secure password sharing
- multi-factor authentication
- least privilege
- no unnecessary production-data use
- incident reporting
- removal of access
21. Liability
Also define return or deletion of confidential information after termination.
If the freelancer processes personal data on the client’s behalf, a GDPR-compliant data processing agreement may be required.
22. Contractual penalties
It should define subject, duration, purpose, data types, data subjects, security, subprocessors and deletion or return.
Set practical access controls, secure password transfer, least privilege, incident reporting and removal of access.
23. Subcontractors
Define liability and exclusions. In B2B work, parties may negotiate a reasonable cap with appropriate exceptions.
Do not accept responsibility for external platforms, hosting, algorithms, client materials or commercial results outside your control.
24. Warranty, support and maintenance
Contractual penalties can secure non-monetary duties such as confidentiality or delivery. They are not a substitute for late-payment interest.
- confirmed-defect correction period
- definition of defect
- response time
- exclusions for third-party changes
- post-period support pricing
- updates for libraries, hosting and systems
25. Duration and termination
Define triggers, amount, proportionality and whether additional damages may be claimed.
- ordinary termination with notice
- immediate termination for material breach
- payment for completed stages
- return and access removal
- handover of work in progress
- surviving confidentiality and rights
26. Client cancellation during the project
State whether subcontractors are permitted and whether client approval is required.
Ensure copyright, confidentiality and data obligations also bind subcontractors.
27. Force majeure and external events
Separate defect correction from new improvements, updates and maintenance.
Define support period, response times, exclusions and post-warranty pricing.
28. Governing law and disputes
A one-off contract ends after performance, acceptance and payment. Ongoing work needs duration, notice and handover rules.
State ordinary termination, immediate termination, payment for completed work and post-termination duties.
29. Order of precedence
Explain how work is settled when the client cancels without freelancer fault.
- governing law and court
- currency and transfer costs
- tax and invoicing
- controlling language
- time zone and business days
- data transfers outside the EEA
- copyright territory and licence duration
30. Communication and formal notices
Consumer protections may override B2B-style cancellation terms.
Force majeure clauses may regulate exceptional events outside reasonable control.
Consumer contracts
They should require prompt notice and mitigation rather than excuse every delay.
For international clients, specify governing law, language, court or dispute mechanism.
Sole trader with consumer rights
Consumer protection may limit freedom to choose law and court.
International clients
- main agreement
- statement of work or order
- price proposal
- brief
- schedule
- approved change requests
Is email enough?
Set the order of precedence between contract, statement of work, proposal, brief, schedule and later changes.
Identify official email addresses and tools and which decisions require written confirmation.
Common freelancer contract mistakes
- vague scope
- no exclusions
- missing client duties
- no acceptance or revision limits
- copyright transfer without fields
- rights transferred before payment
- no extra-work process
- no cancellation rules
- unlimited liability
- wrong template
Minimum contract checklist
- parties and authority
- subject and scope
- dates and dependencies
- price, advance and payments
- acceptance and revisions
- scope changes
- copyright or licence
- confidentiality and data
- liability
- termination and final settlement
- governing law and communication
When should a lawyer review the contract?
- high value or long duration
- important copyright transfer
- data, security or infrastructure responsibility
- international client
- unusual penalties or broad liability
- consumer work
- subcontractors and personal data
- large client’s imposed contract
Key conclusion
Special legal forms still apply to termination, copyright transfer or other formal acts where required.
Distance contracts with consumers may trigger information duties and withdrawal rights.
Do not use B2B clauses that unfairly remove statutory consumer rights.
