Independent contractor agreement template: clauses and completion guide

Key takeaways

• Choose the agreement type before editing. A professional-services form fits many contractor engagements, but it does not replace an employment, subcontracting or construction agreement where the parties, work or local law call for a different structure.
• Treat the contract label as one fact in a status assessment. The actual working practices and the applicable jurisdiction determine how the relationship is assessed.
• Replace each bracketed field with agreed facts: parties, scope, deliverables, fees, dates, acceptance criteria, rights, confidentiality, data duties, risk allocation, termination terms and governing law.
• Use a project-specific statement of work to connect each deliverable to its exclusions, revision rounds, approver, acceptance evidence, milestone and invoice trigger.
• Check the rights and data chain before delivery. Identify who created each item, which existing or third-party materials are involved, and whether the contractor processes personal data on the client’s behalf.
• Retain the complete signed packet: the final agreement, statement of work, amendments, signature and authority records, acceptance evidence and rights instruments.

Choose the right agreement before editing

An independent contractor agreement is a suitable starting point when a business commissions defined professional services from an independent provider. Before you customize it, identify the parties, the work, the actual working practices and every relevant location. The document label does not decide worker status, and a general contractor form may not fit employment, construction or subcontracting arrangements.

Contractor, services, subcontractor or employment agreement?

Start with the legal and commercial relationship rather than the filename:

• Independent contractor or contract for services: use for professional services performed by an independent provider under the arrangement you actually intend to operate.
• General service agreement: use when the commercial structure is broader than contractor status and the agreement covers ongoing services without depending on an individual contractor classification.
• Subcontractor agreement: use when the provider is delivering work to another contractor or intermediary within a larger project. Identify that relationship in the recitals and preserve approval, quality, access and rights obligations.
• Employment agreement: use when the working relationship belongs under employment law. Do not adapt a contractor form merely to avoid employment obligations.
• Construction agreement: use a construction-specific form when the work is governed by construction requirements, site obligations or statutory construction rules. A general professional-services template does not cover those issues.

UK copyright guidance distinguishes a contract for services from a contract of service in its discussion of commissioned work. That distinction explains the labels; it does not determine employment status across jurisdictions. For a US federal tax assessment, the IRS looks at behavioral control, financial control and the relationship between the parties. The question is whether the wording reflects how the work is actually performed.

The form should also reflect the party structure. If the client buys work from a contractor business, identify that business and the individual who will perform the services. If an individual signs the agreement while working through a company, settle which entity employs or engages the individual and whether the company is also a party to the agreement. Australian government contractor guidance recommends recording when a contractor needs a subcontractor and including the agreed arrangement in the contract; that is a practical drafting point, not a universal rule.

Check the working relationship and relevant locations

A written agreement cannot create independent status merely by calling the worker a contractor. Your status screen should compare the contract with day-to-day practices such as:

• who directs the work and controls the working methods;
• who sets hours, schedules and working location;
• who provides equipment, systems and other business resources;
• whether the provider can work for other clients and offer services through substitute businesses;
• how fees, expenses and financial risk are arranged;
• whether the arrangement provides for a continuous engagement or work controlled by the client.

These factors need different treatment in different legal systems. In the United States, the IRS asks whether the substance of the relationship demonstrates control and independence for federal employment tax purposes. In Great Britain, GOV.UK says employment status depends on the reality of the working relationship and that the written contract is only one part of the assessment. Neither source supplies a universal test for another country or for every employment-law question.

A large historical study also cautions against using one economic signal as a shortcut. Using digitized US tax records from 2001–2016, Eleanor Wilking found that the median number of payers in 2016 was two for both recorded employees and contractors. These records describe economic proxies rather than adjudicated status, so client count cannot decide whether an individual is a contractor.

Record the relevant locations before choosing the governing-law, dispute and mandatory-clause provisions:

1. the country or state where each party is established;
2. where the contractor regularly performs the work;
3. where the client receives and uses the services or deliverables;
4. where personal data is collected, stored or processed; and
5. where the agreement will be signed and enforced.

The answers may point to several legal systems. US federal tax guidance does not decide employment rights in Great Britain; EU GDPR does not apply to every contractor relationship; and a governing-law clause does not remove mandatory protections in another relevant jurisdiction.

Know when a template needs local review

Seek case-specific legal review before signing when the template could determine a material legal outcome. The clearest warning signs are:

• the client controls the working hours, methods or day-to-day work like an organization managing its own workforce;
• the provider appears to work exclusively for the client, cannot serve other clients and has no genuine business risk;
• the work belongs to a regulated profession, construction project or another sector with mandatory terms;
• the parties are in different countries and the agreement must allocate tax, employment, data, intellectual property or dispute obligations;
• the contractor will process personal data, use subprocessors or transfer data across borders;
• the client requires ownership or an exclusive licence for high-value intellectual property;
• one party is an individual and the other wants broad indemnities, restraint provisions or extensive liability obligations; or
• the engagement involves unusual payment, insurance, liability or termination terms that the template cannot explain.

Set the liability cap, insurance amount, governing law and any cross-border terms for the particular work. The parties’ risks, bargaining position and applicable law affect those choices.

Keep the review request specific. Give the reviewer the proposed relationship, the real working practices, the statement of work, the parties’ locations, the data involved, the intended use of the work product and the risk allocation. A completed draft lets the reviewer test actual terms; a document labeled “independent contractor agreement” does not answer the underlying questions.

Copyable independent contractor agreement template

The following framework is designed for a business commissioning independent professional services. Replace every bracketed field with the agreed fact. Delete optional provisions that do not apply, and flag terms that require professional review because they concern status, mandatory local law, intellectual property, personal data, liability, insurance or cross-border enforcement.

Parties, effective date and term

INDEPENDENT CONTRACTOR AGREEMENT

This Independent Contractor Agreement (the “Agreement”) is entered into on [effective date] by and between:

[Client legal name], of [registered address], represented by [name and title] (the “Client”); and

[Contractor legal name], of [registered address], represented by [name and title] (the “Contractor”).

The Client and the Contractor may each be a “Party” and together the “Parties.”

1. Relationship and services

The Contractor will provide the professional services described in Section 2 and any statement of work attached as Exhibit A (the “Services”). The Contractor has sole responsibility for determining the manner and means of performing the Services, subject to the agreed deliverables, deadlines, access requirements and acceptance criteria.

