Fill in these first
- Contract type and parties: [e.g. software licence between our company and a supplier]
- Our side: [which party we are]
- Contract text: [paste the full signed contract; remove bank and ID numbers]
- Start date: [date]
- Team members who own each area: [e.g. finance, operations, legal, account manager]
Task
Turn the contract into a working tracker that shows who must do what, by when, and which dates must not be missed.
Output format
- Summary in five lines: parties, term, value, renewal type, termination rights.
- Obligations: | # | Clause | Obligation | Party responsible | Due date or frequency | Owner on our side | Consequence if missed |
- Key dates calendar: | Date | Event | Clause | Reminder date (30 days before) |
- Renewal and notice: auto-renewal yes or no, notice period, last date to give notice.
- Payment terms: amounts, due dates, late fees, price increase rules.
- Unclear or one-sided clauses to clarify, quoted exactly.
Rules
- Start the output with: "This tracker summarises the contract for planning only and is not legal advice. The signed contract governs."
- Quote clause numbers for every row; if a clause has no number, quote its first words.
- Calculate dates from the start date and show any date that depends on an event, such as delivery, as [after event].
- Do not interpret ambiguous clauses as settled; list them under clarifications.
- Mark any term whose effect depends on local law, such as late payment interest or auto-renewal limits, as [jurisdiction-dependent].






