# Leg Evidence Documentation Standard

> Establish and maintain evidence standards for claims and disputes including document retention, chain of custody, and admissibility

- Skill: `construct-ai-primary/leg-evidence-documentation-standard` (Agent Skill)
- Install (CLI): `npx skillmds@latest add construct-ai-primary/leg-evidence-documentation-standard`
- Raw SKILL.md: https://api.skillmd.com/api/skills/construct-ai-primary/leg-evidence-documentation-standard/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- Author: Construct-AI-primary (https://skillmd.com/u/construct-ai-primary)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/construct-ai-primary/leg-evidence-documentation-standard

---


# Legal Evidence and Documentation Standards

## Overview
Establish and maintain evidence standards for claims and disputes including document retention, chain of custody, and admissibility

**Announce at start:** "I'm using the leg-evidence-documentation-standard skill for 01750_Legal operations."

## When to Use This Skill

**Trigger Conditions:** Dispute anticipated, evidence required, document production ordered
**Prerequisites:** 
- Domain knowledge available (01750_legal domain knowledge)
- Appropriate authority and permissions granted
- Relevant contracts/policies/standards accessible
- Required input data gathered

## Step-by-Step Procedure

### Step 1: Initiation and Scoping
1. Identify the specific 01750_legal task or request triggering this skill
2. Verify the requesting party has appropriate authority
3. Gather all required input documents, contracts, and supporting data
4. Confirm the scope clearly matches this skill's purpose

### Step 2: Analysis and Assessment
1. Review all relevant domain knowledge sections for this discipline
2. Identify applicable standards, codes, and regulatory requirements
3. Assess any dependencies on other disciplines or agents
4. Document any gaps, ambiguities, or conflicting requirements

### Step 3: Execution
1. Apply discipline-specific methods and tools for establish and maintain evidence standards for claims and disputes including document retention, chain of custody, and admissibility
2. Generate required outputs using approved templates and formats
3. Maintain full audit trail of all actions, decisions, and outputs
4. Cross-reference with related contracts, policies, and standards

### Step 4: Quality Review
1. Validate all outputs against domain knowledge requirements
2. Verify compliance with applicable standards and regulations
3. Ensure all required documentation is complete and accurate
4. Identify any exceptions, deviations, or non-standard items

### Step 5: Approval and Routing
1. Route outputs through appropriate approval workflow
2. Ensure approval authority matches delegated authority limits
3. Incorporate any required revisions from reviewers
4. Obtain final approval and sign-off

### Step 6: Close-Out and Filing
1. File all outputs in appropriate registers and repositories
2. Update relevant tracking systems and databases
3. Archive working documents per retention policy
4. Update legal records and logs

## Success Criteria

- [ ] Task scope clearly defined and authorized
- [ ] All required inputs gathered and validated
- [ ] Legal Evidence and Documentation Standards output generated per requirements
- [ ] Compliance with applicable standards verified
- [ ] Quality review completed and documented
- [ ] Approval obtained through proper workflow
- [ ] Outputs filed in appropriate registers
- [ ] Audit trail complete and accurate
- [ ] Success metric achieved: Evidence standards established, documents preserved, production requests managed

## Common Pitfalls

1. **Incomplete Inputs** — Attempting execution without all required documents. Always verify completeness before starting.
2. **Outdated References** — Using superseded contracts, policies, or regulatory requirements. Always check for current versions.
3. **Missing Authority** — Acting beyond delegated authority limits. Always verify approver authority before routing.
4. **Inadequate Documentation** — Failing to maintain audit trail or file outputs properly. Every action must be documented.
5. **Non-Compliant Outputs** — Generating outputs that don't meet applicable standards. Always validate against requirements.
6. **Time-Sensitive Actions** — Missing contractual or regulatory time limits. Track all deadlines and notice periods.

## Cross-References

### Related Skills
- Additional governance skills for related governance functions
- Other skills for cross-functional tasks

### Related Agents
- **Primary:** Legal Manager
- **Supporting:** Governance Administrator for document management
- **Oversight:** Governance Manager for review and approval

### Related Domain Knowledge
- 01750_Legal Domain Knowledge for role responsibilities
- 01750_Legal Glossary for terminology and definitions