A freelance developer explains a document to a new client: "Before we start, I need us to sign a Statement of Work. It defines exactly what I'll deliver, the timeline, my rate, and what's explicitly out of scope. It prevents disagreements later — if you ask for something not in the SOW, we handle it as a change request with an updated price." What is a Statement of Work (SOW)?
Statement of Work (SOW): one of the most important documents in freelancing. It defines what is being built, what isn't being built, when, for how much, and under what conditions. Prevents scope creep and payment disputes. SOW key sections: Scope / Deliverables — explicit list of what will be delivered (screens, features, APIs, documentation). Exclusions — what is NOT included (critical — list common assumptions). Timeline / Milestones — key dates, phases, delivery checkpoints. Price / Payment terms — fixed price, hourly rate, milestone payments, or retainer. Acceptance criteria — how the client will confirm deliverables are done. Change request process — out-of-scope requests trigger a formal change request with new timeline and price. Freelance contract vocabulary: Master Service Agreement (MSA) — a framework contract covering the ongoing relationship (liability, IP, dispute resolution); individual projects are governed by SOWs under the MSA. NDA (Non-Disclosure Agreement) — confidentiality agreement protecting client's business information. IP assignment clause — specifies that IP created during the project transfers to the client upon payment. Intellectual Property (IP) — ownership of code, designs, documents created. Warranty period — after delivery, a defined period (e.g., 30 days) during which the contractor fixes bugs at no extra cost. In conversation: "After two scope-creep projects I learned to put the exclusions list in bold. Now change requests pay for themselves within a week."
2 / 30
A contractor explains their billing model to a potential client: "I work on a milestone-based model: 30% upfront before I start, 40% when I deliver the working prototype, and 30% on final delivery and sign-off. Each payment is triggered by a specific, agreed deliverable — not by time elapsed." What is milestone-based billing and why do contractors prefer it?
Milestone-based billing: payment is released when a specific, agreed deliverable is completed. Structure protects both parties: contractor gets paid progressively (not 100% at end); client pays for tangible, verifiable value. Common milestone structures: 1) Discovery/kickoff payment — upfront; shows client commitment; covers initial research and planning. 2) Mid-project delivery — working prototype, MVP, or first phase. 3) Final delivery + acceptance — completed, tested, documented deliverable with client sign-off. Billing vocabulary: Retainer — a fixed monthly fee for ongoing availability (e.g., 20 hours/month reserved). Predictable for both parties. Time & Materials (T&M) — pay per hour/day; client bears risk of overrun; flexible for evolving scope. Fixed price — one price for the whole project; contractor bears risk; works only with a very well-defined scope. Day rate — a daily billing rate (common in UK contracting). Invoice terms — NET 30 (payment due 30 days after invoice), NET 15, NET 60. Late payment clause — specifies interest or penalties on overdue invoices. Escrow — a third party holds payment until deliverable is accepted; reduces risk for both parties. Kill fee — a percentage payment owed if the client cancels after work has begun. In conversation: "I stopped doing fixed-price contracts without a kill fee — two cancellations after months of work taught me that lesson."
3 / 30
A senior contractor explains a legal concept during a client onboarding call: "The contract has an IP assignment clause — all code, designs, and documentation created under this engagement become your intellectual property upon final payment. Until payment clears, technically I retain ownership. That's standard. It also has a carve-out for my pre-existing open source libraries." What is an IP assignment clause and what is a carve-out?
IP Assignment Clause: a contractual term stating that all intellectual property (code, designs, written content, prototypes) created under the contract belongs to the client, typically upon final payment. This is standard in most freelance and contractor agreements. Carve-out: an explicit exclusion from the IP assignment — typically covering the contractor's pre-existing tools, libraries, frameworks, or reusable components they bring to multiple projects. Freelance IP vocabulary: Work for hire (US) — a doctrine where work created by an employee or under a written agreement automatically belongs to the employer/client. Copyright default (EU/UK) — by default, the creator owns copyright; an explicit assignment clause is needed to transfer it. Moral rights — in some jurisdictions, the creator retains the right to be identified as author, even after IP assignment. Open source license compliance — if the contractor uses GPL-licensed code in client software, the client's code may need to be open source too; always disclose. Portfolio rights — contractors often negotiate the right to mention the project in their portfolio even if the work is confidential. Non-compete clause — a clause preventing the contractor from working for competitors; often unenforceable depending on jurisdiction. Non-solicitation clause — prevents the contractor from poaching the client's employees (and vice versa). In conversation: "I carve out my animation utility library in every contract — I've been building it for 5 years and it would be absurd to license it to each client."
4 / 30
A developer who recently started contracting in the UK asks for advice: "My recruiter mentioned IR35 — apparently HMRC can reclassify me as an employee instead of an independent contractor, which would mean paying much more tax. I need to make sure my working practices reflect genuine independence." What is IR35 and what does it mean for contractors?
IR35: UK tax legislation (officially: the "Intermediaries Legislation", Chapter 8 ITEPA 2003) designed to catch "disguised employment" — contractors who work like employees but are paid through a limited company to avoid employment taxes. Inside IR35: HMRC considers you an employee for tax purposes → you pay income tax + employee NI + employer NI on earnings. Financial impact: contractors typically see 20-25% higher tax burden. Outside IR35: genuinely self-employed; retains tax advantages of contracting. IR35 determination factors: Control — controls their own work schedule and methods (outside) vs client dictates hours and how work is done (inside). Substitution — can send a substitute to do the work (strong outside IR35 indicator). Mutuality of obligation (MOO) — no obligation to accept work or for client to offer it (outside). Financial risk — contractor bears their own business risk (outside). IR35 globally: IR35 (UK) — intermediary legislation. 1099 vs W-2 (US) — independent contractor vs employee; companies face IRS penalties for misclassification. Self-employed vs "bogus self-employment" (EU) — similar concept; labour law in France, Germany, Netherlands scrutinise contractor arrangements. In conversation: "I use multiple clients simultaneously and have a substitution clause in every contract — two things that keep me outside IR35."
5 / 30
An experienced freelancer mentors a junior developer starting their first freelance project: "Before anything, run a conflicts-of-interest check and get an NDA signed. Then scope the project clearly in the SOW, include a change request process, and structure milestones so you're never more than 30 days of work ahead on unpaid work. Get everything in writing — verbal agreements don't protect you." What is an NDA (Non-Disclosure Agreement) and when is it essential for freelancers?
NDA (Non-Disclosure Agreement): a legal contract where one or both parties agree to keep confidential information shared during the engagement secret and not disclose it to third parties. Two types: Unilateral NDA — one party discloses; the other agrees to keep it confidential (most common: client discloses to contractor). Mutual NDA — both parties disclose; both agree to confidentiality. When an NDA is critical: client shares unreleased product roadmaps, access to production systems or customer data, financial data, business strategies, or trade secrets. NDA vocabulary: Confidential information definition — the clause defining what counts as confidential; should be clear. Overly broad NDAs ("everything we ever mention") are sometimes unenforceable. Exclusions — information that's already public, independently developed, or received from a third party isn't covered. Duration — how long the NDA applies (typically 2-5 years after engagement ends). Remedies — penalties for breach; often includes injunctive relief (court order to stop disclosure). Freelance contract checklist: ☑ NDA (before sensitive discussions), ☑ SOW (before work starts), ☑ IP assignment clause, ☑ payment terms, ☑ change request process, ☑ acceptance criteria, ☑ warranty period, ☑ kill fee. In conversation: "The NDA I almost skipped for a 'quick project' turned out to cover their entire pre-IPO roadmap — always get it signed."
6 / 30
Sarah (Senior Developer): "Okay, team, let's discuss the pull request. I've added a new function to handle user authentication – it integrates with our existing OAuth2 provider. I've included detailed comments explaining the logic and error handling. Please review the code thoroughly, paying particular attention to the security aspects and testing coverage."
This scenario illustrates a common practice in software development: a pull request review. The question tests understanding of this process—specifically, the purpose of providing feedback on proposed changes *before* they are implemented. Options A and B are not relevant to the immediate context; option C is the correct answer.
7 / 30
"Mark (Project Manager): 'We need to define Service Level Agreements (SLAs) for this project. For example, we guarantee 99.9% uptime for the API and respond to support tickets within 4 hours. These agreements will be crucial for managing expectations and holding us accountable.'
This question assesses understanding of SLAs – Service Level Agreements. SLAs are specifically defined performance targets and their associated guarantees. Option A is a Statement of Work; option B accurately describes the definition, while options C and D relate to other project management concepts.
8 / 30
"David (Freelancer): 'I'm using a REST API to fetch data from the server. The response is in JSON format, and I've used a library to parse it automatically. I need to handle potential errors like invalid JSON or network timeouts.'
This question focuses on API interaction and error handling. The scenario describes a common task—using a REST API. The correct answer highlights the fundamental process of making HTTP requests to external servers. Options A and B describe related but distinct technologies; option D is related to database queries.
9 / 30
"Emily (Junior Developer): 'My client wants me to build a custom reporting dashboard. They've provided me with a detailed requirements document, but they're asking for features that aren't explicitly outlined – like integrating with a third-party analytics platform. Should I push back on these requests?'
This scenario presents a common challenge for freelancers: 'scope creep' – the gradual expansion of project requirements beyond the original agreement. Option A is a SOW; option B describes an amendment process; and option C accurately reflects the correct approach to managing this situation.
10 / 30
"Ben (Experienced Consultant): 'I've been asked to provide a technical assessment of this new cloud infrastructure. I need to document the architecture, identify potential vulnerabilities, and recommend security best practices.'
This question tests understanding of risk assessment – a crucial skill in IT consulting. The scenario describes a situation where Ben needs to evaluate potential problems with a new infrastructure. Option A and D describe different aspects of system design/performance; option B is the precise definition.
11 / 30
Sarah (Senior Developer): "Okay, team, let's discuss the pull request. I've added a new function to handle user authentication – it integrates with our existing OAuth2 provider. I've included detailed comments explaining the logic and error handling. Please review the code thoroughly, paying particular attention to the security aspects and testing coverage."
This scenario illustrates a common practice in software development: a pull request review. The question tests understanding of this process—specifically, the purpose of providing feedback on proposed changes *before* they are implemented. Options A and B are not relevant to the immediate context; option C is the correct answer.
12 / 30
"Mark (Project Manager): 'We need to define Service Level Agreements (SLAs) for this project. For example, we guarantee 99.9% uptime for the API and respond to support tickets within 4 hours. These agreements will be crucial for managing expectations and holding us accountable.'
This question assesses understanding of SLAs – Service Level Agreements. SLAs are specifically defined performance targets and their associated guarantees. Option A is a Statement of Work; option B accurately describes the definition, while options C and D relate to other project management concepts.
13 / 30
"David (Freelancer): 'I'm using a REST API to fetch data from the server. The response is in JSON format, and I've used a library to parse it automatically. I need to handle potential errors like invalid JSON or network timeouts.'
This question focuses on API interaction and error handling. The scenario describes a common task—using a REST API. The correct answer highlights the fundamental process of making HTTP requests to external servers. Options A and B describe related but distinct technologies; option D is related to database queries.
14 / 30
"Emily (Junior Developer): 'My client wants me to build a custom reporting dashboard. They've provided me with a detailed requirements document, but they're asking for features that aren't explicitly outlined – like integrating with a third-party analytics platform. Should I push back on these requests?'
This scenario presents a common challenge for freelancers: 'scope creep' – the gradual expansion of project requirements beyond the original agreement. Option A is a SOW; option B describes an amendment process; and option C accurately reflects the correct approach to managing this situation.
15 / 30
"Ben (Experienced Consultant): 'I've been asked to provide a technical assessment of this new cloud infrastructure. I need to document the architecture, identify potential vulnerabilities, and recommend security best practices.'
This question tests understanding of risk assessment – a crucial skill in IT consulting. The scenario describes a situation where Ben needs to evaluate potential problems with a new infrastructure. Option A and D describe different aspects of system design/performance; option B is the precise definition.
16 / 30
Sarah (Senior Developer): "Okay, team, let's discuss the pull request. I've added a new function to handle user authentication – it integrates with our existing OAuth2 provider. I've included detailed comments explaining the logic and error handling. Please review the code thoroughly, paying particular attention to the security aspects and testing coverage."
This scenario illustrates a common practice in software development: a pull request review. The question tests understanding of this process—specifically, the purpose of providing feedback on proposed changes *before* they are implemented. Options A and B are not relevant to the immediate context; option C is the correct answer.
17 / 30
"Mark (Project Manager): 'We need to define Service Level Agreements (SLAs) for this project. For example, we guarantee 99.9% uptime for the API and respond to support tickets within 4 hours. These agreements will be crucial for managing expectations and holding us accountable.'
This question assesses understanding of SLAs – Service Level Agreements. SLAs are specifically defined performance targets and their associated guarantees. Option A is a Statement of Work; option B accurately describes the definition, while options C and D relate to other project management concepts.
18 / 30
"David (Freelancer): 'I'm using a REST API to fetch data from the server. The response is in JSON format, and I've used a library to parse it automatically. I need to handle potential errors like invalid JSON or network timeouts.'
This question focuses on API interaction and error handling. The scenario describes a common task—using a REST API. The correct answer highlights the fundamental process of making HTTP requests to external servers. Options A and B describe related but distinct technologies; option D is related to database queries.
19 / 30
"Emily (Junior Developer): 'My client wants me to build a custom reporting dashboard. They've provided me with a detailed requirements document, but they're asking for features that aren't explicitly outlined – like integrating with a third-party analytics platform. Should I push back on these requests?'
This scenario presents a common challenge for freelancers: 'scope creep' – the gradual expansion of project requirements beyond the original agreement. Option A is a SOW; option B describes an amendment process; and option C accurately reflects the correct approach to managing this situation.
20 / 30
"Ben (Experienced Consultant): 'I've been asked to provide a technical assessment of this new cloud infrastructure. I need to document the architecture, identify potential vulnerabilities, and recommend security best practices.'
This question tests understanding of risk assessment – a crucial skill in IT consulting. The scenario describes a situation where Ben needs to evaluate potential problems with a new infrastructure. Option A and D describe different aspects of system design/performance; option B is the precise definition.
21 / 30
Sarah (Senior Developer): "Okay, team, let's discuss the pull request. I've added a new function to handle user authentication – it integrates with our existing OAuth2 provider. I've included detailed comments explaining the logic and error handling. Please review the code thoroughly, paying particular attention to the security aspects and testing coverage."
This scenario illustrates a common practice in software development: a pull request review. The question tests understanding of this process—specifically, the purpose of providing feedback on proposed changes *before* they are implemented. Options A and B are not relevant to the immediate context; option C is the correct answer.
22 / 30
"Mark (Project Manager): 'We need to define Service Level Agreements (SLAs) for this project. For example, we guarantee 99.9% uptime for the API and respond to support tickets within 4 hours. These agreements will be crucial for managing expectations and holding us accountable.'
This question assesses understanding of SLAs – Service Level Agreements. SLAs are specifically defined performance targets and their associated guarantees. Option A is a Statement of Work; option B accurately describes the definition, while options C and D relate to other project management concepts.
23 / 30
"David (Freelancer): 'I'm using a REST API to fetch data from the server. The response is in JSON format, and I've used a library to parse it automatically. I need to handle potential errors like invalid JSON or network timeouts.'
This question focuses on API interaction and error handling. The scenario describes a common task—using a REST API. The correct answer highlights the fundamental process of making HTTP requests to external servers. Options A and B describe related but distinct technologies; option D is related to database queries.
24 / 30
"Emily (Junior Developer): 'My client wants me to build a custom reporting dashboard. They've provided me with a detailed requirements document, but they're asking for features that aren't explicitly outlined – like integrating with a third-party analytics platform. Should I push back on these requests?'
This scenario presents a common challenge for freelancers: 'scope creep' – the gradual expansion of project requirements beyond the original agreement. Option A is a SOW; option B describes an amendment process; and option C accurately reflects the correct approach to managing this situation.
25 / 30
"Ben (Experienced Consultant): 'I've been asked to provide a technical assessment of this new cloud infrastructure. I need to document the architecture, identify potential vulnerabilities, and recommend security best practices.'
This question tests understanding of risk assessment – a crucial skill in IT consulting. The scenario describes a situation where Ben needs to evaluate potential problems with a new infrastructure. Option A and D describe different aspects of system design/performance; option B is the precise definition.
26 / 30
Sarah (Senior Developer): "Okay, team, let's discuss the pull request. I've added a new function to handle user authentication – it integrates with our existing OAuth2 provider. I've included detailed comments explaining the logic and error handling. Please review the code thoroughly, paying particular attention to the security aspects and testing coverage."
This scenario illustrates a common practice in software development: a pull request review. The question tests understanding of this process—specifically, the purpose of providing feedback on proposed changes *before* they are implemented. Options A and B are not relevant to the immediate context; option C is the correct answer.
27 / 30
"Mark (Project Manager): 'We need to define Service Level Agreements (SLAs) for this project. For example, we guarantee 99.9% uptime for the API and respond to support tickets within 4 hours. These agreements will be crucial for managing expectations and holding us accountable.'
This question assesses understanding of SLAs – Service Level Agreements. SLAs are specifically defined performance targets and their associated guarantees. Option A is a Statement of Work; option B accurately describes the definition, while options C and D relate to other project management concepts.
28 / 30
"David (Freelancer): 'I'm using a REST API to fetch data from the server. The response is in JSON format, and I've used a library to parse it automatically. I need to handle potential errors like invalid JSON or network timeouts.'
This question focuses on API interaction and error handling. The scenario describes a common task—using a REST API. The correct answer highlights the fundamental process of making HTTP requests to external servers. Options A and B describe related but distinct technologies; option D is related to database queries.
29 / 30
"Emily (Junior Developer): 'My client wants me to build a custom reporting dashboard. They've provided me with a detailed requirements document, but they're asking for features that aren't explicitly outlined – like integrating with a third-party analytics platform. Should I push back on these requests?'
This scenario presents a common challenge for freelancers: 'scope creep' – the gradual expansion of project requirements beyond the original agreement. Option A is a SOW; option B describes an amendment process; and option C accurately reflects the correct approach to managing this situation.
30 / 30
"Ben (Experienced Consultant): 'I've been asked to provide a technical assessment of this new cloud infrastructure. I need to document the architecture, identify potential vulnerabilities, and recommend security best practices.'
This question tests understanding of risk assessment – a crucial skill in IT consulting. The scenario describes a situation where Ben needs to evaluate potential problems with a new infrastructure. Option A and D describe different aspects of system design/performance; option B is the precise definition.
What does the "Freelance & Contractor Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to freelance & contractor vocabulary through 30 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 30 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.