The Parties intend an independent-contractor relationship. Nothing in this Agreement creates an employment relationship. [Review this provision where the actual working practices, status rules or mandatory law make status uncertain.]

2. Effective date and term

This Agreement begins on [effective date] and continues until [end date or completion of the Services], unless ended earlier under Sections 22–25. Work performed before the effective date is governed by [prior written agreement or state that no prior agreement applies].

Services, deliverables and statement of work

3. Scope of services

The Contractor will perform:

• [Services or work packages]
• [Deliverables and formats]
• [Milestones and target dates]
• [Location or working mode]
• [Named client contact]

The Contractor will perform the Services with reasonable skill and care and in accordance with the specifications in Exhibit A.

4. Statement of work

The Parties will attach a statement of work to this Agreement. It must identify:

• the agreed work and results;
• deliverables and exclusions;
• the client’s dependencies and responsibilities;
• review and acceptance criteria;
• the person authorized to accept each deliverable;
• the number of included revision rounds;
• milestones, fees and invoice triggers;
• agreed assumptions that materially affect the scope and any assumptions approved in writing by both Parties;
• any work required from a subcontractor; and
• the process for approving changes.

Exhibit A — Statement of work

Deliverable or milestone	Included work and exclusions	Due date and acceptance evidence	Included revisions	Approved change
[Deliverable 1]	Included: [work]; excluded: [work]	Due: [date]; accepted on: [observable criterion and approver]	[Number or none]	[Written approval method]
[Deliverable 2]	Included: [work]; excluded: [work]	Due: [date]; accepted on: [observable criterion and approver]	[Number or none]	[Written approval method]

5. Order of documents

The body of this Agreement and Exhibits A, B and C form part of this Agreement. If their terms conflict, [state which provision or exhibit takes priority for each conflict].

Fees, expenses and invoicing

6. Fees

The Client will pay the Contractor:

• [fixed fee for specified work];
• [hourly, daily or unit rate] at [rate]; or
• [milestone amounts] as set out in Exhibit A.

The fee includes [included expenses, equipment, tools and services]. The Parties will state any taxes that apply and will not assign a tax treatment that the applicable law does not support.

7. Invoice procedure

The Contractor will invoice:

• [on signature of this Agreement];
• [on completion of each milestone];
• [on written acceptance of each deliverable];
• [on the dates set out in Exhibit A]; or
• [other agreed trigger].

Each invoice will identify [invoice reference, services performed or milestone achieved, amount, currency, tax information and payment details required by the Parties]. The Client will pay an undisputed amount within [payment period] after receiving a valid invoice.

8. Expenses

The Contractor will not incur an expense for reimbursement unless it falls within [approved categories], follows [approval threshold and procedure, if applicable] and has the required supporting record. Pre-approved expenses will be reimbursed within [payment period] in accordance with Section 7.

9. Disputed amounts

The Client will notify the Contractor of a disputed amount within [dispute-notice period] and identify the reasonable basis for the dispute. The Parties will work in good faith to resolve it. A dispute does not require either Party to waive its legal rights or prevent the Parties from performing undisputed parts of the Agreement. [Review this provision against the Parties’ intended process and applicable law.]

Work product and pre-existing materials

10. Work product

“Work Product” means the deliverables and other materials specifically identified as created for the Client under this Agreement, excluding the Contractor’s Pre-existing Materials and third-party materials listed in Exhibit B.

The Parties intend the Client to [own the Work Product outright / receive the licence described in Exhibit C], effective [assignment date, delivery date, payment date, or another agreed event].

The Contractor will identify the creator of each Work Product item. The Parties will use [an assignment instrument / a written licence] and record any restrictions needed for the intended use.

[Review jurisdiction-specific ownership and transfer wording. U.S. work-made-for-hire treatment is conditional, and a written copyright transfer follows separate requirements. UK commissioned-work ownership also depends on the applicable rule and the parties’ written agreement.]

11. Pre-existing materials

“Pre-existing Materials” means materials owned, controlled or developed by the Contractor outside the Services and identified in Exhibit B, including relevant [templates, code, tools, libraries, methods or know-how].

The Contractor retains ownership of its Pre-existing Materials. The Contractor grants the Client a [territory], [term], [revocable or irrevocable], [transferable or non-transferable], [royalty-free or fee-bearing] licence to use the Pre-existing Materials incorporated into or required to use, modify, maintain or exploit the Work Product.

12. Third-party and open-source materials

The Contractor will identify material third-party or open-source inputs incorporated into the Work Product and disclose their applicable terms in Exhibit B. The Contractor will not incorporate third-party material that obligates the Client to disclose proprietary information or distribute source code unless the Parties approve that condition in writing.

13. Further assurance

At the Client’s reasonable request, the Contractor will execute documents needed to confirm the agreed rights in the Work Product. Any additional fee for work outside the agreed scope will be handled under the fee provisions in Section 6 and the written change procedure in Section 20. [Review this provision against the selected rights mechanism and applicable formalities.]

Confidentiality and personal data

14. Confidential information

“Confidential Information” means information disclosed by or for the Client that is marked confidential or that a reasonable person would understand to be confidential given its nature and the circumstances of disclosure. It includes [client information, product plans, source material, credentials and customer or personal data].

The Contractor will use Confidential Information only to perform the Services, protect it from unauthorized use or disclosure and disclose it only to personnel who need it for the Services and are bound by equivalent confidentiality duties. The Contractor will notify the Client without undue delay after discovering an unauthorized access or disclosure.

Confidentiality does not apply to information that the Contractor can document [was lawfully known without restriction, became public without breach, was received lawfully from another source, or is independently developed without use of Confidential Information].

The Contractor will return or delete Confidential Information at the Client’s request or when the Services end, subject to [required legal retention and any separate data-processing obligations]. Confidentiality, data duties, rights and other provisions that by their nature should survive termination will survive under Section 25.

15. Personal data and security

If the Contractor processes personal data on the Client’s behalf, it will follow the Client’s documented instructions, except where applicable law requires otherwise. The Parties will document, where applicable:

• the personal data and processing activities;
• the purpose and duration of processing;
• the applicable technical and organizational measures;
• assistance with security, data-subject requests and regulatory obligations;
• incident notification and cooperation;
• deletion or return at the end of the services; and
• any permitted subcontractor or subprocessor.

[If the Contractor processes personal data for the Client and EU GDPR applies, attach the appropriate controller–processor terms. A separate data-processing agreement may be required where the Parties act in that legal capacity. Do not treat this confidentiality clause as a substitute for those terms.]

