1---2name: draft-markup-counterparty-contract-amendment3task_id: intellectual-property/draft-markup-of-counterparty-contract-amendment4description: Annotated redline of a proposed contract amendment with marginal commentary and a cover memo, evaluated against the operative agreement history and internal contracting guidance.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/draft-markup-counterparty-contract-amendment8---910# Skill: Draft Markup of Counterparty Contract Amendment1112## 1. Subject-matter triage1314- Confirm the operative baseline before editing: the current agreement, all prior amendments, incorporated exhibits or schedules, and any side letters or referenced policies that modify the live text.15- Read the supplier’s proposed amendment together with the business-context email and procurement playbook before drafting any markup.16- If the source set contains multiple amendments, versions, or related attachments, enumerate them first and map which document controls each disputed provision.17- Identify whether any business instruction overrides the default playbook position; if so, note the override and its source before redlining.1819## 2. Failure modes the skill is correcting2021- Marking up the amendment against the wrong baseline because earlier amendments or incorporated documents were not folded into the operative text.22- Applying generic playbook positions without reconciling the specific business context, which can produce edits that conflict with deal priorities.23- Drafting a redline that is only visually marked up and cannot be reconstructed from plain text after export.24- Omitting marginal comments, or using comments that state a change without explaining its legal or commercial basis.25- Failing to separate must-have positions from preferred asks and items needing further review.26- Delivering a cover memo that summarizes the deal but does not actually steer the negotiation.27- Stating conclusions about enforceability, ownership, liability, pricing, confidentiality, data use, termination, or similar terms without tying the position to a controlling authority or governing contract language.2829## 3. Legal frameworks / domain conventions that apply3031- Treat the amendment as an exercise in contract interpretation and contract drafting: the operative text is read as a whole, with amendments and incorporated documents construed together.32- Apply the procurement playbook as the company’s internal drafting authority for standard and fallback positions; use the business email for transaction-specific deviations.33- For each substantive edit, identify the governing source of the position: the agreement history, playbook, business instruction, or the amendment’s own drafting logic.34- Where a legal proposition is invoked, identify the controlling authority by name and section or comparable citation form used in the source materials or standard practice authority.35- Use amendment-appropriate conventions for defined terms, conforming edits, hierarchy clauses, survival language, precedence, and express preservation of unchanged terms.36- Treat legal and commercial provisions as distinct: legal risk positions may warrant different treatment from pricing or operational changes.37- For recurring contracting topics, check consistency across related clauses rather than editing one provision in isolation, especially where liability, IP, confidentiality, data handling, indemnity, termination, audit, or payment mechanics interact.3839## 4. Analytical scaffolds4041- Baseline reconstruction:42 - Rebuild the operative contract from the full agreement stack before evaluating any proposed change.43 - Identify the provisions the amendment purports to change and any adjacent provisions that must be conformed.44- Provision-by-provision comparison:45 - Compare each proposed edit against the operative baseline, the playbook, and the business context.46 - Mark only the changes that are necessary to secure the client’s position; preserve acceptable language where possible.47- Change typing:48 - Use explicit textual markup that survives format conversion: [DELETED: …], [INSERTED: …], and [REPLACED: old → new].49 - Attach a short [Rationale: …] comment to each substantive change so the reader can understand the legal or commercial reason for the edit.50- Priority classification:51 - Label each issue or comment with a uniform ordinal severity scale defined once at the outset, such as Critical / High / Medium / Low.52 - Use the same severity labels throughout the markup commentary and cover memo.53- Cross-document checking:54 - For each issue, note the related clause, schedule, exhibit, amendment, or policy that affects the same topic.55 - If a provision depends on a defined term or cross-reference, confirm the defined term still works after the amendment.56- Negotiation posture:57 - Distinguish mandatory positions, preferred positions, and items flagged for further review.58 - Draft comments so they can be used directly in negotiation, not merely as internal notes.59- Issue closure:60 - For each commented issue, explain the practical consequence if the counterparty’s language is accepted as written.61 - Where relevant, include the scope or magnitude of the concern using figures or thresholds from the source set, without inventing new arithmetic.6263## 5. Vertical / structural / temporal relationships6465- Preserve amendment hierarchy: the new amendment should state clearly what it changes, what survives, and whether prior inconsistent language is superseded.66- Check temporal sequencing: make sure effective dates, notice periods, payment timing, transition periods, and survival provisions do not conflict with earlier documents.67- If the amendment is part of a series, distinguish provisions that apply only prospectively from provisions intended to confirm past conduct or cure prior defaults.68- Where multiple source documents address the same subject, reconcile them in control order rather than averaging them.69- Ensure that conforming changes are made to defined terms, exhibits, and referenced policies so the amendment does not create internal inconsistency.7071## 6. Output structure conventions7273- Primary deliverable first: produce the markup document as the operative output, and ensure it is complete before drafting the cover memo.74- Redline markup:75 - Present the amendment in a form that is visibly annotated and textually recoverable in plain text.76 - Include margin-style comments or inline notes for each substantive edit, each with a brief rationale and an explicit severity label.77 - Keep comments tied to the exact provision being changed; do not consolidate unrelated issues into one note.78- Cover memo:79 - Follow the markup with a concise memo that identifies the main issues, the overall risk posture, and the recommended negotiation approach.80 - End with a Recommended Actions section that uses imperative verbs, names the responsible role from the source materials where available, and includes a timing anchor tied to the deal timeline or a stated deadline.81- Final sanity check:82 - Confirm the markup file is non-empty and contains the operative revised language, not just a summary of proposed edits.83 - Confirm the memo does not replace the redline and does not omit the priority issues needed for negotiation.