Contract repository (contrathèque)

The French word contrathèque is built like bibliothèque, a library: a place where contracts are filed and found. It spread through French legal departments in the 2010s, when shared drives and filing cabinets reached their limits. English-speaking teams say contract repository. In both languages the notion goes beyond storage: it names what the company knows about its own commitments.

A proper repository knows, for each contract, the parties, the signature date, the effective date, the term, the renewal mechanism, the notice period, the amounts and the governing law. It links the contract to its amendments, which modify it by mutual consent (French Civil Code, article 1193), and to its schedules. It knows which version is authoritative.

The first step is the inventory: where are the contracts? On a server, in mailboxes, at branch offices, in the signature tool, on paper. Collection follows, mostly as PDFs, scans and Word files. A bulk import brings them into one place, where OCR makes scans readable and each document receives a folder, tags and access rights.

The third step is data extraction. Long typed in by hand, it is now handed to AI, which reads each contract, proposes parties, dates, terms, notice periods and deadlines, and shows the clause each value comes from. The lawyer validates, which turns a stock of files into a database. The last step is continuous feeding: every newly signed contract joins the repository with its data.

A shared drive or a document management system files documents by folder and finds them by name or full text. It does not know what a contract contains. It cannot tell that a services agreement auto-renews in four months, or that the termination notice is six months. The repository structures that data and puts it to work: deadline alerts, filters by counterparty, exports to finance.

The repository is also the memory of the CLM, of which it is the final stage: what was drafted from a template, negotiated, approved and signed ends up there with its version history and signature evidence file. An e-signature tool, by contrast, keeps signed documents but links them neither to their amendments nor to their deadlines.

For the legal department, the repository ends the mailbox searches and the approximate answers. An audit, a due diligence or a request from the statutory auditor is handled with an export: the list of active contracts, their parties, amounts and end dates. The lawyer also finds the position negotiated with a counterparty before reopening a discussion.

For finance, it is the source of off-balance-sheet commitments, leases and subscriptions to provision for. For procurement, it holds negotiated terms and renewal dates, a sensitive point: under French law, tacit renewal creates a new contract identical in content to the previous one but of indefinite duration (Civil Code, article 1215). For HR, it is each employee’s contractual file, amendments included.

Completeness first: a repository missing the contracts signed by subsidiaries or branches cannot support any confident answer. Data reliability next: every date and amount should be traceable to its source clause. Access rights last: employment contracts, non-disclosure agreements and strategic contracts do not have the same readers.

Retention follows statutory periods: ten years for accounting records (Commercial Code, article L123-22), five years for the general limitation period (Civil Code, article 2224), and for personal data no longer than the purpose requires (GDPR, article 5). A repository that archives with a retention end date makes those decisions easier.

Common mistakes: typing data by hand with no link to the contract, importing without folders or tags, opening access to everyone, or keeping only contracts signed in the tool and forgetting the existing stock. The lack of continuous feeding is the costliest: a repository frozen on import day is a shared drive again within a year.