If the Contractor will appoint a subprocessor, the Contractor will obtain the Client’s prior written authorization where required and ensure that the subprocessor is bound by protective terms. The Parties will verify whether any international-transfer terms are needed for the actual data and locations.

Liability, insurance and delegation

16. Warranties and responsibility for the work

The Contractor warrants that:

• it will perform the Services with reasonable skill and care;
• the deliverables will materially conform to the agreed acceptance criteria;
• it has authority to enter into this Agreement and perform the Services; and
• it will not knowingly include malicious code or knowingly misappropriate third-party rights in the Work Product.

The Contractor is responsible for correcting work that does not materially conform to the agreed acceptance criteria within [remedy period]. The Parties will state separately how the remedy applies to excluded work, new requirements and requests outside the included revision rounds.

[Complete any additional warranty only after checking the work, the law and the Parties’ risk.]

17. Liability and indemnities

The Party responsible for a breach or loss bears responsibility to the extent stated by applicable law and this Agreement. The Parties will agree the following terms for the engagement:

• liability cap: [amount, formula or exclusion subject to review];
• carve-outs: [categories of liability that will not be limited];
• indemnity: [conduct covered, third-party claims covered, procedure, defence control and settlement terms];
• excluded loss: [agreed exclusions and their scope];
• mitigation: [duty to reduce reasonably foreseeable loss].

The Parties will confirm that the allocation reflects the work, the control each Party exercises, the available insurance and any mandatory law. [Do not insert a universal cap or coverage amount without case-specific review.]

18. Insurance

The Contractor will maintain insurance appropriate to the Services and its obligations under this Agreement, including [types of coverage], with limits of [amounts or basis], where commercially available and appropriate. Before the Services begin, the Contractor will provide [certificate, evidence or other confirmation] on reasonable request.

The Parties will align the insurance with the contractual risks. A coverage amount that does not correspond to the work or the agreed liability allocation does not resolve the underlying exposure. [Confirm the required types and limits for this engagement.]

19. Delegation and subcontractors

The Contractor may subcontract [parts of the Services] only with the Client’s [prior written consent / consent not to be unreasonably withheld]. The Contractor remains responsible for its subcontractors’ performance, confidentiality, security, data duties and compliance with this Agreement.

Before engaging a subcontractor, the Contractor will provide the information required to verify [subcontractor identity, relevant competence, insurance, data-processing arrangements and rights in the Work Product]. The Contractor will bind each subcontractor to confidentiality, data, intellectual property, security and audit obligations appropriate to the work.

The Contractor may not substitute another person or business without [approval procedure]. Any approval does not release the Contractor from responsibility for the Services.

Changes, termination and signatures

20. Changes and variations

A change to the agreed outcomes, scope, deliverables, timeline, price or other contract term takes effect only when both Parties approve it in writing. The approval will identify:

• the requested change;
• its effect on scope, cost and timing;
• the revised deliverable, fee or milestone;
• the date the change takes effect; and
• whether it replaces or supplements an earlier instruction.

The Parties will attach the signed variation or written correspondence to this Agreement. Urgent instructions do not expand the scope or fee unless confirmed through the agreed change procedure.

21. Suspension

The Client may instruct the Contractor to suspend part or all of the Services if the Client reasonably considers that continued performance presents a material operational, security, legal or reputational risk. The Parties will agree in writing how the suspension affects fees, deadlines, access, responsibilities and resumption. [Review any statutory or contractual suspension rights in the relevant jurisdiction.]

22. Termination for cause

Either Party may terminate this Agreement for material breach if the breaching Party does not remedy that breach within [cure period] after receiving written notice. Immediate termination applies only to the situations expressly stated in this Agreement or permitted by applicable law.

23. Termination for convenience

[Either Party / The Client / The Contractor] may terminate this Agreement for convenience by giving [notice period]’s written notice. On termination, the Client will pay for [accepted work and other amounts specified in this Agreement], subject to the Parties resolving any disputed amount.

24. Handover and unfinished work

On expiry or termination, the Contractor will:

• deliver work completed or in progress at the Client’s reasonable request;
• identify incomplete items and outstanding dependencies;
• provide agreed handover materials;
• account for amounts paid for undelivered work where applicable;
• return or delete Confidential Information and personal data; and
• provide reasonable cooperation needed to transition the Services.

[Specify the handover period, format, costs and the treatment of partial work.]

25. Post-termination duties

The Parties will specify the treatment of:

• accrued fees and invoices;
• expenses;
• rights in paid-for Work Product;
• confidentiality and personal data;
• warranties and indemnities;
• records and return or deletion; and
• dispute resolution.

Provisions that by their nature should continue after termination will survive. [Review duration and survival language for the specific engagement.]

26. Independent contractor and compliance

The Contractor controls how the Services are performed and is responsible for the contractor’s personnel, taxes and legal obligations arising from that performance, subject to the Parties’ agreement and applicable law. Nothing in this Agreement requires the Contractor to act as the Client’s agent or to make a statement on the Client’s behalf.

27. Notices

Notices will be sent to the addresses in the signature block or the latest address notified in writing. A notice is effective according to [agreed rule]. The Parties may also agree that project records and change approvals will be exchanged through [specified system or address].

28. Governing law and disputes

This Agreement is governed by the laws of [jurisdiction], without making that choice applicable to any mandatory law that applies to the work or parties notwithstanding the clause. Courts in [venue] have jurisdiction, subject to any mandatory jurisdiction that cannot be excluded.

The Parties will first attempt to resolve a dispute through [escalation process and period]. Nothing in this section prevents either Party from seeking urgent relief or using another remedy available under applicable law.

29. Entire agreement and assignment

This Agreement, including its exhibits, contains the agreed terms for the Services. A change must be recorded under Section 20. Neither Party may assign the Agreement or delegate its duties without the other Party’s written consent, except where the agreed delegation provision applies.

30. Severability and waiver

If a provision is unenforceable, the Parties will replace it with an enforceable provision that most closely reflects its intended commercial effect, to the extent permitted by law. A failure to enforce a provision once does not waive it.

31. Counterparts and electronic signatures

The Parties may sign this Agreement and its exhibits in counterparts. They may use electronic signatures where the applicable law recognizes that method and any document-specific formalities are satisfied. The Parties will retain the completed executed version together with its exhibits. [Review the execution method and formalities in the governing jurisdiction.]

SIGNATURES

