Draft Contract Amendment For Cloud Infrastructure Services Agreement

---
name: draft-contract-amendment-cloud-msa
task_id: intellectual-property/draft-contract-amendment-for-cloud-infrastructure-services-agreement
description: Amendment to an existing cloud infrastructure services master services agreement resolving conflicts between a proposed revision and internal requirements, with a cover memo detailing discrepancies, resolutions, and residual risks.
activates_for: [planner, solver, checker]
---

# Skill: Draft Contract Amendment for Cloud Infrastructure Services Agreement

## 1. Subject-matter triage

Confirm the operative contract stack before drafting: the base cloud services MSA, all prior amendments, any data-protection addendum, and any order form or incorporated policy that changes the operative terms. Identify which provisions are actually being revised, and whether the new amendment replaces, supplements, or clarifies prior language.

If the services touch regulated health information, determine at the outset whether the amendment must coordinate with a business associate arrangement, privacy/security addendum, incident notice terms, and audit/inspection rights. Treat those as contract-formation and allocation issues, not as afterthought compliance language.

When more than one clause, policy, or incorporated exhibit may be affected, enumerate the affected items before drafting so the amendment tracks each operative touchpoint cleanly.

## 2. Failure modes the skill is correcting

- Drafting against the original MSA without reconciling prior amendments and incorporated addenda
- Resolving only part of a vendor proposal conflict and leaving a residual inconsistency in the operative text
- Producing a memo that describes discrepancies but does not actually state how each one is resolved in the amendment
- Treating healthcare privacy, security, and incident response terms as optional operational preferences rather than binding contractual requirements
- Failing to anchor each legal position to the controlling contractual language or governing legal rule
- Missing the need to preserve the amendment as the primary deliverable and the memo as a secondary advisory document

## 3. Legal frameworks / domain conventions that apply

- Amendments should identify the specific section(s) being changed and state whether the prior language is amended, restated, added, deleted, or superseded
- Operative hierarchy matters: later amendments, exhibits, and incorporated addenda can override earlier draft language if the contract so provides
- Healthcare cloud contracting usually requires explicit treatment of protected health information, security safeguards, breach notification, subcontractor flow-downs, audit cooperation, and termination/return or destruction obligations
- If a business associate framework applies, the amendment should align with the privacy/security addendum and allocate responsibilities consistently with applicable healthcare privacy and security rules
- Regulatory compliance statements should be drafted as ongoing obligations or refreshed representations where the contract needs a current compliance assurance
- Each legal assertion in the amendment or memo should be tied to the governing contract clause, statute, regulation, or recognized doctrine that supports it

## 4. Analytical scaffolds

- Amendment history review: build a clause-by-clause map of the current operative agreement before touching text
- Conflict inventory: for each vendor proposal point, identify the exact internal requirement it conflicts with and the contractual provision implicated
- Priority resolution: decide whether the issue is solved by substitution, carve-out, clarification, hierarchy language, or a new standalone covenant
- Compliance alignment: ensure privacy, security, incident response, subcontracting, retention, and audit provisions are internally consistent across the amendment package
- Residual-risk check: where the solution is a compromise, state what risk remains and what operational control or follow-up document mitigates it
- Authority check: for each substantive proposition, cite the relevant contract provision or legal source in the drafting rationale rather than stating conclusions nakedly

## 5. Vertical / structural / temporal relationships

Draft the amendment so it sits correctly in the contract hierarchy: original MSA first, then existing amendments, then any attached privacy or security addendum, then the new amendment. Use recitals to establish chronology and operative status.

Where a clause depends on another clause, preserve that dependency in the text. For example, a breach notice provision should align with security incident definitions; data-use limits should align with retention/destruction obligations; audit rights should align with confidentiality and access-control mechanics.

If the amendment changes ongoing obligations, distinguish immediate effective changes from obligations that apply only after a trigger event, certification, or implementation period. If multiple dates or triggering events matter, state them distinctly so the amended obligations can be administered without ambiguity.

## 6. Output structure conventions

### Amendment draft
- Draft the amendment as the primary deliverable and complete it before the memo
- Use a conventional amendment form with title, date line, parties, recitals, operative sections, and signature blocks if appropriate
- Identify the amended provisions by section number or exhibit name and state the exact modification mechanism
- Resolve conflicts affirmatively in the client’s favor where possible, using precise contract language rather than commentary
- Where the amendment adds a new compliance covenant or security obligation, place it in the operative text, not only in recitals
- Keep the drafting clean and internally consistent; if a provision is restated, the restated text should read as the operative clause

### Cover memo
- Follow the amendment with a concise advisory memo describing the discrepancies, the adopted resolution, and any remaining risk
- Organize the memo by issue, with one issue per operative conflict or cluster of closely related conflicts
- State the legal or contractual basis for each resolution by naming the governing clause, addendum, statute, regulation, or rule
- Where the resolution is imperfect, identify the residual risk and the practical mitigation
- End with a short recommended-actions section that assigns next steps to the relevant business or legal owner and gives a timing anchor tied to execution, launch, renewal, or regulatory implementation
- Keep the memo explanatory and decision-oriented; do not turn it into a pure issue dump

### File handling
- Produce the amendment file first, then the memo after the amendment exists and contains operative text
- Before finishing, confirm that both named deliverables are present, non-empty, and contain the actual drafted content rather than a summary of it