The notice period nobody saw coming

The most persistent loss in an organisation is rarely dramatic. It is a contract that quietly renews for another year because the notice period fell three months before the end date and nobody knew.

This piece is about a process that looks dull and therefore suits an agent well: the contract register. What goes into it, what the agent does, and why the decision stays with a person.

The numbers are an example from general professional knowledge, not research and not from a real organisation. The pattern is what matters.

The problem in a small organisation

Take a consultancy with thirty people. About eighty contracts are running: the rent, a few lease cars, software, cleaning, insurance. The originals are in folders, some in email, some with a colleague who no longer works there. Who knows when each contract ends and how far ahead you have to give notice?

Usually nobody does, until it is too late. Then it turns out a software subscription runs for another year. That is nobody's particular mistake. It is what happens when important dates live in eighty places and in nobody's calendar.

In a large organisation it is the same, only bigger: thousands of contracts, rent, licences, suppliers, and a few that run on for a year or more every year by accident. They are not big amounts one by one. Added up, they are.

What the agent does

An agent can do this work well. It reads each contract and pulls out a fixed set of things: the term, the end date, the notice period, whether it renews tacitly, whether indexation applies, and special clauses. From that it builds a register: one line per contract, with the details side by side.

The first register is already useful, because for the first time you see everything in one place. But the real gain comes after that. The register knows the date by which you must decide, not only the date the contract ends. A contract that ends on 1 December with three months' notice has its decision moment around 1 September. That is what the reminder is for: ninety, sixty and thirty days ahead.

With the reminder, the agent prepares what is needed to decide: what does it cost now, what did it cost last year, what are the alternatives, which special rules apply. An overview of one page, not a pile.

Where it can go wrong

An agent that reads contracts can make mistakes. A date that differs in two places, a term changed in an appendix, a poor-quality scan. That is no reason not to do it. It is a reason to set up the process so a mistake becomes visible before it costs anything.

Three rules make the difference.

Every claim has a page reference. The agent does not just write "notice period three months", it also writes where that is stated. A person can check it in ten seconds, and so it really gets checked.

Uncertainty stays visible. If a term is unclear, if there are two different dates, or if the scan is unreadable, the agent says so instead of putting a guess in the register. A register with a question mark is more honest than one that is always confident.

Giving notice never happens automatically. The agent can prepare a draft letter, but the owner decides and signs. Cancelling a contract you needed by mistake costs far more than letting one run a year too long. What you cannot undo, you leave to a person.

What changes for the people

For the people, the change is mostly in their heads. Nobody has to remember when anything ends. It is a quiet change, and it is exactly what you want from a good process: the work depends less on anyone's memory.

It also makes conversations better. Whoever knows three months ahead that a contract is ending can negotiate. Whoever hears a week before that it has been renewed can only pay.

What a register also shows

Once the register exists, questions surface that nobody had asked. Which suppliers do we have twice, under two names? Which licences are paid for people who no longer work here? Which contracts have an indexation that runs on every year without anyone starting the conversation?

Those are not questions for an agent. They are questions for you. The agent makes it visible and you decide what to do with it. It is a good example of what I expect from agents: not that they decide, but that they make sure you know what there is to decide.

There is an honest caveat too. A register is only as good as its upkeep. When a new contract arrives it has to go in. So the step belongs in the process: whoever signs a contract passes it to the same process, and the agent reads it along. Without that habit the register is out of date within a year, and then it is more dangerous than no register, because everyone relies on it.

How to start small

You do not have to buy a system. Start with forty contracts, in whatever form they are in, and let the agent make a register of them. Check the register yourself, line by line, the first time. You see straight away where it does well and where it hesitates, and you learn which fields you really want. Usually there are fewer than you thought.

Then switch on the reminders, and watch for a few months how often a reminder leads to a real decision. That is the measure: not how many contracts are in the register, but how many decisions you managed to make in time.

What it costs, and what it returns

The register reads each contract once and afterwards only when something changes. So the cost is mostly in the first reading, and that stays within a ceiling: you set in advance how much the agent may use for it. The return shows in decisions you took in time. One contract you cancel or renegotiate in time often outweighs the whole reading effort. Keep track as a simple list: which contract, which decision, when. After a year you have your own numbers, and they are worth more than any example.

The pattern

An agent reads, sorts and warns. A person decides and signs. Between the two sits a reference to the source, so the person does not have to trust blindly. It is one of the simplest processes to start with, because the boundary is clear and the benefit is visible straight away. A good first step, even if you want to move on to more complicated work afterwards.

If you want to set up a process like this with an organisation, that is exactly the question I like to spend a day on: which work deserves an agent, and where should a person keep the last step?

Which contract at your place ran on last year without anyone deciding it?

#AIAgents #ContractManagement #WorkProcesses #RiskManagement

All pieces