For the Client	For the Contractor
Legal name: [Client legal name]	Legal name: [Contractor legal name]
Name: [signatory name]	Name: [signatory name]
Title: [signatory title]	Title: [signatory title]
Authority confirmed: [Yes/Not applicable and basis]	Authority confirmed: [Yes/Not applicable and basis]
Signature: [signature]	Signature: [signature]
Date: [date]	Date: [date]

Exhibit B — Pre-existing, third-party and open-source materials

Material	Owner or source	Component affected	Licence or restriction	Evidence held
[Material]	[Owner or source]	[Deliverable or use]	[Terms or restriction]	[Link, file or other record]

Exhibit C — Licence details

• Licensor: [Contractor or other owner]
• Licensee: [Client]
• Pre-existing or third-party materials covered: [description]
• Permitted purpose: [purpose]
• Territory: [territory]
• Term: [duration]
• Transferability: [transfer terms]
• Attribution or display obligation: [requirements]
• Other restrictions: [restrictions]

Turn the scope into an acceptance and payment record

A contract becomes operational when each deliverable has an observable completion standard, a named approver, a place in the project timetable and a defined billing trigger. The statement of work should carry that chain. Otherwise, the agreement may contain a scope clause and an invoice clause while leaving both parties to infer when the work is complete and payable.

Use the worksheet below for each material output. It is a practical project-record design informed by Australian government guidance, not a universal legal requirement.

Deliverables, exclusions and revision rounds

Describe what the contractor will deliver and what the client can reasonably expect to receive. A useful deliverable is identifiable and measurable: a named file, system, report, campaign, component, decision or other stated result.

Australian Government guidance for contractors recommends describing the work or results. Applied to a professional-services engagement, that means writing the expected outcome rather than relying on broad labels such as “support,” “creative services” or “technical assistance.” Give each deliverable its own row so that the acceptance and invoice records can point to the same item.

Record exclusions as carefully as included work. The contractor may provide [number] rounds of revisions for each deliverable within [revision period]. A revision corrects work against the agreed acceptance criteria. It does not include [new deliverables, new concepts, changed requirements, additional formats, third-party procurement or other excluded work].

So state in your contract how many rounds of revisions, if any, are included in your fee.

— Vinay Jain, attorney and former freelance writer

State the price or approval route for work outside that allowance. The parties can agree a fixed additional fee, a time-based rate or another mechanism before the work starts. That protects the working relationship from a dispute over whether a request is another revision or a change in scope.

Acceptance criteria, milestones and change approval

An acceptance criterion must produce an observable answer. “Satisfactory” or “of professional quality” does not tell either party how the client decides. Use criteria that identify the required outcome, the evidence and the approver.

For each milestone, state:

• the result or event that completes it;
• the evidence the contractor must submit;
• who reviews it;
• the review period;
• how the client gives written acceptance;
• what happens when the client requests changes; and
• the agreed fee or invoice trigger.

Australian government guidance links milestone payments with the amount, due date, result and what counts as acceptable work. That supports the worksheet’s operational chain, but its legal guidance applies to Australia. Your agreement should use criteria suited to the actual service and jurisdiction.

A workable acceptance sequence is:

1. The contractor submits the named deliverable with supporting evidence.
2. The named client approver reviews it against the recorded criteria.
3. The approver accepts it in writing or identifies specific changes.
4. The contractor completes an included revision or the Parties approve a change.
5. Acceptance or another agreed event triggers the relevant invoice.
6. The Parties retain the submission, response and approval with the project record.

Do not make acceptance depend on an unspecified internal process if the commercial terms depend on it. Name the approver, define the review period and record what happens if the client does not respond. If the client may reject the work, state the basis for rejection and the correction process.

A scope change requires the same discipline as the original scope. The Parties should document the requested change, its effect on deliverables, price and timing, and the approval before the changed work begins. Australian guidance suggests recording changes to outcomes, timelines, pricing and terms, then attaching the signed variation or corresponding correspondence to the existing contract.

Fee structure, invoice triggers and disputed work

Choose the fee structure that matches the work you can define and administer.

• Fixed fee: use when the deliverables and revision allowance are clear. Record the total fee, included work, revision rounds, expense treatment and invoice milestones.
• Time-based fee: use when the work requires variable effort. State the rate, the units, the time required to complete the work, reporting expectations and the maximum or estimated amount where appropriate.
• Milestone fee: use when the project has identifiable stages. Link each amount to a named result, acceptance criterion and approved invoice trigger.
• Combination: use fixed fees for defined outputs and time-based fees for separately approved work. State how the two parts appear on the invoice and what approval each requires.

The invoice clause should answer four questions:

1. Does the contractor need to issue an invoice?
2. What event permits an invoice: signature, milestone completion, written acceptance or a fixed date?
3. What information must the invoice contain?
4. When is an undisputed amount due?

Australian guidance recommends stating whether an invoice is required, when payment is due and what the invoice should include, including the service performed or milestone achieved. Use the same trigger in the agreement, statement of work and invoice record.

Keep the acceptance record attached to the invoice evidence. A milestone invoice should identify the milestone, the approval reference and the amount due. If the Parties permit invoicing before final acceptance, state that sequence and explain what event supports the invoice.

Disputes need a bounded process. Set a period for the client to notify the Contractor of a disputed amount, require a reasonable explanation and specify that undisputed amounts remain payable according to the agreement. State whether work continues while the Parties resolve the amount and how any resulting change to scope, price or timing must be approved.

Record the agreed terms and completion evidence for each deliverable:

Deliverable or milestone	Exclusions and revision rounds	Acceptance criterion, approver and review period	Fee or invoice trigger	Change record and completion evidence
[Deliverable]	[Excluded work; included revisions]	Criterion: [observable result]; approver: [name, role]; review: [period]	[Fee, amount and trigger]	Change: [reference and approval date]; completion: [file, approval or report]
[Milestone]	[Excluded work; included revisions]	Criterion: [observable result]; approver: [name, role]; review: [period]	[Fee, amount and trigger]	Change: [reference and approval date]; completion: [file, approval or report]
[Milestone]	[Excluded work; included revisions]	Criterion: [observable result]; approver: [name, role]; review: [period]	[Fee, amount and trigger]	Change: [reference and approval date]; completion: [file, approval or report]
[Deliverable]	[Excluded work; included revisions]	Criterion: [observable result]; approver: [name, role]; review: [period]	[Fee, amount and trigger]	Change: [reference and approval date]; completion: [file, approval or report]

