Renewals and expiry
A renewal table is not a risk review. The deliverable is a list of dates to act on, and the failure mode is not a wrong clause summary — it is a notice window that closed while nobody was looking at it.
Contract review compares the same set of agreements for risk. This page asks a narrower question of them and turns the answer into a calendar. The two tables can live in one workspace and read the same documents, because ingestion is charged once.
What a row is
An agreement as amended. That qualifier does all the work here: an amendment that extended a term or cut a notice period is the thing you are trying to find, so a table that reads the original agreement alone will produce a calendar that is confidently wrong.
Bundle each agreement with its amendments, order forms and extension letters, most recent first — see bundles. If you only ever bundle for one table, bundle for this one.
The starting columns
Two columns come from the Legal & Procurement preset that ships in the app:
| Column | Type | Prompt |
|---|---|---|
| Effective Date | Date | What is the effective date of this contract? |
| Renewal Terms | Text | Summarize the renewal terms of this contract (e.g. auto-renewal, notice period). |
The preset is built for risk review rather than for dates, so the rest of this table is written by hand. These four columns are not in the app — copy them in yourself:
| Column | Type | Prompt |
|---|---|---|
| Auto-renews | Yes/No | Does this contract renew automatically unless notice is given, as opposed to expiring at the end of its term? |
| Notice period (months) | Number | How many months of notice are required to prevent renewal or to terminate at the end of the current term? Answer in months as a number. |
| Current term ends | Date | On what date does the current term of this contract end, taking into account any extension or renewal already exercised? |
| Termination for convenience | Yes/No | May either party terminate this contract for convenience during the term, without cause? |
Keep Renewal Terms even though three of the added columns cover the same ground. The prose column is what you read when the structured answers disagree with each other, and on renewal clauses they will.
What it looks like filled in
| Row | Documents | Current term ends | Notice (months) | Auto-renews | Terminate for convenience |
|---|---|---|---|---|---|
| Northgate logistics MSA.pdf | 31 Mar 2027 cl. 3.1 | 3 cl. 14.2 | Yes cl. 14.1 | No cl. 15 | |
| Facilities services MSA.pdfAmendment 3.pdf | 11 Sep 2026 Am. 3, cl. 1 | 1 Am. 3, cl. 2 | Yes cl. 14.1 | Yes, 60 days either party Am. 3, cl. 4 | |
| Reseller agreement.pdfOrder form.pdf | 29 Jun 2028 Order form, p.1 | Not stated | No cl. 4.1 | No cl. 4.3 |
Setting it up
- One workspace per contract set — a supplier book, a customer book, an entity.
- Bundle every agreement with its amendments and order forms first. This table is worth less than nothing if that step is skipped.
- Create the table, take the two preset columns, and add the four above. Set the types deliberately: notice period is a number so it can be arithmetic, and the term end is a date so it can be sorted.
- Run the three agreements you already know the renewal dates for, and check the table agrees with you before running the rest.
- Export to XLSX and subtract the notice period from the term end to get the date you actually need in a calendar. Ragextract will not do that arithmetic for you, and asking a column to is how you get a plausible wrong date.
What to check before relying on it
- The notice window, not the expiry date. The date that matters is the last day to serve notice, which is the term end minus the notice period. Nothing in the table computes it — that is the one step to do yourself, in the export.
- Terms already extended. “Current term ends” asks the model to account for an exercised renewal. Check that answer hardest, on any agreement that has been running longer than its initial term.
- Notice periods in the wrong unit. Ninety days and three months are not the same, and a number column asked for months will return 3 for both. Keep the prose Renewal Terms column beside it and read the two together.
- Notice served on the wrong party or by the wrong method. Nothing here captures that, and it is a common reason a served notice fails. Treat the table as the list of contracts to go and read, not as the instruction.
- Blank notice periods. “Not stated” on an agreement that does not auto-renew is usually correct. On one that does, it is a cell to open.
Keeping it current
Put the table in auto mode and every agreement added to the workspace joins the calendar without anyone rebuilding it. Amendments are the exception: an amendment belongs in the bundle with its agreement rather than as a new row, and that is a manual step.
Roughly what it costs
Two hundred agreements averaging 30 pages is 6,000 pages — 6,000 credits, $60, once, and shared with any other table in the same workspace. Six typed columns across two hundred rows is 1,200 credits, about $12. See how credits work.
Two of the columns above are quoted from a preset that ships in the app; the other four are written for this page and are illustrative starting points rather than legal definitions. Nothing here is advice about your contracts.