Licences and subscriptions
Under the supplier, with the renewal date and the notice period, so the owner decides before the next term begins.
A supplier contract renewed itself because the notice date sat in one person's calendar. We set up a register where each contract has its dates and an owner, who gets a task before the notice date. Drafts and the signed copy stay with the contract.

Contract management software, also called contract lifecycle management (CLM), keeps every contract in one register with its counterparty, its owner and the dates that matter. It runs approval and signature as a workflow and reminds the right person before a notice date. Supplier and customer contracts, NDAs, leases, licences, framework agreements and data processing agreements all belong in it.
A new contract starts from your approved template in Word, and the template fills in the counterparty and the dates from the details on the contract.
Review and approval are tasks with deadlines. Each handover is recorded with the time and the user, and the workflow moves on when all approvers have responded.
With the DocuSign or Adobe Acrobat Sign integration and your own subscription to that service, the signed contract comes back to the register by itself.
One copy of the contract appears under the customer or supplier, under its owner and in the register, because those are its metadata rather than folders.
A task goes to the contract owner a set time before the notice date. Reminders are configured, so other dates on the contract can carry a task of their own.
When a contract has ended, a retention rule archives or deletes it after the period you set, and someone can be told before that happens.
When one stage is done, the next person is told it is their turn. The stages are a workflow, set up around the way you approve contracts today.
Contract owner and the other party
The contract is written in Word from an approved template. With CtrlShare, from our development partner CtrlDocs, the other party is invited by email to work on the same draft.
Reviewers and approvers
Reviewers and approvers each get a task with a deadline and a reminder before it, and every step is logged with who and when.
Contract owner
The contract goes out for signature with DocuSign or Adobe Acrobat Sign, using your own subscription to that service, and the signed copy returns to the contract by itself. The drafts stay in its version history.
Everyone with access
The contract is found under the counterparty and in the register, sorted by end date or notice date. Other obligations in it can reach the person responsible as tasks.
Before the notice date, the contract owner gets a task to decide. A contract that has ended is archived or deleted by a retention rule after the time you set.

Contracts are written in Word, negotiated by email and belong to customers and suppliers your other systems already know. Our contract management runs on M‑Files, which connects to each of them.
Open, edit and save contracts from Office and fill in the metadata as you save. Details from M‑Files, such as the counterparty, can be inserted into the document itself and kept up to date.
The emails around a negotiation are filed from Outlook with their metadata, and M‑Files can pick up the counterparty or the contact from the email.
Share a draft with the other party in one step. They are invited by email and edit in the browser, and the result comes back to the contract as a new version. From our development partner CtrlDocs.
Lists such as customers and suppliers are kept in sync with your business system, so a contract is filed under the same counterparty your ERP knows, spelled one way.
Open contracts and search the vault from Teams.
Signed paper contracts are scanned, and M‑Files OCR makes them searchable PDFs, so an old agreement is found by the words in it.
A contract is always with someone: a supplier, a customer, an employee or a landlord. The same vault keeps each contract with that party, next to the rest of its documents.
Under the supplier, next to its certificates and the list of what expires next.
Learn moreUnder the customer, with the proposal, the emails and the opportunity they came from.
Learn moreIn the employee file, open to HR and the manager only, and deleted by rule after the leaving date.
Learn moreUnder the supplier, with the renewal date and the notice period, so the owner decides before the next term begins.
Under the landlord, with one task before the notice date and another before each rent review.
Under the party they were signed with, and open only to the people involved in the talks.
M‑Files Aino, the AI assistant built into M‑Files, answers questions about a contract and shows the document each answer came from. It sums up a long agreement, translates the summary for a colleague, and only uses content the person asking may see.
A contract list in Excel works while one person keeps it up to date and the contracts are few. This is what changes when they move into a register.
| Feature | In a spreadsheet | In the contract register |
|---|---|---|
| Renewals | A date in a cell, seen when someone opens the file | A task to the owner before the notice date |
| Approvals | An email thread | Tasks with deadlines, and each step logged with who and when |
| The signed copy | Wherever the person who signed it saved it | On the contract, with the drafts in its version history |
| The counterparty | Typed by hand, sometimes spelled several ways | One customer or supplier, with the contract filed under it |
| Access | Everyone who opens the file sees every contract | Follows the kind of contract |
| When someone leaves | The reminders in their calendar go with them | Tasks go to the role, and the history stays in the log |
| Questions about the content | Open each contract and read it | Ask Aino and see the source |
Your customers and suppliers are probably in a CRM or an ERP already. A contract system that uses the same list saves typing each counterparty again and spelling it a second way.
Employment contracts, NDAs and supplier agreements seldom have the same readers. List the kinds, and decide who may open each, before you look at any screens.
Some companies want drafting, negotiation and approval in one flow. Others mainly need a reliable list and a reminder before each notice date. Knowing which tells you how big the first step should be.
Contracts are drafted in Word, sent back and forth in Outlook and discussed in Teams. Ask to see the system from inside those programs, because that is where people will use it.
A separate tool is one more place to look. In the document system you already run, contracts sit next to the proposal, the emails and the supplier's certificates. If that system is SharePoint, our comparison of M‑Files and SharePoint shows how the two differ.
Take a framework agreement that ends on 31 December, with three months' notice. The end date is 31 December, but the date that counts is 30 September, the last day to give notice. The register keeps both, and the owner's task arrives before the earlier one.
| Detail | What it does |
|---|---|
| Kind of contract | NDA, lease, licence, framework agreement, data processing agreement and so on. It decides who may open the contract. |
| Counterparty | Files the contract under the customer or supplier. The list of counterparties can be kept in step with your CRM or ERP. |
| Owner | Receives the tasks. The owner is named on the contract, so a new owner takes over the next task. |
| Start and end date | Order the register and show which contracts are running. |
| Notice date | Sets off a task to the owner a set time before it. |
| Renewal terms | Whether the contract renews by itself, and for how long, written where the owner sees it. |
| Other dates | Price adjustments, deliveries and certificates due from the supplier, each with a task and a deadline of its own. |
| Value | Added up across contracts in a CtrlPortals list, from our development partner CtrlDocs. |
| Status | Where the contract is in its workflow, from draft to ended. Every change is logged with time and user. |
We scope and deliver the set-up on M‑Files, and contracts make a good pilot: start with the ones that have a notice date. The price depends on the M‑Files edition, the licence types, cloud or your own servers and the scope of the set-up. Pricing and editions sets out what a quote contains.
Together
We go through the kinds of contract you hold, who owns them, which dates matter and who may see what.
Our consultants
The contract type, its metadata, the register, the workflow and the reminders are set up, your templates are brought in, and counterparties are connected to your CRM or ERP where you want them.
Together
Existing contracts are scanned or moved in with their counterparty and dates. With the M‑Files Metadata Agent, metadata can be suggested for existing documents in bulk.
After go-live you have fast access to specialist knowledge, an agreed SLA, technical advice and support, and enquiries are answered the same working day.