Keep the table with the contract. When a payment is questioned, you can reconstruct the deliverable, its revision allowance, the acceptance evidence, the approval, the invoice trigger and every approved change without relying on memory or scattered messages.

Confirm the rights and access chain

Before relying on contractor work, trace each item from its creator to the client’s intended use. The contract must identify whether the client receives ownership or a licence, which pre-existing and third-party materials are involved, and whether a subcontractor or other contributor can grant the promised rights. If the contractor handles personal data, a separate data-role check is needed because confidentiality language does not establish every processor duty.

Ownership, licence and third-party inputs

Start with an inventory of the work:

Asset or work item	Creator and material type	Third-party or open-source inputs	Intended client use and rights instrument	Evidence held
[Deliverable]	Creator: [creator]; type: [new work or pre-existing material]	[Inputs or none]	Use: [use]; rights: [assignment or licence]	[Signed instrument or other record]
[Deliverable]	Creator: [creator]; type: [new work or pre-existing material]	[Inputs or none]	Use: [use]; rights: [assignment or licence]	[Signed instrument or other record]
[Existing component]	Owner: [owner]; type: [pre-existing material]	[Inputs or none]	Use: [use]; rights: [licence terms]	[Schedule, licence or other record]

Do not use one rights clause to cover every category. A new deliverable created specifically for the client, a reusable contractor template, a third-party library and a subcontractor’s contribution may require different instruments.

The correct choice depends on the client’s intended use and the applicable jurisdiction:

• Ownership or assignment transfers the relevant rights to the client. The agreement should identify the rights, assets, effective date and any agreed exceptions.
• A licence gives the client permission to use material that the contractor or another owner keeps. It should define the permitted purpose, territory, duration, transferability, attribution and material restrictions.
• A work-made-for-hire clause has conditional meaning in the United States. A specially commissioned or commissioned work qualifies only if it falls within an eligible statutory category and the parties meet the written-agreement, express-statement and signature requirements. If a work fails any requirement, it is not a work made for hire.
• A separate written transfer is another US route. Under section 204(a) of the US Copyright Act, a transfer of copyright ownership, other than by operation of law, requires a written instrument or memorandum signed by the owner of the conveyed rights or an authorized agent.
• UK commissioned work follows a different starting point. The UK Intellectual Property Office states that the creator is the first legal owner unless the Parties agree otherwise in writing. A contractor operating under a contract for services usually retains copyright unless the Parties agree otherwise. An implied licence may be found in some circumstances, but it does not necessarily transfer ownership.

These rules answer different legal questions and must stay jurisdiction-specific. US work-made-for-hire treatment does not establish the ownership rule for UK work, and the UK creator-first rule does not set a global default.

Third-party inputs need their own record. List open-source software, stock assets, fonts, templates, plugins, reference material and content supplied by another party. Record the applicable licence or permission and any attribution, redistribution, confidentiality or source-disclosure condition. If the intended commercial use conflicts with those terms, the client needs a different licence or a different component.

Confidentiality versus data-processing terms

Confidentiality and personal-data processing answer different questions.

Confidentiality limits how the contractor may use or disclose the Client’s confidential information. It can cover commercial plans, credentials, source material and other information that is marked confidential or should reasonably be understood as confidential.

Data processing concerns personal data processed for the Client. The first question is whether the contractor acts as a controller or processor in the actual arrangement. A processor handles personal data on behalf of a controller and acts under the controller’s instructions. Receiving information does not by itself establish that role.

EU GDPR does not apply to every engagement merely because a contractor handles data. Its territorial scope depends on matters such as an EU or EEA establishment, offering products or services to people in the EEA, monitoring their behaviour, and certain cases involving a non-EEA processor. The contractor’s location alone does not settle the issue.

Where EU GDPR applies and the Parties have a controller–processor relationship, the contract must document the processing operations and means of processing. The Parties also need appropriate terms covering instructions, security, assistance, deletion or return, and information needed for audits. The EDPB identifies these as processor responsibilities beyond confidentiality.

Use a separate data-processing agreement when the relationship and applicable law require it. Attach the processing details rather than hiding them in a general confidentiality clause:

• the subject matter, duration, nature and purpose of processing;
• the personal-data categories and data subjects;
• the Client’s documented instructions;
• the required security measures;
• assistance with data-subject requests and regulatory compliance;
• incident-notification duties and cooperation;
• end-of-service deletion or return;
• audit information and assistance; and
• authorized subprocessors.

If the Contractor appoints a subprocessor, the EDPB guidance requires the controller’s prior written authorization. The processor must also draw up a binding contract giving the subprocessor protection equivalent to the processor’s own obligations. The general agreement should not authorize a subprocessor through an undefined phrase such as “approved suppliers.”

This gate also applies to non-personal information that still creates access obligations. System credentials, client repositories, production data and confidential product plans may require technical and organizational controls even when a separate controller–processor agreement is unnecessary.

Subcontractors, substitution and flow-down duties

Identify who may perform the Services. The agreement should state whether the Contractor may:

• appoint subcontractors for all or specified work;
• replace a named individual with another person or business;
• perform any part of the Services through an affiliate or another service provider;
• use a substitute without prior notice; or
• continue using the same subcontractor for the full engagement.

If approval is required, name the approver and response period. A clause that permits subcontracting without stating the limits leaves the client without a clear record of who performs the work.

Australian Government contractor guidance recommends discussing subcontractor use with the hirer and including the arrangement in the contract. It does not prescribe a universal approval threshold or status outcome.

Apply flow-down obligations to every subcontractor that will receive Confidential Information, access the client’s systems or create part of the Work Product. At minimum, the downstream terms should cover the work, confidentiality, data protection, security, intellectual property, records and audit cooperation. The Contractor remains responsible for the subcontractor’s performance and compliance with the agreement.

Check the rights chain at the same time. The Contractor cannot grant rights it does not control. Require the Contractor to obtain the necessary assignment or licence from each subcontractor and provide evidence on request. For third-party or open-source components, the downstream record should identify the source and its terms.

Substitution language also belongs in the status assessment. If the client directs the substitute’s hours, methods and performance while treating the substitute as part of its own operation, the wording may not match the working practices. The client should not use a right to substitute as a substitute for reviewing how the relationship operates.

Before signing, collect:

