Subcontractor Agreement (US) by OCS
US subcontractor agreement with state-specific options for worker classification and non-competes.
SUBCONTRACTOR AGREEMENT
This Subcontractor Agreement (this "Agreement") is entered into as of [effective date] (the "Effective Date") by and between:
Contractor: [contractor legal name], a [contractor state of formation] [contractor entity type] with an address at [contractor address] ("Contractor"); and
Subcontractor: [subcontractor legal name], a [subcontractor state of formation or 'individual'] [subcontractor entity type] with an address at [subcontractor address] ("Subcontractor").
Contractor and Subcontractor are each a "Party" and together the "Parties."
BACKGROUND
A. Contractor has entered into a prime contract or engagement with [client / customer name] (the "Client") to perform certain work (the "Prime Work").
B. Contractor wishes to sub-contract a portion of the Prime Work to Subcontractor, and Subcontractor is willing to perform such work on the terms set out in this Agreement.
NOW, THEREFORE, in consideration of the mutual covenants set out below, the Parties agree as follows:
1. SERVICES AND DELIVERABLES
Note: This section defines exactly what the Subcontractor will do and what they will deliver. Be as specific as possible: vague scope descriptions are one of the most common sources of disputes. If the work is complex, attach a detailed scope of work as Exhibit A.
1.1 Services. Subcontractor will perform the services described in Exhibit A (Key Commercial Terms) (the "Services") in a professional and workmanlike manner, in accordance with the terms of this Agreement and any requirements of the Prime Work that Contractor has given Subcontractor in writing.
1.2 Deliverables and Acceptance. Subcontractor will deliver the work product described in Exhibit A (the "Deliverables") by the dates in Exhibit A. A Deliverable is accepted when delivered unless Contractor notifies Subcontractor in writing within [acceptance period, e.g., 10] days that a Deliverable does not materially conform to the requirements in Exhibit A and identifies the non-conformity. Subcontractor will have 10 days to correct and re-deliver. If the corrected Deliverable is still materially non-conforming, Contractor may reject it by written notice, terminate under Section 2.3(a) without a further cure period, and withhold payment for that Deliverable. Any disagreement about conformity is a dispute under Section 16.
1.3 Changes. Any material change to scope, timeline, or fees must be agreed in writing by both Parties before Subcontractor performs the changed work. Contractor may not unilaterally change the scope of the Services without Subcontractor's written consent.
Note: Avoid scope descriptions that look like 'any tasks as assigned'. That kind of unlimited scope creates classification risk and payment disputes. Define outcomes and deliverables, not just activities.
2. TERM AND TERMINATION
2.1 Term. This Agreement starts on the Effective Date and continues until [end date or 'completion of the services'], unless terminated earlier under this Section 2 (the "Term").
2.2 Termination for Convenience. Either Party may terminate this Agreement for any reason by giving the other Party at least [notice period, e.g., 14] days' written notice.
This is a preview. The full template is free on GitLaw.
5.0 out of 5 on Google
Read reviewsAs seen in
Frequently asked questions
A template isn't binding on its own - like any contract, it becomes binding once it's properly completed and signed. Templates in our curated library are professionally drafted for US or UK law; review any template before you sign it.
Yes. Chat with GitLaw to edit any section, or make changes directly in the editor.
Yes, read about team plans here.
Describe what you need in the chat and GitLaw will draft it for you.
Templates in our curated library are professionally drafted for US or UK law. The wider library comes from the GitLaw community and public sources - a solid starting point, but check any template fits your situation before you rely on it.
Mostly US and UK law. Some templates use general commercial terms that work across jurisdictions, and many note which law they're written for.
It depends on the situation. Templates work well for routine business agreements. For anything involving significant money, complex IP, employment, or areas you're unsure about, it's worth getting professional advice before you sign. GitLaw provides templates and tools, not legal advice.
Open any template in GitLaw and describe the change you want in the chat — 'make clause 4 mutual' or 'add a 30-day notice period', for example. GitLaw drafts the revised language and shows it as a suggested edit. You accept, reject, or keep editing from there.
Yes. Upload a Word, PDF, or Markdown file and GitLaw will open it in the editor. You can review, edit, or chat with GitLaw about it the same way you would with any template from the library.
Trusted by 5,000+ businesses
From template to signed, in one place
Every template opens in an editor with an AI agent alongside it.
Open
Pick a template and open it. Nothing to download, and no credit card to start.
Free to open
Edit with AI
Describe your situation in chat and the agent adapts the wording, clause by clause.
Tracked changes you can review
Send and sign
Share it for negotiation, then collect signatures without leaving GitLaw.
eSign included
Built for your legal work,
with practicing lawyers
Trained on 5,500+ clauses and specialist areas of law. Built with a standards committee of independent lawyers.
As seen in
Ready to get started?
No sales calls, no credit card. Just chat with GitLaw.
GitLaw provides templates and tools, not legal advice. Templates are a starting point, not a substitute for advice on your situation - for anything significant, speak to a qualified lawyer.