Comparing trust draft documents against client instructions requires provision-by-provision deviation analysis that traces the practical downstream consequences of each departure and explains the drafting decisions behind any intentional divergence.
Scanned 9/11/2026
Install to Claude Code
npx -y skills add sunyifeisb-art/legalwork --skill compare-trust-documents-against-client-instructions --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Compare Trust Documents Against Client Instructions?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sunyifeisb-art-compare-trust-documents-against-client-instruction)More formats (shields.io, HTML) on the badges page.
---
name: compare-trust-documents-against-client-instructions
task_id: trusts-estates-private-client/compare-trust-documents-against-client-instructions
description: Comparing trust draft documents against client instructions requires provision-by-provision deviation analysis that traces the practical downstream consequences of each departure and explains the drafting decisions behind any intentional divergence.
activates_for: [planner, solver, checker]
---
# Skill: Compare Trust Documents Against Client Instructions — Deviation Report
## 1. Subject-matter triage
- Treat the client instruction memo as the baseline directive and compare each draft trust and pour-over will provision against it.
- First enumerate the draft documents and the major planning topics they cover, then compare each topic against the corresponding instruction set before drawing conclusions.
- If only one draft addresses a topic, say so expressly; if multiple drafts address the same topic, compare them together to catch coordination errors.
- Write the report as an advisory deviation analysis, not a rewrite or a summary of the documents.
## 2. Failure modes the skill is correcting
- Identifying differences without stating the practical downstream effect on the client’s plan, administration, or beneficiary outcomes.
- Missing intentional departures from instructions and failing to explain the legal or practical reason for the deviation.
- Overlooking age-triggered or milestone-triggered provisions where one drafting error propagates through later distribution timing or termination mechanics.
- Treating trustee selection as a stylistic choice when it may affect administration, bonding, conflicts, or acceptance logistics.
- Leaving personal-property gifts vague when the instructions call for specific items, named recipients, and special-handling or storage directions.
- Failing to coordinate the trust, pour-over will, and any other companion estate-planning documents for consistency in fiduciary appointments, residuary language, naming, and funding mechanics.
- Reporting issues without a uniform severity judgment or without a concrete next step.
- Stating legal conclusions without identifying the governing doctrine, rule, or statutory framework supporting the conclusion.
## 3. Legal frameworks / domain conventions that apply
- The client instruction memo governs drafting choices unless a legal or practical reason justifies departure; unexplained divergence is a deviation.
- Trusts and wills are read as a coordinated estate plan, so fiduciary appointments, dispositive provisions, trust references, and funding language must be internally consistent across documents.
- Age-based distributions and termination provisions must be checked for downstream timing effects; any numeric error can alter later milestones and administration dates.
- Trustee selection is not merely nominal; qualifications, conflicts, bonding, and institutional administration considerations can make an apparently small departure material.
- Personal-property dispositions require specificity: identify the asset, the intended recipient, and any custodial, insurance, climate-control, or handling instruction needed for execution.
- Where the draft diverges intentionally, the report should state the drafting rationale and the authority or practical constraint that supports the alternative.
- Any legal proposition in the report should be tied to a controlling source, as identified in the materials or by generally recognized estate-planning doctrine.
- Use a uniform ordinal severity scale throughout the report, and define the scale once before applying it.
## 4. Analytical scaffolds
1. Enumerate the documents and provisions in scope before analysis:
- trust draft,
- pour-over will draft,
- instruction memo,
- background summary,
- any companion drafting notes or internal references.
2. For each issue, identify:
- the instruction or background point,
- the draft provision,
- the nature of the divergence,
- the practical effect if executed as written,
- the correction or clarification needed.
3. For every issue, close the analysis by:
- anchoring the issue to the relevant instruction or operative term,
- cross-referencing any related clause or companion document,
- stating the beneficiary, fiduciary, tax, administrative, or litigation consequence.
4. For any intentional deviation, state:
- why the departure was made,
- what legal or practical constraint supports it,
- what alternative drafting approach was chosen.
5. For age or milestone provisions, trace the effect forward through later timing-based clauses rather than stopping at the first discrepancy.
6. For trustee and fiduciary provisions, test both the named person and the appointment mechanics for internal consistency with the rest of the estate plan.
7. For personal-property gifts, confirm item specificity, recipient designation, and any special-care instructions; if any are missing, flag the item as incomplete.
8. For cross-document review, check that naming conventions, residuary dispositions, trust references, funding language, and pour-over mechanics align exactly enough to function together.
## 5. Vertical / structural / temporal relationships
- Read the trust and pour-over will vertically, from definitions and fiduciary appointments through dispositive provisions and administrative mechanics, because a mismatch at the top of the document can infect later sections.
- Read the documents temporally, checking whether one provision changes the operation of a later distribution date, termination event, fiduciary power, or funding step.
- When a provision affects another clause in the same document or in a companion document, describe that relationship directly rather than listing the issue in isolation.
- If a term, name, age, or milestone appears in more than one document, compare all instances and reconcile them before reporting the deviation.
## 6. Output structure conventions
- Use an issue-by-issue deviation report organized in conventional memo form.
- Define a clear ordinal severity scale near the top and apply it uniformly to every issue.
- For each issue, include:
- severity,
- instruction reference,
- draft provision reference,
- deviation description,
- practical impact,
- related provision or cross-document inconsistency,
- correction or clarification needed.
- Distinguish between required corrections and open points needing client confirmation before execution.
- Group related deviations where doing so improves clarity, but do not merge distinct issues that have different effects or fixes.
- Include a short recommended-actions section at the end with imperative next steps, the responsible role, and a timing anchor tied to the drafting or signing process.
- If the materials identify a controlling statute, rule, or doctrine, cite it by name and section or other controlling citation when stating the applicable legal point.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!