# Contracts Correspondence Management

> Manage all formal contract correspondence, maintain contract records, track outstanding contractual matters, and ensure proper documentation of all contractual events

- Skill: `construct-ai-primary/contracts-correspondence-management` (Agent Skill)
- Install (CLI): `npx skillmds@latest add construct-ai-primary/contracts-correspondence-management`
- Raw SKILL.md: https://api.skillmd.com/api/skills/construct-ai-primary/contracts-correspondence-management/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-22
- Page: https://skillmd.com/skills/construct-ai-primary/contracts-correspondence-management

---


# Contracts Correspondence Management

## Overview
Manage all formal contract correspondence, maintain contract records, track outstanding contractual matters, and ensure proper documentation of all contractual events

**Announce at start:** "I'm using the contracts-correspondence-management skill for Contracts operations."

## When to Use This Skill
**Trigger Conditions:** Manage all formal contract correspondence, maintain contract records, track outstanding contractual matters, and ensure proper documentation of all contractual events task required, contracts team task or request received
**Prerequisites:**
- Domain knowledge available (Contracts 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 contracts 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; escalate if out of scope

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

### Step 3: Execution
1. Apply discipline-specific methods and tools for manage all formal contract correspondence, maintain contract records, track outstanding contractual matters, and ensure proper documentation of all contractual events
2. Generate required outputs using approved templates, formats, and systems
3. Maintain full audit trail of all actions, calculations, decisions, and outputs
4. Cross-reference with related contracts, policies, standards, and specifications

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

### Step 5: Approval and Routing
1. Route outputs through appropriate approval workflow based on value/complexity
2. Verify approval authority matches delegated authority limits
3. Incorporate any required revisions from reviewers
4. Obtain final approval and sign-off from authorized personnel

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

## Success Criteria
- [ ] Task scope clearly defined and authorized
- [ ] All required inputs gathered and validated
- [ ] Contracts Correspondence Management 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
- [ ] Contracts Correspondence Management completed successfully

## Common Pitfalls
1. **Incomplete Inputs** — Attempting execution without all required documents or data. 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 before approval.
6. **Time-Sensitive Actions** — Missing contractual or regulatory time limits. Track all deadlines and notice periods.

## Cross-References

### Related Skills
- Additional contracts skills for related functions
- Skills from interfacing disciplines for cross-functional tasks

### Related Agents
- **Primary:** Contracts Administrator — Main execution
- **Supporting:** Contracts Administrator for document and data management
- **Oversight:** Contracts Manager for review, approval, and escalation

### Related Domain Knowledge
- Contracts Domain Knowledge for role responsibilities and frameworks
- Contracts Glossary for terminology, definitions, and abbreviations