Contract Renewal & Expiration Manager

Manage vendor contract renewals proactively with alerts, decision scoring, renegotiation prep, and documentation to avoid missed deadlines and optimize terms.

Security Scan

Instruction-only contract renewal playbook that is internally consistent with its stated purpose, but it assumes integration with calendars, file storage, and alerting mechanisms without declaring how those integrations/credentials will be handled.

Purpose & Capability

The name, description, and SKILL.md all describe a human/agent-facing process for tracking and managing contract renewals. The required artifacts (renewal calendar, scoring, notices, templates) align with the stated purpose and there are no unrelated binaries, env vars, or install steps requested.

Instruction Scope

The instructions are procedural and scoped to the renewal lifecycle. They reference automation steps (automated/calendar alerts, owner notifications) and another skill ('Vendor Performance Audit skill'), but do not specify which calendar/alert/email systems to use or how automation should be authorized. That omission means the skill assumes the agent has tools/permissions to perform those actions; the SKILL.md itself does not ask the user to provide or limit those permissions.

Install Mechanism

There is no install spec and no code files — the skill is instruction-only, which minimizes disk-write and install risks.

Credentials

The skill does not declare any environment variables or credentials, yet it instructs storing contracts in external services (Drive, Notion) and sending automated alerts/notifications. Performing those actions in practice requires access credentials; the documentation does not request or describe the minimal/proper credentials or scopes, which is an omission users should be aware of.

Persistence & Privilege

The skill does not request always-on presence and does not declare any capabilities that would modify other skills or global agent configuration. Autonomous invocation is allowed by platform default but nothing in the SKILL.md elevates its privilege beyond typical agent actions.

Assessment

This is a coherent, instruction-only playbook for managing contract renewals and appears safe from an internal-consistency perspective. Before installing or enabling the skill: (1) confirm which calendar, email, or storage connectors the agent will use to implement automated alerts and document storage; only grant the minimal scopes (e.g., calendar event write only, limited Drive folder access) and prefer a dedicated service account or folder for contracts; (2) verify any automatic notification behavior — avoid giving broad send-email or admin access unless you intend the agent to act autonomously; (3) review integrations with other skills (the referenced 'Vendor Performance Audit' skill) to understand data flows; and (4) treat contract documents as sensitive — ensure storage/encryption and access controls are appropriate. If you want purely human-guidance behavior, keep the skill instruction-only and deny connectors that enable automatic outbound actions.

Framework: Renewal Readiness Protocol Output: A proactive renewal calendar + decision framework + renegotiation prep package

Missing a contract renewal costs real money — auto-renewals at bad rates, emergency re-sourcing, lost leverage. This system gives you a structured process to manage every vendor contract renewal proactively: alert triggers, renewal decisions, renegotiation prep, and documentation.

---

Phase 1: Renewal Inventory & Calendar Setup

Step 1 — Build your renewal calendar

For every active vendor contract, capture:

Field	What to Record
Vendor Name	Legal name + DBA
Contract Start	Date
Contract End	Date
Auto-Renewal Clause	Yes/No — if yes, notice period required
Notice Deadline	Contract end date minus notice period
Annual Value	$ACV or total contract value
Category	Software / Services / Suppliers / Professional Services
Owner	Internal stakeholder responsible for this vendor

Priority flag: Any contract with ACV > $10K or auto-renewal clause = Priority tier (review 90 days out). All others = Standard tier (review 60 days out).

---

Phase 2: The 90/60/30-Day Alert Protocol

90 days before renewal:

• Owner receives automated/calendar alert
• Trigger: Vendor Performance Audit (see Vendor Performance Audit skill)
• Decision: Is this vendor still the right solution? Flag for review.
• Action: Schedule renewal decision meeting

60 days before renewal:

• Complete renewal decision (renew vs. renegotiate vs. replace)
• If renewing as-is: confirm terms, draft renewal notice
• If renegotiating: begin prep (Phase 3)
• If replacing: begin vendor search, trigger parallel onboarding timeline

30 days before renewal:

• All paperwork finalized and signed
• If auto-renewal with notice clause: send written notice by this date
• Confirm successor vendor is ready (if replacing)
• Update renewal calendar for next cycle

Emergency Protocol (< 30 days discovered): If a renewal is discovered < 30 days out:

1. Immediate owner notification
2. Assess: Can we extend month-to-month? Is auto-renewal acceptable short-term?
3. If replacing: begin emergency sourcing
4. Document the miss and add this vendor to Priority tier going forward

---

Phase 3: Renewal Decision Framework

For each renewal, score across 4 dimensions (1-5 each):

Dimension	Score 1	Score 3	Score 5
Performance	Consistently below SLA	Meets SLA most of the time	Exceeds SLA reliably
Value	Overpriced vs. market	Market rate	Below market, strong value
Strategic fit	No longer fits our direction	Neutral / functional	Core to our operations
Relationship	Difficult to work with	Professional, transactional	Strong partnership

Decision matrix:

• 16-20: Renew, consider expanding scope
• 11-15: Renew, assess for renegotiation
• 6-10: Renegotiate or evaluate alternatives
• 1-5: Replace — begin sourcing

---

Phase 4: Renegotiation Prep

If decision is to renegotiate, complete this prep package before any vendor conversation:

Market positioning:

• What are 2-3 comparable alternatives? Get quotes.
• What's the market rate for this category today vs. when contract was signed?
• What's your BATNA (Best Alternative to Negotiated Agreement)?

Value ledger:

• What have you gotten from this vendor over the contract period? (Quantify where possible)
• What problems have occurred? Document with dates and business impact.
• What do you want changed? Rank by priority: price → terms → SLA → scope

Opening position:

• State your ask clearly before the first call
• Lead with value received, then the gap between current and desired terms
• Anchor to market data, not just preference

Concession ladder:

• What will you trade? (longer term for lower price, volume commitment for discount, etc.)
• What is non-negotiable? (Define in advance, not under pressure)

---

Phase 5: Documentation Templates

Renewal Notice Letter (for contracts requiring written notice):

[Date]
[Vendor Name]
[Address]

RE: Contract Renewal Notice — [Contract ID / Service Description]

Dear [Vendor Contact],

This letter serves as formal notice of our intent to [renew / not renew] the agreement dated [Contract Start Date] for [Service Description].

[If renewing:] We look forward to continuing our relationship under the same terms for an additional [term]. Please confirm receipt of this notice.

[If not renewing:] Please consider this our formal notice of non-renewal per Section [X] of our agreement. We will coordinate transition details separately.

Regards,
[Name, Title]
[Company]

Internal Renewal Summary (for stakeholder records):

• Vendor, Contract ID, Term, ACV
• Renewal decision + rationale
• Changes negotiated (if any)
• Next renewal date
• Owner sign-off

---

Implementation Checklist

• Build renewal inventory for all active contracts
• Set calendar alerts at 90/60/30-day marks for all Priority contracts
• Set 60/30-day alerts for Standard contracts
• Assign owners to every contract
• Complete renewal decision framework for any contracts due within 90 days
• Store all contracts in a single accessible location (Drive folder, Notion, etc.)