- Home
- Skills
- Legal & Compliance
- Contract Deadline Radar — Dates, Renewals & Critical Events
Works with the AI Agents you already use
Contract Deadline Radar — Dates, Renewals & Critical Events
Extract fixed and event-triggered contract dates with source lineage, renewal windows, uncertainties and review tasks.
$9.99
Contract Deadline Radar — Dates, Renewals & Critical Events
Example session with this skill installed
Illustrative clauses: Term ends 31 December 2026. Non-renewal notice must be received at least 60 calendar days before term end. Invoice payment is due 30 calendar days after receipt; receipt date is unknown. No amendment, holiday rule, timezone or notice method is supplied. Build a provisional deadline register, calculation lineage and internal reminder plan. Do not create reminders or send notices.
- Read your context and instructions
- Compiled the contract deadline radar
Provisional deadline radar
Non-renewal needs immediate verification of the complete clause and delivery rules. Payment date cannot be calculated until invoice receipt is known. This is a scenario-based operational calendar, not a legal conclusion.
| Event | Anchor / rule | Provisional date | Status |
|---|---|---|---|
| Term end | Explicit supplied date | 31 December 2026 | Supplied; full-document verification needed |
| Non-renewal receipt threshold | Term end minus 60 calendar days | 1 November 2026 | Calculated; interpretation and notice mechanics require review |
| Invoice payment | Receipt date plus 30 calendar days | Unknown | Trigger pending |
Calculation lineage
31 December 2026 − 60 calendar days = 1 November 2026 using ordinary date subtraction. The supplied text requires receipt, not merely sending. Inclusive counting, exact time, timezone, delivery method, deemed receipt, weekend/holiday adjustments, amendments and precedence are not supplied. Do not treat the calculated threshold as a confirmed legally controlling deadline without review.
For invoice payment: record actual receipt evidence first, then calculate under the verified contractual definition. Do not substitute invoice issue date for receipt date.
Proposed internal reminders—not contractual dates
- 90 days before term end: start business review of renewal/non-renewal options.
- 75 days before term end: confirm decision owner, approval route and notice delivery mechanics.
- Before the verified receipt deadline with sufficient delivery buffer: obtain approved decision and, only if authorized, prepare the notice.
Exact preparation and send targets must be chosen after validating receipt rules and operational constraints. These are suggested internal controls, not obligations invented into the agreement.
Verification queue
Obtain executed agreement and amendments; confirm parties, source clause, temporal definitions, current term, notice address/method and decision authority. Assign an owner and backup. Capture invoice receipt date/source and verify any payment exceptions.
Safety and status
No reminder, calendar event, notice, renewal decision or termination was executed. Preserve draft status until source review and authorized action. A missed evidence item remains an unknown, not a silently calculated date.
Connects securely to your tools. The creator never sees your data.
About this skill
Make contract timing traceable
Contract Deadline Radar helps contract, procurement and operations teams organize supplied agreements and amendments into dates, notice windows, triggers, recurring obligations and decision points.
It distinguishes explicit from calculated dates, renewal from notice deadlines, calendar from business days and contractual dates from internal preparation targets. Coverage can include non-renewal, termination/cure, payments, deliverables, acceptance, SLA claims, reporting and expiries. It calculates only from verified anchors and preserves source and method.
Reports surface missing event dates, superseded terms, ambiguous timing and unassigned obligations. File/OCR/code, CLM and reminder integrations are optional; no live monitoring is assumed. Contract notices, termination and exercise of rights require explicit authority and appropriate review. It does not guarantee all legal deadlines or controlling dates are identified.
Complete executed documents, amendments, temporal definitions and accurate anchors are required. OCR can miss clauses; business-day calendars and legal interpretation may matter. Cannot guarantee every legal date or that a calculated date controls. Missing triggers stay unknown. Actual reminders, monitoring and messages depend on tools; no notice action is implied.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago
Permissions
File Scopes
Read authorized agreements, amendments and event-date evidence; write draft registers in agreed locations. Optional OCR/code, CLM, calendar/task/email and document repository access requires actual host tools and least privilege. No connection is required for manual extraction. Do not disclose confidential terms. Creating reminders needs authorized supported capability; sending notices, terminating, accepting or exercising rights requires explicit authority and appropriate review.