{"id":"4469adc7-bcd4-4dbc-8c3a-81119fe4d565","entityType":"agent","slug":"clawhub-redkiwi1688-prog-construction-claim-strategy","name":"Construction Claim Strategy","canonicalUrl":"https://www.xpersona.co/agent/clawhub-redkiwi1688-prog-construction-claim-strategy","canonicalPath":"/agent/clawhub-redkiwi1688-prog-construction-claim-strategy","generatedAt":"2026-10-11T05:34:33.302Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-11T03:14:25.857Z","emptyReason":null},"description":"Strategic planning framework for construction claim responses — plan direction, scope, arguments, and disclosure strategy BEFORE selecting clauses or draftin... Skill: Construction Claim Strategy Owner: redkiwi1688-prog Summary: Strategic planning framework for construction claim responses — plan direction, scope, arguments, and disclosure strategy BEFORE selecting clauses or draftin... Tags: latest:1.7.6 Version history: v1.7.6 | 2026-05-17T10:34:10.649Z | user v1.7.6: Added 'Working out the actual deadline' section (calendar-day counting, s.50(a), ad-hoc holidays, points t","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.","installCommand":"clawhub skill install s17amvshtfxjppkedfhxdzt9s1855xxx:construction-claim-strategy","sourceUrl":"https://clawhub.ai/redkiwi1688-prog/construction-claim-strategy","homepage":"https://clawhub.ai/redkiwi1688-prog/skills/construction-claim-strategy","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/redkiwi1688-prog/construction-claim-strategy","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/redkiwi1688-prog/skills/construction-claim-strategy","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":61,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"Strategic planning framework for construction claim responses — plan direction, scope, arguments, and disclosure strategy BEFORE selecting clauses or draftin..."},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-11T03:14:25.857Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T03:14:25.857Z","emptyReason":null},"stars":null,"forks":null,"downloads":1176,"packageName":null,"latestVersion":"1.7.6","tractionLabel":"1.2K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-11T03:14:25.785Z","emptyReason":null},"lastUpdatedAt":"2026-10-11T03:14:25.857Z","lastCrawledAt":"2026-10-11T03:14:25.785Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-12T03:14:25.785Z","lastVerifiedAt":null,"highlights":[{"version":"1.7.6","createdAt":"2026-05-17T10:34:10.649Z","changelog":"v1.7.6: Added 'Working out the actual deadline' section (calendar-day counting, s.50(a), ad-hoc holidays, points to construction-law SOP calculator). Replaced Companion skill section with 4-step end-to-end workflow. Wizard prompt sharpened to nudge toward specific dates. No cross-skill code coupling — paired via documentation only.","fileCount":30,"zipByteSize":75831},{"version":"1.7.5","createdAt":"2026-05-17T09:41:13.519Z","changelog":"v1.7.5: Sanitised test docstrings/comments — removed function-call patterns in English text that ClawHub static analysis was pattern-matching as suspicious.dynamic_code_execution.","fileCount":29,"zipByteSize":73005},{"version":"1.7.4","createdAt":"2026-05-17T09:37:34.801Z","changelog":"v1.7.4: Replaced string-grep forbidden-imports test with ast.parse tree-walking — catches compile/exec/eval regardless of whitespace or indirection, no false-positives on comments/docstrings/strings.","fileCount":29,"zipByteSize":72985},{"version":"1.7.3","createdAt":"2026-05-17T09:33:43.346Z","changelog":"v1.7.3: Rewrote test_smoke.py to eliminate ClawScan suspicious.dynamic_code_execution flag — tests now import main() directly via unittest.mock.patch instead of subprocess. Tightened forbidden-imports list (urllib.request/error not blanket urllib; added importlib, pickle, marshal, compile). Tests run 20x faster.","fileCount":29,"zipByteSize":72419},{"version":"1.7.2","createdAt":"2026-05-17T08:18:52.481Z","changelog":"v1.7.2: Required-key validation (6 mandatory keys for --file mode), unified _safe_write helper, interactive mode error handling, docs: --help output, no telemetry, files written, required keys table, unittest over pytest","fileCount":29,"zipByteSize":71841},{"version":"1.7.1","createdAt":"2026-05-17T07:51:21.397Z","changelog":"v1.7.1: Added forbidden-imports test (enforces no-network/no-subprocess security claim); updated Python requirement from 3.6+ to 3.10+ (honest about what's actually tested)","fileCount":29,"zipByteSize":70077},{"version":"1.7.0","createdAt":"2026-05-17T07:12:09.987Z","changelog":"v1.7.0: Replaced example scenario with realistic PSSCOC EOT case (Contractor responding to SO rejection under Clause 13.2). Updated strategy_input.json with correct flat-key schema, regenerated strategy_report_sample.md from actual script output, improved test docstrings. Includes v1.6.1 changes: JSON input validation, file I/O error handling, dead code removal.","fileCount":29,"zipByteSize":69549},{"version":"1.6.1","createdAt":"2026-05-17T07:09:15.600Z","changelog":"v1.6.1: JSON input validation (dict check, unknown key warnings), file I/O error handling (friendly messages for missing/unreadable files), removed dead code (_prompt_yesno)","fileCount":29,"zipByteSize":70578}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s17amvshtfxjppkedfhxdzt9s1855xxx:construction-claim-strategy","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-redkiwi1688-prog-construction-claim-strategy/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-redkiwi1688-prog-construction-claim-strategy/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-redkiwi1688-prog-construction-claim-strategy/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-redkiwi1688-prog-construction-claim-strategy/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-redkiwi1688-prog-construction-claim-strategy/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-redkiwi1688-prog-construction-claim-strategy/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-11T05:34:33.298Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-redkiwi1688-prog-construction-claim-strategy/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-redkiwi1688-prog-construction-claim-strategy/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-redkiwi1688-prog-construction-claim-strategy/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-redkiwi1688-prog-construction-claim-strategy/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-11T03:14:25.857Z","emptyReason":null},"readme":"Skill: Construction Claim Strategy\n\nOwner: redkiwi1688-prog\n\nSummary: Strategic planning framework for construction claim responses — plan direction, scope, arguments, and disclosure strategy BEFORE selecting clauses or draftin...\n\nTags: latest:1.7.6\n\nVersion history:\n\nv1.7.6 | 2026-05-17T10:34:10.649Z | user\n\nv1.7.6: Added 'Working out the actual deadline' section (calendar-day counting, s.50(a), ad-hoc holidays, points to construction-law SOP calculator). Replaced Companion skill section with 4-step end-to-end workflow. Wizard prompt sharpened to nudge toward specific dates. No cross-skill code coupling — paired via documentation only.\n\nv1.7.5 | 2026-05-17T09:41:13.519Z | user\n\nv1.7.5: Sanitised test docstrings/comments — removed function-call patterns in English text that ClawHub static analysis was pattern-matching as suspicious.dynamic_code_execution.\n\nv1.7.4 | 2026-05-17T09:37:34.801Z | user\n\nv1.7.4: Replaced string-grep forbidden-imports test with ast.parse tree-walking — catches compile/exec/eval regardless of whitespace or indirection, no false-positives on comments/docstrings/strings.\n\nv1.7.3 | 2026-05-17T09:33:43.346Z | user\n\nv1.7.3: Rewrote test_smoke.py to eliminate ClawScan suspicious.dynamic_code_execution flag — tests now import main() directly via unittest.mock.patch instead of subprocess. Tightened forbidden-imports list (urllib.request/error not blanket urllib; added importlib, pickle, marshal, compile). Tests run 20x faster.\n\nv1.7.2 | 2026-05-17T08:18:52.481Z | user\n\nv1.7.2: Required-key validation (6 mandatory keys for --file mode), unified _safe_write helper, interactive mode error handling, docs: --help output, no telemetry, files written, required keys table, unittest over pytest\n\nv1.7.1 | 2026-05-17T07:51:21.397Z | user\n\nv1.7.1: Added forbidden-imports test (enforces no-network/no-subprocess security claim); updated Python requirement from 3.6+ to 3.10+ (honest about what's actually tested)\n\nv1.7.0 | 2026-05-17T07:12:09.987Z | user\n\nv1.7.0: Replaced example scenario with realistic PSSCOC EOT case (Contractor responding to SO rejection under Clause 13.2). Updated strategy_input.json with correct flat-key schema, regenerated strategy_report_sample.md from actual script output, improved test docstrings. Includes v1.6.1 changes: JSON input validation, file I/O error handling, dead code removal.\n\nv1.6.1 | 2026-05-17T07:09:15.600Z | user\n\nv1.6.1: JSON input validation (dict check, unknown key warnings), file I/O error handling (friendly messages for missing/unreadable files), removed dead code (_prompt_yesno)\n\nv1.6.0 | 2026-05-10T13:36:56.059Z | user\n\nAdded examples (PSSCOC 2014), smoke tests, LICENSE, vocabulary normalisation, removed bespoke wording, clarified references framing\n\nv1.5.0 | 2026-05-09T13:15:57.892Z | user\n\nAdded comprehensive Delay Analysis Study Guide — SCL Protocol 22 Core Principles, 7 delay analysis methods (incl. Retrospective Longest Path), negative float and EOT entitlement, concurrent delay (Malmaison/North Midland/City Inn), pacing delays, disruption causation (Walter Lilly test), force majeure vs hardship, COVID-19 lessons, 15 key cases with citations, full definitions glossary. Total: 22 reference documents.\n\nv1.4.0 | 2026-05-09T13:08:36.755Z | user\n\nMajor expansion: Integrated full Construction Claim Strategy Practical Tools Guide v1.4. Added 11 new reference documents — Notice Requirements Checklist, Expert Engagement, Legal Precedents, Concurrent Delay Strategy, Disruption Claims Strategy, Delay Analysis Methods, Arbitration Tactics & Prolongation Strategies, ADR Overview, Quantum Worked Examples (8 examples: Eichleay/Hudson/Emden/Measured Mile/Actual Cost/Total Cost), Common Pitfalls, Risk Assessment Framework, Record Keeping Checklist, Claim Preparation Checklist. Total: 21 reference documents.\n\nv1.3.0 | 2026-05-09T11:48:38.039Z | user\n\nMajor content expansion: 7-dimension detailed guide with good/bad examples, 4 fully worked examples (Variation, EOT, Disruption, Combined EOT+Disruption) with complete strategy worksheets and sample response letters, blank strategy worksheet template, EOT vs Disruption comparison table. All fully generic with proper disclaimers.\n\nv1.2.0 | 2026-05-09T11:32:52.365Z | user\n\nMajor content update: detailed argument ranking guide with response structures, primary+fallback combination patterns, argument-disclosure interaction table, response letter template, quick reference card, training workshop guide. All fully generic. Added 4 new reference documents.\n\nv1.1.0 | 2026-05-09T11:18:10.444Z | user\n\nFully sanitized — all generic/neutral language. No jurisdiction-specific references. Improved wizard with validation. Legal disclaimer added.\n\nv1.0.1 | 2026-05-09T10:57:41.050Z | user\n\nScrubbed all project-specific references. All examples now generic/hypothetical. Added disclaimer.\n\nv1.0.0 | 2026-05-09T10:40:15.958Z | user\n\nInitial release — strategic planning framework for construction claim responses. Covers situation assessment, scope control, direction decisions, argument ranking, disclosure control, response architecture, and risk assessment.\n\nArchive index:\n\nArchive v1.7.6: 30 files, 75831 bytes\n\nFiles: examples/strategy_input.json (3646b), examples/strategy_report_sample.md (10456b), references/adr_overview.md (4045b), references/arbitration_tactics.md (3206b), references/argument_ranking_guide.md (6855b), references/blank_worksheet.md (1864b), references/claim_preparation_checklist.md (2116b), references/common_pitfalls.md (2224b), references/concurrent_delay.md (3039b), references/delay_analysis_methods.md (3239b), references/delay_analysis_study_guide.md (21978b), references/disruption_claims.md (3980b), references/expert_engagement.md (2431b), references/legal_precedents.md (2960b), references/notice_requirements_checklist.md (1770b), references/quantum_worked_examples.md (6312b), references/quick_reference_card.md (2634b), references/record_keeping_checklist.md (1910b), references/response_template.md (2667b), references/risk_assessment_framework.md (2467b), references/seven_dimensions_guide.md (8586b), references/strategy_patterns.md (4636b), references/training_guide.md (4950b), references/worked_examples.md (12735b), scripts/strategy_advisor.py (34038b), scripts/version.py (282b), skill-card.md (3384b), SKILL.md (21689b), tests/test_smoke.py (7462b), _meta.json (146b)\n\nFile v1.7.6:SKILL.md\n\n---\nname: construction-claim-strategy\ndescription: Strategic planning framework for construction claim responses — plan direction, scope, arguments, and disclosure strategy BEFORE selecting clauses or drafting. Covers situation assessment, scope control, direction decisions, argument ranking, disclosure control, response architecture, and risk assessment for EOT, delay, disruption, variation, and payment claims under PSSCOC, FIDIC, NEC, SIA, and bespoke forms. Includes practical checklists, quantum calculation methods, ADR strategies, delay analysis methods, concurrent delay, disruption claims, arbitration tactics, expert engagement, notice compliance, and legal precedent guidance.\n---\n\n# Construction Claim Strategy\n\n**Strategic planning framework for construction claim responses.**\n\nPlan your direction, scope, arguments, and disclosure strategy **before** selecting clauses or drafting correspondence.\n\n---\n\n## Why use this?\n\n- Stop jumping straight to clause selection — plan the strategy first.\n- Rank arguments by strength (Textual Interpretation is strongest).\n- Control what to disclose precisely, keep general, or defer.\n- Choose proven response structures.\n- Avoid common mistakes that weaken your position.\n\n---\n\n## Who this is for\n\n- Contract managers\n- Claims consultants\n- Quantity surveyors\n- Commercial managers\n- Construction lawyers\n- Anyone preparing responses to claims or formal queries under construction contracts\n\n---\n\n## What this skill does\n\nUse this tool to systematically work through 7 key dimensions:\n\n1. **Situation Assessment** — Understand exactly what you are responding to.\n2. **Scope Control** — Decide what to address and what to avoid volunteering.\n3. **Direction Decision** — Choose primary and fallback arguments, and what to avoid.\n4. **Argument Strategy** — Select the strongest type of argument available.\n5. **Disclosure Control** — Decide what to state precisely, keep general, or defer.\n6. **Response Architecture** — Choose the most effective structure for your reply.\n7. **Risk Assessment** — Identify counter-arguments, weak points, and timing risks.\n\nPlus **practical tools and reference guides** covering:\n\n- Record keeping checklists\n- Claim preparation checklists (adjudication & arbitration)\n- Notice requirements compliance\n- Expert engagement guidance\n- ADR strategy (negotiation, mediation, adjudication, arbitration)\n- Concurrent delay strategic approach\n- Disruption claims strategy\n- Delay analysis methods (As-Planned vs As-Built, TIA, Collapsed As-Built, Windows)\n- Arbitration tactics and prolongation strategies\n- Quantum calculation worked examples (Eichleay, Hudson, Emden, Measured Mile, Actual Cost, Total Cost)\n- Legal precedents overview (Prevention Principle, Common Law vs Civil Law)\n- Common pitfalls and how to avoid them\n- Risk assessment framework\n\n---\n\n## Supported contract forms\n\nWorks with any construction contract form:\n- PSSCOC (Construction Works / D&B)\n- FIDIC (Red, Yellow, Silver, Emerald)\n- NEC (NEC3, NEC4)\n- SIA Conditions\n- JCT\n- Bespoke contract conditions\n\n---\n\n## Working out the actual deadline\n\nMost construction claim responses are time-bound. Before using this skill, identify the actual calendar deadline for your response.\n\nFor Singapore matters under the Building and Construction Industry Security of Payment Act (SOPA), or for contracts using calendar-day notice periods (PSSCOC, SIA, FIDIC, NEC), the deadline calculation is not just \"today + N days\". It must account for:\n\n- **Calendar-day counting** — Saturdays count; Sundays and public holidays generally do not, per s.50(a) of the Interpretation Act\n- **In-lieu Mondays** where a public holiday falls on a Sunday\n- **Ad-hoc declared holidays** (e.g. Polling Day) which are not in the standard gazetted list\n\nThe companion skill **construction-law** includes a Singapore SOPA deadline calculator that handles these rules. Calculate the actual deadline there first, then provide the resulting date when prompted by this skill.\n\nIf your contract is governed by a different jurisdiction, apply the equivalent local rule. Do not assume \"calendar day\" means simple date arithmetic — it almost never does.\n\n---\n\n## Start here\n\n### Quick Reference (all strategy patterns)\n\n```bash\npython3 scripts/strategy_advisor.py --reference\n```\n\nOutputs all argument types, disclosure levels, response patterns, scope control rules, and risk checklists in one view.\n\n### Interactive Strategy Session (Recommended)\n\n```bash\npython3 scripts/strategy_advisor.py\n```\n\nThe wizard walks you through all 7 dimensions and produces a structured strategy report.\n\n### Non-Interactive (from JSON)\n\n```bash\npython3 scripts/strategy_advisor.py --file strategy_input.json --output strategy_report.md\n```\n\n### Save Strategy for Reuse\n\n```bash\npython3 scripts/strategy_advisor.py --save-strategy my_strategy.json\n```\n\n---\n\n## Examples\n\nThe `examples/` folder contains a worked scenario demonstrating the full 7-Dimension workflow:\n\n| File | Description |\n|------|-------------|\n| `strategy_input.json` | Sample JSON input — PSSCOC 2014 (7th Edition) EOT scenario |\n| `strategy_report_sample.md` | Generated strategy report from the above input |\n\n**Note:** The example uses **PSSCOC 2014** clause references (Clauses 12.5, 14.2(m), 14.2(n), 22.1(h), 22.1(i), 14.3, 23.1). The **7-Dimension methodology itself is contract-form neutral** — it applies equally to FIDIC, NEC, SIA, JCT, and bespoke contracts. Future versions will include additional worked examples for other contract forms.\n\n---\n\n## Key Concepts\n\n### Argument Strength Ranking\n\n1. **Textual Interpretation** (Strongest) — Argue from the actual wording of the relevant clause in the Contract.\n2. **Factual Distinction** (Strong) — Show that the facts fall outside the clause's scope or trigger conditions.\n3. **Concede-then-Distinguish** (Moderate-Strong) — Acknowledge the normal case, then distinguish the current situation.\n4. **Implied Terms** (Weakest) — Use only as a last resort when no express clause wording supports the position.\n\n### Disclosure Control Levels\n\n| Level | Use for |\n|-------|---------|\n| **State Precisely** | Clause references, formal correspondence, key dates, and legal reasoning |\n| **Keep General** | Operational context and high-level details |\n| **Defer** | Detailed quantification and supporting analysis |\n\n### Recommended Response Patterns\n\n- **Standard Query Response** — acknowledge, pivot, argue, reserve, close\n- **Risk Allocation Rebuttal** — concede ordinary application, distinguish, factual support, legal conclusion, mitigation evidence, close cooperatively\n- **Chronology-Based Response** — state known facts, flag pending items, commit to supplement, reserve\n- **Cost / Quantum Claim Response** — contractual basis, heads of claim, ongoing assessment, commit to detailed breakdown, reserve\n- **Reservation of Rights Closing** — always recommended\n\n### Scope Control Rules\n\n1. **Limit to letter** — respond only to what was asked; do not volunteer unrequested information.\n2. **Preserve future claims** — use \"reserves its position\" and \"without prejudice\" language.\n3. **Keep operational details general** — do not name specific zones or quantities prematurely.\n\n### Common Anti-Patterns to Avoid\n\n- ❌ Citing the wrong clause (e.g., a clause for other contractors when the Employer caused the issue)\n- ❌ Leading with \"the clause doesn't apply\" — this antagonises the other party\n- ❌ Volunteering information about topics not yet raised\n- ❌ Naming specific zones/quantities before they are finalised\n- ❌ Reaching for implied terms when express clause text supports your case\n- ❌ Hedging dates that have formal letter references behind them\n- ❌ Quantifying costs before records are complete\n\n---\n\n## How to use\n\n### CLI options\n\n```\nusage: strategy_advisor [-h] [--file INPUT_JSON] [--output FILE]\n                        [--format {md,txt}] [--save-strategy PATH]\n                        [--reference] [--version]\n\nStrategy Advisor — Strategic planning framework for construction claim\nresponses. Plan your direction, scope, and argument strategy BEFORE selecting\nclauses.\n\noptions:\n  -h, --help            show this help message and exit\n  --file INPUT_JSON     Non-interactive: read strategy inputs from a JSON\n                        file.\n  --output, -o FILE     Write report to file instead of stdout.\n  --format, -f {md,txt}\n                        Output format (default: md).\n  --save-strategy PATH  Save the strategy data as JSON for reuse.\n  --reference           Print all reference tables (argument types, patterns,\n                        etc.) and exit.\n  --version             show program's version number and exit\n```\n\n### Required JSON keys (for `--file` mode)\n\nThe following 6 keys are **required** in the input JSON. If any are missing, the tool exits with a clear error listing what’s needed.\n\n| Key | Description |\n|-----|-------------|\n| `situation_type` | What you’re dealing with (e.g. “Responding to a rejection of our claim”) |\n| `other_side_position` | The other party’s stated position |\n| `trigger_event` | Key facts / what triggered this response |\n| `primary_argument` | Your primary contractual argument |\n| `chosen_argument_type` | Argument type (e.g. “Textual Interpretation”) |\n| `chosen_pattern` | Response architecture pattern (e.g. “Risk Allocation Rebuttal”) |\n\nAll other keys are optional — the tool fills empty fields gracefully. See `examples/strategy_input.json` for a complete example with all 21 supported keys.\n\n### Commands\n\n```bash\n# Show all reference tables\npython3 scripts/strategy_advisor.py --reference\n\n# Run interactive wizard\npython3 scripts/strategy_advisor.py\n\n# Non-interactive from JSON\npython3 scripts/strategy_advisor.py --file input.json --output report.md\n\n# Save strategy for reuse\npython3 scripts/strategy_advisor.py --save-strategy strategy.json\n```\n\n---\n\n## Reference Library\n\nAll reference documents are in the `references/` folder. These are standalone reading material for human use — the `strategy_advisor.py` script does not load them at runtime.\n\n| Document | Description |\n|----------|-------------|\n| `seven_dimensions_guide.md` | Full guide to the 7-Dimension framework |\n| `argument_ranking_guide.md` | Detailed argument types with examples |\n| `worked_examples.md` | 4 complete worked strategy examples (Variation, EOT, Disruption, Combined) |\n| `delay_analysis_study_guide.md` | Comprehensive delay analysis study guide — SCL Protocol 22 principles, 7 analysis methods, concurrent delay, pacing, float, disruption, force majeure, case law |\n| `quantum_worked_examples.md` | 8 quantum calculation examples (Eichleay, Hudson, Emden, Measured Mile, Actual Cost, Total Cost) |\n| `adr_overview.md` | ADR methods comparison and strategy recommendations |\n| `arbitration_tactics.md` | Arbitration tactics and prolongation claim strategies |\n| `concurrent_delay.md` | Concurrent delay — strategic approach within the 7-Dimension framework |\n| `disruption_claims.md` | Disruption claims strategy — Common Law vs Civil Law |\n| `delay_analysis_methods.md` | Delay analysis methods — strategic overview |\n| `legal_precedents.md` | Legal precedents and the Prevention Principle |\n| `notice_requirements_checklist.md` | Notice compliance checklist |\n| `expert_engagement.md` | Expert engagement tips and best practices |\n| `record_keeping_checklist.md` | Printable record keeping checklist |\n| `claim_preparation_checklist.md` | Claim preparation checklist for adjudication & arbitration |\n| `common_pitfalls.md` | 10 most common claim pitfalls and how to avoid them |\n| `risk_assessment_framework.md` | Expanded risk assessment categories and practical questions |\n| `response_template.md` | Letter template mapping strategy to formal response |\n| `quick_reference_card.md` | One-page desk reference card |\n| `blank_worksheet.md` | Printable blank 7-Dimension worksheet |\n| `training_guide.md` | Workshop-ready training material |\n| `strategy_patterns.md` | All strategy patterns reference |\n\n---\n\n## How to use with the construction-law companion skill\n\nThis skill is designed to pair with **construction-law**, which handles clause analysis, notice drafting, and deadline calculation. The typical end-to-end workflow uses both skills in sequence:\n\n1. **Identify the applicable clause and notice period** — use construction-law to look up the relevant contract clause (e.g. EOT notice provision, SOPA payment response window) and the prescribed time limit.\n\n2. **Calculate the actual deadline** — use construction-law’s SOP calculator (or its equivalent for your contract form) to compute the calendar date, accounting for weekends, public holidays, and statutory roll-forward rules. Do not rely on simple date arithmetic.\n\n3. **Plan the response strategy** — use this skill to work through the 7 strategy dimensions. Pass the calculated deadline as the `response_deadline` input.\n\n4. **Draft the response** — return to construction-law for clause-level drafting and formal correspondence templates, using the strategy from step 3 as input.\n\nKeeping strategy and execution in separate skills produces more commercially realistic outputs than trying to combine them. Each skill stays focused on what it does well: this one decides the direction; construction-law executes the analysis and drafting.\n\n---\n\n## Requirements\n\n- Python 3.10+\n- Standard library only — no third-party dependencies\n\n## Tests\n\n```bash\npython3 -m unittest tests.test_smoke\n```\n\n---\n## Security & Safety\n\n- ✅ No network access\n- ✅ No external calls\n- ✅ No subprocess execution\n- ✅ No dynamic code loading\n- ✅ No telemetry: this tool does not collect or transmit usage data\n- ✅ Safe for use with confidential project information\n- ✅ **Safe to install and use** 🛡️\n\n### Files written\n\nThis tool writes files **only** when you pass explicit flags:\n\n| Flag | What is written | Format |\n|------|----------------|--------|\n| `--output FILE` | Strategy report | UTF-8 (Markdown or plain text) |\n| `--save-strategy PATH` | Strategy data for reuse | UTF-8 JSON |\n\nIf neither flag is provided, output is printed to stdout. No files are created, modified, or read beyond the `--file` input (when given).\n\n---\n\n## Changelog\n\n### v1.7.6 (May 2026)\n- **Docs:** Added \"Working out the actual deadline\" section — explains calendar-day counting, s.50(a) roll-forward, ad-hoc holidays; points users to construction-law SOP calculator before running strategy\n- **Docs:** Replaced \"Companion skill\" section with \"How to use with construction-law\" — 4-step end-to-end workflow (identify clause → calculate deadline → plan strategy → draft response)\n- **Wizard:** Response deadline prompt sharpened to nudge toward specific calendar dates and reference the SOP calculator\n- **Design decision:** No cross-skill code coupling. Date math stays in construction-law; strategy planning stays here. Skills are paired via documentation, not imports.\n\n### v1.7.5 (May 2026)\n- **Security:** Sanitised test docstrings and comments — removed function-call patterns (e.g. `compile(...)`) that ClawHub static analysis flagged as `suspicious.dynamic_code_execution`. The actual detection logic uses `ast.parse` and was never affected; the scanner was pattern-matching against English text in comments.\n\n### v1.7.4 (May 2026)\n- **Security:** Replaced string-grep forbidden-imports check with `ast.parse` tree-walking — properly catches `compile(...)`, `exec(...)`, `eval(...)` regardless of whitespace or indirection; no longer false-positives on comments, docstrings, or strings containing those words\n\n### v1.7.3 (May 2026)\n- **Security:** Rewrote `test_smoke.py` to avoid `subprocess.run()` entirely — now imports `main()` directly and patches `sys.argv`. Resolves ClawHub ClawScan `suspicious.dynamic_code_execution` false positive on the test file\n- **Security:** Tightened forbidden-imports list: `urllib.request`/`urllib.error` (not blanket `urllib`), added `importlib`, `pickle`, `marshal`, `compile(`\n- **Performance:** Tests now run in ~0.01s (was ~0.2s with subprocess overhead)\n\n### v1.7.2 (May 2026)\n- **Fix:** Interactive mode now wraps file writes (`--output`, `--save-strategy`) with friendly error messages (consistent with non-interactive mode)\n- **Added:** Required-key validation for `--file` JSON input — missing keys produce a clear error listing what's needed, instead of empty fields\n- **Added:** `_safe_write` helper — unified error handling for all file output paths\n- **Docs:** Added `--help` output to SKILL.md so users can evaluate CLI flags without installing\n- **Docs:** Added explicit \"No telemetry\" statement in Security section\n- **Docs:** Added \"Files written\" section documenting exactly what is written and when\n- **Docs:** Documented the 6 required JSON keys for `--file` mode\n- **Docs:** Changed test instructions to recommend `python3 -m unittest` (stdlib) over `pytest`\n\n### v1.7.1 (May 2026)\n- **Security:** Added `test_no_forbidden_imports` — enforces the \"no network / no subprocess\" claim at test time by scanning for forbidden imports (subprocess, socket, requests, urllib, etc.)\n- **Compatibility:** Updated Python requirement from 3.6+ to 3.10+ (reflects what is actually tested)\n\n### v1.7.0 (May 2026)\n- **Changed:** Replaced example scenario with a realistic PSSCOC EOT case (Contractor responding to SO rejection under Clause 13.2)\n- **Changed:** `strategy_input.json` rewritten with correct flat-key schema matching all 7 dimensions\n- **Changed:** `strategy_report_sample.md` regenerated from actual script output (not hand-written)\n- **Changed:** Improved test docstrings and header matching\n\n### v1.6.1 (May 2026)\n- **Added:** JSON input validation for `--file` mode — checks file exists, valid JSON, root is a dict; warns on unrecognised keys (typo protection)\n- **Added:** File I/O error handling — friendly messages for missing files, permission errors, and malformed JSON (no raw tracebacks)\n- **Removed:** Dead code (`_prompt_yesno` function was defined but never called)\n\n### v1.6.0 (May 2026)\n- **Added:** `examples/strategy_input.json` and `examples/strategy_report_sample.md` — preview output before installing\n- **Added:** `tests/test_smoke.py` — smoke test covering `--reference`, `--file`, and `--version` modes\n- **Added:** `LICENSE` file (MIT-0) shipped at package root\n- **Added:** Requirements section in SKILL.md (Python 3.6+, stdlib only)\n- **Added:** Tests section in SKILL.md\n- **Changed:** Vocabulary normalisation — replaced contract-form-specific terms (\"Authority\", \"Engineer\") with neutral language (\"certifier\", \"the other party\") for consistent applicability across PSSCOC, FIDIC, NEC, SIA, JCT, and bespoke contracts\n- **Changed:** SKILL.md clarifies that `references/` is human reading material, not loaded by the script at runtime\n- **Fixed:** Removed stale reference to `construction_law.py` in module docstring\n- **Fixed:** Removed dead conditional branch in title block of `generate_report`\n\n### v1.5.0 (May 2026)\n- **Added:** Delay Analysis Study Guide — comprehensive reference covering SCL Protocol 22 Core Principles, 7 delay analysis methods (incl. Retrospective Longest Path), negative float & EOT entitlement, concurrent delay (Malmaison, North Midland, City Inn), pacing delays, disruption causation (Walter Lilly test), force majeure vs hardship, COVID-19 lessons, 15 key cases, and full definitions glossary\n- Sanitised from project-specific study guide; all generic content with public case law citations\n- Total reference documents: 22\n\n### v1.4.0 (May 2026)\n- **Major expansion:** Integrated full Construction Claim Strategy Practical Tools Guide v1.4\n- Added: Notice Requirements Checklist\n- Added: Expert Engagement Tips\n- Added: Legal Precedents guide (Prevention Principle, Common Law vs Civil Law)\n- Added: Concurrent Delay — Strategic Approach\n- Added: Disruption Claims Strategy (with Common Law vs Civil Law comparison)\n- Added: Delay Analysis Methods — Strategic Overview (As-Planned vs As-Built, TIA, Collapsed As-Built, Windows)\n- Added: Arbitration Tactics & Prolongation Claim Strategies\n- Added: ADR Overview with Adjudication vs Arbitration detailed comparison\n- Added: Quantum Calculation Worked Examples (8 examples: Eichleay, Hudson, Emden, 2× Measured Mile, Actual Cost, Productivity Loss, Total Cost)\n- Added: Common Claim Pitfalls (10 pitfalls with fixes)\n- Added: Risk Assessment Framework (expanded categories and practical questions)\n- Added: Record Keeping Checklist (printable)\n- Added: Claim Preparation Checklist (printable, adjudication & arbitration)\n- Total reference documents: 21\n\n### v1.3.0 (May 2026)\n- Added argument ranking guide, seven dimensions guide, worked examples\n- Added response template, quick reference card, blank worksheet\n- Added training guide and strategy patterns\n\n### v1.1.0 (May 2026)\n- Fully sanitized — all examples use generic/neutral language\n- Improved interactive wizard with examples and input validation\n- Better README for public listing\n- Added review step before report generation\n\n### v1.0.1 (May 2026)\n- Removed all project-specific references\n- Added disclaimer\n\n### v1.0.0 (May 2026)\n- Initial release — 7 strategy dimensions\n- Interactive wizard mode\n- Non-interactive JSON mode\n- Reference tables dump\n- Strategy save/reload\n\n---\n\n*This is a generic strategic planning tool. It does not constitute legal advice. Users should verify all information independently and seek qualified legal counsel before relying on any analysis for dispute resolution, adjudication, arbitration, or court proceedings.*\n\nFile v1.7.6:_meta.json\n\n{\n  \"ownerId\": \"kn77g2eearfhaq251ab7jtrctn854v1s\",\n  \"slug\": \"construction-claim-strategy\",\n  \"version\": \"1.7.6\",\n  \"publishedAt\": 1779014050649\n}\n\nFile v1.7.6:references/adr_overview.md\n\n# ADR in Construction Claims — Overview & Strategies\n\nAlternative Dispute Resolution (ADR) provides ways to resolve disputes without going to full court litigation. Choosing the right method depends on your goals: speed, cost, finality, cash flow, and relationship preservation.\n\n---\n\n## ADR Methods Comparison\n\n| Method | Description | Binding? | Speed | Cost | Best Used When |\n|--------|-------------|----------|-------|------|---------------|\n| **Negotiation** | Direct discussion between parties | No | Fast | Low | Early stage, good relationship |\n| **Mediation** | Neutral facilitator helps reach settlement | No (usually) | Fast | Low–Medium | Preserve relationship, complex issues |\n| **Adjudication** | Fast interim decision by adjudicator | Yes (usually interim/temporary) | Very Fast | Medium | Cash flow or interim relief needed |\n| **Arbitration** | Private tribunal makes final decision | Yes (final) | Medium–Slow | High | Final resolution, international disputes |\n| **Litigation** | Court proceedings | Yes (final) | Slow | High | Last resort, complex legal points |\n\n---\n\n## ADR Strategy Recommendations\n\n1. **Start with negotiation** where possible — many disputes can be resolved early if approached professionally\n2. **Use mediation** when preserving the commercial relationship is important or when issues are complex\n3. **Consider adjudication** (where available) for fast interim cash flow or time-related decisions\n4. **Choose arbitration** for final, binding resolution, especially in international projects\n5. **Use litigation** generally as a last resort due to cost, time, and relationship impact\n\n---\n\n## Adjudication vs Arbitration — Detailed Comparison\n\n| Aspect | Adjudication | Arbitration |\n|--------|-------------|-------------|\n| **Nature** | Fast interim decision | Final and binding decision |\n| **Speed** | Very fast (usually 28–42 days in statutory regimes) | Slow to medium (6–24 months) |\n| **Cost** | Relatively low | High |\n| **Binding** | Binding until finally determined by arbitration or litigation | Final and binding |\n| **Enforceability** | Enforceable in jurisdictions with statutory adjudication | Enforceable internationally (New York Convention) |\n| **Right of appeal** | Limited (usually only jurisdiction or natural justice) | Limited, depends on seat of arbitration |\n| **Procedure** | Relatively informal and fast | More formal, similar to litigation |\n| **Evidence** | Often limited written submissions | Full hearing with witnesses and experts |\n| **Relationship impact** | Can be less damaging if used early | Often more adversarial |\n\n### When to Choose Adjudication\n\n- Need **quick cash flow** relief\n- Want to keep the project moving during dispute resolution\n- Dispute is relatively straightforward\n- Available under a statutory regime or contract\n\n### When to Choose Arbitration\n\n- Need a **final and binding** decision\n- Dispute is complex, high-value, or multi-issue\n- International enforceability matters\n- Parties can choose arbitrators with relevant expertise\n\n---\n\n## Decision Guide\n\n| Your Goal | Recommended Route |\n|-----------|-------------------|\n| Need money / relief quickly | **Adjudication** (if available) |\n| Want a final and binding decision | **Arbitration** |\n| Want to preserve commercial relationship | Start with **Negotiation → Mediation** |\n| High-value, complex, international dispute | **Arbitration** |\n| Domestic dispute needing fast interim relief | **Adjudication** |\n\n---\n\n## Common Law vs Civil Law Perspective\n\n| Aspect | Common Law | Civil Law |\n|--------|-----------|-----------|\n| **Adjudication** | Very common (often statutory) | Less common (more voluntary) |\n| **Arbitration** | Widely used | Very widely used |\n| **Preference** | Often adjudication first, then arbitration | Tend to go straight to arbitration or mediation |\n| **Statutory support** | Strong statutory regimes for adjudication | Generally rely on contractual ADR clauses |\n\n---\n\n*This is a generic reference guide. It does not constitute legal advice.*\n\nFile v1.7.6:references/arbitration_tactics.md\n\n# Arbitration Tactics & Prolongation Claim Strategies\n\n---\n\n## Arbitration Tactics — Common Law vs Civil Law\n\n### Common Law Arbitrations\n\n- Heavy emphasis on **contemporaneous documents**, detailed witness statements, and expert reports\n- Cross-examination is often rigorous — be prepared to defend methodology and credibility in detail\n- Broader **document disclosure** is common; failure to disclose can damage credibility\n- Significant reliance on **case law and precedents** in areas such as notice, prevention principle, and quantum methods\n- **Strategy:** Build a document-heavy, precedent-supported case with strong expert evidence\n\n### Civil Law / Mixed Arbitrations\n\n- Greater emphasis on overall **fairness, good faith, and commercial equity**\n- Cross-examination may be less confrontational, depending on tribunal and rules\n- Disclosure is usually **narrower**\n- More reliance on principles of good faith and fairness than strict precedent\n- **Strategy:** Combine strong factual evidence with clear arguments on equity and the parties' reasonable expectations\n\n---\n\n## Comparison Table\n\n| Aspect | Common Law Arbitration | Civil Law / Mixed Arbitration |\n|--------|----------------------|------------------------------|\n| Documents | Heavy reliance; broad disclosure | Narrower disclosure |\n| Witnesses | Detailed statements; rigorous cross-exam | Less confrontational |\n| Experts | Essential for complex claims | Important but approach may differ |\n| Precedents | Key part of submissions | Persuasive but less central |\n| Good faith | Developing | Central principle |\n| Strategy focus | Document + precedent | Equity + evidence |\n\n---\n\n## Prolongation Claim Strategies in Arbitration\n\n### Common Law Approach\n\n- Strong focus on proving **EOT first** (critical path impact) before claiming prolongation costs\n- Expect detailed scrutiny of quantum methods and baseline assumptions\n- Concurrent delay arguments are common and must be addressed **proactively**\n- **Strategy:** Secure the EOT foundation first, then build a well-supported prolongation claim — preferably based on actual costs with formula methods as fallback\n\n### Civil Law Approach\n\n- The link between EOT and prolongation costs may be assessed **more flexibly**, depending on governing law and tribunal approach\n- Actual costs remain preferred, but good faith and fairness arguments may help bridge gaps in strict causation proof\n- **Strategy:** Emphasise the overall impact and equity of the situation while still providing clear cost evidence\n\n---\n\n## Practical Recommendations\n\n1. **Know your tribunal** — research the arbitrators' backgrounds and preferred approaches\n2. **Prepare for cross-examination** — ensure witnesses and experts are thoroughly prepared\n3. **Disclosure strategy** — balance completeness with risk of revealing unhelpful documents\n4. **Quantum foundation** — always anchor prolongation to a clear EOT finding\n5. **Address concurrent delay proactively** — don't leave it for the other side to raise\n6. **Clear visuals** — timelines, charts, and cost summaries are often more effective than dense narrative\n\n---\n\n*This is a generic strategic guide. It does not constitute legal advice.*\n\nFile v1.7.6:references/argument_ranking_guide.md\n\n# Argument Ranking — Detailed Guide\n\n*Construction Claim Strategy Framework — Fully Generic*\n\n---\n\n## Why the Ranking Exists\n\nNot all arguments carry the same weight. Stronger arguments are harder to rebut and more likely to be accepted by tribunals, adjudicators, and courts. Weaker arguments are easier to challenge.\n\nAlways start from the top of the ranking. Only move down when stronger options are unavailable.\n\n---\n\n## Rank 1: Textual Interpretation (Strongest)\n\n**What it is:**\nArgue directly from the actual words used in the Contract clause.\n\n**Why it is strongest:**\n- Based on express terms the parties agreed to.\n- Most objective and difficult for the other side to dismiss.\n- Tribunals and courts prefer to give effect to clear wording.\n\n**When to use:** Whenever the wording of the clause supports your position.\n\n**Example structure:**\n> The Contract provides that the Contractor shall be entitled to [entitlement] where the Authority issues an instruction which changes the scope of the Works.\n> On [date], the Authority issued Instruction No. X which required the Contractor to [specific change]. This instruction directly changed the scope.\n> Accordingly, the Contractor is entitled to [relief] pursuant to the clear wording of the clause.\n\n**Recommended disclosure level:** State Precisely — you can be confident and specific.\n\n---\n\n## Rank 2: Factual Distinction (Strong)\n\n**What it is:**\nAccept that the clause exists, but argue that the facts of your case fall outside the situation the clause was intended to cover.\n\n**Why it is strong:**\nStays close to the Contract wording while showing why the clause does not apply to the current situation.\n\n**When to use:** When the clause wording is not clearly in your favour, but the facts are materially different from what the clause contemplates.\n\n**Example structure:**\n> While the Contract contains provisions regarding [subject], those provisions are predicated on the assumption that [normal situation].\n> In the present case, the situation is materially different because [key factual difference].\n> Accordingly, the clause does not operate to [deny the claim / allocate risk in the way suggested].\n\n**Recommended disclosure level:** State Precisely or Keep General — be precise on facts that support the distinction.\n\n---\n\n## Rank 3: Concede-then-Distinguish (Moderate-Strong)\n\n**What it is:**\nConcede that the clause would normally apply, then explain why the current situation is extraordinary or materially different.\n\n**Why it is moderate-strong:**\nShows reasonableness (not denying the clause entirely), while still protecting your position.\n\n**When to use:** When the clause appears to go against you at first glance, but there are good reasons why it should not apply in this specific case.\n\n**Example structure:**\n> The Contractor acknowledges that, in normal circumstances, [risk] would be allocated to the Contractor under the Contract.\n> However, the present situation is materially different. The Authority [did X / failed to do Y / provided incorrect information], which fundamentally changed the nature of the risk.\n> In these exceptional circumstances, it would be inconsistent with the Contract for the risk to remain with the Contractor.\n> Accordingly, the Contractor is entitled to [relief].\n\n**Recommended disclosure level:** Keep General — be careful not to over-disclose internal thinking.\n\n---\n\n## Rank 4: Implied Terms / Prevention Principle (Weakest)\n\n**What it is:**\nArgue that a term should be implied into the Contract, or that the Authority's actions prevented you from performing.\n\n**Why it is weakest:**\n- Implied terms are harder to prove.\n- Prevention principle is heavily contested.\n- Moves away from express Contract words.\n- Easier for the other side to challenge.\n\n**When to use:** Only as a last resort, when none of the stronger arguments are available.\n\n**Example structure:**\n> It is a well-established principle that a party to a contract must not do anything to prevent the other party from performing its obligations.\n> In this case, the Authority's [action / inaction / instruction] had the effect of preventing the Contractor from [completing the works / mitigating losses].\n> As a result, the Contractor is entitled to [relief].\n\n**Note:** More commonly used in Common Law jurisdictions. In Civil Law systems, similar concepts exist under good faith (*bonne foi* / *Treu und Glauben*).\n\n**Recommended disclosure level:** Keep General — these arguments are more vulnerable.\n\n---\n\n## How to Choose\n\n| Rank | Argument Type | Strength | When to Use | Recommendation |\n|------|---|---|---|---|\n| 1 | Textual Interpretation | Strongest | Clause wording supports your position | Use first |\n| 2 | Factual Distinction | Strong | Facts are materially different | Strong backup |\n| 3 | Concede-then-Distinguish | Moderate-Strong | Clause appears unfavourable but facts are exceptional | Use carefully |\n| 4 | Implied Terms / Prevention | Weakest | No better argument available | Last resort |\n\n---\n\n## Combining Arguments (Primary + Fallback)\n\nYou can and often should use a primary + fallback approach in the same response.\n\n**Recommended structure:**\n1. Lead with the strongest available argument.\n2. Clearly signal the fallback.\n3. Use clear paragraph breaks or numbering.\n\n**Example — Textual Interpretation + Factual Distinction:**\n\n> **Primary Position — Textual Interpretation**\n> The Contract states that the Contractor is entitled to additional time and cost where the Authority issues an instruction which varies the Works. The Authority's Instruction dated [X] required the Contractor to [change]. This falls squarely within the wording of the clause.\n>\n> **Alternative Position — Factual Distinction**\n> Without prejudice to the above, even if the clause were interpreted more restrictively, the facts of this case are materially different from the normal situation contemplated by the Contract. At the time of the instruction, [key fact that makes it different]. Accordingly, the clause does not operate to exclude the Contractor's entitlement.\n\n---\n\n## Argument Strength ↔ Disclosure Control Interaction\n\n| Argument Type | Strength | Disclosure Level | Reason |\n|---|---|---|---|\n| Textual Interpretation | Strongest | State Precisely | Position is robust; confidence is high |\n| Factual Distinction | Strong | State Precisely / Keep General | Precise on supporting facts |\n| Concede-then-Distinguish | Moderate-Strong | Keep General | Partial concession; don't over-disclose |\n| Implied Terms / Prevention | Weakest | Keep General | Vulnerable; avoid giving material to attack |\n\n**Rule:** Stronger arguments → more precise disclosure. Weaker arguments → more general disclosure. Always apply scope control regardless.\n\n---\n\n*This is a workflow and analysis aid only. It does not constitute legal advice.*\n\nFile v1.7.6:references/blank_worksheet.md\n\n# Blank Strategy Worksheet\n\n**Construction Claim Strategy — Quick Worksheet**\n\n**Date:** _______________\n**Claim / Query Type:** _______________\n\n---\n\n## 1. Situation Assessment\nWhat exactly are we responding to?\n\n____________________________________________________________________________\n\n## 2. Scope Control\n**Must address:**\n\n____________________________________________________________________________\n\n**Must avoid:**\n\n____________________________________________________________________________\n\n## 3. Direction Decision\n**Primary argument:**\n\n____________________________________________________________________________\n\n**Fallback argument:**\n\n____________________________________________________________________________\n\n**Arguments to avoid:**\n\n____________________________________________________________________________\n\n## 4. Argument Strategy\nChosen argument type:\n☐ Textual Interpretation (Strongest)\n☐ Factual Distinction (Strong)\n☐ Concede-then-Distinguish (Moderate-Strong)\n☐ Implied Terms (Weakest — last resort)\n\nReason:\n\n____________________________________________________________________________\n\n## 5. Disclosure Control\n\n| Level | What to include |\n|---|---|\n| **State Precisely** | |\n| **Keep General** | |\n| **Defer** | |\n\n## 6. Response Architecture\nChosen structure:\n☐ Standard Query Response\n☐ Risk Allocation Rebuttal\n☐ Chronology-Based Response\n☐ Cost / Quantum Claim Response\n\nReason:\n\n____________________________________________________________________________\n\n## 7. Risk Assessment\nMain risks / counter-arguments:\n\n____________________________________________________________________________\n\nHow to address them:\n\n____________________________________________________________________________\n\n---\n\n**Next Step:** Use this completed worksheet to draft the formal response.\n\n*Plan → Strategise → Draft*\n\nFile v1.7.6:references/claim_preparation_checklist.md\n\n# Claim Preparation Checklist\n\nUse this checklist when preparing claims for Adjudication or Arbitration. Thorough preparation significantly improves outcomes.\n\n---\n\n**Project:** _______________________________ **Claim Type:** _______________\n\n## Phase 1: Strategy & Planning\n\n- [ ] Reviewed the contract dispute resolution clause\n- [ ] Completed the 7-Dimension Strategy Worksheet\n- [ ] Identified the main heads of claim (EOT, disruption, variation, prolongation, acceleration)\n- [ ] Decided whether to submit claims separately or combined\n\n## Phase 2: Evidence Collection\n\n- [ ] Compiled a clear chronology of events\n- [ ] Collected and organised all relevant correspondence\n- [ ] Gathered all notices with proof of submission\n- [ ] Collected programme, progress, and site records\n- [ ] Gathered cost and quantum supporting documents\n- [ ] Identified and addressed any gaps in records\n\n## Phase 3: Claim Development\n\n- [ ] Prepared a clear summary of the claim\n- [ ] Developed Primary and Fallback arguments\n- [ ] Prepared quantum calculation with clear methodology\n- [ ] Identified and prepared witnesses, if required\n- [ ] Engaged experts (delay analyst, quantum expert, technical expert) if needed\n\n## Phase 4: Risk Assessment & Review\n\n- [ ] Conducted honest Risk Assessment of own case\n- [ ] Identified likely counter-arguments from the other side\n- [ ] Reviewed and strengthened weak areas\n- [ ] Finalised disclosure strategy\n\n## Phase 5: Final Preparation & Submission\n\n- [ ] Prepared position paper / submissions\n- [ ] Organised document bundle, indexed and paginated\n- [ ] Prepared opening statement / summary\n- [ ] Conducted internal review\n- [ ] Submitted on time\n\n## Adjudication-Specific Items\n\n- [ ] Kept submissions concise and focused\n- [ ] Prioritised speed and clarity\n\n## Arbitration-Specific Items\n\n- [ ] Prepared more detailed and comprehensive submissions\n- [ ] Arranged witness statements and expert evidence\n- [ ] Planned for possible hearings\n\n**Prepared by:** ___________________________ **Date:** _______________\n\n---\n\n*This is a generic checklist. It does not constitute legal advice.*\n\nFile v1.7.6:references/common_pitfalls.md\n\n# Common Claim Pitfalls & How to Avoid Them\n\nMost claims fail or are significantly weakened due to **process issues** rather than weak facts.\n\n---\n\n## The 10 Most Common Pitfalls\n\n| # | Pitfall | Why It's Harmful | How to Avoid |\n|---|---------|-----------------|--------------|\n| 1 | **Jumping straight to drafting** without proper strategy | Leads to weak arguments and poor structure | Complete the 7-Dimension Strategy Worksheet first |\n| 2 | **Volunteering unrequested information** | Creates new issues or admissions the other side can exploit | Apply strict Scope Control — respond only to what was asked |\n| 3 | **Using the weakest argument first** | Damages credibility from the outset | Follow the argument ranking: Textual → Factual → Concede-then-Distinguish → Implied Terms |\n| 4 | **Over-disclosing sensitive information too early** | Gives the other side material to attack your position | Match disclosure level to argument strength; defer where appropriate |\n| 5 | **Mixing EOT and disruption claims** without clear separation | Creates confusion and weakens both claims | Keep them clearly separated unless both are genuinely present and can be distinguished |\n| 6 | **Quantifying costs or delay before records are complete** | Numbers can be attacked if not fully supported | Defer detailed quantum until records are complete |\n| 7 | **Ignoring or missing contractual notice requirements** | Claim can be time-barred or rejected | Check notice provisions early in Risk Assessment; use the Notice Requirements Checklist |\n| 8 | **Using a poor or aggressive tone** in correspondence | Damages commercial relationship and credibility | Use professional, factual language throughout |\n| 9 | **Failing to include a reservation of rights** | Can limit future claims or entitlements | Always include a clear Reservation of Rights |\n| 10 | **Not conducting honest risk assessment** before submitting | Surprised by strong counter-arguments later | Complete the Risk Assessment dimension honestly |\n\n## Key Prevention\n\nComplete the **7-Dimension Strategy** first and apply strict **Scope Control** and **Disclosure Control**.\n\n---\n\n*This is a generic reference guide. It does not constitute legal advice.*\n\nFile v1.7.6:references/concurrent_delay.md\n\n# Concurrent Delay — Strategic Approach\n\nConcurrent delay occurs when two or more independent delay events — typically one caused by the Contractor and one by the Employer/Authority — overlap in time and both are alleged to affect the completion date.\n\nIt is one of the most complex and disputed areas in construction claims.\n\n---\n\n## Why Concurrent Delay Matters Strategically\n\n- It directly impacts **Extension of Time** entitlement and **liquidated damages** exposure\n- It affects **prolongation cost claims**\n- Different jurisdictions apply **different approaches**, creating strategic risk if not handled correctly\n- Poor handling of concurrent delay is a common reason claims are **reduced or rejected** in adjudication and arbitration\n\n---\n\n## Common Approaches\n\n### Common Law Jurisdictions\n\nApproaches vary and may include:\n- **Dominant cause** — which delay had the greater impact?\n- **Apportionment** — split responsibility between the parties\n- **First-in-time / prevention principle** — the first cause takes precedence\n\nThe applicable approach must be checked against the governing law and contract terms.\n\n### Civil Law Jurisdictions\n\n- More reliance on **good faith and fairness**\n- Tribunals may look at overall impact and whether one party's actions prevented the other from mitigating delay\n- Less rigid adherence to a single analysis method\n\n---\n\n## Strategic Recommendations — 7-Dimension Framework\n\n### 1. Situation Assessment & Risk Assessment\n\n- Identify all delaying events early and classify them as **Employer-caused**, **Contractor-caused**, or **neutral**\n- Analyse periods of potential concurrency and document them\n- Assess the risk of the other side arguing concurrency to reduce EOT or impose liquidated damages\n\n### 2. Argument Strategy\n\n- **Primary:** Use strong factual evidence to show Employer delay events were on the critical path and that Contractor delays did not cause overall delay\n- **Fallback:** Argue for apportionment or prevention/good faith reasoning if full EOT is not accepted\n- **Avoid** weak global arguments — be specific about which events caused which delay\n\n### 3. Disclosure Control\n\n- Be careful with full programme disclosure if it shows Contractor-caused delays — seek legal advice on what must be disclosed\n- Clearly separate Employer-caused delay from Contractor-caused delay in submissions\n\n### 4. Response Architecture\n\n- **Proactively** address potential concurrency arguments rather than waiting for the other side to raise them\n- Use clear diagrams or summaries showing critical path and overlapping periods\n\n---\n\n## Practical Tips\n\n- Maintain detailed and updated programmes throughout the project\n- Use a consistent delay analysis method and be prepared to justify it\n- In international arbitration, be ready to explain which approach should apply based on governing law and contract\n- Consider engaging a delay expert early if concurrency is likely to be a major issue\n\n---\n\n*This is a generic strategic guide. It does not constitute legal advice.*\n\nFile v1.7.6:references/delay_analysis_methods.md\n\n# Delay Analysis Methods — Strategic Overview\n\nDelay analysis is the process of investigating the causes and effects of delays on a construction project. The method chosen can significantly impact the strength of an Extension of Time or prolongation claim.\n\n---\n\n## Main Delay Analysis Methods\n\n### As-Planned vs As-Built\n\nCompares the original baseline programme with actual progress.\n\n- **Strengths:** Simple, easy to understand\n- **Weaknesses:** Can be challenged if the baseline was unrealistic\n- **Best for:** Simple delay scenarios with a clear baseline\n\n### Time Impact Analysis (TIA)\n\nAdds delay events one by one to an updated programme to show the impact at the time they occurred.\n\n- **Strengths:** Generally considered robust and widely accepted\n- **Weaknesses:** Requires good contemporaneous programme records; can be complex\n- **Best for:** Complex projects with multiple delay events\n\n### Collapsed As-Built / But-For Analysis\n\nRemoves delay events from the as-built programme to show what the completion date would have been \"but for\" those events.\n\n- **Strengths:** Uses actual as-built data\n- **Weaknesses:** Retrospective; can be challenged on assumptions about what \"would have\" happened\n- **Best for:** Post-completion analysis\n\n### Windows Analysis\n\nDivides the project into time windows and analyses delays within each window.\n\n- **Strengths:** Useful for complex projects with multiple issues; can isolate periods of delay\n- **Weaknesses:** Complex; window boundaries can be disputed\n- **Best for:** Large, complex projects with multiple overlapping events\n\n---\n\n## Method Comparison\n\n| Method | Complexity | Reliance on Programme | Timing | Acceptance |\n|--------|------------|----------------------|--------|------------|\n| As-Planned vs As-Built | Low | Baseline + As-built | Post-completion | Moderate |\n| Time Impact Analysis | High | Updated programmes | Prospective | High |\n| Collapsed As-Built | Medium | As-built | Retrospective | Moderate-High |\n| Windows Analysis | High | Updated programmes | Either | High |\n\n---\n\n## Strategic Considerations — Common Law vs Civil Law\n\n### Common Law\n\n- Often a strong preference for methods that demonstrate **causation at the time the delay occurred** (e.g. TIA)\n- Tribunals may expect a clear link between specific events and critical path impact\n\n### Civil Law\n\n- The approach may be more **flexible and pragmatic**\n- Tribunals may focus on overall fairness, good faith, and whether the claimed events genuinely impacted progress\n- Analysis must still be logical and supported by contemporaneous records\n\n---\n\n## Strategic Recommendations\n\n1. Choose a method appropriate to the **project complexity** and **quality of available records**\n2. Be **consistent** — changing methods mid-claim without good reason damages credibility\n3. In common law jurisdictions, be prepared to defend the method by reference to established practice\n4. In civil law or international arbitration, focus on demonstrating overall impact and fairness while still providing clear analysis\n5. **Maintain and update the programme contemporaneously** — this is the foundation of credible delay analysis\n\n---\n\n*This is a generic strategic guide. It does not constitute legal advice.*\n\nFile v1.7.6:references/delay_analysis_study_guide.md\n\n# Delay Analysis Study Guide for Contract Managers\n\nPractical study notes for delay analysis in construction and infrastructure projects.\n\n**Sources:** SCL Delay and Disruption Protocol 2nd Edition (February 2017) + Rider 1 (February 2022), AACEi Recommended Practice 29R-03, published case law.\n\n> **Caution:** Always confirm which contract edition applies before relying on any clause references. This guide does not constitute legal advice.\n\n---\n\n## Part 1: What Is Delay Analysis?\n\nDelay analysis is the process of identifying what caused a project delay, who is responsible, and what the time/cost consequences are.\n\nIt answers two distinct questions:\n1. **Is the contractor entitled to an Extension of Time (EOT)?** — a time question\n2. **Is the contractor entitled to compensation?** — a money question\n\nThese are linked but separate inquiries (see SCL Principle 12).\n\n---\n\n## Part 2: Key Concepts\n\n### 2.1 Delay vs Disruption vs Prolongation\n\n| Concept | What It Is | Result | Claim Type |\n|---------|-----------|--------|------------|\n| **Delay** | Activity takes longer than planned or starts late | Critical path pushed → later completion | EOT (time) |\n| **Disruption** | Reduced productivity / efficiency — more resources needed per unit of work | Additional cost, may or may not affect completion date | Money (cost) |\n| **Prolongation** | Extended presence on site due to delay | Additional preliminaries, site overheads | Money (cost) |\n\n**Key distinction:** You can have disruption WITHOUT delay (if the affected activity is not on the critical path). You can also have delay WITHOUT disruption (if the activity simply stops).\n\n### 2.2 Types of Delay\n\n| Type | Who Bears Risk | EOT? | Compensation? |\n|------|---------------|------|---------------|\n| **Employer Risk Event** (late instructions, design changes, site access) | Employer | ✓ Yes | ✓ Yes (usually) |\n| **Neutral/Excusable Event** (exceptionally adverse weather, force majeure) | Shared | ✓ Yes | ✗ Usually not |\n| **Contractor Risk Event** (poor planning, resource shortages) | Contractor | ✗ No | ✗ No |\n| **Concurrent Delay** (employer + contractor delays at same time) | Complex | ✓ Yes (SCL view) | Debatable — see 2.4 |\n\n**Excusable vs Compensable:** An excusable delay relieves the contractor from LD (i.e. EOT). A compensable delay additionally entitles the contractor to money. All compensable delays are excusable, but not all excusable delays are compensable.\n\n### 2.3 Critical Path & Float\n\nThe **critical path** is the longest sequence of activities that determines the project completion date. Only delays to activities on the critical path will actually delay the project.\n\n**Float** = the time an activity can slip without affecting the critical path.\n\n**Who owns the float?** The SCL Protocol says float should generally be available to the project (not owned by either party) unless the contract says otherwise.\n\n#### Understanding Float Types\n\n| Float Type | What It Means | EOT Implication |\n|-----------|---------------|-----------------|\n| **Positive Float** | Activity has buffer — can slip without delaying completion | Employer delay may consume float before affecting critical path |\n| **Zero Float** | Activity is on the critical path — any delay directly delays completion | Every day of employer delay = one day of EOT entitlement |\n| **Negative Float** | Projected completion already exceeds contract completion date | EOT can still be claimed for employer risk events — see below |\n\n#### Negative Float & EOT Entitlement\n\nNegative float does **NOT** bar an EOT claim. Negative float occurs when the programme's projected completion date already exceeds the contract completion date, even before a new delay event arises. This is common on complex infrastructure projects.\n\nThe SCL Protocol (Principles 6, 7 and 10) requires that each delay event be assessed for its own **incremental impact** on the critical path. If an employer risk event extends the completion date by a further 2 weeks — even where the programme already shows negative float — that 2-week impact remains an employer-caused delay.\n\n**Three practical scenarios:**\n\n- **Scenario 1 — Negative float from contractor delays:** The contractor still claims EOT for any employer risk event's incremental impact. Time Impact Analysis (TIA) handles this best.\n- **Scenario 2 — Negative float from employer delays:** This strengthens the EOT position. The employer delay events that drove the programme into negative float are themselves grounds for EOT.\n- **Scenario 3 — Concurrent delay with negative float:** The most complex scenario. Under the *Malmaison* approach, the contractor still gets EOT to protect against LDs but may not recover prolongation costs for the concurrent period.\n\n**Bottom line:** Float status (positive, zero, or negative) does not determine EOT entitlement. It is the **cause and incremental impact** of each delay event that matters.\n\n#### Terminal Float\n\nTerminal float is the gap between the contractor's planned completion date and the contract completion date.\n\nPer SCL Protocol Principle 13 (Early Completion): if the contractor planned to finish early and an employer delay consumes that terminal float, the contractor may still have a **compensation claim** for disruption to its planned programme — even if the contract date has not been breached.\n\n### 2.4 Concurrent Delay\n\n**SCL Protocol position:** Where employer delay is concurrent with contractor delay → contractor gets EOT (to protect from LD). But contractor may **NOT** recover prolongation costs for the concurrent period. This is the *Malmaison* approach (*Henry Boot v Malmaison* [1999]).\n\n#### Three Critical Nuances\n\n**Nuance 1 — True Concurrent vs Sequential Concurrent**\n\nTrue concurrent delay means two delay events start and end at the same time, both independently affecting the critical path. Sequential concurrent delay means the events overlap but do not start together. Tribunals apply the *Malmaison* approach more readily to true concurrent delay; sequential concurrent delay is often analysed by isolating each event's impact via TIA.\n\n**Nuance 2 — Contractual Allocation**\n\nThe *Malmaison* default can be contracted out. In *North Midland Building Ltd v Cyden Homes Ltd* [2018] EWCA Civ 1744, the English Court of Appeal upheld a contract clause that expressly excluded EOT where contractor delay was concurrent with employer delay. Parties are free to allocate the risk of concurrent delay as they choose.\n\n**Practical action:** Read the EOT clause carefully. Some bespoke amendments may include a \"contractor caused concurrent delay\" carve-out that strips the contractor of EOT entitlement. If found, raise this with management early — it is a major risk allocation issue.\n\n**Nuance 3 — Apportionment Approach**\n\nIn *City Inn Ltd v Shepherd Construction Ltd* [2010] CSIH 68, the Scottish courts took a different view: where it is impossible to say which delay was \"dominant\", the tribunal can apportion the EOT between employer and contractor causes (e.g. 60/40). This approach has not been adopted in English courts but remains influential and may be argued in arbitration.\n\n**Practical tip:** Always try to separate and identify each delay cause individually. Strong contemporaneous records are the best defence against concurrent delay arguments.\n\n### 2.5 Pacing Delays\n\n**What is pacing?** Pacing occurs when one party (usually the contractor) deliberately slows non-critical work to match the pace of the other party who is causing the critical path delay. It is a rational business decision.\n\n**Why it matters:** Pacing is **not** a contractor culpable delay. But it is frequently mischaracterised as one — especially in retrospective analysis.\n\n**How to prove pacing:**\n- Issue contemporaneous notice that you are pacing in response to the specific employer delay event\n- Identify the employer delay event you are pacing (cite notice/event reference)\n- Show the activity being paced was not on the critical path but for the employer delay\n- Demonstrate you had the resources and capability to proceed at planned pace\n- Confirm pacing did not extend the project completion date beyond the employer delay impact\n\n**Quick test:** \"Could I have proceeded at planned pace if the employer delay event had not occurred?\" If YES → pacing. If NO → genuine contractor delay.\n\n---\n\n## Part 3: The SCL Protocol — 22 Core Principles\n\n> References are to the SCL Delay and Disruption Protocol, 2nd Edition (February 2017), as supplemented by Rider 1 (February 2022). Rider 1 added guidance on COVID-19, BIM, concurrent delay analysis, and the relationship between EOT and compensation.\n\n| # | Principle | Key Point |\n|---|-----------|-----------|\n| 1 | **Programme & Records** | Maintain a proper baseline programme and comprehensive contemporaneous records. No records = no claim. |\n| 2 | **Purpose of EOT** | EOT relieves the contractor from LD liability and preserves the employer's right to levy LD. |\n| 3 | **Contractual Requirements** | Comply with notice requirements strictly. Late notice can be a time-bar. |\n| 4 | **Do NOT \"Wait and See\"** | Analyse delay impact contemporaneously. Prospective analysis is preferred over retrospective. |\n| 5 | **Procedure for Granting EOT** | Contract Administrator should assess and grant EOT promptly. |\n| 6 | **Effect of Delay** | Distinguish between employer risk events and contractor risk events. |\n| 7 | **Incremental Review** | Review EOT entitlement incrementally as delay events occur. |\n| 8–9 | **Float** | Float belongs to the project, not one party. See Section 2.3 for negative float. |\n| 10 | **Concurrent Delay & EOT** | Contractor entitled to EOT for employer delay even if concurrent with contractor delay. |\n| 11 | **Time-Distant Analysis** | Use recognised methods for retrospective analysis (see Part 4). |\n| 12 | **EOT ≠ Compensation** | EOT entitlement does not automatically mean compensation. |\n| 13 | **Early Completion** | Employer delay consuming terminal float may still entitle contractor to compensation. |\n| 14 | **Concurrent Delay & Compensation** | Contractor may not recover prolongation costs during concurrent delay periods. |\n| 15 | **Mitigation** | Both parties have mitigation obligations. |\n| 16 | **Acceleration** | Directed → compensation. Voluntary → own cost. Constructive → may claim costs (notify first!). |\n| 17 | **Global Claims** | Permissible only when impracticable to separate causes/effects. Courts are sceptical. |\n| 18 | **Disruption** | Distinct from delay. Prove using measured mile, project-specific study, earned value, or industry studies. |\n| 19 | **Variations** | Variations can cause both time and cost impact. Consider disruptive effect. |\n| 20 | **Prolongation Costs** | Based on actual additional cost incurred due to extended time on site. |\n| 21 | **Tender Allowances** | Actual cost, not tender rates, should be the basis for prolongation compensation. |\n| 22 | **Period of Evaluation** | Assess compensation for the period the delay actually affected. |\n\n---\n\n## Part 4: Delay Analysis Methods\n\n### Method Frameworks\n\nTwo recognised frameworks:\n- **SCL Protocol** (UK) — identifies six delay analysis methodologies\n- **AACEi Recommended Practice 29R-03** (US) — classifies methods using a 9-method matrix\n\nBoth are accepted in international arbitration.\n\n### Overview — Seven Methods\n\n| Method | When Used | Prospective/Retrospective | Complexity |\n|--------|-----------|--------------------------|------------|\n| **As-Planned vs As-Built** | Simple comparison | Retrospective | Low |\n| **Impacted As-Planned** | Add delay events to baseline | Prospective | Medium |\n| **Collapsed As-Built (But-For)** | Remove delay events from as-built | Retrospective | Medium-High |\n| **Time Impact Analysis (TIA)** | Insert delay events at time they occurred | Both | High |\n| **Windows Analysis** | Divide project into time windows | Both | High |\n| **Retrospective Longest Path** | Trace longest path on as-built | Retrospective | Medium |\n\n### As-Planned vs As-Built\n- Compare the original programme to what actually happened\n- **Pros:** Simple, easy to understand\n- **Cons:** Doesn't show causation; doesn't account for logic changes\n- **Best for:** Initial overview or simple disputes\n\n### Impacted As-Planned\n- Start with the baseline programme; add delay events as constraints\n- **Pros:** Forward-looking; easy to model\n- **Cons:** Assumes baseline was realistic; doesn't consider actual progress\n- **Best for:** Early-stage EOT applications\n\n### Collapsed As-Built (But-For)\n- Start with the as-built programme; remove delay events\n- **Pros:** Based on what actually happened\n- **Cons:** Difficult to reconstruct; subjective removal of events\n- **Best for:** Post-completion claims\n\n### Time Impact Analysis (TIA) — Preferred Method\n- Insert each delay event into the programme at the time it occurred\n- Analyse the critical path impact of each event progressively\n- **Pros:** Most rigorous; shows causation; accepted by tribunals; handles negative float correctly\n- **Cons:** Resource-intensive; requires good records and updated programmes\n- **Best for:** Complex projects, especially where negative float is present\n\n### Windows Analysis\n- Divide the project into time \"windows\" (e.g. monthly or by milestone)\n- Analyse the critical path and delays within each window\n- **Pros:** Systematic; handles concurrent delays well\n- **Cons:** Window boundary selection is subjective; very resource-intensive\n- **Best for:** Large projects with many delay events\n\n### Retrospective Longest Path Analysis\n- Identify the longest path on the as-built programme (the actual critical path)\n- Walk back through the activities and identify what delayed each one\n- **Pros:** Grounded in what actually happened; intuitive; useful when baseline is disputed\n- **Cons:** May ignore parallel critical paths; can miss delays absorbed by float\n- **Best for:** Disputes where the baseline programme is challenged\n\n### Choosing a Method\n\n**For prospective/ongoing analysis:**\n- Time Impact Analysis — insert delay events as they occur\n- Impacted As-Planned — for quick early-stage EOT applications\n\n**For retrospective/post-completion analysis:**\n- Windows Analysis — if many delay events across the project\n- Collapsed As-Built — if isolating specific employer delay events\n- Retrospective Longest Path — if as-built records are strong but baseline is disputed\n\n---\n\n## Part 5: Disruption Claims — How to Prove It\n\n### The Walter Lilly Test (UK, 2012)\n\nFour elements:\n1. **Compensable event** — identify the contract clause\n2. **Event caused disruption** — causal link (but-for test)\n3. **Disruption caused loss** — quantify the financial impact\n4. **Notice given** — comply with contractual notice requirements\n\n### Causation Standard\n\nPer *Costain Ltd v Charles Haswell & Partners Ltd* [2009] EWHC B25 (TCC): the contractor must prove not just that disruption occurred but that the **specific event caused identifiable productivity loss**. General assertions of \"inefficiency\" without linking specific events to specific losses will fail.\n\n**Practical implication:** For each disruption claim, build a causation chain:\n1. What was the event?\n2. Which activities were affected?\n3. What was the productivity benchmark?\n4. What was the actual productivity?\n5. What is the difference in cost?\n\n### How to Quantify Disruption\n\n| Method | Description | Persuasiveness |\n|--------|-------------|----------------|\n| **Measured Mile** | Compare productivity in disrupted vs undisrupted period on the same project | Highest |\n| **Project-Specific Study** | Detailed analysis of the project's productivity data | High |\n| **Earned Value Analysis** | Compare planned vs actual resource usage per unit of work | Medium-High |\n| **Industry Studies** | Published productivity loss factors (Leonard, MCAA) | Lower |\n| **System Dynamics** | Computer modelling of productivity impacts | Variable |\n\nMeasured Mile is the most accepted method. Industry studies are weakest because tribunals view them as too generic.\n\n### Common Causes of Disruption\n\n- Variations / change orders\n- Late information or approvals\n- Change in work sequencing\n- Restricted site access\n- Trade stacking (too many trades in same area)\n- Acceleration instructions\n\n---\n\n## Part 6: Force Majeure & Frustration\n\n### Force Majeure (Contract-Based)\n\n- Defined in the contract — check the specific FM clause\n- Consequences depend on contract terms (EOT? Termination? Cost sharing?)\n- Common FM events: war, pandemic, natural disaster, government action\n\n#### Hardship vs Force Majeure\n\n**Hardship is NOT Force Majeure.** An event becoming more expensive or difficult does not qualify as FM. FM requires the event to make performance **impossible or legally impermissible**, not merely uneconomical.\n\n#### COVID-19 Lessons\n\n- Generic FM clauses without specific pandemic reference often failed to trigger\n- Government-mandated shutdowns generally qualified as FM (or \"change in law\")\n- Modern FM clauses now expressly list \"pandemic\", \"epidemic\", and \"public health emergency\"\n- Notice and mitigation obligations were strictly enforced\n\n### Frustration (Common Law — Last Resort)\n\n- Contract is discharged — both parties walk away\n- Only applies when performance is impossible, illegal, or radically different\n- Very rarely successful — courts set a very high bar\n- **NOT frustration:** cost increases, labour shortages, bad weather, design changes\n\n---\n\n## Part 7: Key Case Law Quick Reference\n\n| Case | Jurisdiction | Key Principle |\n|------|-------------|---------------|\n| *Henry Boot v Malmaison* [1999] | UK | Concurrent delay — contractor gets EOT even if own delay is concurrent |\n| *Walter Lilly v Mackay* [2012] | UK | Disruption: 4 elements + notice; global basis possible |\n| *North Midland v Cyden Homes* [2018] EWCA Civ 1744 | UK | Parties can contract out of Malmaison — concurrent delay risk allocation is enforceable |\n| *City Inn v Shepherd* [2010] CSIH 68 | Scotland | Apportionment approach — tribunal can split EOT between causes |\n| *Costain v Charles Haswell* [2009] EWHC B25 (TCC) | UK | Disruption causation — must link specific events to specific productivity losses |\n| *Cleveland Bridge* [2012] | UK | Reasoned assessment on balance of probabilities |\n| *Van Oord v Allseas* [2015] | UK | Notice requirements matter |\n| *Alliance Concrete v Sato Kogyo* [2014] | Singapore | Frustration — high bar for frustration |\n| *Davis Contractors v Fareham* [1956] | UK | Frustration — 8-to-22-month overrun NOT frustration |\n| *Evergreat v Presscrete* [2006] | Singapore | Employer must do all things necessary for completion |\n| *TT International v Ho Lee* [2017] | Singapore | Employer must not prevent contractor from performing |\n| *Zurich Insurance v B-Gold* [2008] | Singapore | Extrinsic evidence admissible for contract interpretation |\n| *Lim Chin San v LW Infrastructure* [2011] | Singapore | Proper assessment by SO required; failure opens right to damages |\n| *John Doyle v Laing* [2004] | UK | Global claims — permissible if impracticable to separate |\n| *Wong Lai Ying v Chinachem* [1979] | Hong Kong | Unforeseeable landslip = frustration |\n\n---\n\n## Part 8: Key Definitions\n\n| Term | Definition |\n|------|-----------|\n| **EOT** | Extension of Time — additional time to complete without LD |\n| **LD** | Liquidated Damages — pre-agreed daily rate for late completion |\n| **Critical Path** | Longest chain of dependent activities determining completion date |\n| **Positive Float** | Time an activity can be delayed without affecting the critical path |\n| **Zero Float** | Activity is on the critical path — any delay directly delays completion |\n| **Negative Float** | Projected completion already exceeds contract completion date. Does NOT bar EOT claims. |\n| **Terminal Float** | Buffer between contractor's planned completion and contract completion date |\n| **Pacing Delay** | Deliberate slowing of non-critical work to match employer-caused critical path delay. Not contractor culpable delay. |\n| **Excusable Delay** | A delay that entitles the contractor to EOT. May or may not be compensable. |\n| **Compensable Delay** | A delay that entitles the contractor to both EOT and money. |\n| **Inexcusable Delay** | A contractor risk delay — no EOT, no compensation. |\n| **Logic Links** | Programme dependencies: FS (Finish-to-Start), SS (Start-to-Start), FF (Finish-to-Finish), SF (Start-to-Finish, rare). |\n| **Approved Programme** | Programme formally accepted by the Employer/Engineer. Reference point for delay analysis. |\n| **Working Programme** | Contractor's internal updated programme reflecting current progress and forecasts. |\n| **Baseline Programme** | Original approved programme — reference point for delay analysis |\n| **As-Built Programme** | Record of what actually happened |\n| **Time-Bar** | Contractual deadline — miss it and you lose the claim |\n| **Prolongation** | Extended site presence due to delay |\n| **Disruption** | Reduced productivity (more resources per unit of output) |\n| **Acceleration** | Measures to recover delay (additional resources, overtime, resequencing) |\n| **Concurrent Delay** | Two or more delay events occurring simultaneously, at least one employer risk and one contractor risk |\n| **Compensation Event** | NEC term for an event entitling contractor to time and/or money |\n| **Measured Mile** | Comparing productivity in disrupted vs undisrupted periods |\n\n---\n\n*This document is based on publicly available sources including the SCL Delay and Disruption Protocol (2nd Ed, Feb 2017 + Rider 1, Feb 2022), AACEi RP 29R-03, and published case law. It is a study and reference aid only. It does not constitute legal advice. Users should verify all information against their specific contract terms and seek qualified legal counsel where required.*\n\nFile v1.7.6:references/disruption_claims.md\n\n# Disruption Claims Strategy\n\nDisruption claims seek compensation for **loss of productivity or inefficiency** caused by events that do not necessarily delay the overall completion date. They are often more difficult to prove than pure delay claims but can represent significant value.\n\n---\n\n## Key Characteristics\n\n- Focus on **loss of productivity** rather than delay to completion\n- Often arise from **cumulative effects** of multiple instructions, changes, or interference\n- Require strong evidence linking disrupting events to reduced efficiency\n- Usually quantified using **Measured Mile**, productivity studies, or actual cost comparison\n\n---\n\n## Strategic Approach — 7-Dimension Framework\n\n### 1. Situation Assessment & Scope Control\n\nClearly define the claim as a **disruption/productivity claim**, not an EOT claim. Avoid mixing the two unless both are genuinely present and can be separated.\n\n### 2. Argument Strategy\n\n- In **common law** contexts: strong factual evidence and a credible Measured Mile are usually important\n- In **civil law** or mixed settings: good faith and fairness may also support the overall impact argument, but factual evidence remains essential\n\n### 3. Disclosure Control\n\nBe cautious with early disclosure of internal productivity data or tender assumptions. Consider phased disclosure where appropriate.\n\n### 4. Risk Assessment\n\nA major risk is the argument that some disruption was **normal and priced in the tender**. Mitigate by demonstrating that the volume, nature, timing, or cumulative effect exceeded normal expectations.\n\n---\n\n## Recommended Primary Argument\n\n**Factual Distinction** is usually the strongest approach:\n\n1. Acknowledge that some level of instruction or change is normal under the contract\n2. Distinguish **why** the actual events created materially different and more inefficient working conditions than could reasonably have been anticipated\n\n---\n\n## Common Law vs Civil Law Comparison\n\n| Aspect | Common Law | Civil Law |\n|--------|-----------|-----------|\n| **Evidential standard** | Strong emphasis on proof of productivity loss | More reliance on good faith and fairness |\n| **Measured Mile** | Highly regarded when properly applied | Less rigid requirement for a perfect comparison |\n| **Baseline assumptions** | Greater scrutiny on productivity assumptions | Focus on whether changes exceeded reasonable expectations |\n| **Cumulative impact** | Needs clear causal chain | May consider cumulative impact and equity |\n\n**Strategic implication:** In common law jurisdictions, invest heavily in strong factual evidence and credible Measured Mile analysis. In civil law or international arbitration, balance factual evidence with fairness and overall impact arguments.\n\n---\n\n## Illustrative Scenarios\n\n### Scenario A — Cumulative Instructions\n\nA contractor experiences 47 instructions over 8 months. Productivity on finishing trades drops significantly. Using a Measured Mile from an unaffected period, the contractor demonstrates a 28% productivity loss. A tribunal would likely scrutinise the quality of the Measured Mile and the link between instructions and loss.\n\n### Scenario B — Repeated Interference\n\nThe Employer repeatedly changes access arrangements and work sequences at short notice. The contractor argues that the cumulative effect made efficient working impossible. In a civil law or good faith context, the argument may focus on the Employer not creating conditions that undermine efficient performance.\n\n---\n\n## Arbitration Considerations for Disruption Claims\n\n- Clearly separate disruption from any concurrent EOT claim\n- Use clear visuals — productivity charts and comparison tables\n- Justify why the level of disruption exceeded what was reasonably foreseeable at tender stage\n- In international arbitration, explain which legal tradition or hybrid approach should apply based on the governing law clause\n\n---\n\n*This is a generic strategic guide. It does not constitute legal advice.*\n\nArchive v1.7.5: 29 files, 73005 bytes\n\nFiles: examples/strategy_input.json (3646b), examples/strategy_report_sample.md (10456b), references/adr_overview.md (4045b), references/arbitration_tactics.md (3206b), references/argument_ranking_guide.md (6855b), references/blank_worksheet.md (1864b), references/claim_preparation_checklist.md (2116b), references/common_pitfalls.md (2224b), references/concurrent_delay.md (3039b), references/delay_analysis_methods.md (3239b), references/delay_analysis_study_guide.md (21978b), references/disruption_claims.md (3980b), references/expert_engagement.md (2431b), references/legal_precedents.md (2960b), references/notice_requirements_checklist.md (1770b), references/quantum_worked_examples.md (6312b), references/quick_reference_card.md (2634b), references/record_keeping_checklist.md (1910b), references/response_template.md (2667b), references/risk_assessment_framework.md (2467b), references/seven_dimensions_guide.md (8586b), references/strategy_patterns.md (4636b), references/training_guide.md (4950b), references/worked_examples.md (12735b), scripts/strategy_advisor.py (33926b), scripts/version.py (282b), SKILL.md (18722b), tests/test_smoke.py (7462b), _meta.json (146b)\n\nFile v1.7.5:SKILL.md\n\n---\nname: construction-claim-strategy\ndescription: Strategic planning framework for construction claim responses — plan direction, scope, arguments, and disclosure strategy BEFORE selecting clauses or drafting. Covers situation assessment, scope control, direction decisions, argument ranking, disclosure control, response architecture, and risk assessment for EOT, delay, disruption, variation, and payment claims under PSSCOC, FIDIC, NEC, SIA, and bespoke forms. Includes practical checklists, quantum calculation methods, ADR strategies, delay analysis methods, concurrent delay, disruption claims, arbitration tactics, expert engagement, notice compliance, and legal precedent guidance.\n---\n\n# Construction Claim Strategy\n\n**Strategic planning framework for construction claim responses.**\n\nPlan your direction, scope, arguments, and disclosure strategy **before** selecting clauses or drafting correspondence.\n\n---\n\n## Why use this?\n\n- Stop jumping straight to clause selection — plan the strategy first.\n- Rank arguments by strength (Textual Interpretation is strongest).\n- Control what to disclose precisely, keep general, or defer.\n- Choose proven response structures.\n- Avoid common mistakes that weaken your position.\n\n---\n\n## Who this is for\n\n- Contract managers\n- Claims consultants\n- Quantity surveyors\n- Commercial managers\n- Construction lawyers\n- Anyone preparing responses to claims or formal queries under construction contracts\n\n---\n\n## What this skill does\n\nUse this tool to systematically work through 7 key dimensions:\n\n1. **Situation Assessment** — Understand exactly what you are responding to.\n2. **Scope Control** — Decide what to address and what to avoid volunteering.\n3. **Direction Decision** — Choose primary and fallback arguments, and what to avoid.\n4. **Argument Strategy** — Select the strongest type of argument available.\n5. **Disclosure Control** — Decide what to state precisely, keep general, or defer.\n6. **Response Architecture** — Choose the most effective structure for your reply.\n7. **Risk Assessment** — Identify counter-arguments, weak points, and timing risks.\n\nPlus **practical tools and reference guides** covering:\n\n- Record keeping checklists\n- Claim preparation checklists (adjudication & arbitration)\n- Notice requirements compliance\n- Expert engagement guidance\n- ADR strategy (negotiation, mediation, adjudication, arbitration)\n- Concurrent delay strategic approach\n- Disruption claims strategy\n- Delay analysis methods (As-Planned vs As-Built, TIA, Collapsed As-Built, Windows)\n- Arbitration tactics and prolongation strategies\n- Quantum calculation worked examples (Eichleay, Hudson, Emden, Measured Mile, Actual Cost, Total Cost)\n- Legal precedents overview (Prevention Principle, Common Law vs Civil Law)\n- Common pitfalls and how to avoid them\n- Risk assessment framework\n\n---\n\n## Supported contract forms\n\nWorks with any construction contract form:\n- PSSCOC (Construction Works / D&B)\n- FIDIC (Red, Yellow, Silver, Emerald)\n- NEC (NEC3, NEC4)\n- SIA Conditions\n- JCT\n- Bespoke contract conditions\n\n---\n\n## Start here\n\n### Quick Reference (all strategy patterns)\n\n```bash\npython3 scripts/strategy_advisor.py --reference\n```\n\nOutputs all argument types, disclosure levels, response patterns, scope control rules, and risk checklists in one view.\n\n### Interactive Strategy Session (Recommended)\n\n```bash\npython3 scripts/strategy_advisor.py\n```\n\nThe wizard walks you through all 7 dimensions and produces a structured strategy report.\n\n### Non-Interactive (from JSON)\n\n```bash\npython3 scripts/strategy_advisor.py --file strategy_input.json --output strategy_report.md\n```\n\n### Save Strategy for Reuse\n\n```bash\npython3 scripts/strategy_advisor.py --save-strategy my_strategy.json\n```\n\n---\n\n## Examples\n\nThe `examples/` folder contains a worked scenario demonstrating the full 7-Dimension workflow:\n\n| File | Description |\n|------|-------------|\n| `strategy_input.json` | Sample JSON input — PSSCOC 2014 (7th Edition) EOT scenario |\n| `strategy_report_sample.md` | Generated strategy report from the above input |\n\n**Note:** The example uses **PSSCOC 2014** clause references (Clauses 12.5, 14.2(m), 14.2(n), 22.1(h), 22.1(i), 14.3, 23.1). The **7-Dimension methodology itself is contract-form neutral** — it applies equally to FIDIC, NEC, SIA, JCT, and bespoke contracts. Future versions will include additional worked examples for other contract forms.\n\n---\n\n## Key Concepts\n\n### Argument Strength Ranking\n\n1. **Textual Interpretation** (Strongest) — Argue from the actual wording of the relevant clause in the Contract.\n2. **Factual Distinction** (Strong) — Show that the facts fall outside the clause's scope or trigger conditions.\n3. **Concede-then-Distinguish** (Moderate-Strong) — Acknowledge the normal case, then distinguish the current situation.\n4. **Implied Terms** (Weakest) — Use only as a last resort when no express clause wording supports the position.\n\n### Disclosure Control Levels\n\n| Level | Use for |\n|-------|---------|\n| **State Precisely** | Clause references, formal correspondence, key dates, and legal reasoning |\n| **Keep General** | Operational context and high-level details |\n| **Defer** | Detailed quantification and supporting analysis |\n\n### Recommended Response Patterns\n\n- **Standard Query Response** — acknowledge, pivot, argue, reserve, close\n- **Risk Allocation Rebuttal** — concede ordinary application, distinguish, factual support, legal conclusion, mitigation evidence, close cooperatively\n- **Chronology-Based Response** — state known facts, flag pending items, commit to supplement, reserve\n- **Cost / Quantum Claim Response** — contractual basis, heads of claim, ongoing assessment, commit to detailed breakdown, reserve\n- **Reservation of Rights Closing** — always recommended\n\n### Scope Control Rules\n\n1. **Limit to letter** — respond only to what was asked; do not volunteer unrequested information.\n2. **Preserve future claims** — use \"reserves its position\" and \"without prejudice\" language.\n3. **Keep operational details general** — do not name specific zones or quantities prematurely.\n\n### Common Anti-Patterns to Avoid\n\n- ❌ Citing the wrong clause (e.g., a clause for other contractors when the Employer caused the issue)\n- ❌ Leading with \"the clause doesn't apply\" — this antagonises the other party\n- ❌ Volunteering information about topics not yet raised\n- ❌ Naming specific zones/quantities before they are finalised\n- ❌ Reaching for implied terms when express clause text supports your case\n- ❌ Hedging dates that have formal letter references behind them\n- ❌ Quantifying costs before records are complete\n\n---\n\n## How to use\n\n### CLI options\n\n```\nusage: strategy_advisor [-h] [--file INPUT_JSON] [--output FILE]\n                        [--format {md,txt}] [--save-strategy PATH]\n                        [--reference] [--version]\n\nStrategy Advisor — Strategic planning framework for construction claim\nresponses. Plan your direction, scope, and argument strategy BEFORE selecting\nclauses.\n\noptions:\n  -h, --help            show this help message and exit\n  --file INPUT_JSON     Non-interactive: read strategy inputs from a JSON\n                        file.\n  --output, -o FILE     Write report to file instead of stdout.\n  --format, -f {md,txt}\n                        Output format (default: md).\n  --save-strategy PATH  Save the strategy data as JSON for reuse.\n  --reference           Print all reference tables (argument types, patterns,\n                        etc.) and exit.\n  --version             show program's version number and exit\n```\n\n### Required JSON keys (for `--file` mode)\n\nThe following 6 keys are **required** in the input JSON. If any are missing, the tool exits with a clear error listing what’s needed.\n\n| Key | Description |\n|-----|-------------|\n| `situation_type` | What you’re dealing with (e.g. “Responding to a rejection of our claim”) |\n| `other_side_position` | The other party’s stated position |\n| `trigger_event` | Key facts / what triggered this response |\n| `primary_argument` | Your primary contractual argument |\n| `chosen_argument_type` | Argument type (e.g. “Textual Interpretation”) |\n| `chosen_pattern` | Response architecture pattern (e.g. “Risk Allocation Rebuttal”) |\n\nAll other keys are optional — the tool fills empty fields gracefully. See `examples/strategy_input.json` for a complete example with all 21 supported keys.\n\n### Commands\n\n```bash\n# Show all reference tables\npython3 scripts/strategy_advisor.py --reference\n\n# Run interactive wizard\npython3 scripts/strategy_advisor.py\n\n# Non-interactive from JSON\npython3 scripts/strategy_advisor.py --file input.json --output report.md\n\n# Save strategy for reuse\npython3 scripts/strategy_advisor.py --save-strategy strategy.json\n```\n\n---\n\n## Reference Library\n\nAll reference documents are in the `references/` folder. These are standalone reading material for human use — the `strategy_advisor.py` script does not load them at runtime.\n\n| Document | Description |\n|----------|-------------|\n| `seven_dimensions_guide.md` | Full guide to the 7-Dimension framework |\n| `argument_ranking_guide.md` | Detailed argument types with examples |\n| `worked_examples.md` | 4 complete worked strategy examples (Variation, EOT, Disruption, Combined) |\n| `delay_analysis_study_guide.md` | Comprehensive delay analysis study guide — SCL Protocol 22 principles, 7 analysis methods, concurrent delay, pacing, float, disruption, force majeure, case law |\n| `quantum_worked_examples.md` | 8 quantum calculation examples (Eichleay, Hudson, Emden, Measured Mile, Actual Cost, Total Cost) |\n| `adr_overview.md` | ADR methods comparison and strategy recommendations |\n| `arbitration_tactics.md` | Arbitration tactics and prolongation claim strategies |\n| `concurrent_delay.md` | Concurrent delay — strategic approach within the 7-Dimension framework |\n| `disruption_claims.md` | Disruption claims strategy — Common Law vs Civil Law |\n| `delay_analysis_methods.md` | Delay analysis methods — strategic overview |\n| `legal_precedents.md` | Legal precedents and the Prevention Principle |\n| `notice_requirements_checklist.md` | Notice compliance checklist |\n| `expert_engagement.md` | Expert engagement tips and best practices |\n| `record_keeping_checklist.md` | Printable record keeping checklist |\n| `claim_preparation_checklist.md` | Claim preparation checklist for adjudication & arbitration |\n| `common_pitfalls.md` | 10 most common claim pitfalls and how to avoid them |\n| `risk_assessment_framework.md` | Expanded risk assessment categories and practical questions |\n| `response_template.md` | Letter template mapping strategy to formal response |\n| `quick_reference_card.md` | One-page desk reference card |\n| `blank_worksheet.md` | Printable blank 7-Dimension worksheet |\n| `training_guide.md` | Workshop-ready training material |\n| `strategy_patterns.md` | All strategy patterns reference |\n\n---\n\n## Companion skill\n\nFor clause analysis, notice calendars, obligations registers, SOP calculator, and claims templates, see the companion skill `construction-law` on ClawHub.\n\n---\n\n## Requirements\n\n- Python 3.10+\n- Standard library only — no third-party dependencies\n\n## Tests\n\n```bash\npython3 -m unittest tests.test_smoke\n```\n\n---\n## Security & Safety\n\n- ✅ No network access\n- ✅ No external calls\n- ✅ No subprocess execution\n- ✅ No dynamic code loading\n- ✅ No telemetry: this tool does not collect or transmit usage data\n- ✅ Safe for use with confidential project information\n- ✅ **Safe to install and use** 🛡️\n\n### Files written\n\nThis tool writes files **only** when you pass explicit flags:\n\n| Flag | What is written | Format |\n|------|----------------|--------|\n| `--output FILE` | Strategy report | UTF-8 (Markdown or plain text) |\n| `--save-strategy PATH` | Strategy data for reuse | UTF-8 JSON |\n\nIf neither flag is provided, output is printed to stdout. No files are created, modified, or read beyond the `--file` input (when given).\n\n---\n\n## Changelog\n\n### v1.7.5 (May 2026)\n- **Security:** Sanitised test docstrings and comments — removed function-call patterns (e.g. `compile(...)`) that ClawHub static analysis flagged as `suspicious.dynamic_code_execution`. The actual detection logic uses `ast.parse` and was never affected; the scanner was pattern-matching against English text in comments.\n\n### v1.7.4 (May 2026)\n- **Security:** Replaced string-grep forbidden-imports check with `ast.parse` tree-walking — properly catches `compile(...)`, `exec(...)`, `eval(...)` regardless of whitespace or indirection; no longer false-positives on comments, docstrings, or strings containing those words\n\n### v1.7.3 (May 2026)\n- **Security:** Rewrote `test_smoke.py` to avoid `subprocess.run()` entirely — now imports `main()` directly and patches `sys.argv`. Resolves ClawHub ClawScan `suspicious.dynamic_code_execution` false positive on the test file\n- **Security:** Tightened forbidden-imports list: `urllib.request`/`urllib.error` (not blanket `urllib`), added `importlib`, `pickle`, `marshal`, `compile(`\n- **Performance:** Tests now run in ~0.01s (was ~0.2s with subprocess overhead)\n\n### v1.7.2 (May 2026)\n- **Fix:** Interactive mode now wraps file writes (`--output`, `--save-strategy`) with friendly error messages (consistent with non-interactive mode)\n- **Added:** Required-key validation for `--file` JSON input — missing keys produce a clear error listing what's needed, instead of empty fields\n- **Added:** `_safe_write` helper — unified error handling for all file output paths\n- **Docs:** Added `--help` output to SKILL.md so users can evaluate CLI flags without installing\n- **Docs:** Added explicit \"No telemetry\" statement in Security section\n- **Docs:** Added \"Files written\" section documenting exactly what is written and when\n- **Docs:** Documented the 6 required JSON keys for `--file` mode\n- **Docs:** Changed test instructions to recommend `python3 -m unittest` (stdlib) over `pytest`\n\n### v1.7.1 (May 2026)\n- **Security:** Added `test_no_forbidden_imports` — enforces the \"no network / no subprocess\" claim at test time by scanning for forbidden imports (subprocess, socket, requests, urllib, etc.)\n- **Compatibility:** Updated Python requirement from 3.6+ to 3.10+ (reflects what is actually tested)\n\n### v1.7.0 (May 2026)\n- **Changed:** Replaced example scenario with a realistic PSSCOC EOT case (Contractor responding to SO rejection under Clause 13.2)\n- **Changed:** `strategy_input.json` rewritten with correct flat-key schema matching all 7 dimensions\n- **Changed:** `strategy_report_sample.md` regenerated from actual script output (not hand-written)\n- **Changed:** Improved test docstrings and header matching\n\n### v1.6.1 (May 2026)\n- **Added:** JSON input validation for `--file` mode — checks file exists, valid JSON, root is a dict; warns on unrecognised keys (typo protection)\n- **Added:** File I/O error handling — friendly messages for missing files, permission errors, and malformed JSON (no raw tracebacks)\n- **Removed:** Dead code (`_prompt_yesno` function was defined but never called)\n\n### v1.6.0 (May 2026)\n- **Added:** `examples/strategy_input.json` and `examples/strategy_report_sample.md` — preview output before installing\n- **Added:** `tests/test_smoke.py` — smoke test covering `--reference`, `--file`, and `--version` modes\n- **Added:** `LICENSE` file (MIT-0) shipped at package root\n- **Added:** Requirements section in SKILL.md (Python 3.6+, stdlib only)\n- **Added:** Tests section in SKILL.md\n- **Changed:** Vocabulary normalisation — replaced contract-form-specific terms (\"Authority\", \"Engineer\") with neutral language (\"certifier\", \"the other party\") for consistent applicability across PSSCOC, FIDIC, NEC, SIA, JCT, and bespoke contracts\n- **Changed:** SKILL.md clarifies that `references/` is human reading material, not loaded by the script at runtime\n- **Fixed:** Removed stale reference to `construction_law.py` in module docstring\n- **Fixed:** Removed dead conditional branch in title block of `generate_report`\n\n### v1.5.0 (May 2026)\n- **Added:** Delay Analysis Study Guide — comprehensive reference covering SCL Protocol 22 Core Principles, 7 delay analysis methods (incl. Retrospective Longest Path), negative float & EOT entitlement, concurrent delay (Malmaison, North Midland, City Inn), pacing delays, disruption causation (Walter Lilly test), force majeure vs hardship, COVID-19 lessons, 15 key cases, and full definitions glossary\n- Sanitised from project-specific study guide; all generic content with public case law citations\n- Total reference documents: 22\n\n### v1.4.0 (May 2026)\n- **Major expansion:** Integrated full Construction Claim Strategy Practical Tools Guide v1.4\n- Added: Notice Requirements Checklist\n- Added: Expert Engagement Tips\n- Added: Legal Precedents guide (Prevention Principle, Common Law vs Civil Law)\n- Added: Concurrent Delay — Strategic Approach\n- Added: Disruption Claims Strategy (with Common Law vs Civil Law comparison)\n- Added: Delay Analysis Methods — Strategic Overview (As-Planned vs As-Built, TIA, Collapsed As-Built, Windows)\n- Added: Arbitration Tactics & Prolongation Claim Strategies\n- Added: ADR Overview with Adjudication vs Arbitration detailed comparison\n- Added: Quantum Calculation Worked Examples (8 examples: Eichleay, Hudson, Emden, 2× Measured Mile, Actual Cost, Productivity Loss, Total Cost)\n- Added: Common Claim Pitfalls (10 pitfalls with fixes)\n- Added: Risk Assessment Framework (expanded categories and practical questions)\n- Added: Record Keeping Checklist (printable)\n- Added: Claim Preparation Checklist (printable, adjudication & arbitration)\n- Total reference documents: 21\n\n### v1.3.0 (May 2026)\n- Added argument ranking guide, seven dimensions guide, worked examples\n- Added response template, quick reference card, blank worksheet\n- Added training guide and strategy patterns\n\n### v1.1.0 (May 2026)\n- Fully sanitized — all examples use generic/neutral language\n- Improved interactive wizard with examples and input validation\n- Better README for public listing\n- Added review step before report generation\n\n### v1.0.1 (May 2026)\n- Removed all project-specific references\n- Added disclaimer\n\n### v1.0.0 (May 2026)\n- Initial release — 7 strategy dimensions\n- Interactive wizard mode\n- Non-interactive JSON mode\n- Reference tables dump\n- Strategy save/reload\n\n---\n\n*This is a generic strategic planning tool. It does not constitute legal advice. Users should verify all information independently and seek qualified legal counsel before relying on any analysis for dispute resolution, adjudication, arbitration, or court proceedings.*\n\nFile v1.7.5:_meta.json\n\n{\n  \"ownerId\": \"kn77g2eearfhaq251ab7jtrctn854v1s\",\n  \"slug\": \"construction-claim-strategy\",\n  \"version\": \"1.7.5\",\n  \"publishedAt\": 1779010873519\n}\n\nFile v1.7.5:references/adr_overview.md\n\n# ADR in Construction Claims — Overview & Strategies\n\nAlternative Dispute Resolution (ADR) provides ways to resolve disputes without going to full court litigation. Choosing the right method depends on your goals: speed, cost, finality, cash flow, and relationship preservation.\n\n---\n\n## ADR Methods Comparison\n\n| Method | Description | Binding? | Speed | Cost | Best Used When |\n|--------|-------------|----------|-------|------|---------------|\n| **Negotiation** | Direct discussion between parties | No | Fast | Low | Early stage, good relationship |\n| **Mediation** | Neutral facilitator helps reach settlement | No (usually) | Fast | Low–Medium | Preserve relationship, complex issues |\n| **Adjudication** | Fast interim decision by adjudicator | Yes (usually interim/temporary) | Very Fast | Medium | Cash flow or interim relief needed |\n| **Arbitration** | Private tribunal makes final decision | Yes (final) | Medium–Slow | High | Final resolution, international disputes |\n| **Litigation** | Court proceedings | Yes (final) | Slow | High | Last resort, complex legal points |\n\n---\n\n## ADR Strategy Recommendations\n\n1. **Start with negotiation** where possible — many disputes can be resolved early if approached professionally\n2. **Use mediation** when preserving the commercial relationship is important or when issues are complex\n3. **Consider adjudication** (where available) for fast interim cash flow or time-related decisions\n4. **Choose arbitration** for final, binding resolution, especially in international projects\n5. **Use litigation** generally as a last resort due to cost, time, and relationship impact\n\n---\n\n## Adjudication vs Arbitration — Detailed Comparison\n\n| Aspect | Adjudication | Arbitration |\n|--------|-------------|-------------|\n| **Nature** | Fast interim decision | Final and binding decision |\n| **Speed** | Very fast (usually 28–42 days in statutory regimes) | Slow to medium (6–24 months) |\n| **Cost** | Relatively low | High |\n| **Binding** | Binding until finally determined by arbitration or litigation | Final and binding |\n| **Enforceability** | Enforceable in jurisdictions with statutory adjudication | Enforceable internationally (New York Convention) |\n| **Right of appeal** | Limited (usually only jurisdiction or natural justice) | Limited, depends on seat of arbitration |\n| **Procedure** | Relatively informal and fast | More formal, similar to litigation |\n| **Evidence** | Often limited written submissions | Full hearing with witnesses and experts |\n| **Relationship impact** | Can be less damaging if used early | Often more adversarial |\n\n### When to Choose Adjudication\n\n- Need **quick cash flow** relief\n- Want to keep the project moving during dispute resolution\n- Dispute is relatively straightforward\n- Available under a statutory regime or contract\n\n### When to Choose Arbitration\n\n- Need a **final and binding** decision\n- Dispute is complex, high-value, or multi-issue\n- International enforceability matters\n- Parties can choose arbitrators with relevant expertise\n\n---\n\n## Decision Guide\n\n| Your Goal | Recommended Route |\n|-----------|-------------------|\n| Need money / relief quickly | **Adjudication** (if available) |\n| Want a final and binding decision | **Arbitration** |\n| Want to preserve commercial relationship | Start with **Negotiation → Mediation** |\n| High-value, complex, international dispute | **Arbitration** |\n| Domestic dispute needing fast interim relief | **Adjudication** |\n\n---\n\n## Common Law vs Civil Law Perspective\n\n| Aspect | Common Law | Civil Law |\n|--------|-----------|-----------|\n| **Adjudication** | Very common (often statutory) | Less common (more voluntary) |\n| **Arbitration** | Widely used | Very widely used |\n| **Preference** | Often adjudication first, then arbitration | Tend to go straight to arbitration or mediation |\n| **Statutory support** | Strong statutory regimes for adjudication | Generally rely on contractual ADR clauses |\n\n---\n\n*This is a generic reference guide. It does not constitute legal advice.*\n\nFile v1.7.5:references/arbitration_tactics.md\n\n# Arbitration Tactics & Prolongation Claim Strategies\n\n---\n\n## Arbitration Tactics — Common Law vs Civil Law\n\n### Common Law Arbitrations\n\n- Heavy emphasis on **contemporaneous documents**, detailed witness statements, and expert reports\n- Cross-examination is often rigorous — be prepared to defend methodology and credibility in detail\n- Broader **document disclosure** is common; failure to disclose can damage credibility\n- Significant reliance on **case law and precedents** in areas such as notice, prevention principle, and quantum methods\n- **Strategy:** Build a document-heavy, precedent-supported case with strong expert evidence\n\n### Civil Law / Mixed Arbitrations\n\n- Greater emphasis on overall **fairness, good faith, and commercial equity**\n- Cross-examination may be less confrontational, depending on tribunal and rules\n- Disclosure is usually **narrower**\n- More reliance on principles of good faith and fairness than strict precedent\n- **Strategy:** Combine strong factual evidence with clear arguments on equity and the parties' reasonable expectations\n\n---\n\n## Comparison Table\n\n| Aspect | Common Law Arbitration | Civil Law / Mixed Arbitration |\n|--------|----------------------|------------------------------|\n| Documents | Heavy reliance; broad disclosure | Narrower disclosure |\n| Witnesses | Detailed statements; rigorous cross-exam | Less confrontational |\n| Experts | Essential for complex claims | Important but approach may differ |\n| Precedents | Key part of submissions | Persuasive but less central |\n| Good faith | Developing | Central principle |\n| Strategy focus | Document + precedent | Equity + evidence |\n\n---\n\n## Prolongation Claim Strategies in Arbitration\n\n### Common Law Approach\n\n- Strong focus on proving **EOT first** (critical path impact) before claiming prolongation costs\n- Expect detailed scrutiny of quantum methods and baseline assumptions\n- Concurrent delay arguments are common and must be addressed **proactively**\n- **Strategy:** Secure the EOT foundation first, then build a well-supported prolongation claim — preferably based on actual costs with formula methods as fallback\n\n### Civil Law Approach\n\n- The link between EOT and prolongation costs may be assessed **more flexibly**, depending on governing law and tribunal approach\n- Actual costs remain preferred, but good faith and fairness arguments may help bridge gaps in strict causation proof\n- **Strategy:** Emphasise the overall impact and equity of the situation while still providing clear cost evidence\n\n---\n\n## Practical Recommendations\n\n1. **Know your tribunal** — research the arbitrators' backgrounds and preferred approaches\n2. **Prepare for cross-examination** — ensure witnesses and experts are thoroughly prepared\n3. **Disclosure strategy** — balance completeness with risk of revealing unhelpful documents\n4. **Quantum foundation** — always anchor prolongation to a clear EOT finding\n5. **Address concurrent delay proactively** — don't leave it for the other side to raise\n6. **Clear visuals** — timelines, charts, and cost summaries are often more effective than dense narrative\n\n---\n\n*This is a generic strategic guide. It does not constitute legal advice.*\n\nFile v1.7.5:references/argument_ranking_guide.md\n\n# Argument Ranking — Detailed Guide\n\n*Construction Claim Strategy Framework — Fully Generic*\n\n---\n\n## Why the Ranking Exists\n\nNot all arguments carry the same weight. Stronger arguments are harder to rebut and more likely to be accepted by tribunals, adjudicators, and courts. Weaker arguments are easier to challenge.\n\nAlways start from the top of the ranking. Only move down when stronger options are unavailable.\n\n---\n\n## Rank 1: Textual Interpretation (Strongest)\n\n**What it is:**\nArgue directly from the actual words used in the Contract clause.\n\n**Why it is strongest:**\n- Based on express terms the parties agreed to.\n- Most objective and difficult for the other side to dismiss.\n- Tribunals and courts prefer to give effect to clear wording.\n\n**When to use:** Whenever the wording of the clause supports your position.\n\n**Example structure:**\n> The Contract provides that the Contractor shall be entitled to [entitlement] where the Authority issues an instruction which changes the scope of the Works.\n> On [date], the Authority issued Instruction No. X which required the Contractor to [specific change]. This instruction directly changed the scope.\n> Accordingly, the Contractor is entitled to [relief] pursuant to the clear wording of the clause.\n\n**Recommended disclosure level:** State Precisely — you can be confident and specific.\n\n---\n\n## Rank 2: Factual Distinction (Strong)\n\n**What it is:**\nAccept that the clause exists, but argue that the facts of your case fall outside the situation the clause was intended to cover.\n\n**Why it is strong:**\nStays close to the Contract wording while showing why the clause does not apply to the current situation.\n\n**When to use:** When the clause wording is not clearly in your favour, but the facts are materially different from what the clause contemplates.\n\n**Example structure:**\n> While the Contract contains provisions regarding [subject], those provisions are predicated on the assumption that [normal situation].\n> In the present case, the situation is materially different because [key factual difference].\n> Accordingly, the clause does not operate to [deny the claim / allocate risk in the way suggested].\n\n**Recommended disclosure level:** State Precisely or Keep General — be precise on facts that support the distinction.\n\n---\n\n## Rank 3: Concede-then-Distinguish (Moderate-Strong)\n\n**What it is:**\nConcede that the clause would normally apply, then explain why the current situation is extraordinary or materially different.\n\n**Why it is moderate-strong:**\nShows reasonableness (not denying the clause entirely), while still protecting your position.\n\n**When to use:** When the clause appears to go against you at first glance, but there are good reasons why it should not apply in this specific case.\n\n**Example structure:**\n> The Contractor acknowledges that, in normal circumstances, [risk] would be allocated to the Contractor under the Contract.\n> However, the present situation is materially different. The Authority [did X / failed to do Y / provided incorrect information], which fundamentally changed the nature of the risk.\n> In these exceptional circumstances, it would be inconsistent with the Contract for the risk to remain with the Contractor.\n> Accordingly, the Contractor is entitled to [relief].\n\n**Recommended disclosure level:** Keep General — be careful not to over-disclose internal thinking.\n\n---\n\n## Rank 4: Implied Terms / Prevention Principle (Weakest)\n\n**What it is:**\nArgue that a term should be implied into the Contract, or that the Authority's actions prevented you from performing.\n\n**Why it is weakest:**\n- Implied terms are harder to prove.\n- Prevention principle is heavily contested.\n- Moves away from express Contract words.\n- Easier for the other side to challenge.\n\n**When to use:** Only as a last resort, when none of the stronger arguments are available.\n\n**Example structure:**\n> It is a well-established principle that a party to a contract must not do anything to prevent the other party from performing its obligations.\n> In this case, the Authority's [action / inaction / instruction] had the effect of preventing the Contractor from [completing the works / mitigating losses].\n> As a result, the Contractor is entitled to [relief].\n\n**Note:** More commonly used in Common Law jurisdictions. In Civil Law systems, similar concepts exist under good faith (*bonne foi* / *Treu und Glauben*).\n\n**Recommended disclosure level:** Keep General — these arguments are more vulnerable.\n\n---\n\n## How to Choose\n\n| Rank | Argument Type | Strength | When to Use | Recommendation |\n|------|---|---|---|---|\n| 1 | Textual Interpretation | Strongest | Clause wording supports your position | Use first |\n| 2 | Factual Distinction | Strong | Facts are materially different | Strong backup |\n| 3 | Concede-then-Distinguish | Moderate-Strong | Clause appears unfavourable but facts are exceptional | Use carefully |\n| 4 | Implied Terms / Prevention | Weakest | No better argument available | Last resort |\n\n---\n\n## Combining Arguments (Primary + Fallback)\n\nYou can and often should use a primary + fallback approach in the same response.\n\n**Recommended structure:**\n1. Lead with the strongest available argument.\n2. Clearly signal the fallback.\n3. Use clear paragraph breaks or numbering.\n\n**Example — Textual Interpretation + Factual Distinction:**\n\n> **Primary Position — Textual Interpretation**\n> The Contract states that the Contractor is entitled to additional time and cost where the Authority issues an instruction which varies the Works. The Authority's Instruction dated [X] required the Contractor to [change]. This falls squarely within the wording of the clause.\n>\n> **Alternative Position — Factual Distinction**\n> Without prejudice to the above, even if the clause were interpreted more restrictively, the facts of this case are materially different from the normal situation contemplated by the Contract. At the time of the instruction, [key fact that makes it different]. Accordingly, the clause does not operate to exclude the Contractor's entitlement.\n\n---\n\n## Argument Strength ↔ Disclosure Control Interaction\n\n| Argument Type | Strength | Disclosure Level | Reason |\n|---|---|---|---|\n| Textual Interpretation | Strongest | State Precisely | Position is robust; confidence is high |\n| Factual Distinction | Strong | State Precisely / Keep General | Precise on supporting facts |\n| Concede-then-Distinguish | Moderate-Strong | Keep General | Partial concession; don't over-disclose |\n| Implied Terms / Prevention | Weakest | Keep General | Vulnerable; avoid giving material to attack |\n\n**Rule:** Stronger arguments → more precise disclosure. Weaker arguments → more general disclosure. Always apply scope control regardless.\n\n---\n\n*This is a workflow and analysis aid only. It does not constitute legal advice.*\n\nFile v1.7.5:references/blank_worksheet.md\n\n# Blank Strategy Worksheet\n\n**Construction Claim Strategy — Quick Worksheet**\n\n**Date:** _______________\n**Claim / Query Type:** _______________\n\n---\n\n## 1. Situation Assessment\nWhat exactly are we responding to?\n\n____________________________________________________________________________\n\n## 2. Scope Control\n**Must address:**\n\n____________________________________________________________________________\n\n**Must avoid:**\n\n____________________________________________________________________________\n\n## 3. Direction Decision\n**Primary argument:**\n\n____________________________________________________________________________\n\n**Fallback argument:**\n\n____________________________________________________________________________\n\n**Arguments to avoid:**\n\n____________________________________________________________________________\n\n## 4. Argument Strategy\nChosen argument type:\n☐ Textual Interpretation (Strongest)\n☐ Factual Distinction (Strong)\n☐ Concede-then-Distinguish (Moderate-Strong)\n☐ Implied Terms (Weakest — last resort)\n\nReason:\n\n____________________________________________________________________________\n\n## 5. Disclosure Control\n\n| Level | What to include |\n|---|---|\n| **State Precisely** | |\n| **Keep General** | |\n| **Defer** | |\n\n## 6. Response Architecture\nChosen structure:\n☐ Standard Query Response\n☐ Risk Allocation Rebuttal\n☐ Chronology-Based Response\n☐ Cost / Quantum Claim Response\n\nReason:\n\n____________________________________________________________________________\n\n## 7. Risk Assessment\nMain risks / counter-arguments:\n\n____________________________________________________________________________\n\nHow to address them:\n\n____________________________________________________________________________\n\n---\n\n**Next Step:** Use this completed worksheet to draft the formal response.\n\n*Plan → Strategise → Draft*\n\nFile v1.7.5:references/claim_preparation_checklist.md\n\n# Claim Preparation Checklist\n\nUse this checklist when preparing claims for Adjudication or Arbitration. Thorough preparation significantly improves outcomes.\n\n---\n\n**Project:** _______________________________ **Claim Type:** _______________\n\n## Phase 1: Strategy & Planning\n\n- [ ] Reviewed the contract dispute resolution clause\n- [ ] Completed the 7-Dimension Strategy Worksheet\n- [ ] Identified the main heads of claim (EOT, disruption, variation, prolongation, acceleration)\n- [ ] Decided whether to submit claims separately or combined\n\n## Phase 2: Evidence Collection\n\n- [ ] Compiled a clear chronology of events\n- [ ] Collected and organised all relevant correspondence\n- [ ] Gathered all notices with proof of submission\n- [ ] Collected programme, progress, and site records\n- [ ] Gathered cost and quantum supporting documents\n- [ ] Identified and addressed any gaps in records\n\n## Phase 3: Claim Development\n\n- [ ] Prepared a clear summary of the claim\n- [ ] Developed Primary and Fallback arguments\n- [ ] Prepared quantum calculation with clear methodology\n- [ ] Identified and prepared witnesses, if required\n- [ ] Engaged experts (delay analyst, quantum expert, technical expert) if needed\n\n## Phase 4: Risk Assessment & Review\n\n- [ ] Conducted honest Risk Assessment of own case\n- [ ] Identified likely counter-arguments from the other side\n- [ ] Reviewed and strengthened weak areas\n- [ ] Finalised disclosure strategy\n\n## Phase 5: Final Preparation & Submission\n\n- [ ] Prepared position paper / submissions\n- [ ] Organised document bundle, indexed and paginated\n- [ ] Prepared opening statement / summary\n- [ ] Conducted internal review\n- [ ] Submitted on time\n\n## Adjudication-Specific Items\n\n- [ ] Kept submissions concise and focused\n- [ ] Prioritised speed and clarity\n\n## Arbitration-Specific Items\n\n- [ ] Prepared more detailed and comprehensive submissions\n- [ ] Arranged witness statements and expert evidence\n- [ ] Planned for possible hearings\n\n**Prepared by:** ___________________________ **Date:** _______________\n\n---\n\n*This is a generic checklist. It does not constitute legal advice.*\n\nFile v1.7.5:references/common_pitfalls.md\n\n# Common Claim Pitfalls & How to Avoid Them\n\nMost claims fail or are significantly weakened due to **process issues** rather than weak facts.\n\n---\n\n## The 10 Most Common Pitfalls\n\n| # | Pitfall | Why It's Harmful | How to Avoid |\n|---|---------|-----------------|--------------|\n| 1 | **Jumping straight to drafting** without proper strategy | Leads to weak arguments and poor structure | Complete the 7-Dimension Strategy Worksheet first |\n| 2 | **Volunteering unrequested information** | Creates new issues or admissions the other side can exploit | Apply strict Scope Control — respond only to what was asked |\n| 3 | **Using the weakest argument first** | Damages credibility from the outset | Follow the argument ranking: Textual → Factual → Concede-then-Distinguish → Implied Terms |\n| 4 | **Over-disclosing sensitive information too early** | Gives the other side material to attack your position | Match disclosure level to argument strength; defer where appropriate |\n| 5 | **Mixing EOT and disruption claims** without clear separation | Creates confusion and weakens both claims | Keep them clearly separated unless both are genuinely present and can be distinguished |\n| 6 | **Quantifying costs or delay before records are complete** | Numbers can be attacked if not fully supported | Defer detailed quantum until records are complete |\n| 7 | **Ignoring or missing contractual notice requirements** | Claim can be time-barred or rejected | Check notice provisions early in Risk Assessment; use the Notice Requirements Checklist |\n| 8 | **Using a poor or aggressive tone** in correspondence | Damages commercial relationship and credibility | Use professional, factual language throughout |\n| 9 | **Failing to include a reservation of rights** | Can limit future claims or entitlements | Always include a clear Reservation of Rights |\n| 10 | **Not conducting honest risk assessment** before submitting | Surprised by strong counter-arguments later | Complete the Risk Assessment dimension honestly |\n\n## Key Prevention\n\nComplete the **7-Dimension Strategy** first and apply strict **Scope Control** and **Disclosure Control**.\n\n---\n\n*This is a generic reference guide. It does not constitute legal advice.*\n\nFile v1.7.5:references/concurrent_delay.md\n\n# Concurrent Delay — Strategic Approach\n\nConcurrent delay occurs when two or more independent delay events — typically one caused by the Contractor and one by the Employer/Authority — overlap in time and both are alleged to affect the completion date.\n\nIt is one of the most complex and disputed areas in construction claims.\n\n---\n\n## Why Concurrent Delay Matters Strategically\n\n- It directly impacts **Extension of Time** entitlement and **liquidated damages** exposure\n- It affects **prolongation cost claims**\n- Different jurisdictions apply **different approaches**, creating strategic risk if not handled correctly\n- Poor handling of concurrent delay is a common reason claims are **reduced or rejected** in adjudication and arbitration\n\n---\n\n## Common Approaches\n\n### Common Law Jurisdictions\n\nApproaches vary and may include:\n- **Dominant cause** — which delay had the greater impact?\n- **Apportionment** — split responsibility between the parties\n- **First-in-time / prevention principle** — the first cause takes precedence\n\nThe applicable approach must be checked against the governing law and contract terms.\n\n### Civil Law Jurisdictions\n\n- More reliance on **good faith and fairness**\n- Tribunals may look at overall impact and whether one party's actions prevented the other from mitigating delay\n- Less rigid adherence to a single analysis method\n\n---\n\n## Strategic Recommendations — 7-Dimension Framework\n\n### 1. Situation Assessment & Risk Assessment\n\n- Identify all delaying events early and classify them as **Employer-caused**, **Contractor-caused**, or **neutral**\n- Analyse periods of potential concurrency and document them\n- Assess the risk of the other side arguing concurrency to reduce EOT or impose liquidated damages\n\n### 2. Argument Strategy\n\n- **Primary:** Use strong factual evidence to show Employer delay events were on the critical path and that Contractor delays did not cause overall delay\n- **Fallback:** Argue for apportionment or prevention/good faith reasoning if full EOT is not accepted\n- **Avoid** weak global arguments — be specific about which events caused which delay\n\n### 3. Disclosure Control\n\n- Be careful with full programme disclosure if it shows Contractor-caused delays — seek legal advice on what must be disclosed\n- Clearly separate Employer-caused delay from Contractor-caused delay in submissions\n\n### 4. Response Architecture\n\n- **Proactively** address potential concurrency arguments rather than waiting for the other side to raise them\n- Use clear diagrams or summaries showing critical path and overlapping periods\n\n---\n\n## Practical Tips\n\n- Maintain detailed and updated programmes throughout the project\n- Use a consistent delay analysis method and be prepared to justify it\n- In international arbitration, be ready to explain which approach should apply based on governing law and contract\n- Consider engaging a delay expert early if concurrency is likely to be a major issue\n\n---\n\n*This is a generic strategic guide. It does not constitute legal advice.*\n\nFile v1.7.5:references/delay_analysis_methods.md\n\n# Delay Analysis Methods — Strategic Overview\n\nDelay analysis is the process of investigating the causes and effects of delays on a construction project. The method chosen can significantly impact the strength of an Extension of Time or prolongation claim.\n\n---\n\n## Main Delay Analysis Methods\n\n### As-Planned vs As-Built\n\nCompares the original baseline programme with actual progress.\n\n- **Strengths:** Simple, easy to understand\n- **Weaknesses:** Can be challenged if the baseline was unrealistic\n- **Best for:** Simple delay scenarios with a clear baseline\n\n### Time Impact Analysis (TIA)\n\nAdds delay events one by one to an updated programme to show the impact at the time they occurred.\n\n- **Strengths:** Generally considered robust and widely accepted\n- **Weaknesses:** Requires good contemporaneous programme records; can be complex\n- **Best for:** Complex projects with multiple delay events\n\n### Collapsed As-Built / But-For Analysis\n\nRemoves delay events from the as-built programme to show what the completion date would have been \"but for\" those events.\n\n- **Strengths:** Uses actual as-built data\n- **Weaknesses:** Retrospective; can be challenged on assumptions about what \"would have\" happened\n- **Best for:** Post-completion analysis\n\n### Windows Analysis\n\nDivides the project into time windows and analyses delays within each window.\n\n- **Strengths:** Useful for complex projects with multiple issues; can isolate periods of delay\n- **Weaknesses:** Complex; window boundaries can be disputed\n- **Best for:** Large, complex projects with multiple overlapping events\n\n---\n\n## Method Comparison\n\n| Method | Complexity | Reliance on Programme | Timing | Acceptance |\n|--------|------------|----------------------|--------|------------|\n| As-Planned vs As-Built | Low | Baseline + As-built | Post-completion | Moderate |\n| Time Impact Analysis | High | Updated programmes | Prospective | High |\n| Collapsed As-Built | Medium | As-built | Retrospective | Moderate-High |\n| Windows Analysis | High | Updated programmes | Either | High |\n\n---\n\n## Strategic Considerations — Common Law vs Civil Law\n\n### Common Law\n\n- Often a strong preference for methods that demonstrate **causation at the time the delay occurred** (e.g. TIA)\n- Tribunals may expect a clear link between specific events and critical path impact\n\n### Civil Law\n\n- The approach may be more **flexible and pragmatic**\n- Tribunals may focus on overall fairness, good faith, and whether the claimed events genuinely impacted progress\n- Analysis must still be logical and supported by contemporaneous records\n\n---\n\n## Strategic Recommendations\n\n1. Choose a method appropriate to the **project complexity** and **quality of available records**\n2. Be **consistent** — changing methods mid-claim without good reason damages credibility\n3. In common law jurisdictions, be prepared to defend the method by reference to established practice\n4. In civil law or international arbitration, focus on demonstrating overall impact and fairness while still providing clear analysis\n5. **Maintain and update the programme contemporaneously** — this is the foundation of credible delay analysis\n\n---\n\n*This is a generic strategic guide. It does not constitute legal advice.*\n\nFile v1.7.5:references/delay_analysis_study_guide.md\n\n# Delay Analysis Study Guide for Contract Managers\n\nPractical study notes for delay analysis in construction and infrastructure projects.\n\n**Sources:** SCL Delay and Disruption Protocol 2nd Edition (February 2017) + Rider 1 (February 2022), AACEi Recommended Practice 29R-03, published case law.\n\n> **Caution:** Always confirm which contract edition applies before relying on any clause references. This guide does not constitute legal advice.\n\n---\n\n## Part 1: What Is Delay Analysis?\n\nDelay analysis is the process of identifying what caused a project delay, who is responsible, and what the time/cost consequences are.\n\nIt answers two distinct questions:\n1. **Is the contractor entitled to an Extension of Time (EOT)?** — a time question\n2. **Is the contractor entitled to compensation?** — a money question\n\nThese are linked but separate inquiries (see SCL Principle 12).\n\n---\n\n## Part 2: Key Concepts\n\n### 2.1 Delay vs Disruption vs Prolongation\n\n| Concept | What It Is | Result | Claim Type |\n|---------|-----------|--------|------------|\n| **Delay** | Activity takes longer than planned or starts late | Critical path pushed → later completion | EOT (time) |\n| **Disruption** | Reduced productivity / efficiency — more resources needed per unit of work | Additional cost, may or may not affect completion date | Money (cost) |\n| **Prolongation** | Extended presence on site due to delay | Additional preliminaries, site overheads | Money (cost) |\n\n**Key distinction:** You can have disruption WITHOUT delay (if the affected activity is not on the critical path). You can also have delay WITHOUT disruption (if the activity simply stops).\n\n### 2.2 Types of Delay\n\n| Type | Who Bears Risk | EOT? | Compensation? |\n|------|---------------|------|---------------|\n| **Employer Risk Event** (late instructions, design changes, site access) | Employer | ✓ Yes | ✓ Yes (usually) |\n| **Neutral/Excusable Event** (exceptionally adverse weather, force majeure) | Shared | ✓ Yes | ✗ Usually not |\n| **Contractor Risk Event** (poor planning, resource shortages) | Contractor | ✗ No | ✗ No |\n| **Concurrent Delay** (employer + contractor delays at same time) | Complex | ✓ Yes (SCL view) | Debatable — see 2.4 |\n\n**Excusable vs Compensable:** An excusable delay relieves the contractor from LD (i.e. EOT). A compensable delay additionally entitles the contractor to money. All compensable delays are excusable, but not all excusable delays are compensable.\n\n### 2.3 Critical Path & Float\n\nThe **critical path** is the longest sequence of activities that determines the project completion date. Only delays to activities on the critical path will actually delay the project.\n\n**Float** = the time an activity can slip without affecting the critical path.\n\n**Who owns the float?** The SCL Protocol says float should generally be available to the project (not owned by either party) unless the contract says otherwise.\n\n#### Understanding Float Types\n\n| Float Type | What It Means | EOT Implication |\n|-----------|---------------|-----------------|\n| **Positive Float** | Activity has buffer — can slip without delaying completion | Employer delay may consume float before affecting critical path |\n| **Zero Float** | Activity is on the critical path — any delay directly delays completion | Every day of employer delay = one day of EOT entitlement |\n| **Negative Float** | Projected completion already exceeds contract completion date | EOT can still be claimed for employer risk events — see below |\n\n#### Negative Float & EOT Entitlement\n\nNegative float does **NOT** bar an EOT claim. Negative float occurs when the programme's projected completion date already exceeds the contract completion date, even before a new delay event arises. This is common on complex infrastructure projects.\n\nThe SCL Protocol (Principles 6, 7 and 10) requires that each delay event be assessed for its own **incremental impact** on the critical path. If an employer risk event extends the completion date by a further 2 weeks — even where the programme already shows negative float — that 2-week impact remains an employer-caused delay.\n\n**Three practical scenarios:**\n\n- **Scenario 1 — Negative float from contractor delays:** The contractor still claims EOT for any employer risk event's incremental impact. Time Impact Analysis (TIA) handles this best.\n- **Scenario 2 — Negative float from employer delays:** This strengthens the EOT position. The employer delay events that drove the programme into negative float are themselves grounds for EOT.\n- **Scenario 3 — Concurrent delay with negative float:** The most complex scenario. Under the *Malmaison* approach, the contractor still gets EOT to protect against LDs but may not recover prolongation costs for the concurrent period.\n\n**Bottom line:** Float status (positive, zero, or negative) does not determine EOT entitlement. It is the **cause and incremental impact** of each delay event that matters.\n\n#### Terminal Float\n\nTerminal float is the gap between the contractor's planned completion date and the contract completion date.\n\nPer SCL Protocol Principle 13 (Early Completion): if the contractor planned to finish early and an employer delay consumes that terminal float, the contractor may still have a **compensation claim** for disruption to its planned programme — even if the contract date has not been breached.\n\n### 2.4 Concurrent Delay\n\n**SCL Protocol position:** Where employer delay is concurrent with contractor delay → contractor gets EOT (to protect from LD). But contractor may **NOT** recover prolongation costs for the concurrent period. This is the *Malmaison* approach (*Henry Boot v Malmaison* [1999]).\n\n#### Three Critical Nuances\n\n**Nuance 1 — True Concurrent vs Sequential Concurrent**\n\nTrue concurrent delay means two delay events start and end at the same time, both independently affecting the critical path. Sequential concurrent delay means the events overlap but do not start together. Tribunals apply the *Malmaison* approach more readily to true concurrent delay; sequential concurrent delay is often analysed by isolating each event's impact via TIA.\n\n**Nuance 2 — Contractual Allocation**\n\nThe *Malmaison* default can be contracted out. In *North Midland Building Ltd v Cyden Homes Ltd* [2018] EWCA Civ 1744, the English Court of Appeal upheld a contract clause that expressly excluded EOT where contractor delay was concurrent with employer delay. Parties are free to allocate the risk of concurrent delay as they choose.\n\n**Practical action:** Read the EOT clause carefully. Some bespoke amendments may include a \"contractor caused concurrent delay\" carve-out that strips the contractor of EOT entitlement. If found, raise this with management early — it is a major risk allocation issue.\n\n**Nuance 3 — Apportionment Approach**\n\nIn *City Inn Ltd v Shepherd Construction Ltd* [2010] CSIH 68, the Scottish courts took a different view: where it is impossible to say which delay was \"dominant\", the tribunal can apportion the EOT between employer and contractor causes (e.g. 60/40). This approach has not been adopted in English courts but remains influential and may be argued in arbitration.\n\n**Practical tip:** Always try to separate and identify each delay cause individually. Strong contemporaneous records are the best defence against concurrent delay arguments.\n\n### 2.5 Pacing Delays\n\n**What is pacing?** Pacing occurs when one party (usually the contractor) deliberately slows non-critical work to match the pace of the other party who is causing the critical path delay. It is a rational business decision.\n\n**Why it matters:** Pacing is **not** a contractor culpable delay. But it is frequently mischaracterised as one — especially in retrospective analysis.\n\n**How to prove pacing:**\n- Issue contemporaneous notice that you are pacing in response to the specific employer delay event\n- Identify the employer delay event you are pacing (cite notice/event reference)\n- Show the activity being paced was not on the critical path but for the employer delay\n- Demonstrate you had the resources and capability to proceed at planned pace\n- Confirm pacing did not extend the project completion date beyond the employer delay impact\n\n**Quick test:** \"Could I have proceeded at planned pace if the employer delay event had not occurred?\" If YES → pacing. If NO → genuine contractor delay.\n\n---\n\n## Part 3: The SCL Protocol — 22 Core Principles\n\n> References are to the SCL Delay and Disruption Protocol, 2nd Edition (February 2017), as supplemented by Rider 1 (February 2022). Rider 1 added guidance on COVID-19, BIM, concurrent delay analysis, and the relationship between EOT and compensation.\n\n| # | Principle | Key Point |\n|---|-----------|-----------|\n| 1 | **Programme & Records** | Maintain a proper baseline programme and comprehensive contemporaneous records. No records = no claim. |\n| 2 | **Purpose of EOT** | EOT relieves the contractor from LD liability and preserves the employer's right to levy LD. |\n| 3 | **Contractual Requirements** | Comply with notice requirements strictly. Late notice can be a time-bar. |\n| 4 | **Do NOT \"Wait and See\"** | Analyse delay impact contemporaneously. Prospective analysis is preferred over retrospective. |\n| 5 | **Procedure for Granting EOT** | Contract Administrator should assess and grant EOT promptly. |\n| 6 | **Effect of Delay** | Distinguish between employer risk events and contractor risk events. |\n| 7 | **Incremental Review** | Review EOT entitlement incrementally as delay events occur. |\n| 8–9 | **Float** | Float belongs to the project, not one party. See Section 2.3 for negative float. |\n| 10 | **Concurrent Delay & EOT** | Contractor entitled to EOT for employer delay even if concurrent with contractor delay. |\n| 11 | **Time-Distant Analysis** | Use recognised methods for retrospective analysis (see Part 4). |\n| 12 | **EOT ≠ Compensation** | EOT entitlement does not automatically mean compensation. |\n| 13 | **Early Completion** | Employer delay consuming terminal float may still entitle contractor to compensation. |\n| 14 | **Concurrent Delay & Compensation** | Contractor may not recover prolongation costs during concurrent delay periods. |\n| 15 | **Mitigation** | Both parties have mitigation obligations. |\n| 16 | **Acceleration** | Directed → compensation. Voluntary → own cost. Constructive → may claim costs (notify first!). |\n| 17 | **Global Claims** | Permissible only when impracticable to separate causes/effects. Courts are sceptical. |\n| 18 | **Disruption** | Distinct from delay. Prove using measured mile, project-specific study, earned value, or industry studies. |\n| 19 | **Variations** | Variations can cause both time and cost impact. Consider disruptive effect. |\n| 20 | **Prolongation Costs** | Based on actual additional cost incurred due to extended time on site. |\n| 21 | **Tender Allowances** | Actual cost, not tender rates, should be the basis for prolongation compensation. |\n| 22 | **Period of Evaluation** | Assess compensation for the period the delay actually affected. |\n\n---\n\n## Part 4: Delay Analysis Methods\n\n### Method Frameworks\n\nTwo recognised frameworks:\n- **SCL Protocol** (UK) — identifies six delay analysis methodologies\n- **AACEi Recommended Practice 29R-03** (US) — classifies methods using a 9-method matrix\n\nBoth are accepted in international arbitration.\n\n### Overview — Seven Methods\n\n| Method | When Used | Prospective/Retrospective | Complexity |\n|--------|-----------|--------------------------|------------|\n| **As-Planned vs As-Built** | Simple comparison | Retrospective | Low |\n| **Impacted As-Planned** | Add delay events to baseline | Prospective | Medium |\n| **Collapsed As-Built (But-For)** | Remove delay events from as-built | Retrospective | Medium-High |\n| **Time Impact Analysis (TIA)** | Insert delay events at time they occurred | Both | High |\n| **Windows Analysis** | Divide project into time windows | Both | High |\n| **Retrospective Longest Path** | Trace longest path on as-built | Retrospective | Medium |\n\n### As-Planned vs As-Built\n- Compare the original programme to what actually happened\n- **Pros:** Simple, easy to understand\n- **Cons:** Doesn't show causation; doesn't account for logic changes\n- **Best for:** Initial overview or simple disputes\n\n### Impacted As-Planned\n- Start with the baseline programme; add delay events as constraints\n- **Pros:** Forward-looking; easy to model\n- **Cons:** Assumes baseline was realistic; doesn't consider actual progress\n- **Best for:** Early-stage EOT applications\n\n### Collapsed As-Built (But-For)\n- Start with the as-built programme; remove delay events\n- **Pros:** Based on what actually happened\n- **Cons:** Difficult to reconstruct; subjective removal of events\n- **Best for:** Post-completion claims\n\n### Time Impact Analysis (TIA) — Preferred Method\n- Insert each delay event into the programme at the time it occurred\n- Analyse the critical path impact of each event progressively\n- **Pros:** Most rigorous; shows causation; accepted by tribunals; handles negative float correctly\n- **Cons:** Resource-intensive; requires good records and updated programmes\n- **Best for:** Complex projects, especially where negative float is present\n\n### Windows Analysis\n- Divide the project into time \"windows\" (e.g. monthly or by milestone)\n- Analyse the critical path and delays within each window\n- **Pros:** Systematic; handles concurrent delays well\n- **Cons:** Window boundary selection is subjective; very resource-intensive\n- **Best for:** Large projects with many delay events\n\n### Retrospective Longest Path Analysis\n- Identify the longest path on the as-built programme (the actual critical path)\n- Walk back through the activities and identify what delayed each one\n- **Pros:** Grounded in what actually happened; intuitive; useful when baseline is disputed\n- **Cons:** May ignore parallel critical paths; can miss delays absorbed by float\n- **Best for:** Disputes where the baseline programme is challenged\n\n### Choosing a Method\n\n**For prospective/ongoing analysis:**\n- Time Impact Analysis — insert delay events as they occur\n- Impacted As-Planned — for quick early-stage EOT applications\n\n**For retrospective/post-completion analysis:**\n- Windows Analysis — if many delay events across the project\n- Collapsed As-Built — if isolating specific employer delay events\n- Retrospective Longest Path — if as-built records are strong but baseline is disputed\n\n---\n\n## Part 5: Disruption Claims — How to Prove It\n\n### The Walter Lilly Test (UK, 2012)\n\nFour elements:\n1. **Compensable event** — identify the contract clause\n2. **Event caused disruption** — causal link (but-for test)\n3. **Disruption caused loss** — quantify the financial impact\n4. **Notice given** — comply with contractual notice requirements\n\n### Causation Standard\n\nPer *Costain Ltd v Charles Haswell & Partners Ltd* [2009] EWHC B25 (TCC): the contractor must prove not just that disruption occurred but that the **specific event caused identifiable productivity loss**. General assertions of \"inefficiency\" without linking specific events to specific losses will fail.\n\n**Practical implication:** For each disruption claim, build a causation chain:\n1. What was the event?\n2. Which activities were affected?\n3. What was the productivity benchmark?\n4. What was the actual productivity?\n5. What is the difference in cost?\n\n### How to Quantify Disruption\n\n| Method | Description | Persuasiveness |\n|--------|-------------|----------------|\n| **Measured Mile** | Compare productivity in disrupted vs undisrupted period on the same project | Highest |\n| **Project-Specific Study** | Detailed analysis of the project's productivity data | High |\n| **Earned Value Analysis** | Compare planned vs actual resource usage per unit of work | Medium-High |\n| **Industry Studies** | Published productivity loss factors (Leonard, MCAA) | Lower |\n| **System Dynamics** | Computer modelling of productivity impacts | Variable |\n\nMeasured Mile is the most accepted method. Industry studies are weakest because tribunals view them as too generic.\n\n### Common Causes of Disruption\n\n- Variations / change orders\n- Late information or approvals\n- Change in work sequencing\n- Restricted site access\n- Trade stacking (too many trades in same area)\n- Acceleration instructions\n\n---\n\n## Part 6: Force Majeure & Frustration\n\n### Force Majeure (Contract-Based)\n\n- Defined in the contract — check the specific FM clause\n- Consequences depend on contract terms (EOT? Termination? Cost sharing?)\n- Common FM events: war, pandemic, natural disaster, government action\n\n#### Hardship vs Force Majeure\n\n**Hardship is NOT Force Majeure.** An event becoming more expensive or difficult does not qualify as FM. FM requires the event to make performance **impossible or legally impermissible**, not merely uneconomical.\n\n#### COVID-19 Lessons\n\n- Generic FM clauses without specific pandemic reference often failed to trigger\n- Government-mandated shutdowns generally qualified as FM (or \"change in law\")\n- Modern FM clauses now expressly list \"pandemic\", \"epidemic\", and \"public health emergency\"\n- Notice and mitigation obligations were strictly enforced\n\n### Frustration (Common Law — Last Resort)\n\n- Contract is discharged — both parties walk away\n- Only applies when performance is impossible, illegal, or radically different\n- Very rarely successful — courts set a very high bar\n- **NOT frustration:** cost increases, labour shortages, bad weather, design changes\n\n---\n\n## Part 7: Key Case Law Quick Reference\n\n| Case | Jurisdiction | Key Principle |\n|------|-------------|---------------|\n| *Henry Boot v Malmaison* [1999] | UK | Concurrent delay — contractor gets EOT even if own delay is concurrent |\n| *Walter Lilly v Mackay* [2012] | UK | Disruption: 4 elements + notice; global basis possible |\n| *North Midland v Cyden Homes* [2018] EWCA Civ 1744 | UK | Parties can contract out of Malmaison — concurrent delay risk allocation is enforceable |\n| *City Inn v Shepherd* [2010] CSIH 68 | Scotland | Apportionment approach — tribunal can split EOT between causes |\n| *Costain v Charles Haswell* [2009] EWHC B25 (TCC) | UK | Disruption causation — must link specific events to specific productivity losses |\n| *Cleveland Bridge* [2012] | UK | Reasoned assessment on balance of probabilities |\n| *Van Oord v Allseas* [2015] | UK | Notice requirements matter |\n| *Alliance Concrete v Sato Kogyo* [2014] | Singapore | Frustration — high bar for frustration |\n| *Davis Contractors v Fareham* [1956] | UK | Frustration — 8-to-22-month overrun NOT frustration |\n| *Evergreat v Presscrete* [2006] | Singapore | Employer must do all things necessary for completion |\n| *TT International v Ho Lee* [2017] | Singapore | Employer must not prevent contractor from performing |\n| *Zurich Insurance v B-Gold* [2008] | Singapore | Extrinsic evidence admissible for contract interpretation |\n| *Lim Chin San v LW Infrastructure* [2011] | Singapore | Proper assessment by SO required; failure opens right to damages |\n| *John Doyle v Laing* [2004] | UK | Global claims — permissible if impracticable to separate |\n| *Wong Lai Ying v Chinachem* [1979] | Hong Kong | Unforeseeable landslip = frustration |\n\n---\n\n## Part 8: Key Definitions\n\n| Term | Definition |\n|------|-----------|\n| **EOT** | Extension of Time — additional time to complete without LD |\n| **LD** | Liquidated Damages — pre-agreed daily rate for late completion |\n| **Critical Path** | Longest chain of dependent activities determining completion date |\n| **Positive Float** | Time an activity can be delayed without affecting the critical path |\n| **Zero Float** | Activity is on the critical path — any delay directly delays completion |\n| **Negative Float** | Projected completion already exceeds contract completion date. Does NOT bar EOT claims. |\n| **Terminal Float** | Buffer between contractor's planned completion and contract completion date |\n| **Pacing Delay** | Deliberate slowing of non-critical work to match employer-caused critical path delay. Not contractor culpable delay. |\n| **Excusable Delay** | A delay that entitles the contractor to EOT. May or may not be compensable. |\n| **Compensable Delay** | A delay that entitles the contractor to both EOT and money. |\n| **Inexcusable Delay** | A contractor risk delay — no EOT, no compensation. |\n| **Logic Links** | Programme dependencies: FS (Finish-to-Start), SS (Start-to-Start), FF (Finish-to-Finish), SF (Start-to-Finish, rare). |\n| **Approved Programme** | Programme formally accepted by the Employer/Engineer. Reference point for delay analysis. |\n| **Working Programme** | Contractor's internal updated programme reflecting current progress and forecasts. |\n| **Baseline Programme** | Original approved programme — reference point for delay analysis |\n| **As-Built Programme** | Record of what actually happened |\n| **Time-Bar** | Contractu\n\nArchive v1.7.4: 29 files, 72985 bytes\n\nFiles: examples/strategy_input.json (3646b), examples/strategy_report_sample.md (10456b), references/adr_overview.md (4045b), references/arbitration_tactics.md (3206b), references/argument_ranking_guide.md (6855b), references/blank_worksheet.md (1864b), references/claim_preparation_checklist.md (2116b), references/common_pitfalls.md (2224b), references/concurrent_delay.md (3039b), references/delay_analysis_methods.md (3239b), references/delay_analysis_study_guide.md (21978b), references/disruption_claims.md (3980b), references/expert_engagement.md (2431b), references/legal_precedents.md (2960b), references/notice_requirements_checklist.md (1770b), references/quantum_worked_examples.md (6312b), references/quick_reference_card.md (2634b), references/record_keeping_checklist.md (1910b), references/response_template.md (2667b), references/risk_assessment_framework.md (2467b), references/seven_dimensions_guide.md (8586b), references/strategy_patterns.md (4636b), references/training_guide.md (4950b), references/worked_examples.md (12735b), scripts/strategy_advisor.py (33926b), scripts/version.py (282b), SKILL.md (18375b), tests/test_smoke.py (7723b), _meta.json (146b)\n\nArchive v1.7.3: 29 files, 72419 bytes\n\nFiles: examples/strategy_input.json (3646b), examples/strategy_report_sample.md (10456b), references/adr_overview.md (4045b), references/arbitration_tactics.md (3206b), references/argument_ranking_guide.md (6855b), references/blank_worksheet.md (1864b), references/claim_preparation_checklist.md (2116b), references/common_pitfalls.md (2224b), references/concurrent_delay.md (3039b), references/delay_analysis_methods.md (3239b), references/delay_analysis_study_guide.md (21978b), references/disruption_claims.md (3980b), references/expert_engagement.md (2431b), references/legal_precedents.md (2960b), references/notice_requirements_checklist.md (1770b), references/quantum_worked_examples.md (6312b), references/quick_reference_card.md (2634b), references/record_keeping_checklist.md (1910b), references/response_template.md (2667b), references/risk_assessment_framework.md (2467b), references/seven_dimensions_guide.md (8586b), references/strategy_patterns.md (4636b), references/training_guide.md (4950b), references/worked_examples.md (12735b), scripts/strategy_advisor.py (33926b), scripts/version.py (282b), SKILL.md (18073b), tests/test_smoke.py (6374b), _meta.json (146b)\n\nArchive v1.7.2: 29 files, 71841 bytes\n\nFiles: examples/strategy_input.json (3646b), examples/strategy_report_sample.md (10456b), references/adr_overview.md (4045b), references/arbitration_tactics.md (3206b), references/argument_ranking_guide.md (6855b), references/blank_worksheet.md (1864b), references/claim_preparation_checklist.md (2116b), references/common_pitfalls.md (2224b), references/concurrent_delay.md (3039b), references/delay_analysis_methods.md (3239b), references/delay_analysis_study_guide.md (21978b), references/disruption_claims.md (3980b), references/expert_engagement.md (2431b), references/legal_precedents.md (2960b), references/notice_requirements_checklist.md (1770b), references/quantum_worked_examples.md (6312b), references/quick_reference_card.md (2634b), references/record_keeping_checklist.md (1910b), references/response_template.md (2667b), references/risk_assessment_framework.md (2467b), references/seven_dimensions_guide.md (8586b), references/strategy_patterns.md (4636b), references/training_guide.md (4950b), references/worked_examples.md (12735b), scripts/strategy_advisor.py (33926b), scripts/version.py (282b), SKILL.md (17584b), tests/test_smoke.py (5229b), _meta.json (146b)\n\nArchive v1.7.1: 29 files, 70077 bytes\n\nFiles: examples/strategy_input.json (3646b), examples/strategy_report_sample.md (10456b), references/adr_overview.md (4045b), references/arbitration_tactics.md (3206b), references/argument_ranking_guide.md (6855b), references/blank_worksheet.md (1864b), references/claim_preparation_checklist.md (2116b), references/common_pitfalls.md (2224b), references/concurrent_delay.md (3039b), references/delay_analysis_methods.md (3239b), references/delay_analysis_study_guide.md (21978b), references/disruption_claims.md (3980b), references/expert_engagement.md (2431b), references/legal_precedents.md (2960b), references/notice_requirements_checklist.md (1770b), references/quantum_worked_examples.md (6312b), references/quick_reference_card.md (2634b), references/record_keeping_checklist.md (1910b), references/response_template.md (2667b), references/risk_assessment_framework.md (2467b), references/seven_dimensions_guide.md (8586b), references/strategy_patterns.md (4636b), references/training_guide.md (4950b), references/worked_examples.md (12735b), scripts/strategy_advisor.py (33273b), scripts/version.py (282b), SKILL.md (13350b), tests/test_smoke.py (5203b), _meta.json (146b)\n\nArchive v1.7.0: 29 files, 69549 bytes\n\nFiles: examples/strategy_input.json (3646b), examples/strategy_report_sample.md (10456b), references/adr_overview.md (4045b), references/arbitration_tactics.md (3206b), references/argument_ranking_guide.md (6855b), references/blank_worksheet.md (1864b), references/claim_preparation_checklist.md (2116b), references/common_pitfalls.md (2224b), references/concurrent_delay.md (3039b), references/delay_analysis_methods.md (3239b), references/delay_analysis_study_guide.md (21978b), references/disruption_claims.md (3980b), references/expert_engagement.md (2431b), references/legal_precedents.md (2960b), references/notice_requirements_checklist.md (1770b), references/quantum_worked_examples.md (6312b), references/quick_reference_card.md (2634b), references/record_keeping_checklist.md (1910b), references/response_template.md (2667b), references/risk_assessment_framework.md (2467b), references/seven_dimensions_guide.md (8586b), references/strategy_patterns.md (4636b), references/training_guide.md (4950b), references/worked_examples.md (12735b), scripts/strategy_advisor.py (33273b), scripts/version.py (282b), SKILL.md (13349b), tests/test_smoke.py (3783b), _meta.json (146b)\n\nArchive v1.6.1: 29 files, 70578 bytes\n\nFiles: examples/strategy_input.json (5161b), examples/strategy_report_sample.md (12265b), references/adr_overview.md (4045b), references/arbitration_tactics.md (3206b), references/argument_ranking_guide.md (6855b), references/blank_worksheet.md (1864b), references/claim_preparation_checklist.md (2116b), references/common_pitfalls.md (2224b), references/concurrent_delay.md (3039b), references/delay_analysis_methods.md (3239b), references/delay_analysis_study_guide.md (21978b), references/disruption_claims.md (3980b), references/expert_engagement.md (2431b), references/legal_precedents.md (2960b), references/notice_requirements_checklist.md (1770b), references/quantum_worked_examples.md (6312b), references/quick_reference_card.md (2634b), references/record_keeping_checklist.md (1910b), references/response_template.md (2667b), references/risk_assessment_framework.md (2467b), references/seven_dimensions_guide.md (8586b), references/strategy_patterns.md (4636b), references/training_guide.md (4950b), references/worked_examples.md (12735b), scripts/strategy_advisor.py (33273b), scripts/version.py (282b), SKILL.md (13349b), tests/test_smoke.py (3584b), _meta.json (146b)\n\nArchive v1.6.0: 29 files, 70237 bytes\n\nFiles: examples/strategy_input.json (5161b), examples/strategy_report_sample.md (12265b), references/adr_overview.md (4045b), references/arbitration_tactics.md (3206b), references/argument_ranking_guide.md (6855b), references/blank_worksheet.md (1864b), references/claim_preparation_checklist.md (2116b), references/common_pitfalls.md (2224b), references/concurrent_delay.md (3039b), references/delay_analysis_methods.md (3239b), references/delay_analysis_study_guide.md (21978b), references/disruption_claims.md (3980b), references/expert_engagement.md (2431b), references/legal_precedents.md (2960b), references/notice_requirements_checklist.md (1770b), references/quantum_worked_examples.md (6312b), references/quick_reference_card.md (2634b), references/record_keeping_checklist.md (1910b), references/response_template.md (2667b), references/risk_assessment_framework.md (2467b), references/seven_dimensions_guide.md (8586b), references/strategy_patterns.md (4636b), references/training_guide.md (4950b), references/worked_examples.md (12735b), scripts/strategy_advisor.py (31625b), scripts/version.py (282b), SKILL.md (13349b), tests/test_smoke.py (3584b), _meta.json (146b)\n\nArchive v1.5.0: 26 files, 60845 bytes\n\nFiles: references/adr_overview.md (4045b), references/arbitration_tactics.md (3206b), references/argument_ranking_guide.md (6855b), references/blank_worksheet.md (1864b), references/claim_preparation_checklist.md (2116b), references/common_pitfalls.md (2224b), references/concurrent_delay.md (3039b), references/delay_analysis_methods.md (3239b), references/delay_analysis_study_guide.md (21978b), references/disruption_claims.md (3980b), references/expert_engagement.md (2431b), references/legal_precedents.md (2960b), references/notice_requirements_checklist.md (1770b), references/quantum_worked_examples.md (6312b), references/quick_reference_card.md (2634b), references/record_keeping_checklist.md (1910b), references/response_template.md (2667b), references/risk_assessment_framework.md (2467b), references/seven_dimensions_guide.md (8586b), references/strategy_patterns.md (4636b), references/training_guide.md (4950b), references/worked_examples.md (12735b), scripts/strategy_advisor.py (31470b), scripts/version.py (282b), SKILL.md (11449b), _meta.json (146b)","readmeExcerpt":"Skill: Construction Claim Strategy Owner: redkiwi1688-prog Summary: Strategic planning framework for construction claim responses — plan direction, scope, arguments, and disclosure strategy BEFORE selecting clauses or draftin... Tags: latest:1.7.6 Version history: v1.7.6 | 2026-05-17T10:34:10.649Z | user v1.7.6: Added 'Working out the actual deadline' section (calendar-day counting, s.50(a), ad-hoc holidays, points t","codeSnippets":[],"executableExamples":[{"language":"bash","snippet":"python3 scripts/strategy_advisor.py --reference"},{"language":"bash","snippet":"python3 scripts/strategy_advisor.py"},{"language":"bash","snippet":"python3 scripts/strategy_advisor.py --file strategy_input.json --output strategy_report.md"},{"language":"bash","snippet":"python3 scripts/strategy_advisor.py --save-strategy my_strategy.json"},{"language":"text","snippet":"usage: strategy_advisor [-h] [--file INPUT_JSON] [--output FILE]\n                        [--format {md,txt}] [--save-strategy PATH]\n                        [--reference] [--version]\n\nStrategy Advisor — Strategic planning framework for construction claim\nresponses. Plan your direction, scope, and argument strategy BEFORE selecting\nclauses.\n\noptions:\n  -h, --help            show this help message and exit\n  --file INPUT_JSON     Non-interactive: read strategy inputs from a JSON\n                        file.\n  --output, -o FILE     Write report to file instead of stdout.\n  --format, -f {md,txt}\n                        Output format (default: md).\n  --save-strategy PATH  Save the strategy data as JSON for reuse.\n  --reference           Print all reference tables (argument types, patterns,\n                        etc.) and exit.\n  --version             show program's version number and exit"},{"language":"bash","snippet":"# Show all reference tables\npython3 scripts/strategy_advisor.py --reference\n\n# Run interactive wizard\npython3 scripts/strategy_advisor.py\n\n# Non-interactive from JSON\npython3 scripts/strategy_advisor.py --file input.json --output report.md\n\n# Save strategy for reuse\npython3 scripts/strategy_advisor.py --save-strategy strategy.json"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: construction-claim-strategy\ndescription: Strategic planning framework for construction claim responses — plan direction, scope, arguments, and disclosure strategy BEFORE selecting clauses or drafting. Covers situation assessment, scope control, direction decisions, argument ranking, disclosure control, response architecture, and risk assessment for EOT, delay, disruption, variation, and payment claims under PSSCOC, FIDIC, NEC, SIA, and bespoke forms. Includes practical checklists, quantum calculation methods, ADR strategies, delay analysis methods, concurrent delay, disruption claims, arbitration tactics, expert engagement, notice compliance, and legal precedent guidance.\n---\n\n# Construction Claim Strategy\n\n**Strategic planning framework for construction claim responses.**\n\nPlan your direction, scope, arguments, and disclosure strategy **before** selecting clauses or drafting correspondence.\n\n---\n\n## Why use this?\n\n- Stop jumping straight to clause selection — plan the strategy first.\n- Rank arguments by strength (Textual Interpretation is strongest).\n- Control what to disclose precisely, keep general, or defer.\n- Choose proven response structures.\n- Avoid common mistakes that weaken your position.\n\n---\n\n## Who this is for\n\n- Contract managers\n- Claims consultants\n- Quantity surveyors\n- Commercial managers\n- Construction lawyers\n- Anyone preparing responses to claims or formal queries under construction contracts\n\n---\n\n## What this skill does\n\nUse this tool to systematically work through 7 key dimensions:\n\n1. **Situation Assessment** — Understand exactly what you are responding to.\n2. **Scope Control** — Decide what to address and what to avoid volunteering.\n3. **Direction Decision** — Choose primary and fallback arguments, and what to avoid.\n4. **Argument Strategy** — Select the strongest type of argument available.\n5. **Disclosure Control** — Decide what to state precisely, keep general, or defer.\n6. **Response Architecture** — Choose the most effective structure for your reply.\n7. **Risk Assessment** — Identify counter-arguments, weak points, and timing risks.\n\nPlus **practical tools and reference guides** covering:\n\n- Record keeping checklists\n- Claim preparation checklists (adjudication & arbitration)\n- Notice requirements compliance\n- Expert engagement guidance\n- ADR strategy (negotiation, mediation, adjudication, arbitration)\n- Concurrent delay strategic approach\n- Disruption claims strategy\n- Delay analysis methods (As-Planned vs As-Built, TIA, Collapsed As-Built, Windows)\n- Arbitration tactics and prolongation strategies\n- Quantum calculation worked examples (Eichleay, Hudson, Emden, Measured Mile, Actual Cost, Total Cost)\n- Legal precedents overview (Prevention Principle, Common Law vs Civil Law)\n- Common pitfalls and how to avoid them\n- Risk assessment framework\n\n---\n\n## Supported contract forms\n\nWorks with any construction contract form:\n- PSSCOC (Construction Works / D&B)\n- FIDIC (Red, Yellow, Silver, Emerald)\n- NEC (NEC3, "},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn77g2eearfhaq251ab7jtrctn854v1s\",\n  \"slug\": \"construction-claim-strategy\",\n  \"version\": \"1.7.6\",\n  \"publishedAt\": 1779014050649\n}"},{"path":"references/adr_overview.md","content":"# ADR in Construction Claims — Overview & Strategies\n\nAlternative Dispute Resolution (ADR) provides ways to resolve disputes without going to full court litigation. Choosing the right method depends on your goals: speed, cost, finality, cash flow, and relationship preservation.\n\n---\n\n## ADR Methods Comparison\n\n| Method | Description | Binding? | Speed | Cost | Best Used When |\n|--------|-------------|----------|-------|------|---------------|\n| **Negotiation** | Direct discussion between parties | No | Fast | Low | Early stage, good relationship |\n| **Mediation** | Neutral facilitator helps reach settlement | No (usually) | Fast | Low–Medium | Preserve relationship, complex issues |\n| **Adjudication** | Fast interim decision by adjudicator | Yes (usually interim/temporary) | Very Fast | Medium | Cash flow or interim relief needed |\n| **Arbitration** | Private tribunal makes final decision | Yes (final) | Medium–Slow | High | Final resolution, international disputes |\n| **Litigation** | Court proceedings | Yes (final) | Slow | High | Last resort, complex legal points |\n\n---\n\n## ADR Strategy Recommendations\n\n1. **Start with negotiation** where possible — many disputes can be resolved early if approached professionally\n2. **Use mediation** when preserving the commercial relationship is important or when issues are complex\n3. **Consider adjudication** (where available) for fast interim cash flow or time-related decisions\n4. **Choose arbitration** for final, binding resolution, especially in international projects\n5. **Use litigation** generally as a last resort due to cost, time, and relationship impact\n\n---\n\n## Adjudication vs Arbitration — Detailed Comparison\n\n| Aspect | Adjudication | Arbitration |\n|--------|-------------|-------------|\n| **Nature** | Fast interim decision | Final and binding decision |\n| **Speed** | Very fast (usually 28–42 days in statutory regimes) | Slow to medium (6–24 months) |\n| **Cost** | Relatively low | High |\n| **Binding** | Binding until finally determined by arbitration or litigation | Final and binding |\n| **Enforceability** | Enforceable in jurisdictions with statutory adjudication | Enforceable internationally (New York Convention) |\n| **Right of appeal** | Limited (usually only jurisdiction or natural justice) | Limited, depends on seat of arbitration |\n| **Procedure** | Relatively informal and fast | More formal, similar to litigation |\n| **Evidence** | Often limited written submissions | Full hearing with witnesses and experts |\n| **Relationship impact** | Can be less damaging if used early | Often more adversarial |\n\n### When to Choose Adjudication\n\n- Need **quick cash flow** relief\n- Want to keep the project moving during dispute resolution\n- Dispute is relatively straightforward\n- Available under a statutory regime or contract\n\n### When to Choose Arbitration\n\n- Need a **final and binding** decision\n- Dispute is complex, high-value, or multi-issue\n- International enforceability matters\n- Parties can choose arb"},{"path":"references/arbitration_tactics.md","content":"# Arbitration Tactics & Prolongation Claim Strategies\n\n---\n\n## Arbitration Tactics — Common Law vs Civil Law\n\n### Common Law Arbitrations\n\n- Heavy emphasis on **contemporaneous documents**, detailed witness statements, and expert reports\n- Cross-examination is often rigorous — be prepared to defend methodology and credibility in detail\n- Broader **document disclosure** is common; failure to disclose can damage credibility\n- Significant reliance on **case law and precedents** in areas such as notice, prevention principle, and quantum methods\n- **Strategy:** Build a document-heavy, precedent-supported case with strong expert evidence\n\n### Civil Law / Mixed Arbitrations\n\n- Greater emphasis on overall **fairness, good faith, and commercial equity**\n- Cross-examination may be less confrontational, depending on tribunal and rules\n- Disclosure is usually **narrower**\n- More reliance on principles of good faith and fairness than strict precedent\n- **Strategy:** Combine strong factual evidence with clear arguments on equity and the parties' reasonable expectations\n\n---\n\n## Comparison Table\n\n| Aspect | Common Law Arbitration | Civil Law / Mixed Arbitration |\n|--------|----------------------|------------------------------|\n| Documents | Heavy reliance; broad disclosure | Narrower disclosure |\n| Witnesses | Detailed statements; rigorous cross-exam | Less confrontational |\n| Experts | Essential for complex claims | Important but approach may differ |\n| Precedents | Key part of submissions | Persuasive but less central |\n| Good faith | Developing | Central principle |\n| Strategy focus | Document + precedent | Equity + evidence |\n\n---\n\n## Prolongation Claim Strategies in Arbitration\n\n### Common Law Approach\n\n- Strong focus on proving **EOT first** (critical path impact) before claiming prolongation costs\n- Expect detailed scrutiny of quantum methods and baseline assumptions\n- Concurrent delay arguments are common and must be addressed **proactively**\n- **Strategy:** Secure the EOT foundation first, then build a well-supported prolongation claim — preferably based on actual costs with formula methods as fallback\n\n### Civil Law Approach\n\n- The link between EOT and prolongation costs may be assessed **more flexibly**, depending on governing law and tribunal approach\n- Actual costs remain preferred, but good faith and fairness arguments may help bridge gaps in strict causation proof\n- **Strategy:** Emphasise the overall impact and equity of the situation while still providing clear cost evidence\n\n---\n\n## Practical Recommendations\n\n1. **Know your tribunal** — research the arbitrators' backgrounds and preferred approaches\n2. **Prepare for cross-examination** — ensure witnesses and experts are thoroughly prepared\n3. **Disclosure strategy** — balance completeness with risk of revealing unhelpful documents\n4. **Quantum foundation** — always anchor prolongation to a clear EOT finding\n5. **Address concurrent delay proactively** — don't leave it for the other side to raise"},{"path":"references/argument_ranking_guide.md","content":"# Argument Ranking — Detailed Guide\n\n*Construction Claim Strategy Framework — Fully Generic*\n\n---\n\n## Why the Ranking Exists\n\nNot all arguments carry the same weight. Stronger arguments are harder to rebut and more likely to be accepted by tribunals, adjudicators, and courts. Weaker arguments are easier to challenge.\n\nAlways start from the top of the ranking. Only move down when stronger options are unavailable.\n\n---\n\n## Rank 1: Textual Interpretation (Strongest)\n\n**What it is:**\nArgue directly from the actual words used in the Contract clause.\n\n**Why it is strongest:**\n- Based on express terms the parties agreed to.\n- Most objective and difficult for the other side to dismiss.\n- Tribunals and courts prefer to give effect to clear wording.\n\n**When to use:** Whenever the wording of the clause supports your position.\n\n**Example structure:**\n> The Contract provides that the Contractor shall be entitled to [entitlement] where the Authority issues an instruction which changes the scope of the Works.\n> On [date], the Authority issued Instruction No. X which required the Contractor to [specific change]. This instruction directly changed the scope.\n> Accordingly, the Contractor is entitled to [relief] pursuant to the clear wording of the clause.\n\n**Recommended disclosure level:** State Precisely — you can be confident and specific.\n\n---\n\n## Rank 2: Factual Distinction (Strong)\n\n**What it is:**\nAccept that the clause exists, but argue that the facts of your case fall outside the situation the clause was intended to cover.\n\n**Why it is strong:**\nStays close to the Contract wording while showing why the clause does not apply to the current situation.\n\n**When to use:** When the clause wording is not clearly in your favour, but the facts are materially different from what the clause contemplates.\n\n**Example structure:**\n> While the Contract contains provisions regarding [subject], those provisions are predicated on the assumption that [normal situation].\n> In the present case, the situation is materially different because [key factual difference].\n> Accordingly, the clause does not operate to [deny the claim / allocate risk in the way suggested].\n\n**Recommended disclosure level:** State Precisely or Keep General — be precise on facts that support the distinction.\n\n---\n\n## Rank 3: Concede-then-Distinguish (Moderate-Strong)\n\n**What it is:**\nConcede that the clause would normally apply, then explain why the current situation is extraordinary or materially different.\n\n**Why it is moderate-strong:**\nShows reasonableness (not denying the clause entirely), while still protecting your position.\n\n**When to use:** When the clause appears to go against you at first glance, but there are good reasons why it should not apply in this specific case.\n\n**Example structure:**\n> The Contractor acknowledges that, in normal circumstances, [risk] would be allocated to the Contractor under the Contract.\n> However, the present situation is materially different. The Authority [did X "}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"Strategic planning framework for construction claim responses — plan direction, scope, arguments, and disclosure strategy BEFORE selecting clauses or draftin... Skill: Construction Claim Strategy Owner: redkiwi1688-prog Summary: Strategic planning framework for construction claim responses — plan direction, scope, arguments, and disclosure strategy BEFORE selecting clauses or draftin... Tags: latest:1.7.6 Version history: v1.7.6 | 2026-05-17T10:34:10.649Z | user v1.7.6: Added 'Working out the actual deadline' section (calendar-day counting, s.50(a), ad-hoc holidays, points t","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":2181,"uniquenessScore":46,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-11T03:14:25.857Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-11T03:14:25.857Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-11T05:34:33.302Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}