• the approved subcontractor or substitute;
• the work assigned to that party;
• the relevant flow-down terms;
• evidence of confidentiality and data-processing obligations;
• the rights granted for the assigned output;
• any third-party component record; and
• the Contractor’s continuing responsibility for that work.

If the contractor plans to use a subcontractor but will not identify the party or obtain the rights it needs, resolve that gap before the work begins. A permission clause cannot repair a missing creator, permission or downstream obligation.

Allocate risk and plan the exit

A contractor agreement should allocate each risk to the party that can manage it and make the exit operational. The work, the amount of control, the parties’ bargaining position and the applicable law determine the appropriate warranties, liability limits, indemnities, insurance requirements and termination terms. No universal liability cap or coverage amount fits every engagement.

Warranties, liability, indemnities and insurance

Start with the contractor’s obligations. A professional-services agreement commonly addresses performance, conformity with the agreed criteria, authority to perform the Services, compliance with specified laws and policies, and freedom from malicious code in delivered work. Keep each warranty tied to something the Contractor can control. For example:

• The Contractor will perform the Services with reasonable skill and care.
• The Contractor will materially conform each deliverable to the acceptance criteria in the statement of work.
• The Contractor has the authority to enter into the Agreement and perform the Services.
• The Contractor will comply with the client policies attached to the Agreement.
• The Contractor will correct work that materially fails to conform to the agreed criteria within the stated remedy period.
• The Contractor will not include malicious code in the Work Product.

Do not copy a broad warranty about every result if the deliverable remains subject to the acceptance process. Define the standard, review period and correction remedy. Excluded work, new requirements and additional revision rounds should remain outside the original warranty unless the Parties agree otherwise.

Liability determines which losses a party bears and whether the amount is limited. Review these points separately:

• the acts, omissions and breaches that create liability;
• direct losses covered by the allocation;
• indirect or consequential losses excluded;
• agreed caps, if any;
• whether the cap applies per event, per claim or across the agreement;
• carve-outs for matters that cannot lawfully be limited;
• mitigation and causation requirements; and
• the effect of the cap on indemnities, insurance and remedies.

A limit should reflect the value and criticality of the work, the control each party exercises, available insurance and the remedies actually available under applicable law. An uncapped obligation may be appropriate for one risk and disproportionate for another.

An indemnity should identify the loss or claim it covers rather than use a general label. State:

• the third-party claims covered;
• the losses covered, if any, outside the third-party claim;
• the conduct that triggers the indemnity;
• notice, defence-control and settlement procedures;
• mitigation obligations; and
• whether the obligation is subject to the liability cap.

Avoid indemnities for the contractor’s own breach without a clear allocation. The client may already have a direct claim for losses caused by non-performance. An indemnity is more useful when it allocates the cost of a defined third-party claim and preserves the indemnified party’s control of its defence.

Insurance should correspond to the risks that the contractor has agreed to bear. Australian government contractor guidance identifies insurance obligations as a drafting point and advises checking that coverage matches contractual liability. It does not establish a coverage amount that fits every engagement.

Complete the insurance clause against the actual work:

Risk or activity	Required insurance or evidence	Limit or basis	Evidence and timing
[Professional service]	[Coverage type]	[Amount or agreed basis]	[Certificate or other evidence before start]
[Client systems or data access]	[Cyber coverage or security terms]	[Amount or agreed basis]	[Timing]
[Physical or other work, if relevant]	[Coverage type]	[Amount or agreed basis]	[Timing]
[Subcontractor work]	[Evidence of equivalent coverage]	[Amount or agreed basis]	[Before subcontracting or on request]

Confirm that the Contractor carries the types of coverage appropriate to the Services, that the limits correspond to the agreed liability and that the certificate remains current during the engagement. If the Client requires evidence of coverage, state when it must be provided and what happens if the coverage is withdrawn or expires.

Exclusivity, policies and dispute process

Exclusivity should be limited to the time, territory, services and type of work that the Parties actually intend to restrict. “The Contractor will not work with anyone else” can interfere with the contractor’s ability to operate its business and may create enforceability questions in the relevant jurisdiction.

A more precise provision may say that, during [period] and within [territory or market], the Contractor will not provide [specified competing services] to [defined clients or market] while performing the Services. If the Client needs confidentiality, non-solicitation or a more limited restriction, address that need in a separate clause reviewed for the applicable jurisdiction. Do not treat an exclusive arrangement as a substitute for confidentiality.

Policies should be limited to those that affect the work and should be attached or identified clearly enough for the Contractor to comply. A generic requirement to follow “all client policies” may incorporate rules that the Contractor cannot obtain, understand or reasonably perform. List the relevant policies and specify:

• which policies apply to the Services;
• where each policy is available;
• the person who can answer questions;
• whether a material policy change requires a written variation; and
• what happens if a policy conflicts with the Agreement.

Policies should not rewrite the commercial bargain without the Parties’ approval. If a new policy changes deliverables, fees, timing or risk, apply the change procedure and document the adjustment.

A dispute process should move from a practical resolution step to the appropriate legal remedy. Begin with a defined escalation route:

1. The project contacts attempt to resolve the issue within [period].
2. If the issue remains unresolved, the Parties’ [representatives] discuss it within [period].
3. The Parties follow [mediation, adjudication or other agreed procedure], if applicable.
4. Each Party retains the right to seek urgent relief or use another remedy available under law.

State what happens while a dispute continues. The Parties may agree that undisputed work continues, that new work is paused or that a particular deliverable is treated as provisional. Avoid wording that makes continued performance a waiver of the dispute.

The governing-law and forum clause should identify the chosen law and any agreed dispute forum without implying that either choice overrides mandatory rules in another relevant location. The agreement should also address whether costs, fees and confidential information produced during the dispute process are treated as confidential.

Renewal, termination and unfinished work

Define renewal so it cannot occur by accident. The agreement may continue for an initial term and renew only if both Parties agree in writing before the end date. For recurring work, state whether the Parties will sign a new agreement or extend the existing one.

A renewal decision depends on several practical questions:

• Is the work still required, and does the original scope still fit?
• Have the fee, deliverables, acceptance criteria and relevant rights changed?
• Have the data, access or security conditions changed?
• Is the Contractor still the right provider, and are any substitutes approved?
• Do the termination, renewal and notice dates remain workable?

Set the notice period and identify the address or project record where notice must be sent. A renewal clause should state whether notice must be given, accepted or confirmed; otherwise an informal message can create uncertainty over whether work will continue.

For termination, identify:

