document-approval-tracker-scott-margetts
Approval cascade definition and tracking for multi-stakeholder document workflows. Internal review sequences, client approval workflows, regulatory review, overdue chasing with escalation logic, version control coordination, and cross-jurisdiction document dependencies. Use when defining who reviews a document and in what order, tracking where a document is stuck in the approval chain, chasing an overdue reviewer, preventing reviewers working on superseded drafts, or mapping dependencies between documents across jurisdictions. Trigger on: 'who needs to approve this', 'document approval', 'revi
npx skills add lawve-ai/awesome-legal-skills --skill document-approval-tracker-scott-margetts --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The skill designs and tracks multi-stakeholder document approval workflows, including who reviews in what order, how to monitor where a document is in the cascade, chasing overdue reviewers with escalation logic, coordinating version control, and mapping cross-jurisdiction document dependencies.
How it works
Mode 1 — Approval cascade design: At matter setup, defines internal review sequence, client release gate, client-side cascade, regulatory/external review, and cross-document dependencies. Produces an explicit cascade document with sections for DOCUMENT MIGRATION PATH, INTERNAL REVIEW SEQUENCE, CLIENT RELEASE GATE, CLIENT-SIDE CASCADE, REGULATORY / EXTERNAL REVIEW (if applicable), CROSS-DOCUMENT DEPENDENCIES, and GAPS REQUIRING CONFIRMATION BEFORE CASCADE IS ACTIVATED. Requires confirmation of an identifier block before starting cascade design.
Mode 2 — Position tracking and status: When a document is in circulation, generates a status tracker showing current location, time at each step, and SLA-based flags (On track / At risk / Overdue) with an 80% threshold for escalation. Includes an overall status and next actions. Uses the provided cascade design as reference and can populate dates from input where available.
Mode 3 — Overdue chasing and escalation: If a reviewer is overdue, produces a chasing email at the appropriate escalation stage based on days overdue (Day 1, 3, 5, 7+), with templates for Day 1, Day 3, and Day 5. The Day 7+ stage escalates to partner-level. Output is generated first; tone and nuance can be adjusted by the LPM after drafting.
Mode 4 — Version control and superseded draft management: Handles scenarios where reviewers work on incorrect versions and coordinates version control across teams (inputs include current correct version, incorrect version, reviewer, and identification of the issue).
When to use it
- Defining who reviews a document and in what sequence at matter setup
- Tracking which reviewer currently has a document and for how long
- Chasing an overdue reviewer with the right escalation approach
- Preventing reviewers from commenting on superseded draft versions
- Mapping which documents are blocked by other documents across jurisdictions
# Document Approval Tracker You are a Legal Project Management skill that designs and tracks multi-stakeholder document approval workflows — defining review sequences, monitoring document position in the cascade, chasing overdue reviewers, coordinating version control, and mapping cross-jurisdiction document dependencies. Document approval is the invisible critical path on most legal matters. Partners and clients know what documents need to exist; nobody tracks where they are in the review chain until a deadline appears. An SPA that has been with a client contact for six days, a tax opinion waiting for a partner who is travelling, a Dutch filing blocked because the German regulatory determination hasn't landed — these are the failure modes this skill is designed to prevent. The LPM's role in document approval is coordination, not legal review. The LPM tracks position, chases overdue reviewers, manages version control, and flags cross-document dependencies. The supervising attorney decides whether a document is ready to release and whether a reviewer's comments require further legal work. ## When to use this skill - Defining who reviews a document and in what sequence at matter setu
- When to use this skill
- Input Classification — Run This First
- Before Starting Any Mode
- Operating Modes
- Mode 1 — Approval cascade design
- Mode 2 — Position tracking and status
- Mode 3 — Overdue chasing and escalation
- Mode 4 — Version control and superseded draft management
- Domain Knowledge — Why Document Approval Fails
- Output Format
- LPM vs Attorney Boundary
- Cross-Skill Handoffs
- M365 Connected Mode and DMS Integration
- Time-Sensitive Assumptions
What does the document-approval-tracker-scott-margetts skill do?
Approval cascade definition and tracking for multi-stakeholder document workflows. Internal review sequences, client approval workflows, regulatory review, overdue chasing with escalation logic, version control coordination, and cross-jurisdiction document dependencies. Use when defining who reviews a document and in what order, tracking where a document is stuck in the approval chain, chasing an overdue reviewer, preventing reviewers working on superseded drafts, or mapping dependencies between documents across jurisdictions. Trigger on: 'who needs to approve this', 'document approval', 'revi
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill document-approval-tracker-scott-margetts --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.