aiwg
Version:
Deployment tool and support utility for AI context. Copies agents, skills, commands, rules, and behaviors into the paths each AI platform reads (Claude Code, Codex, Copilot, Cursor, Warp, OpenClaw, and 6 more) so one source of truth works across 10 platfo
381 lines (263 loc) • 21.1 kB
Markdown
# Contract Management Template
## Cover Page
- `Project Name`
- `Contract Management Register`
- `Version 1.0`
## Revision History
| Date | Version | Description | Author |
| --- | --- | --- | --- |
| `dd/mmm/yy` | `x.x` | `<details>` | `<name>` |
## Ownership & Collaboration
- Document Owner: Legal Liaison
- Contributor Roles: Project Manager, Procurement, Domain Expert, Risk Manager
- Automation Inputs: Contract repository, vendor management system, SLA monitoring dashboards
- Automation Outputs: Contract obligation tracking, renewal alerts, SLA compliance reports
## 1 Introduction
> Establish comprehensive tracking of all contracts affecting project delivery, including customer agreements, vendor contracts, and partner arrangements.
### 1.1 Purpose
This document tracks contractual obligations, service level agreements, intellectual property terms, data processing agreements, and renewal timelines to ensure project compliance with all contractual commitments and prevent breaches.
### 1.2 Scope
This document covers:
- Customer contracts (SOWs, MSAs, SLAs, DPAs)
- Vendor agreements (cloud providers, software licenses, professional services)
- Partner contracts (integration agreements, reseller agreements)
- Contractual obligations tracking and traceability
- Renewal and termination management
### 1.3 Definitions, Acronyms, and Abbreviations
- **MSA**: Master Service Agreement
- **SOW**: Statement of Work
- **SLA**: Service Level Agreement
- **DPA**: Data Processing Agreement (GDPR)
- **BAA**: Business Associate Agreement (HIPAA)
- **NDA**: Non-Disclosure Agreement
- **IP**: Intellectual Property
- **MTTR**: Mean Time to Repair
- **RPO**: Recovery Point Objective
- **RTO**: Recovery Time Objective
### 1.4 References
- `regulatory-compliance-framework-template.md` - Compliance requirements
- `risk-list-template.md` - Contract risk tracking
- `legal-risk-assessment-template.md` - Legal risk evaluation
- `sli-card.md` - SLA metric tracking
- `contract-requirements-traceability-matrix.md` - Contract-to-requirement mapping
### 1.5 Overview
Section 2 inventories active contracts; Section 3 details customer obligations; Section 4 tracks vendor dependencies; Section 5 covers renewal management; Section 6 addresses termination and exit planning.
## 2 Active Contracts Inventory
> Maintain a comprehensive register of all contracts affecting the project, organized by contract type and business criticality.
### 2.1 Customer Contracts
| Contract ID | Customer Name | Contract Type | Effective Date | Expiration Date | Contract Value | Auto-Renewal? | Termination Notice | Owner |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| CUST-2024-001 | Acme Corp | MSA + SOW | 2024-01-15 | 2026-01-15 | $500K/year | [ ] Yes [x] No | 90 days | Sales |
| CUST-2024-002 | Beta Industries | SOW | 2024-03-01 | 2025-03-01 | $250K | [x] Yes [ ] No | 60 days | Sales |
### 2.2 Vendor Contracts
| Contract ID | Vendor Name | Service Type | Effective Date | Expiration Date | Contract Value | Business Criticality | Owner |
| --- | --- | --- | --- | --- | --- | --- | --- |
| VEND-2023-001 | AWS | Cloud infrastructure | 2023-06-01 | 2026-06-01 | $200K/year | Critical | Engineering |
| VEND-2024-003 | Datadog | Monitoring platform | 2024-02-01 | 2025-02-01 | $50K/year | High | DevOps |
| VEND-2024-005 | Acme Security | Penetration testing | 2024-01-15 | 2025-01-15 | $30K/year | Medium | Security |
### 2.3 Partner Agreements
| Contract ID | Partner Name | Agreement Type | Effective Date | Expiration Date | Scope | Owner |
| --- | --- | --- | --- | --- | --- | --- |
| PART-2024-001 | Integration Partners Inc | Integration agreement | 2024-01-01 | 2026-01-01 | API access, co-marketing | Partnerships |
| PART-2024-002 | Reseller Corp | Reseller agreement | 2024-04-01 | 2025-04-01 | Product resale, revenue share | Sales |
## 3 Customer Contractual Obligations
> Detail obligations to customers, including SLAs, deliverables, milestones, and compliance requirements.
### 3.1 Service Level Agreements (SLAs)
#### 3.1.1 Availability SLAs
| Customer | Contract ID | Availability Commitment | Measurement Method | Penalty Clause | Current Performance | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Acme Corp | CUST-2024-001 | 99.95% uptime (monthly) | Uptime monitoring | 10% credit per 0.1% below SLA | 99.97% (last 30 days) | [x] Green [ ] Yellow [ ] Red |
| Beta Industries | CUST-2024-002 | 99.9% uptime (monthly) | Uptime monitoring | 5% credit per 0.5% below SLA | 99.92% (last 30 days) | [x] Green [ ] Yellow [ ] Red |
**Monitoring**: Uptime tracked via [monitoring tool], reported in customer dashboard, reviewed weekly
**Escalation**: If projected to breach SLA, escalate to Engineering Lead within 48 hours
#### 3.1.2 Performance SLAs
| Customer | Contract ID | Performance Commitment | Measurement Method | Penalty Clause | Current Performance | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Acme Corp | CUST-2024-001 | API response time < 200ms (95th percentile) | APM tooling | 5% credit if > 200ms | 185ms (last 30 days) | [x] Green [ ] Yellow [ ] Red |
| Beta Industries | CUST-2024-002 | Page load time < 2 seconds | Synthetic monitoring | 5% credit if > 2s | 1.8s (last 30 days) | [x] Green [ ] Yellow [ ] Red |
#### 3.1.3 Support SLAs
| Customer | Contract ID | Priority Level | Response Time | Resolution Time | Current Performance | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Acme Corp | CUST-2024-001 | P1 (Critical) | 1 hour | 4 hours | Avg 45 min response, 3.5 hr resolution | [x] Green [ ] Yellow [ ] Red |
| Acme Corp | CUST-2024-001 | P2 (High) | 4 hours | 24 hours | Avg 3 hr response, 18 hr resolution | [x] Green [ ] Yellow [ ] Red |
| Acme Corp | CUST-2024-001 | P3 (Medium) | 24 hours | 5 business days | Avg 18 hr response, 3 days resolution | [x] Green [ ] Yellow [ ] Red |
**Support Channels**: [Email, phone, ticketing system, dedicated Slack channel]
**On-Call Coverage**: [24/7 for P1, business hours for P2/P3]
### 3.2 Deliverable Commitments
| Customer | Contract ID | Deliverable | Description | Acceptance Criteria | Due Date | Status | Owner |
| --- | --- | --- | --- | --- | --- | --- | --- |
| Acme Corp | CUST-2024-001 | Feature X | [Brief description] | [Acceptance criteria from SOW] | 2025-12-01 | [On Track/At Risk/Delayed] | Product Manager |
| Beta Industries | CUST-2024-002 | Integration Module Y | [Brief description] | [Acceptance criteria from SOW] | 2025-11-15 | [On Track/At Risk/Delayed] | Engineering Lead |
**Tracking**: Deliverables tracked in [project management tool], reviewed in weekly status meetings
**Escalation**: If deliverable at risk of missing deadline, escalate to Project Manager and Legal Liaison
### 3.3 Milestone Commitments
| Customer | Contract ID | Milestone | Description | Payment Trigger? | Due Date | Actual Date | Status | Risk |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Acme Corp | CUST-2024-001 | Design approval | Architecture review complete | Yes ($100K) | 2025-10-15 | 2025-10-10 | Complete | None |
| Acme Corp | CUST-2024-001 | Beta release | Feature-complete beta | Yes ($150K) | 2025-11-30 | [Projected date] | In Progress | [None/Low/Medium/High] |
| Acme Corp | CUST-2024-001 | Production release | GA release | Yes ($250K) | 2026-01-15 | [Projected date] | Planned | [None/Low/Medium/High] |
**Financial Impact**: Milestone delays impact revenue recognition and cash flow
**Mitigation**: [Mitigation strategies for at-risk milestones]
### 3.4 Compliance and Regulatory Commitments
| Customer | Contract ID | Commitment | Description | Verification Method | Status | Evidence |
| --- | --- | --- | --- | --- | --- | --- |
| Acme Corp | CUST-2024-001 | SOC 2 Type II | Maintain SOC 2 Type II certification | Annual audit | [Current/Planned] | SOC 2 report dated [yyyy-mm-dd] |
| Acme Corp | CUST-2024-001 | HIPAA compliance | HIPAA-compliant data handling | BAA, HIPAA assessment | [Current/Planned] | BAA signed [yyyy-mm-dd], assessment [yyyy-mm-dd] |
| Beta Industries | CUST-2024-002 | GDPR compliance | GDPR-compliant data processing | DPA, DPIA | [Current/Planned] | DPA signed [yyyy-mm-dd], DPIA [yyyy-mm-dd] |
**Reference**: See `regulatory-compliance-framework-template.md` for detailed compliance tracking
### 3.5 Intellectual Property Terms
| Customer | Contract ID | IP Ownership | License Grants | Restrictions | Open Source Restrictions | Status |
| --- | --- | --- | --- | --- | --- | --- |
| Acme Corp | CUST-2024-001 | Customer owns custom work, vendor retains platform IP | Customer: perpetual license to platform; Vendor: right to reuse non-custom components | No competitive use of custom work | No GPL/AGPL in deliverables | [Compliant/Review Required] |
| Beta Industries | CUST-2024-002 | Vendor retains all IP | Customer: subscription license, non-transferable | No reverse engineering | [Specify allowable licenses] | [Compliant/Review Required] |
**Reference**: See `license-compliance-template.md` for open source license tracking
### 3.6 Data Processing Agreements (DPAs)
| Customer | Contract ID | DPA Status | Processing Scope | Data Location Restrictions | Sub-Processors | Breach Notification |
| --- | --- | --- | --- | --- | --- | --- |
| Acme Corp | CUST-2024-001 | Signed [yyyy-mm-dd] | Customer PII: name, email, usage data | EU data must stay in EU | AWS (Frankfurt), Datadog (EU) | 48 hours |
| Beta Industries | CUST-2024-002 | Signed [yyyy-mm-dd] | Customer PII: name, email, phone | No restrictions | AWS (US), Datadog (US) | 72 hours |
**Reference**: See `privacy-impact-assessment-template.md` for data processing details
## 4 Vendor Dependencies and SLAs
> Track vendor commitments, SLAs, and risks to ensure vendor performance aligns with customer commitments.
### 4.1 Critical Vendor SLAs
| Vendor | Contract ID | Service | SLA Commitment | Our Dependency | Cascading Impact | Monitoring Method | Current Performance |
| --- | --- | --- | --- | --- | --- | --- | --- |
| AWS | VEND-2023-001 | EC2 compute | 99.99% regional availability | Hosting platform | Customer uptime SLA | AWS Health Dashboard | 99.99% (last quarter) |
| AWS | VEND-2023-001 | RDS database | 99.95% Multi-AZ | Database layer | Customer uptime SLA | AWS Health Dashboard | 99.97% (last quarter) |
| Datadog | VEND-2024-003 | Monitoring | 99.9% platform availability | Observability | Blind to incidents if down | Datadog status page | 99.95% (last quarter) |
| Stripe | VEND-2024-007 | Payment processing | 99.99% availability | Payment acceptance | Customer payment failures | Stripe status page | 99.99% (last quarter) |
**Risk Assessment**: If AWS EC2 SLA (99.99%) is lower than customer SLA (99.95%), buffer is only 0.04%. Risk: Medium.
**Mitigation**:
- Multi-region architecture for critical workloads
- Secondary vendor for [specific service]
- Real-time monitoring and alerting for vendor incidents
### 4.2 Vendor Performance Tracking
| Vendor | Contract ID | SLA Breaches (Last 12 Months) | Customer Impact | Resolution | Risk Level |
| --- | --- | --- | --- | --- | --- |
| AWS | VEND-2023-001 | 1 (EC2 outage, 2024-06-15, 45 min) | Customer downtime: 45 min, SLA credit issued | AWS root cause published | Low (isolated incident) |
| Datadog | VEND-2024-003 | 0 | None | N/A | Low |
### 4.3 Vendor Escalation Contacts
| Vendor | Contract ID | Standard Support | Escalation Contact | Emergency Contact | Response SLA |
| --- | --- | --- | --- | --- | --- |
| AWS | VEND-2023-001 | AWS Support (Business tier) | TAM: [name, email] | TAM mobile: [phone] | 1 hour for critical |
| Datadog | VEND-2024-003 | support@datadoghq.com | CSM: [name, email] | CSM mobile: [phone] | 4 hours for critical |
### 4.4 Vendor Compliance and Certifications
| Vendor | Contract ID | Required Certifications | Current Status | Expiration Date | Review Frequency | Owner |
| --- | --- | --- | --- | --- | --- | --- |
| AWS | VEND-2023-001 | SOC 2 Type II, ISO 27001, HIPAA | Valid | Reviewed annually | Annual | Legal Liaison |
| Datadog | VEND-2024-003 | SOC 2 Type II | Valid | 2025-12-31 | Annual | Legal Liaison |
| Acme Security | VEND-2024-005 | [None required] | N/A | N/A | N/A | N/A |
**Verification Process**: Request updated SOC 2 reports and certifications annually, store in vendor management system
**Alerting**: Alert Legal Liaison 90 days before certification expiration
## 5 Renewal and Negotiation Management
> Proactively manage contract renewals, negotiations, and exit strategies to prevent service disruptions and optimize costs.
### 5.1 Renewal Timeline
| Contract ID | Party | Contract Type | Expiration Date | Renewal Notice Period | Review Start Date | Negotiation Start Date | Decision Deadline | Owner |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| CUST-2024-001 | Acme Corp | MSA + SOW | 2026-01-15 | 90 days | 2025-07-15 (T-180) | 2025-09-15 (T-120) | 2025-10-15 (T-90) | Sales |
| VEND-2023-001 | AWS | Cloud services | 2026-06-01 | None (pay-as-you-go) | 2026-03-01 (T-90) | N/A | N/A | Engineering |
| VEND-2024-003 | Datadog | Monitoring | 2025-02-01 | 30 days | 2024-11-01 (T-90) | 2024-12-01 (T-60) | 2025-01-01 (T-30) | DevOps |
**Automation**: Set calendar reminders at T-180, T-90, T-60, T-30 days before expiration
### 5.2 Renewal Decision Criteria
#### 5.2.1 Customer Contract Renewal
- **Customer satisfaction**: NPS score, support ticket trends, escalations
- **Financial performance**: Revenue, profitability, payment history
- **Strategic fit**: Alignment with company strategy, growth potential
- **Operational burden**: Support costs, custom development requirements
- **Competitive landscape**: Competitive pressure, pricing benchmarks
**Decision Framework**: [Renewal recommended / Renewal with renegotiation / Non-renewal]
#### 5.2.2 Vendor Contract Renewal
- **Performance**: SLA compliance, incident frequency, support responsiveness
- **Cost**: Pricing trends, usage optimization opportunities, competitive pricing
- **Strategic value**: Integration depth, switching costs, roadmap alignment
- **Compliance**: Certification status, security posture, audit findings
- **Alternatives**: Competitive alternatives, multi-vendor strategies
**Decision Framework**: [Renew as-is / Renew with renegotiation / Replace vendor / Bring in-house]
### 5.3 Negotiation Strategy
| Contract ID | Party | Negotiation Goals | Leverage Points | Walk-Away Criteria | Negotiator | Legal Support |
| --- | --- | --- | --- | --- | --- | --- |
| CUST-2024-001 | Acme Corp | 20% price increase, extend term to 3 years | High customer satisfaction, low churn | < 10% increase, < 2 year term | Sales Lead | Legal Liaison |
| VEND-2024-003 | Datadog | 10% cost reduction, maintain service level | Usage optimization, competitive pricing | > 5% increase, reduced support tier | DevOps Lead | Procurement |
### 5.4 Exit and Transition Planning
> Plan for contract termination scenarios (planned or unplanned) to ensure business continuity.
#### 5.4.1 Customer Exit Planning
| Customer | Contract ID | Exit Risk | Data Retrieval Obligations | Transition Support | Financial Impact | Owner |
| --- | --- | --- | --- | --- | --- | --- |
| Acme Corp | CUST-2024-001 | Low (satisfied customer) | Export data in CSV/JSON within 30 days | 90 days transition support | Loss of $500K/year revenue | Customer Success |
| Beta Industries | CUST-2024-002 | Medium (price sensitivity) | Export data in CSV/JSON within 30 days | 60 days transition support | Loss of $250K/year revenue | Customer Success |
**Customer Offboarding Process**:
1. Termination notice received → Alert Sales, Customer Success, Engineering
2. Schedule exit interview → Understand reasons, identify retention opportunities
3. Data export → Provide data in contractually agreed format
4. Transition support → Provide documentation, knowledge transfer
5. Service termination → Deactivate accounts, delete data per retention policy
6. Post-exit review → Document lessons learned
#### 5.4.2 Vendor Exit Planning
| Vendor | Contract ID | Exit Trigger | Data Retrieval Plan | Service Continuity | Secondary Vendor | Estimated Migration Time | Owner |
| --- | --- | --- | --- | --- | --- | --- | --- |
| AWS | VEND-2023-001 | Cost optimization, vendor failure | Export snapshots, DB backups | Cutover during maintenance window | Azure, GCP | 6 months | Engineering Lead |
| Datadog | VEND-2024-003 | Cost optimization | Export dashboards, alerts | Parallel run with new tool | Grafana + Prometheus | 3 months | DevOps Lead |
**Vendor Exit Process**:
1. Exit decision → Create migration project plan
2. Secondary vendor selection → RFP, evaluation, contracting
3. Migration planning → Architecture design, data migration, testing
4. Parallel operation → Run both vendors simultaneously to verify functionality
5. Cutover → Switch production traffic, decommission old vendor
6. Contract termination → Provide termination notice, retrieve final data
7. Post-migration review → Document lessons learned, cost savings achieved
## 6 Contract Risk Management
> Identify, assess, and mitigate risks related to contractual obligations.
### 6.1 Contract Risk Register
| Risk ID | Contract ID | Risk Category | Description | Likelihood | Impact | Risk Score | Mitigation | Owner |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| CR-001 | CUST-2024-001 | SLA breach | AWS outage cascades to customer SLA breach | Medium | High | 12 | Multi-region architecture | Engineering Lead |
| CR-002 | CUST-2024-001 | Milestone delay | Feature X delayed, miss milestone payment | Medium | High | 12 | Add resources, reduce scope | Project Manager |
| CR-003 | VEND-2023-001 | Vendor lock-in | Deep AWS integration, high switching cost | High | Medium | 12 | Abstraction layer, multi-cloud strategy | Architect |
| CR-004 | VEND-2024-003 | Certification lapse | Vendor SOC 2 expires, customer requires valid cert | Low | High | 10 | 90-day expiration alert, backup vendor | Legal Liaison |
**Risk Scoring**: Likelihood (1-5) × Impact (1-5) = Risk Score (1-25)
**Reference**: See `risk-list-template.md` for full risk management process
### 6.2 SLA Compliance Monitoring
| Customer | Contract ID | SLA Metric | Target | Current (30 days) | Trend | Projected (Next 30 days) | Risk Level | Action Required |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Acme Corp | CUST-2024-001 | Uptime | 99.95% | 99.97% | Stable | 99.96% | Green | None |
| Acme Corp | CUST-2024-001 | API response time | < 200ms (p95) | 185ms | Improving | 180ms | Green | None |
| Beta Industries | CUST-2024-002 | Uptime | 99.9% | 99.85% | Declining | 99.8% | Yellow | Investigate performance degradation |
**Alerting**: If projected SLA breach within 7 days, escalate to Engineering Lead and Project Manager
**Communication**: If SLA breach imminent, notify customer proactively with mitigation plan
## 7 Reporting and Dashboards
> Provide visibility into contract status, SLA compliance, and renewal timelines.
### 7.1 Executive Contract Dashboard
- **Total contract value**: Active contracts by type (customer, vendor, partner)
- **Renewal pipeline**: Contracts expiring in next 90 days
- **SLA compliance**: Traffic light status by customer
- **Contract risks**: High-risk contracts requiring attention
- **Compliance status**: Vendor certifications valid/expiring
### 7.2 Operational Contract Dashboard
- **Customer SLA metrics**: Real-time uptime, performance, support SLAs
- **Vendor SLA metrics**: Vendor performance tracking
- **Milestone tracking**: Deliverables vs. deadlines
- **Renewal actions**: Upcoming renewal decisions and negotiation status
## Appendices
### Appendix A: Contract Templates
- [Customer MSA template]
- [Customer SOW template]
- [Customer DPA template]
- [Vendor agreement template]
### Appendix B: Negotiation Playbooks
- [Customer contract negotiation guidelines]
- [Vendor contract negotiation guidelines]
- [Red-line clauses (unacceptable terms)]
### Appendix C: Contact Directory
| Role | Name | Email | Phone | Responsibilities |
| --- | --- | --- | --- | --- |
| Legal Liaison | [name] | [email] | [phone] | Contract review, legal approval |
| Sales Lead | [name] | [email] | [phone] | Customer contract negotiation |
| Procurement Lead | [name] | [email] | [phone] | Vendor contract negotiation |
| Customer Success Lead | [name] | [email] | [phone] | Customer relationship management |
## Agent Notes
- Track contract obligations in requirements: Create requirements traceability from contract clauses to system requirements (see `contract-requirements-traceability-matrix.md`)
- Monitor SLA compliance proactively: Detect SLA breaches before they occur, not after
- Automate renewal alerts: Set reminders at T-180, T-90, T-60, T-30 days to prevent lapses
- Verify vendor certifications: Don't assume vendor compliance, verify annually
- Coordinate with Legal Liaison on all contract reviews and renewals
- Verify Automation Outputs entry is satisfied before signaling completion