Contract template for data analysts
Data work runs on the client's information, often including personal data. The contract should say what you can access, where it is stored, who else can see it and what happens to it at the end. Clients increasingly ask this before signing, and having a clear clause ready makes you easier to hire.
The disputes are usually about expectations. A model that predicted well on last year's data does not guarantee next year. A dashboard built on a source the client later changes stops being right. Say plainly that findings depend on the data provided, and that you hand over the code so anyone can rerun and check it.
Not legal advice. This is a plain-language starting point, not a contract drafted for your situation or your country. For anything large or unusual, have a lawyer where you work read it before you sign.
Clauses specific to data analysts
- Data access. The client provides access to the agreed data sources by the agreed date. Delays move the delivery date, and time lost waiting for access is billed at the hourly rate.
- Confidentiality. The analyst keeps the client's data and findings confidential and uses them only for this project. Data is stored on the client's systems or encrypted storage and deleted or returned when the work ends.
- Personal data. Where the data includes personal information, the analyst processes it only on the client's instructions and follows any data processing terms the parties sign.
- Reliance on data. Findings are based on the data the client provides. The analyst is not responsible for errors in source data or for decisions the client makes using the results.
- Handover. On payment, the analyst delivers the queries, notebooks and documentation needed to reproduce the results, and the client owns those deliverables.
- Ad-hoc requests. Questions and reruns outside the agreed deliverables are logged and billed at the hourly rate or against a retainer.
The clauses every freelance contract needs
- Parties. Who the agreement is between: your legal name or business, the client's legal entity, and the addresses of both.
- Scope of work. What you will deliver, in what form, and what is explicitly not included. Refer to the quote or proposal by number if it lists the details.
- Fees and payment terms. The total fee or rate, the currency, any deposit, when invoices are issued and how many days the client has to pay.
- Late payment. What happens when an invoice is late: interest or a fixed fee if you want one, and your right to pause work until the account is settled.
- Changes and revisions. How many revision rounds are included, what counts as a change of scope, and how extra work is priced and approved.
- Timeline and client delays. Key dates, and that deadlines move when the client is late with feedback, content or approvals.
- Ownership and licence. Who owns the finished work and when (usually on full payment), what the client may use it for, and what you keep, such as your tools, templates and know-how.
- Confidentiality. Both sides keep the other's non-public information private, during the project and after it.
- Cancellation. How either side can end the agreement, the notice required, and payment for work done up to that point.
- Liability. A cap on what either side can claim, often the fees paid under the agreement, and no liability for indirect losses.
- Governing law. Which country's law applies and where disputes are heard. Usually where you are based.
A plain-language sample
Copy it, fill in the brackets, and cut what doesn't apply. Shorter is fine as long as the scope, the money and the rights are clear.
1. Parties
This agreement is between [Your name or business], the data analyst ("we"), and [Client legal name], the client ("you"), and starts on [date].
2. The work
We will deliver the work described in quote [number], dated [date]. Anything not listed there is outside this agreement and will be quoted separately before we start on it.
3. Data access
The client provides access to the agreed data sources by the agreed date. Delays move the delivery date, and time lost waiting for access is billed at the hourly rate.
4. Confidentiality
The analyst keeps the client's data and findings confidential and uses them only for this project. Data is stored on the client's systems or encrypted storage and deleted or returned when the work ends.
5. Personal data
Where the data includes personal information, the analyst processes it only on the client's instructions and follows any data processing terms the parties sign.
6. Reliance on data
Findings are based on the data the client provides. The analyst is not responsible for errors in source data or for decisions the client makes using the results.
7. Handover
On payment, the analyst delivers the queries, notebooks and documentation needed to reproduce the results, and the client owns those deliverables.
8. Ad-hoc requests
Questions and reruns outside the agreed deliverables are logged and billed at the hourly rate or against a retainer.
9. Fees and payment
The fee is [amount and currency]. We invoice [a deposit of X on signing and the balance on delivery / monthly in arrears]. Invoices are due within [14] days. If an invoice is more than [14] days late we may pause work until it is paid.
10. Changes
The quote includes [number] rounds of revisions. Further changes, or changes to work you have already approved, are charged at [rate] once you have agreed to the cost in writing.
11. Delays
Dates in the quote assume you send feedback and material on time. If you are late, the dates move by at least the same amount.
12. Confidentiality
We both keep the other's non-public information confidential, during this project and after it ends.
13. Ending the agreement
Either of us can end this agreement with [14] days' written notice. You pay for the work done up to the end date, and anything already paid for is yours to use under the terms above.
14. Liability
Neither of us is liable for indirect or consequential losses. Our total liability under this agreement is limited to the fees you have paid under it.
15. Law
This agreement is governed by the law of [country], and disputes are heard by the courts of [city or country].
Signatures
Data analyst: [name, date]. Client: [name, title, date].
Questions data analysts ask
Do data analysts need a confidentiality agreement?
In practice, yes. Most clients will ask for one, and a contract with a confidentiality and data handling clause covers it without a separate document. It should say where data is stored and what happens to it at the end of the project.
Who owns the analysis code and dashboards?
Usually the client, once paid, since they need to maintain them. You can keep the right to reuse general techniques and your own utility code, as long as no client data or confidential logic goes with it.
Am I liable if the client makes a bad decision based on my analysis?
A contract can limit that by saying the findings depend on the data supplied and that decisions are the client's. It is also worth stating the assumptions and limits inside the report itself.
Get it signed without printing it
OIO has contract templates built in (service agreement, retainer, IP assignment, NDA) that you edit to fit, sign in the Sign app and send as a PDF. The contract sits next to the project and its invoices. Free plan, no card.
Start freeAlso for data analysts: invoice template and quote template. Contract templates for related trades: software developers, business consultants, marketing consultants, SEO consultants. Or browse all contract templates.