The renewal date nobody noticed: finding what your contracts commit you to

Every company has a contract it signed years ago that will renew itself next month. The date is written on page six. Nobody has read page six since the day it was signed, and the notice period for cancelling closed last week.

The short answer

Most of the money lost in contracts is not lost in disputes. It is lost in dates and obligations that nobody tracked: automatic renewals, notice periods, price increases, service levels the supplier missed and nobody claimed. A document pipeline can read a folder of contracts in Arabic and English and turn those clauses into a calendar. The reading is the easy part; deciding which clauses matter and who acts on them is the work.

Where the money goes

World Commerce & Contracting, the industry body for contract management, has reported for years that poor contract management costs companies around 9% of their bottom line. The figure comes from large organisations, and a small business will not lose on the same scale. The pattern, though, is the same at every size: the losses come from terms that were agreed and then forgotten.

For a Kuwaiti business the usual suspects are easy to list. A lease that renews for another year unless notice is given ninety days before. A software subscription that rises by a fixed percentage every renewal. A maintenance contract promising a four-hour response that has not been met for months, with a penalty clause nobody has invoked. A supplier agreement with a volume discount that was never applied.

None of these requires a lawyer to spot. They require somebody to read the contract at the right moment, and that is precisely what does not happen when the contracts live in a filing cabinet or a shared folder.

What to extract, and what to leave alone

The mistake is to try to extract everything. A contract has dozens of clauses and most of them never need action. Start with the handful that carry a date or a number.

Clause	What to capture	Why it matters
Term and renewal	End date, whether it renews automatically	The single most expensive clause to miss
Notice period	Days of notice, and to whom	Sets the real deadline, which is earlier than the end date
Price changes	Escalation percentage or review date	Explains next year’s invoice before it arrives
Service levels	Response times, penalties or credits	Money you are owed and not claiming
Parties and signatory	Legal names, who signed	Needed to act on any of the above

Leave interpretation to people. Whether a clause is enforceable, or what a vague phrase means, is a legal judgement. The pipeline’s job is to find the clause, quote it and show where it sits in the document, so the person who decides can read the original in seconds.

The clauses people forget exist

Beyond the dates, a few clauses cause trouble precisely because nobody remembers agreeing to them. An exclusivity clause that stops you buying the same service from anyone else in Kuwait. A minimum purchase commitment that turns a quiet quarter into an invoice for goods you never ordered. A termination-for-convenience clause that lets the other side walk away on thirty days’ notice while you are locked in for a year.

These do not belong in the reminder calendar, but they belong in the summary the pipeline produces for each contract: one line per clause, quoted, with the page number. When someone proposes a new supplier or a new office, that summary answers in a minute the question that otherwise needs the whole file pulled out of the cabinet.

Why Arabic contracts need extra care

Many contracts in Kuwait are bilingual, with Arabic and English side by side and a clause stating which language prevails. Some are Arabic only, scanned from a signed paper copy. Both create problems that a pipeline tested only on clean English PDFs will not handle.

Scanned Arabic text is where accuracy drops first. Stamps and signatures sit over the text, pages are photographed at an angle, and dates may be written in Hijri or Gregorian, with Arabic-Indic or Latin digits. We covered the same failure points for invoices in reading Arabic invoices with AI, and they apply here with higher stakes, because a misread date on a contract becomes a missed deadline.

Bilingual contracts add a subtler risk: the two versions do not always say the same thing. Extracting from the English side of a contract where the Arabic prevails is extracting from the version that does not count. The pipeline should read the prevailing language, and flag any date or figure that differs between the two.

From extracted clause to action

A spreadsheet of extracted dates is not a result. A reminder that reaches the right person before the deadline is.

For every contract the output should be three things: the key dates with the notice deadline calculated back from the end date, a link to the exact page and clause each date came from, and a named owner who receives the reminder. The owner matters more than the technology. A reminder sent to a shared inbox is a reminder nobody acts on.

Set the reminder to arrive well before the notice deadline, not on it. Deciding whether to renew a lease or switch a supplier takes weeks, and a reminder that arrives on the last possible day only lets you renew by default.

Check it before you trust it

Before relying on the calendar, take twenty contracts whose dates you already know, run them through, and compare. Every wrong or missing date is a finding about your documents: a scan quality problem, an unusual clause wording, a date format the system did not expect. This is the approach in the 100-example test, applied to the documents where an error costs the most.

Keep a person in the loop for anything the system is unsure about. A well-built pipeline says when it is unsure, and those contracts go to a human for a two-minute check rather than into the calendar unverified.

A realistic first project

Start with the contracts that renew: leases, subscriptions, maintenance and supply agreements. For most small and mid-size companies that is somewhere between a few dozen and a few hundred documents, which is small enough to verify properly and large enough that doing it by hand keeps getting postponed.

The first pass usually finds at least one renewal nobody knew about. That one date tends to pay for the exercise, and after it the calendar only needs updating when a new contract is signed.

How we build it

Our document intelligence projects start with a sample of your real contracts, scans and all, and report accuracy on those before anything else is built. The same pipeline handles the other paperwork Kuwaiti businesses deal with, from civil ID copies to government forms. Tell us how many contracts you hold and in which languages, and we will tell you what a first pass would find.

Frequently asked questions

Is it safe to send our contracts to an AI system?

It depends where the processing happens and under what terms. Contracts should be processed under an agreement that excludes training on your data, with access limited to the people who need it. Ask any provider where the documents are stored and for how long.

Can it read handwritten amendments?

Short handwritten changes, such as a corrected date, are often read but should always be flagged for a person. Long handwritten clauses are not reliable enough to extract without review.

Does it replace a lawyer?

No. It finds and organises clauses so that people act on time. Whether a clause is enforceable, and what to do about a breach, remain legal questions.

What about contracts that are only in Arabic?

They are handled the same way, provided the system has been tested on Arabic scans of similar quality. Test on your own documents before relying on any accuracy figure.

How much work is it to keep the calendar current?

Very little once the backlog is done. Each new contract is added when it is signed, which takes minutes, and the reminders run on their own.