• the agreed termination grounds;
• the notice period for termination for convenience;
• the cure period for material breach, where applicable;
• immediate termination circumstances;
• the method for delivering notice; and
• what the Contractor must do after notice.

Australian government guidance identifies situations for early termination, notice, the amount payable on exit and the survival of duties such as confidentiality and intellectual property as drafting points. The guidance does not establish a global termination rule.

Payment on exit should distinguish completed and accepted work from work in progress. State how the Client will pay for:

• accepted deliverables;
• partly completed work the Client elects to retain;
• approved non-cancellable costs;
• fees earned up to termination;
• unused advance amounts;
• disputed amounts; and
• Contractor expenses already incurred.

Agree a method for valuing partial work in the contract, such as a documented proportion of the relevant milestone, an agreed hourly rate for approved work, or another method suited to the engagement.

Handover turns termination into a usable process. Require the Contractor to provide:

• completed and in-progress deliverables;
• a list of incomplete items and dependencies;
• relevant work files and documentation;
• credentials or access transfers;
• a handover meeting or call;
• status of outstanding expenses and third-party commitments;
• return or deletion of Confidential Information and personal data; and
• reasonable transition cooperation.

The agreement should also specify what happens to the Work Product, access, records and further cooperation. Define which clauses survive termination and for how long. Confidentiality, accrued payment obligations, rights in paid-for work, recordkeeping, limitation of liability, dispute procedure and indemnities may need survival, but the final duration and wording depend on the agreement and applicable law.

A practical exit record should connect the notice, work delivered, payment decision, handover items and surviving obligations. If either party cannot answer those questions from the contract and its attachments, the exit plan exists only in correspondence.

Sign, store and reuse the agreement

A reusable form becomes an agreement only after the Parties complete it for a specific engagement, approve the version that will be signed and retain the signed version with its schedules and delivery records. The packet should show what was agreed, who accepted the work, which rights were granted and what changed after signature.

Review the completed terms and execution method

Review the draft as one document, including the body, statement of work, rights schedule, data terms and every exhibit. Bracketed fields, unresolved placeholders and conflicting versions make the execution record harder to interpret. Check at least the following:

• the parties’ full legal names, addresses and authority to sign;
• the effective date, term and renewal conditions;
• the actual scope, deliverables, exclusions and revision rounds;
• the acceptance criteria, named approver and invoice triggers;
• the fee, expenses, invoicing procedure and payment period;
• the ownership or licence terms for each material deliverable;
• the treatment of pre-existing and third-party materials;
• whether the Contractor will receive confidential information or process personal data;
• the confidentiality, data-processing, security and subcontractor obligations;
• warranties, liability, indemnities and insurance;
• change approval, termination, handover and survival terms;
• governing law, venue, notices and dispute escalation; and
• the full document version presented for signature.

Ask the business owner who supplied the scope, the person who will accept deliverables, finance, the security or data owner and legal to review the clauses within their responsibility. This prevents the statement of work from promising a workflow that operations cannot operate or the data schedule from describing a relationship the Parties do not actually have.

Use a version identifier that covers the agreement and its exhibits. A label such as “[contractor] — [service] — [client] — v[number] — [date]” is more useful than a generic file name. Remove drafting comments and hidden revisions before execution, but preserve the approved final document as a single readable file.

The signing method must fit the governing law, the document type and the evidence the Parties need later. Under the law of England and Wales, an electronic signature can execute a document when the signer intends to authenticate it and the applicable execution formalities are satisfied. That is a jurisdiction-specific rule. It does not establish that every document may be signed electronically in every country.

Some England and Wales documents require witnessing or a specified signature form. A deed, for example, requires the signature to be made in the physical presence of a witness who attests it even when the signature itself is electronic. Check the exact document and formalities before selecting an execution method.

For an electronic execution, preserve:

• the final document presented to each signer;
• the signer’s identity and authentication record;
• the consent or action evidencing the signer’s intention to authenticate the signature;
• the date and time associated with each signature;
• the completed signature audit trail supplied by the signing service;
• evidence of authority to sign, where relevant; and
• any required witness record.

For a handwritten execution, retain the physically signed original or an accurate executed copy, along with any required witness details. Do not treat a scan, forwarding email or unsigned draft as the executed agreement merely because someone sent it.

Keep a complete signing and delivery packet

The retained packet should connect the legal agreement to the work performed. Australian government guidance supports attaching signed variations or written correspondence documenting agreed changes to the existing contract. The complete inventory below extends that practice into an operational record; it is not a claim that this packet is legally sufficient in every jurisdiction.

Record	What it should show	Where it belongs
Executed agreement	The final terms approved by both Parties	Agreement record
Statement of work	Deliverables, exclusions, acceptance criteria, fees, milestones and invoice triggers	Linked schedule
Executed variations	Approved changes to scope, deliverables, price, timing or terms	Linked variation record
Signature and authority evidence	Identity, authority, authentication record and execution date	Signing record
Deliverable submissions	The item submitted and the version reviewed	Project or delivery record
Acceptance evidence	Reviewer, approval date and criteria met	Project or delivery record
Rights instruments	Assignment, licence, creator information and third-party records	Rights or IP record
Data-processing terms	Processing instructions, roles, security terms and subprocessors	Data or compliance record
Insurance evidence	Coverage type, relevant limits and validity dates	Contractor compliance record
Handover and exit record	Work, access, materials, payment decision and surviving duties	Exit record
Source materials	Pre-existing components, permissions and source records	Rights or IP record

The UK Intellectual Property Office recommends that employers keep records of which people created a work and which contractual agreements applied. Apply the same operational principle to commissioned contractor work: record the creator, the asset, the agreement that governed it and the evidence supporting the intended rights.

Link the records rather than creating disconnected archives. The signed agreement should point to the statement of work; the statement of work should identify the deliverable; the acceptance record should identify the submitted version; and the rights record should identify the creator and instrument. When an auditor, customer, legal reviewer or financial controller asks what was agreed, the team can trace the answer through one chain.

Keep an index with:

• client and contractor legal names;
• engagement name and identifier;
• start and end dates;
• governing law and dispute clause;
• status, version and execution date;
• links to the agreement, statement of work and variations;
• location of acceptance, rights, data and compliance records; and
• retention or disposal status.

Do not store personal data that the agreement does not require you to retain. Apply the organization’s access controls, retention schedule and deletion procedure to the packet. Signing records and Work Product may have different retention needs, so classify and manage them accordingly.

