Contract & Document Renewal

Contract & Document Renewal recommends a small register that records renewal dates, notice deadlines and owners together. The notice deadline is the trigger to watch because it occurs before the renewal date. Its workflow moves from a recorded contract through the notice window, reminder and review to renewal, amendment or ending. It fits the Growth stage of protection.

The skill first distinguishes advice, review, a requested build and conversion of an existing process. It asks only unanswered questions about contract types, counterparties, renewal dates, notice periods, automatic renewal, owners, signers, storage and the desired calendar or owner list. It asks one question at a time and preserves unknown answers. Advice normally receives a recommendation and an offer to build.

Notice Deadline is calculated rather than typed:

Notice Deadline = End Date - Renewal Notice (Days)

Use calendar days, count the deadline day itself as day one, and store the result as an ISO YYYY-MM-DD date. Renewal Notice (Days) is a count, not a date. Recording only the number of days does not provide the date the register must watch.

Status must describe an actual condition. Expiring Soon covers the window between notice deadline and end date; In Renewal requires a renewal actually agreed or served. A passed deadline with no recorded action must expose the gap in Notes rather than silently claiming a completed renewal. Where automatic renewal occurs under the contract's own terms without notice, the register must not continue to claim In Renewal.

Contract Value also has an explicit Tax Basis. It stays Not confirmed until the user supplies the inclusive or exclusive basis. Currency and amount size do not establish it; tax rate and tax amount fields are added only when tax tracking is requested.

Use it for a contract tracker, renewal calendar or vendor agreement register, including processes currently scattered across spreadsheets or inboxes. It can organize information relevant to expiry alerts, but supplies no automated reminders, synchronization or contract execution. It does not review contract terms or provide legal advice. Consequential legal, tax and HR decisions require human review.

The shared field list covers contract title, counterparty, contract type, owner, department, start and end dates, notice days and deadline, automatic renewal, contract value, tax basis, currency, linked legal record, status and Contract ID. Currency uses an ISO 4217 code. Dates, numeric notice periods, money and booleans retain distinct types; select choices are starting sets.

SQL requires end_date after start_date, nonnegative renewal_notice_days, and a nullable calculated notice_deadline no later than end_date. Status options are Active, Expiring Soon, In Renewal, Renewed, Expired and Terminated. Tax Basis options are Not confirmed, Tax-inclusive and Tax-exclusive. Contract Type starts with Customer, Vendor, Employment, Lease, Service and NDA. Notion keeps imported Contract IDs as text and can add a separate Unique ID. JSON requires Contract Type, Start Date, End Date, Renewal Notice (Days), Contract Value, Tax Basis and Status.

On request, it produces consistent empty CSV, SQL DDL, JSON Schema, Notion mapping or Excel workbook artifacts. Display names stay aligned and SQL identifiers are documented. Excel-compatible CSV uses UTF-8 with a byte order mark and identifies columns needing formatting. Examples appear only when explicitly requested and must be synthetic.

Linked Legal Record stays a text document reference because the signed-document library is outside this build. Owner likewise remains a name rather than a foreign key to an invented directory.

Notion output routes to notion-manual-import. Manual mappings require no connection; workspace changes require verified tools, target and authorization. A static mapping alone is not a completed workspace build. Sensitive review inputs are repeated only where necessary.