Rights and contracts
Contract renewal exception data: notices, amendments and actual use
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
Build each renewal decision as a task packet that ties three evidence chains to one dated decision: notices actually sent and delivered, every signed amendment that changed the term, scope or notice period, and measured use against entitlement. Rank each item by authority, record the rule applied, label the exception, such as a late notice or use far below entitlement, and check the outcome against what happened next.
License terms
Contract renewal exception
Key takeaways
- Three chains meet at one dated decision: notices with proof of delivery, signed changes to the terms, and measured use against entitlement.
- Signed paper outranks tracking systems, and quoting tools can keep a stale notice window or seat count.
- Label the exceptions, such as late or defective notice, an amended notice period or use far below entitlement, because those are where reasoning fails.
- Prove the decision with a dated approval and the outcome with a later record, never with a CRM stage.
- Some outcomes turn on law outside the contract, such as New York's reminder rule for certain service contracts, so counsel reviews those cases.
- Screen privileged advice, confidential terms and personal details before anything leaves the legal team; removing names does not create a right to license.
How do you connect notices, amendments and actual use in a renewal decision task?
Treat the renewal decision as one dated task and hang three evidence chains off it: every notice sent or received with its method and delivery time, every signed amendment that changed the term, scope or notice period, and measured use compared with what the contract entitles. Each item gets an authority rank, the rule it feeds is written down, and any departure from the standard path is labeled as an exception.
The three chains disagree more often than people expect. The renewal date in the CRM was set when the deal closed, an amendment later moved the notice period, someone emailed a non-renewal letter to an address the contract does not name, and usage reports show far fewer active seats than were bought. A model asked whether the contract renewed has to work through all of that, and so does the answer key.
The task is only useful if its outcome is checked against what actually happened afterwards, such as a renewal invoice paid or access ended, not against a status field someone set. That separation between decision, outcome and status is what the packet below is built to keep.
Which renewal exceptions are worth capturing as labeled cases?
Capture the cases where the standard path, renew on the anniversary unless notice is given in time, was disrupted by a notice, an amendment, a usage fact or a rule outside the contract. These are the cases where people make mistakes and where a model needs practice; plain on-time renewals add volume but little signal.
Standard terms show how many moving parts there are. Common Paper's Cloud Service Agreement renews each order form for further subscription periods unless one party gives notice of non-renewal before the non-renewal notice date. The Bonterms Cloud Terms default to a 12-month initial term that renews unless the parties agree on a different renewal order or either party gives non-renewal notice at least 30 days before the term ends. Both let the order form or cover page change those variables, which is why the signed documents, not the template, control each case.
| Exception label | What triggered it | Evidence that controls | Typical wrong answer |
|---|---|---|---|
| Notice late | Non-renewal sent after the deadline | Notice clause in force, delivery record | Treating the send date as the delivery date |
| Notice defective | Wrong address, method or sender | Notice clause, cover page addresses | Accepting any email as valid notice |
| Notice period amended | Amendment changed the window | Signed amendment and its effective date | Using the original agreement's window |
| Renewal by new order | Parties signed a different renewal order | Signed renewal order | Assuming automatic renewal on old terms |
| Stale renewal quote | Quote generated before an amendment | Amendment plus contract record | Copying quantities from the stale quote |
| Use above entitlement | More users or units than licensed | Usage report against entitled quantity | Ignoring the reconciliation obligation |
| Use far below entitlement | Few active users of bought capacity | Usage report, renewal decision memo | Assuming low use means non-renewal happened |
| Statutory condition | A law adds a notice condition | Statute text and counsel's view | Applying the contract clause alone |
Which document wins when signed terms and tracking systems conflict?
The signed documents control, read through the order of precedence they set out, and systems of record only report what those documents say. Each item in the packet should carry its rank so a model can be scored on whether it resolved a conflict the right way.
Standard terms state the ranking rules explicitly. The Bonterms Cloud Terms give additional terms and then attachments priority over the base terms, say an order cannot modify other parts of the agreement unless it identifies the provisions it supersedes, require amendments to be in writing and signed by authorized representatives, and say that terms in business forms, purchase orders or quotes do not amend the agreement. Common Paper's agreement likewise requires any modification to be in writing and signed or electronically accepted by each party.
CRM and quoting tools sit lower because they can lag the paper. Salesforce documents that when a renewal opportunity has Renewal Quoted set, contracting later amendments or add-ons does not flow through to update the renewal quote; the fix is to toggle the flag off and on again. A renewal quote is therefore evidence of what the system believed at a point in time, not of the current terms.
| Rank | Source | Can establish | Cannot establish |
|---|---|---|---|
| 1 | Signed agreement, orders and amendments | Term, renewal rule, notice period and method | Whether notice was actually delivered |
| 2 | Delivery evidence for notices | Who sent what, how and when it arrived | Whether the notice period was the right one |
| 3 | Usage reports and reconciliation records | Measured use against entitled quantity | What the parties agreed to do about it |
| 4 | Renewal memo or approval record | Who decided and on which evidence | That the decision was carried out |
| 5 | CRM and quoting records | What the system recorded and when | Current terms after a later amendment |
| 6 | Emails and chat summaries | Context and timing clues | Any term, unless the contract allows notice that way |
What counts as evidence of actual use at renewal?
A dated measurement of how much of the licensed product was used, compared with the quantity the contract entitles, from a report one of the parties can stand behind. Assigned licenses, active users and metered units are different measures, so the packet should record which one was used and why it matches the contract's unit.
Some programs make the comparison a contractual step. Microsoft's Enterprise Agreement guidance describes the true-up as an annual inventory of products, services, users and devices added during the year, with the annual true-up order due between 60 and 30 days before the agreement anniversary. In a case like that, missing the reconciliation is its own exception, separate from whether the agreement renews.
Watch who owns the usage evidence. Under the Bonterms Cloud Terms, usage data means the provider's technical logs, data and learnings about the customer's use, and the provider may not disclose it externally unless it is de-identified and aggregated with data from other customers. A customer building a dataset from renewal files may hold the provider's usage reports, but that does not settle whether those reports can be shared; the agreement and counsel do.
The rights-screened packet, part by part
The packet below is the asset. Each row is a part a reviewer fills in for one renewal decision, with the source that must back it and the screen it passes before the packet leaves the legal team. Values in the last column are illustrative.
At a glance
The rights-screened packet, part by part
| Packet part | Contents | Must be backed by | Screen before use | Illustrative entry |
|---|---|---|---|---|
| Starting state | Contract id, current term end, renewal rule as signed | Agreement and latest amendment | Counterparty name pseudonymized | 12-month term, notice 60 days before end |
| Document chain | Each signed document with date and what it changed | Executed copies, not drafts | Unsigned drafts excluded and logged | MSA, order, amendment 1 |
| Notice log | Each notice with sender, method, address, sent and delivered time | Delivery records | Personal contact details removed | Email delivered 45 days before end |
| Use record | Measure, entitled quantity, measured quantity, period | Usage report with its source named | Use rights for provider reports confirmed | Active users against licensed users |
| Applicable rule | Clause text paraphrased, plus any statute counsel flags | Clause citation and counsel note | Privileged analysis excluded | Amended notice clause; no statute flagged |
| Decision | What the team decided, who decided, when | Approval record | Names replaced with roles | Renew at reduced quantity |
| Outcome check | What happened next, with date | Invoice, renewal order or access log | Amounts removed | Renewal order signed for the new term |
| Exception label | One or more labels from the exception list | Reviewer judgment, with reason | Second reviewer on disputed labels | Notice period amended; use far below entitlement |
| Counterexample | The nearest case where the same facts led elsewhere | A second packet id | Same screens as the main packet | Notice on time under the original window |
Worked example (illustrative): a 45-day notice against a 60-day window
This case is illustrative; the company, dates and counts are invented. A field services company subscribes to a scheduling platform on a 12-month order that renews unless either party gives notice at least 30 days before the term ends. In month seven the parties sign an amendment that adds 40 seats and changes the non-renewal notice period to 60 days.
In month eleven, operations reviews usage and finds that 25 of 140 licensed seats were active in the last quarter. Procurement emails a non-renewal notice to the provider's notice address 45 days before the term ends, working from the CRM renewal record, which still shows the 30-day window because the renewal quote was generated before the amendment.
The task asks whether the contract renewed. Under the original window the notice would have been on time; under the amended 60-day window it was 15 days late. The packet records the amendment as controlling, labels the case notice period amended and use far below entitlement, and records the decision the company then made: negotiate a renewal order at a lower seat count rather than contest the renewal. The outcome check is the signed renewal order for the new term.
The counterexample packet is a sister contract with no amendment, where the same 45-day notice was on time and access ended at term end. Together the two cases teach the point a model most often misses: the notice window comes from the latest signed document, not from the system that tracks the date.
What proves the renewal decision was made, and what proves it took effect?
The decision is proved by a dated approval from someone with authority to make it, and the outcome by a later record that shows the decision took effect. A CRM stage of closed won or churned is neither; it is a label someone chose, sometimes before the paperwork was done.
At a glance
What proves the renewal decision was made, and what proves it took effect
- Renewed: a signed renewal order or, for automatic renewal, the renewal invoice for the new term and its payment status.
- Not renewed: the provider's acknowledgment of notice or the access end record, plus any data export completed before access closed.
- Renewed on changed terms: the signed renewal order or amendment, compared field by field with the prior order.
- Disputed: the correspondence that opened the dispute and how it ended, with privileged material screened out by counsel.
- Statutory question: counsel's conclusion recorded only as a nonprivileged outcome label, or the case excluded.
Where a contract term is not the whole answer
Some renewal outcomes depend on law outside the contract, and those cases need counsel before they become labeled data. New York's General Obligations Law section 5-903 is one example: for contracts for service, maintenance or repair it makes an automatic renewal provision unenforceable against the person receiving the service unless the provider gives written notice, personally or by certified mail, at least 15 and no more than 30 days before that person's deadline to give notice. The section does not apply where the renewal period is one month or less.
Whether a given contract falls within a statute like that is a legal question for counsel, not a labeling rule. The packet should record that a statute was considered and the nonprivileged conclusion, and exclude cases where the answer turns on privileged advice that cannot be shared.
Also screen for privilege and confidentiality before anything leaves the legal team. Advice from counsel on whether to contest a renewal is typically privileged; the contracts themselves usually carry confidentiality clauses that limit sharing their terms; and the counterparty's people appear in notices and signature blocks. Removing names does not by itself create a right to license the records.
Turning renewal histories into licensable task data
Renewal files that link signed terms, notices, usage and outcomes are a compact record of how a business reasons about contracts, and they are much more useful to AI developers than contract text alone. Before any are shared, keep four questions apart: who can access the files, whether privacy rules permit the use, who owns the records and whether the contracts allow licensing them.
Legal and operations teams that take this path can have SourceX handle rights review and contracting through to preparation, delivery and payment for the licensed dataset. Delivery comes only after the company's signature on agreed scope and terms, with de-identification handled by SourceX through approved processing routes.
Frequently asked questions
Does a contract with an automatic renewal clause always renew if nobody gives notice?
Usually it renews on the terms the signed documents set, but not always. The parties may have signed a different renewal order, and some laws add conditions, such as New York's notice requirement for certain service, maintenance and repair contracts. Counsel should decide cases where a statute may apply.
Can an email count as a non-renewal notice?
Only if the notice clause allows it. Some standard terms deem email notice given on delivery to the address on the cover page, while other contracts require certified mail or personal delivery. Record the method and address and check them against the clause in force.
Should the CRM renewal date be used as the label?
No. The CRM date is useful context but can lag a later amendment, and quoting tools may not update a renewal quote after a change. Label from the signed documents and the outcome record.
What if the amendment was never signed?
An unsigned amendment does not change the terms under agreements that require signed written modifications. Keep it in the document chain as an unsigned draft and do not let it set the notice window or quantities.
Why record actual use if the question is only whether the contract renewed?
Because use often explains the decision and creates its own obligations, such as an annual reconciliation of added users. A case where use fell far below entitlement but the contract still renewed is exactly the kind of exception a model needs to see.
Sources
- Common Paper's Cloud Service Agreement renews order forms unless non-renewal notice is given before the non-renewal notice date, requires signed or electronically accepted written modifications, and deems notices given on confirmed delivery by email. Source
- The Bonterms Cloud Terms set a default 12-month renewing term with 30 days' non-renewal notice, an order of precedence, signed written amendments, notice delivery rules and a definition of provider usage data. Source
- Salesforce documents that later amendments do not update a renewal quote when Renewal Quoted is set, and that toggling the flag regenerates it. Source
- Microsoft describes the Enterprise Agreement true-up as an annual inventory of additions, with the true-up order due 60 to 30 days before the anniversary. Source
- New York General Obligations Law section 5-903 conditions enforcement of automatic renewal provisions in service, maintenance or repair contracts on a written reminder sent 15 to 30 days before the recipient's notice deadline. Source
See if your company qualifies
A short company assessment. No data uploads are needed.