A company and a consulting firm sign one contract setting the general terms for all future work, such as liability, payment terms, and confidentiality. For each engagement they then sign a separate document listing deliverables, timeline, acceptance criteria, and price. What is the per-engagement document?

Many third-party relationships use a two-layer contract structure. The master services agreement establishes the general legal and commercial terms that govern every engagement, including liability limits, indemnification, confidentiality, payment terms, intellectual property, and dispute resolution, so those terms need not be renegotiated each time. A statement of work is then issued for each specific engagement and defines its scope, deliverables, milestones, acceptance criteria, staffing, and price, operating under the umbrella terms. The per-engagement document described in the scenario is therefore the SOW. The MSA is the general contract signed first; calling the project document an MSA reverses the two layers. A memorandum of understanding expresses shared intent or cooperation, often between organizations or departments, and is typically not a binding commercial contract; it would not hold deliverables and acceptance criteria. A non-disclosure agreement protects confidential information exchanged between parties; confidentiality may already be addressed inside the MSA, and an NDA defines no work, schedule, or price. Exam caveat: security requirements such as data handling, breach notification, and right to audit are usually placed in the MSA so that every SOW inherits them. Operational check: confirm each active SOW references the current MSA and that the MSA contains the organization's required security clauses.