Statement of Work in Mexico: Template, Key Clauses and Local Law (2026)

A statement of work (SOW) is the document that describes a specific project: what will be delivered, by when, for how much, and on what terms. In Mexico it almost always sits under a master services agreement (MSA, or contrato marco), which carries the legal terms such as liability, confidentiality and IP, while the SOW carries the project detail. You can also use a standalone SOW, but then it has to carry those legal terms itself. This page is general information, not legal advice. Confirm the current position with a qualified Mexican lawyer before you sign. ## How does a statement of work work under Mexican law? A SOW is not a special legal category in Mexico; it is part of a commercial services contract governed by the Commercial Code (Codigo de Comercio), with the Federal Civil Code (Codigo Civil Federal) filling gaps under Article 2 of the Commercial Code. What matters is the relationship it creates. - Incorporation. When a SOW sits under an MSA, it should state that the MSA governs and that the SOW is subject to it. Set the order of precedence so you know which document wins on a conflict.

• The outsourcing trap. This is the most important point for services in Mexico. Since the 2021 outsourcing reform to the Federal Labour Law, providing personnel for a client's core activity is banned. Only genuine specialised services, outside the client's main economic activity, are permitted, and the provider must be registered in the REPSE registry kept by the Ministry of Labour (registration is valid for three years). A SOW that in substance supplies people rather than a defined, deliverable-based service can be reclassified, exposing the client to joint liability for the provider's labour and tax obligations. Write the SOW around deliverables and outcomes, not around headcount.
• Deliverables versus effort. Describe whether the provider owes a result (a finished deliverable) or a best-effort service. This affects acceptance and payment.
• Tax and language. IVA at 16 percent and CFDI invoicing apply; for enforcement in a Mexican court you will usually need a Spanish version or translation. ## Key clauses in a Mexican statement of work - Reference to the MSA. Identify the governing MSA and confirm the SOW is subject to it, with the order of precedence.
• Scope and deliverables. A precise description of what will be produced, so acceptance is objective.
• Milestones and timeline. Dates, phases and dependencies.
• Acceptance criteria. How deliverables are reviewed, accepted or rejected, and the cure period.
• Fees and payment. Fixed price or time and materials, the schedule, currency, IVA and CFDI invoicing, linked to milestones or acceptance.
• Assumptions and dependencies. What the provider is relying on from the client, and what happens if those slip.
• Change control. How scope changes are requested, priced and approved.
• Personnel. Named roles or skills, and a clear statement that personnel are the provider's own employees (supporting the specialised-services position).
• Intellectual property. Who owns the deliverables; software and written work are protected by copyright under the Federal Law on Copyright, so assign or licence them.
• Acceptance and warranty. The standard the deliverables must meet and the remedy for defects.
• Governing terms. Confirm that liability, confidentiality and dispute terms come from the MSA (or state them if standalone). ## A simple statement of work skeleton you can adapt 1. Reference to the MSA and order of precedence

2. Project overview and objectives
3. Scope and deliverables
4. Out of scope
5. Milestones and timeline
6. Acceptance criteria and process
7. Fees, payment schedule, IVA and invoicing
8. Assumptions and client dependencies
9. Change control
10. Roles, personnel and labour compliance
11. Intellectual property in deliverables
12. Warranty on deliverables
13. Signatures ## Common mistakes in Mexican statements of work - Writing it as a staffing order. A SOW built around headcount rather than deliverables risks reclassification under the 2021 outsourcing reform and joint liability for the client. Frame it around defined services and outcomes, and register in REPSE when the specialised-services rules apply.

• No acceptance criteria. Without objective acceptance tests, payment and sign-off become arguments.
• Floating free of the MSA. A SOW that does not reference the MSA, or contradicts it without saying so, creates uncertainty about which terms apply.
• Vague change control. Scope creep with no agreed process leads to disputes over extra fees.
• Silent on IP. Without assignment or licence, copyright in deliverables can stay with the author.
• English only. Harder to enforce in Mexico; agree a controlling language. ## Keeping your projects under control The hard part of running SOWs is not writing the first one. It is issuing every SOW on consistent terms under the right MSA, tracking milestones and acceptance, spotting a scope or IP clause that drifted, and making sure none of them quietly turns into a staffing arrangement that breaches the outsourcing rules. When this lives in email and shared drives, it is easy to lose the thread. That is the work an AI contract workspace can hold in one place: draft each SOW from your approved template under the right MSA, see per-clause risk flagged against how your company contracts, edit terms in plain language, and keep a live timeline of milestones, versions and obligations. Adira is one such workspace if you want to see the idea in practice. Its depth outside India is on the roadmap, so confirm Mexico-specific labour points with local counsel. ## FAQ