A subcontractor may perform part of a service without becoming the customer's direct contracting party. Check whether subcontracting is permitted and whether consent is required. The main supplier should understand which obligations it retains and which protections need to appear in the subcontract.
Match the subcontract to the actual work, including quality, deadlines, confidentiality, intellectual property and data processing. Copying the main agreement word for word may create obligations the subcontractor cannot perform or omit the interface between the two workstreams.
Identify the part of the main obligation being delegated
Describe the subcontracted task, its inputs and the interface with the main supplier's work. A subcontractor delivering code, installation or specialist analysis needs a clear specification and acceptance route. The main supplier should know what it must check before presenting the combined result to the customer.
Review the main contract for consent, notification and restrictions on further subcontracting. The customer's approval of a named subcontractor does not necessarily release the main supplier from its obligations. Conversely, a subcontract should not promise that the subcontractor can make decisions reserved to the main supplier or customer. Keep the chain of responsibility understandable.
Match deadlines and remedies across the two agreements
Allow time for the main supplier to test the work before its own delivery deadline. A subcontract deadline identical to the customer deadline can leave no room for correction. Identify customer dependencies and how late information is communicated down the chain. Each party should know when an issue requires escalation.
Compare warranties, correction periods and liability limits with the exposure the main supplier has accepted. A mismatch may leave the main supplier responsible for losses it cannot recover from the subcontractor. That does not automatically make every obligation suitable to copy word for word. Assess the work, control and commercial balance rather than using back-to-back as a substitute for review.
Secure rights in the actual deliverables
Identify the creator and ownership arrangements for code, designs, reports and other work. Commissioned copyright may remain with the creator unless an appropriate arrangement provides otherwise. [1] The main supplier needs rights sufficient to meet its customer promise, including any assignment, modification or sublicensing requirement.
Ask about background tools, open-source components, stock assets and further contributors. A subcontractor cannot grant unrestricted rights in material it merely licenses. Keep a rights schedule and obtain necessary permissions before delivery. Technical possession of files does not establish the legal right to transfer or exploit every component in the finished product.
Assess data responsibilities separately
Determine whether the subcontractor will access personal data and in what capacity. The ICO's small-organisation guidance is a starting point for understanding the applicable data protection responsibilities. [2] Where a processor or sub-processor arrangement exists, obtain advice on the required contractual terms and authorisation rather than relying solely on a general confidentiality clause.
Identify data locations, access controls, incident reporting and return or deletion arrangements. The main supplier needs enough information to meet its own customer obligations. Do not promise immediate deletion of every backup without checking the actual systems and legitimate retention requirements. The contractual process should be both legally appropriate and operationally possible.
Keep customer communication under control
State whether the subcontractor may communicate directly with the customer and who can agree changes. Direct technical contact can be useful, but it should not create unapproved scope or pricing commitments. Record material instructions and ensure they reach the main supplier's project owner.
If the customer reports a defect, decide who investigates, who responds and who authorises corrective work. Avoid sending the customer between suppliers while each denies responsibility for the interface. A clear incident and acceptance process helps separate a subcontractor defect from a problem in the main supplier's integration or customer-provided material.
Plan continuity if the subcontractor leaves
Agree handover files, documentation, access and assistance for replacement. Check what happens to incomplete work and accrued fees. The main supplier should be able to continue meeting its customer obligations without depending on an informal promise of future cooperation.
Read Who owns software created by a contractor for contractor software ownership. Supply agreement drafting support can help review subcontract terms against the main agreement, with focused IP and data protection work where the delegated task creates those dependencies.
Check the acceptance interface with an example
Choose one subcontract deliverable and identify who tests it, what evidence is retained and how a defect is distinguished from an integration problem. Give the subcontractor enough information to reproduce the issue without exposing unrelated customer data. The process should produce a clear correction task and owner, rather than a chain of forwarded complaints in which each participant assumes another is responsible for investigating the failure.
Illustrative scenario
An agency hires a developer to build part of a client website. The agency promises the client ownership of the finished code but has not obtained the relevant rights from the developer. Reviewing the subcontract before work starts helps close that ownership gap and establish the required delivery evidence.
Preparation checklist
- Check the main contract’s consent and notification clauses.
- Identify exactly which work will be subcontracted.
- Match confidentiality, data and IP obligations to the task.
- Keep responsibility for acceptance and customer communication clear.
Frequently asked questions
Does customer consent release the main supplier from responsibility?
Not necessarily. Check the main agreement and actual arrangement. Consent to subcontracting is different from transferring the supplier's contractual obligations to another party.
Should the subcontract copy the main contract exactly?
Not automatically. Match relevant obligations to the delegated work, timing and control. Identify gaps and interfaces rather than relying on a mechanical copy.
Why check IP before the subcontractor delivers?
The main supplier may owe the customer rights it has not secured. Obtain appropriate assignments or licences from contributors before promising unrestricted ownership or use.
Is an NDA enough for personal data processing?
No. Assess the parties' data roles and applicable contractual requirements separately. Confidentiality supports protection but does not replace the required data-processing arrangements.
Official sources
Sources checked: 8 September 2026. Check the linked guidance for subsequent changes.
General information only. The appropriate action depends on your circumstances and the applicable jurisdiction.
Report a correction