1---2name: draft-markup-of-counterparty-construction-contract3task_id: real-estate/draft-markup-of-counterparty-construction-contract4description: Guides owner-side markup of a contractor's guaranteed maximum price contract draft by calibrating each redline position against the owner's playbook, lender requirements, insurer requirements, and other deal-specific guidance, and producing both a full redline and a prioritized issues memo.5activates_for: [planner, solver, checker]6metadata:7 source: https://skillmd.com/skills/finchipaiorg/draft-markup-of-counterparty-construction-contract8---910# Skill: Draft Markup of Counterparty Construction Contract — Redlined GMP Agreement1112## 1. Subject-matter triage1314- Confirm the draft is the contractor’s governing form for a GMP project and identify whether the source set includes an owner playbook, financing materials, insurance requirements, and client instructions.15- Enumerate the governing source documents once, then compare the contract against each source in a single pass; if a source is absent, say so and do not infer its terms.16- Treat the redline as the primary deliverable and the issues memo as secondary; the memo should summarize the operative markup, not replace it.17- If only one contractor draft is in scope, state that affirmatively before analyzing article-by-article changes.1819## 2. Failure modes the skill is correcting2021- Marking up against generic market positions instead of the owner’s stated playbook, which misses negotiated deal priorities and accepted concessions.22- Treating lender requirements as optional drafting preferences rather than conditions that can control funding.23- Missing insurer-driven coverage language that affects additional-insured status, waiver of subrogation, primary/noncontributory wording, notice obligations, or limits.24- Failing to sequence issues by severity, leaving the client without a practical negotiation order.25- Issuing a memo that lists problems but does not pair each issue with the exact contract location, benchmark, and proposed counter-language.26- Producing a visually redlined file that cannot be audited from plain text because the substantive change is not explicitly labeled.27- Ignoring compounding risk where multiple provisions jointly shift schedule, price, indemnity, or insurance risk.28- Forgetting to confirm the final files are actually created and contain operative drafting, not just commentary.2930## 3. Legal frameworks / domain conventions that apply3132- Construction agreements are typically read article-by-article, but owner-side markup should preserve the contractor’s structure where possible so negotiation changes remain traceable.33- GMP provisions should be tested together with scope definitions, allowances, contingency, change-order mechanics, and savings provisions because those clauses determine whether the price cap is real or illusory.34- Delay-risk provisions should be analyzed together: liquidated damages, excusable delay, concurrent delay, no-damages-for-delay language, and limitation-of-liability clauses can either reinforce or undercut one another.35- Payment protection, bonding, and completion security often appear in financing materials as funding conditions; if the draft diverges, restore the required language unless the client has approved a concession.36- Insurance provisions must be read against the insurance summary as an independent floor, including coverage type, limits, additional-insured scope, primary and noncontributory treatment, and waiver language.37- Indemnity should be checked alongside insurance because a narrowed indemnity paired with narrower coverage creates a compounded coverage gap.38- Subcontractor approval, key-person rights, assignment, dispute resolution, and termination rights often carry lender or owner-control implications even when they appear as boilerplate.39- Any legal proposition or risk conclusion should be tied to the governing contract clause, the related source document, or the recognized doctrine or rule the position relies on.4041## 4. Analytical scaffolds4243- For each article, identify the contractor’s baseline position, compare it to the playbook or other controlling source, and change every material deviation.44- Classify each issue on a uniform ordinal severity scale defined once at the top of the memo, such as: Critical, High, Medium, Low.45- For every issue in the memo, include:46 - the clause reference,47 - the contractor language or concept at issue,48 - the controlling benchmark,49 - the specific consequence to the client,50 - the recommended counter-position.51- Close each issue with three moves:52 - identify the relevant scale, threshold, term, or exposure level from the source materials,53 - cross-reference the related clause or document that interacts with it,54 - state the downstream economic, operational, transactional, or coverage consequence.55- Treat financing requirements as a non-negotiable floor unless the client instruction expressly approves a deviation.56- Treat insurance deviations as mandatory fixes when they reduce coverage below the stated requirements.57- Treat provisions that jointly erode schedule protection and economic remedies as a single compounded risk, not as isolated edits.58- Use a priority hierarchy that supports negotiation sequencing; do not blend must-fix items with items that are merely market points.59- When the client instruction email flags an item for escalation, preserve that flag in the memo and reflect it in the markup comment.60- In the redline, make every substantive edit auditable in plain text with explicit textual markup such as [DELETED: …], [INSERTED: …], or [REPLACED: old → new], followed by a short rationale note.61- Keep comments tied to the governing benchmark; do not leave a naked edit without a reason.6263## 5. Vertical / structural / temporal relationships6465- Read GMP, contingency, allowances, and savings provisions together because a change in one can alter the practical price ceiling.66- Read delay-damages, excusable-delay, no-damages-for-delay, and consequential-damages waiver provisions together because the remedy architecture must be internally consistent.67- Read indemnity, insurance, defense obligations, and additional-insured language together because the same hazard can be shifted, excluded, or duplicated across clauses.68- Read payment timing, retainage, conditions precedent to payment, and lien-waiver mechanics together because the timing of cash flow and leverage can change across project phases.69- Read subcontractor approval, assignment, termination, and step-in provisions together because control rights can transfer over time and across counterparties.70- Read schedule milestones, substantial completion, and final completion together because milestone language often affects both payment and delay exposure.7172## 6. Output structure conventions7374- Produce `contract-redline.docx` as the primary artifact and confirm it is non-empty and contains the operative redline text.75- Produce `markup-issues-memo.docx` after the redline exists, using the redline as the source of truth.76- Use industry-conventional memo organization rather than any rubric-specific section list.77- The memo should start with the severity scale, then group issues by severity and contract article, with each entry including the clause reference, benchmark, consequence, and recommended counter-position.78- End the memo with a short Recommended Actions block that assigns an imperative action, responsible role, and timing anchor drawn from the transaction posture or a stated deadline.79- The redline should preserve the contract’s numbering where possible and include bracketed rationale comments adjacent to each substantive change.80- Before finishing, verify by filename that both deliverables exist, are non-empty, and contain operative drafting rather than a summary of drafting.