Agreement · Technology, Media & Telecommunications / IT Contracts
Statement of work
Statement of work for services under a master agreement: scope, milestones, fees and acceptance. Copyright in deliverables stays with the creator unless a signed assignment or a real work-made-for-hire path is used.
- Kind
- Agreement. A contract between two or more parties.
- Where it applies
- United States
- AI use
- Yellow You and the tool draft together, with you directing. You check every statement you rely on.
- Law stated as at
- 22 October 2026
- Status
- Maintained. Checked on 22 October 2026 against the 3 authorities it cites, for United States.
- Version
- 1
- Source
- Written for this library
When to use it
Use to record one project under a signed master agreement. Do not use it as the only contract if there is no master, unless counsel adds the missing commercial terms. Do not tick work made for hire unless Circular 30's conditions are met.
Used for these tasks
- Draft a statement of work from the proposal and the MSA
- Draft an outsourcing or managed-services structure from the term sheet
Each task page says how far AI may help with the task and what the lawyer must review.
How AI may be used
AI may turn an approved proposal into the scope, milestone and fee tables. The lawyer chooses licence, assignment or work made for hire, and checks that the master agreement is the one named.
AI may
- Fill scope, dates and fees from the proposal the lawyer has approved
- List deliverables that have no intellectual-property choice and mark them
- Check that the named master agreement matches the file
AI must not
- Must not tick work made for hire for software, a logo or a website unless the lawyer has named one of the nine categories
- Must not treat this statement as an assignment unless the owner signs it
- Must not add acceptance criteria the proposal does not contain
The lawyer checks
- The master agreement named is the contract that governs, and conflicts are resolved the way section 7 says
- Each deliverable is a licence, an assignment signed by the owner, or a work made for hire that meets Circular 30
- Fees and acceptance match the commercial instructions
Method: how the Green, Yellow and Red levels are decided. This is guidance for planning, not legal advice.
Read the full text
The full text is available after you log in. It is free. When you log in you can:
- read the whole precedent, with its drafting notes beside it;
- copy it, or download it as a Word file or Markdown;
- add it to your firm’s knowledge base, so colleagues can find it;
- let the AI tools you connect read it from that knowledge base.
The summary, the law it rests on and the AI-use guidance above stay public. Privacy.
More in Technology, Media & Telecommunications / IT Contracts
- IT services statement of work template (under a master services agreement)
- Ransomware or cyber extortion payment report: fields on the ACSC form
- SaaS / cloud services agreement (Australian law, business customers)
- CCPA service provider and contractor addendum
- SaaS subscription and negative-option checklist
- Website and online platform terms of use (Australian business, with Australian Consumer Law carve-outs)
- AI standard clauses for AI features in cloud services (Bonterms AI Standard Clauses v1.0, CC0)
- Deed of assignment of intellectual property and moral rights consent (contractor or developer software)
- Service level schedule with service credits (SaaS, managed or hosted services)
- Register of Critical Infrastructure Assets: what the CISC page asks for
- Checklist for electronic consumer records
- SaaS subscription agreement
- AI addendum: ownership of AI-generated output, training-data rights and AI-specific warranties (customer-side)
- Email and SMS marketing campaign checklist (Spam Act consent, sender identification and unsubscribe)
- SOCI Act cyber incident report: 12-hour and 72-hour clocks
- Software source code escrow agreement (three-party: supplier, customer and escrow agent)
- AI vendor terms review checklist
- Cross-border disclosure assessment for a technology vendor (APP 8 and s 16C checklist and record)
- Critical infrastructure risk management program: annual report contents
- Australian Government AI model clauses (DTA, BuyICT ClauseBank): use guide for agencies and suppliers
- Open source licence compliance review checklist (technology transactions and product releases)
- Security incident clause
- Consumer Data Right: data holder obligations on the CDR site
- Data protection, security and breach-notification schedule (processor terms)
- Software development agreement with AI coding-assistant and open-source terms
- Checklist: reviewing a vendor SaaS or technology contract (customer side, including AI terms)
All precedents for Technology, Media & Telecommunications / IT Contracts · Tasks and AI use in this area