Update the form for each engagement

Reuse the form’s structure when the work is similar, but replace the facts that make the engagement specific. Keep a completed version as the source of the next draft rather than editing the last signed agreement in place.

Create a pre-signature checklist for each engagement:

1. Confirm the relationship and document type. Check the parties, actual working practices, relevant locations and whether the professional-services form fits the engagement.
2. Replace the general scope with a project statement. Name each deliverable, exclusion, revision allowance, dependency and timetable item.
3. Define acceptance before payment. Assign the approver, observable criterion, review period and invoice trigger.
4. Choose the commercial model. Complete the fee structure, expenses, invoicing requirements, payment period and dispute process.
5. Map the rights. Identify the creator, new output, pre-existing materials, third-party components, intended use and the required assignment or licence.
6. Check the data role. Identify the personal data, processing activities, security needs, subprocessors and any separate data-processing terms.
7. Allocate the actual risk. Complete warranties, remedies, liability, indemnity, insurance, policies and exclusivity against the work and applicable law.
8. Plan changes and exit. Complete the change route, renewal, termination grounds, notice, payment on exit, handover and survival.
9. Check execution formalities. Select the signing method, confirm authority and attach the final exhibits.
10. Open the engagement record. Create the packet index before work begins so acceptance, variation, rights and handover records have a defined home.

Keep reusable text for stable definitions and clause structure, but put every negotiated fact in a field that must be completed. Stable items may include the meaning of Confidential Information, the format of the change record and the order of documents. Facts such as the fee, approval period, liability cap, governing law, data role and rights instrument belong in the engagement record because they can change from one project to the next.

Track changes through a revision log:

Version and date	Owner	Change	Approval or authority	Status
Version: [number]; date: [date]	[name]	[scope, fee, rights, data or other change]	[reference]	[draft or executed]

Do not reuse an expired clause by inertia. Recheck the working relationship, locations, governing law, data role, rights chain, insurance and termination plan for every new engagement. A previous signature does not prove that the same terms remain suitable for new work, new people, new assets or a new operating model.

Frequently asked questions

Is a contractor agreement legally binding if it starts from a template?

A template can provide the structure for a binding agreement, but the template alone does not determine whether the particular agreement is legally binding. Validity depends on the applicable law and the circumstances of the transaction.

Under English law, an enforceable contract requires agreement on the parties’ obligations, an intention to create legal relations, consideration, competent parties and lawful terms. Offer and acceptance may be written, oral or implied. Other legal systems have different requirements; consideration is not universal, as Scots law illustrates.

The label “independent contractor” does not settle worker status. For US federal employment tax purposes, the IRS considers the substance of the relationship, including behavioral control, financial control and the relationship between the parties. In Great Britain, the written contract is only one part of the employment-status assessment. A document may describe an independent relationship while the working practices point elsewhere.

Before signing, remove the blanks, check the actual working practices, select the governing law and have a qualified reviewer examine any consequential status, data, intellectual property, liability or cross-border terms.

Can I use the same agreement in another country?

You can reuse the structure, but you should not assume that the completed agreement will work unchanged in another country. At minimum, review:

• the parties’ legal names and places of establishment;
• where the contractor performs the work;
• the law governing employment status and mandatory worker protections;
• personal-data and international-transfer requirements;
• copyright and other intellectual-property ownership and transfer rules;
• tax and invoicing requirements;
• electronic-signature and witnessing formalities; and
• restrictions on exclusivity, liability and dispute resolution.

A governing-law clause does not remove mandatory rules that apply where the work is performed or where the contractor operates. Obtain local professional review when the parties, work, data, assets or enforcement arrangements cross borders.

Is a freelancer agreement different from an independent contractor agreement?

The terms are often used interchangeably, but the document still has to match the actual relationship. A “freelancer agreement” may describe a person working independently for a client, while an “independent contractor agreement” may use the same commercial structure and add more detailed rights, confidentiality, data, insurance and termination terms.

The name carries less weight than the parties, actual practices and applicable law. UK copyright guidance distinguishes a contract for services from a contract of service for particular purposes, but that terminology does not create one global status test. Decide whether the document covers professional services, employment, subcontracting or another arrangement, then tailor its clauses to that structure.

Who owns work created by an independent contractor?

It depends on the jurisdiction, the work, the creator and the agreement. In the United States, specially commissioned work qualifies as a work made for hire only if it falls within an eligible category and the parties meet the required written-agreement and signature conditions. A separate written transfer of copyright ownership must also meet the statutory signature requirements.

In the United Kingdom, the creator is generally the first legal owner of commissioned copyright work unless the Parties agree otherwise in writing. A contractor under a contract for services usually retains copyright unless they agree otherwise. A court may find an implied licence for the commissioned purpose in some cases, but that does not necessarily transfer ownership.

Do not assume that the client automatically owns code, designs, articles, images, templates or other output. Identify the creator, pre-existing materials, third-party components and intended use, then document the required assignment or licence.

Can the parties sign the agreement electronically?

Often, yes, but the answer depends on the applicable law and document. Under the law of England and Wales, an electronic signature can execute a document if the signer intends to authenticate it and the relevant execution formalities are satisfied. Some documents require witnessing or a specified signature form; a deed requires a witness to be physically present when the signature is made.

The Parties should check the governing jurisdiction before choosing the method. Whichever method they use, retain the final document, signature dates, identity and authentication records, authority evidence, exhibits and any required witness documentation.

Sources

• Employee (common-law employee) — Internal Revenue Service.
• Employment status and employment rights: guidance for HR professionals, legal professionals and other groups — GOV.UK.
• Independent Contractors in Law and in Fact: Evidence from U.S. Tax Returns — Eleanor Wilking, Northwestern University Law Review manuscript hosted by Columbia Law.
• Prepare a contract — Australian Government business.gov.au.
• Circular 30: Works Made for Hire — United States Copyright Office.
• Copyright Act of 1976, Chapter 2 — United States Copyright Office.
• Ownership of copyright works — UK Intellectual Property Office.
• Data protection basics: Does the GDPR apply to your organisation? — European Data Protection Board.
• Data controller or data processor — European Data Protection Board.
• Electronic execution of documents — Law Commission of England and Wales.
• National Minimum Wage Manual: Status—formation of an enforceable contract — HM Revenue & Customs.
• 8 Contract Provisions Every Freelancer Should Know — Freelancers Union guest article by Vinay Jain.