A procurement team mixes up three cloud contract documents: one sets the overall legal terms such as liability, confidentiality and governing law for every engagement; one defines measurable service commitments such as availability and support response times; and one describes specific deliverables for a migration project. What are these documents, in that order?

Cloud and outsourcing contracts are usually layered. The master service agreement sets the general legal and commercial terms that govern the whole relationship and all future work, including liability, indemnification, confidentiality, intellectual property, data protection obligations, governing law and dispute resolution. The service-level agreement defines measurable performance commitments for the service, such as availability targets, support response and resolution times, how performance is measured and reported and what remedies, such as service credits, apply when targets are missed. The statement of work describes a specific engagement under the master agreement, such as a migration project, including scope, deliverables, milestones, responsibilities, acceptance criteria and pricing for that work. Placing the statement of work first and the master agreement last swaps the general and the specific documents. Putting the service-level agreement first confuses performance metrics with the legal framework. Swapping the statement of work and the service-level agreement assigns project deliverables to the performance document and uptime targets to the project document. Exam caveat: the master agreement normally states which document prevails if terms conflict. Operational check: confirm the contract set includes an order of precedence clause and that each statement of work references the governing master agreement.