Contract Tracker Pro

Problem

After a contract is signed, the risk does not disappear; it moves into execution. Payment milestones, delivery deadlines, expiration dates, and penalty clauses are scattered across PDF pages. Manual extraction can miss items, and teams often lack a centralized reminder before deadlines arrive. For engineering, procurement, sales, or operations teams managing multiple contracts, spreadsheets and emails can make overdue milestones hard to catch, especially when payment amounts, delivery content, and penalty ratios need continuous tracking. Without a lightweight ledger, problems may surface too late.

How It Works

Contract Tracker Pro splits contract execution tracking into extraction, ledger, and reminders.
- Input: supports contract PDF upload, pasted key clause text, and queries for existing contract states.
- Extraction: uses a user-configured AI model to read contract name/number, signing date, payment milestones, delivery milestones, expiration date, and penalty clauses.
- Tracking: builds a local execution ledger stored as JSON, exportable to CSV; statuses are pending, completed, and overdue, supporting milestone-level closure.
- Reminders: sends Feishu webhook notifications 3 days before a milestone and on the milestone day; if a milestone remains overdue, it sends daily reminders until a user marks it complete.

Boundaries

This skill is suited for contract milestone reminders and local ledger management. It does not replace contract approval, legal review, e-signature, or financial settlement workflows. AI extraction may still require manual review, especially for scanned documents, complex clauses, non-standard templates, or tables across pages. It requires feishu_webhook and ai_api_key, with optional ai_base_url; the docs mention api_key for tier verification, while a fallback to free capability is supported when network checks fail, avoiding a complete block on use.