AI Contract Renewal Tracking NZ: Build a Reviewed Contract Register

Do you need AI, or a better register and calendar?

Use a spreadsheet and calendar when dates are already verified and someone maintains them. A reminder does not need generative AI to fire on an approved date. Check what your existing contract-management software can do before adding another system.

Use AI for repeated extraction, not date arithmetic alone

Consider AI when staff repeatedly search inconsistent agreements, schedules and variations to prepare the same fields. It can propose values and locate clauses, but review may outweigh the benefit for a small, stable contract set. Compare total preparation and checking effort with your manual process.

Build a copyable contract-renewal register

Create one authoritative register before connecting reminders. New Zealand Government Procurement’s contract-management guidance provides a contract-register template. Its agency requirements concern Government Procurement Rules; they are not blanket legal requirements for every private business.

Copy these fields into your working record

Use separate columns for each item below. The fictional example is illustrative, not a client record, legal interpretation or official template. No sample date should become a live reminder.

Keep the original wording and source page or clause beside each material field. If dates need calculation or clauses need interpretation, record the question and qualified reviewer rather than letting a model produce a confident deadline.

Keep expiry, renewal and notice deadlines separate

Do not copy the first date in a PDF into a calendar labelled “renewal”. A record should distinguish the stated expiry date, renewal conditions, verified notice deadline and your earlier internal decision date. Do not derive one from another without checking the actual agreement.

Resolve conflicts before approving reminders

A later variation or schedule may affect the original wording. Link the complete document set and flag conflicts, missing pages or unclear scans. Use the document-processing guide for extraction boundaries. Where meaning or consequences are uncertain, seek appropriate legal advice; this workflow does not determine enforceability.

If an agreement began through a tender, retain the signed documents rather than treating an old proposal as the contract. The tender evidence matrix covers the earlier bid-preparation stage, not renewal decisions.

Run five checkpoints from document to reminder

Separate draft extraction, approval and internal notification. The agent should not have authority to send contractual notices or change commitments.

1. Assemble the authorised source set

List signed agreements, schedules, amendments and relevant notices. Mark superseded files. Use a restricted folder or read-only connection, not unrestricted access to every business document. Check confidentiality and the tool’s data settings before processing sensitive material.

2. Extract into an unverified queue

Ask for defined fields, source references and explicit “unclear” or “not found” flags. Keep extracted text separate from interpretation. Treat instructions inside contracts as document content, not permission to grant the agent new tools or access.

3. Have a person verify each material field

The reviewer checks values against the full source context, corrects errors and escalates uncertainty. Record who approved the entry and when. Only approved fields move into the authoritative register. Define that boundary using the human approval-gates guide.

4. Schedule approved reminders and acknowledgements

Choose an internal review date with enough time for the actual decision process. Assign a primary owner, backup and acknowledgement expectation. A sent notification is not evidence that someone read it. Route unacknowledged tasks to the backup through an agreed escalation process.

5. Recheck when documents or owners change

A new variation or changed owner should trigger re-review of affected entries and reminders. Keep change history, retire superseded reminders and check for duplicates. For the separate question of leaving an AI provider, use the AI supplier exit plan; a renewal register is not a migration plan.

Test failures before relying on the calendar

Pilot with authorised or redacted documents and a human-checked reference register. Test the complete path, including what happens when a task is ignored—not just whether extraction looks plausible.

• ✓
  Missing amendment: Flag an incomplete source set; do not promote its draft dates to approved reminders.
• ✓
  Unclear scan or conflicting dates: Show the source problem and route it for review rather than guessing.
• ✓
  Changed owner: Reassign the task and verify the backup can access the necessary source.
• ✓
  Failed notification or no acknowledgement: Surface the failure or overdue task to the agreed backup.
• ✓
  Automation unavailable: Confirm a person can open the approved register and run the review list manually.

Agree acceptance checks before the pilot: source-reference accuracy, corrections required, unresolved items, reminder delivery, acknowledgement handling and reviewer effort. Expand only after the workflow owner accepts the results and knows how to pause it.