What Is a Contract Repository (and Why It's Not a CLM)

A contract repository is a single, searchable, access-controlled store of your executed contracts, with the key facts about each one, parties, dates, value, renewal, pulled out into fields you can search and report on. It is not a filing cabinet and it is not a shared drive full of PDFs named "final_v3_FINAL.pdf". A repository answers one question reliably: where is the signed contract with this counterparty, and what does it say. This guide (published by Adira, which sells full contract lifecycle management software, so we have a commercial interest in you eventually needing more than a repository, but this page is written to be useful on its own, whether or not you buy anything from us) sets out what a repository actually needs, the India-specific test almost every "repository" fails, and when a repository stops being enough.

What a good repository actually has

Most teams that say "we have a repository" mean a shared drive. That is a repository only in the loosest sense. A repository worth the name has five things.

A single source of truth, one place, not scattered across email attachments, a shared drive, and someone's downloads folder. Otherwise you do not have a repository, you have a search problem waiting to happen.

OCR on everything, including old paper contracts. Optical character recognition turns a scanned image into searchable text. Without it, a five-year-old paper lease that was scanned and filed is invisible to search, technically stored, practically lost. "We have it somewhere" is not the same as findable.

A metadata schema, not just a filename. Every contract should carry structured fields: counterparty, contract type, effective date, expiry or renewal date, value, governing law, and an internal owner. You cannot query "show every vendor contract expiring in the next 90 days" against a filename.

Version history that keeps every draft, with the final executed copy clearly flagged. If negotiation ran through eight redlines, the repository should hold all eight plus the signed version, not just whichever file someone last saved over the others.

Permissions that are not "everyone with a login sees everything." An NDA with a potential acquirer, a salary term in an employment contract, and a routine vendor purchase order do not belong behind the same access level.

A repository with all five is genuinely useful, and genuinely cheap to build with tools you likely already pay for. A fuller step-by-step build guide, including a workable metadata schema you can copy, is here: how to build a contract repository.

Why a repository is the foundation, not a CLM

A repository stores and finds. It does not draft a contract from a template, route a draft through internal approvers, track redlines against a playbook during negotiation, or flag that a clause has drifted from your standard position across fifty vendor contracts. Those are workflow and negotiation functions, and they sit in contract lifecycle management (CLM) software, a different and larger category. Vendors blur this line constantly, a repository with a renewal-date field gets marketed as "contract management." The full breakdown, with a capability-by-capability comparison table, is here: CLM vs contract management vs contract repository. The short version: if your tool cannot draft from a clause library or route a document for approval before signature, it is a repository, however it is labelled.

The India-specific test: is it the stamped, executed version

This is the part almost every "we have a repository" claim fails on quietly, and it is specific to India in a way most repository advice, written for a US or UK audience, does not mention at all.

In most Indian states, an agreement that creates or transfers rights, a lease, a sale deed, certain loan and security documents, must be stamped, meaning stamp duty is paid on it, either physically or via e-stamping, before or at execution. This is not a formality you can catch up on later without cost. Section 35 of the Indian Stamp Act, 1899 states plainly:

"No instrument chargeable with duty shall be admitted in evidence for any purpose by any person having by law or consent of parties authority to receive evidence, or shall be acted upon, registered or authenticated by any such person or by any public officer, unless such instrument is duly stamped." Source: Section 35, Indian Stamp Act, 1899, Indian Kanoon

Read that carefully. It does not say an unstamped contract is automatically void, an under-stamped instrument can usually be cured by paying the duty plus a penalty at the point it is used, and the section carves out narrow exceptions. But it does say the instrument cannot be admitted in evidence "for any purpose" until that happens. If your repository holds only the version e-mailed around for signature, with no record of whether stamp duty was paid, how, or how much, you have stored a document that may be worthless in a dispute until someone tracks down and pays a duty and penalty you have no record of. A repository built for India needs a field for this: stamp duty status, mode, and amount, not just "signed: yes."

And track registration where relevant

Stamping and registration are two different steps, and a repository needs to track both separately. Section 17 of the Registration Act, 1908 sets out which documents must be registered, including, under Section 17(1)(d), "leases of immovable property from year to year, or for any term exceeding one year, or reserving a yearly rent." A one-year office lease with an auto-renewal clause can fall into this bucket without anyone in procurement realising it. Section 17, Registration Act, 1908, Indian Kanoon.

The consequence of skipping registration where it was required sits in Section 49 of the same Act. A document that needed registration under Section 17 and was not registered:

"...shall not... be received as evidence of any transaction affecting such property or conferring such power, unless it has been registered." Source: Section 49, Registration Act, 1908, Indian Kanoon

There is a narrow proviso, an unregistered document can still be used as evidence of a contract in a suit for specific performance, or to prove a genuinely separate "collateral" transaction. But that exception is deliberately narrow. In K.B. Saha and Sons Pvt Ltd v Development Consultant Ltd, (2008) 8 SCC 564, the Supreme Court held that a lease deed falling under Section 17 and never registered could not be read in evidence to prove the actual terms of the lease, and that a party cannot invoke the "collateral purpose" exception to smuggle in proof of the very terms registration exists to record. See the full judgment on Indian Kanoon. For a repository, the translation is blunt: an unregistered lease is not a safety net if its terms, not just its existence, ever get disputed.

A repository built for Indian contracts should therefore carry, per contract, three things beyond the basics: whether the instrument required registration at all, the registration or book number if it was, and where the certified copy sits. Most repositories, Indian or foreign-built, have none of these fields, because the product was designed around US or UK filing norms, where neither stamping nor registration works this way for ordinary commercial contracts.

A two-minute test you can run right now

Open whatever you currently call your repository. Pick one contract signed more than a year ago, ideally a lease or anything involving immovable property. Try to answer, without reading the PDF end to end:

1. Is this the fully executed, stamped copy, or an earlier draft that happens to be the last one saved?
2. What stamp duty was paid, and how (physical stamp paper or e-stamp)?
3. Did this document need registration, and if so, what is the registration number?
4. Who owns the renewal date, and when does it fall?

If you cannot answer all four inside two minutes, you have a folder, not a repository, a gap that stays invisible until a dispute or audit forces someone to reconstruct it under time pressure.

Red flags in what people call a repository

Normal	Red flag	Why it matters
Final signed PDF stored, with visible signatures and, where applicable, the stamp	Only the last Word redline is stored, no signed PDF	The redline was never authenticated; it is not the document that binds either party
A field records stamp duty status, mode, and amount	No field exists for stamp duty	Under Section 35, an under-stamped instrument is inadmissible until the deficiency and a penalty are paid
A field records whether registration was required, and the registration number	Registration status is never tracked	Leases exceeding a year and similar instruments need registration under Section 17; skipping it weakens the document on its actual terms
Renewal and expiry dates sit in a searchable field	The renewal date only exists as a sentence buried in the PDF	You cannot report on, or get alerted about, text a search index never indexed as a date
Old paper contracts are OCR'd and full-text searchable	Scanned paper contracts sit as unsearchable image files	"We have it somewhere" is not the same as findable
Access is scoped by contract sensitivity	Every employee with a login can open every contract	An NDA with an acquirer should not be one login away from the whole company
Version history keeps every draft, executed copy flagged	Only the "latest" file survives, earlier drafts overwritten	If a dispute turns on what an earlier draft said, an overwritten history cannot answer that
The system logs who opened or downloaded a contract, and when	No access log exists	Without a log, you cannot show who could have altered a copy if authenticity is challenged
Vendor confirms full, usable data export on cancellation	Export on exit is vague or charged as a separate fee	A repository is your asset; a hard exit clause turns it into the vendor's leverage

A repository policy line: bad versus better

Most internal SOPs for "what happens after a contract is signed" are one throwaway sentence that nobody revisits until it fails.

Bad: "All finalised contracts must be uploaded to the shared drive after signing."

What is wrong: it does not say which version (the last draft or the actually executed one), does not mention stamp duty or registration at all, sets no deadline, names no owner, and "shared drive" implies no access control.

Better: "Within 3 business days of full execution, the contract owner must upload to the repository: (a) the fully executed copy and, where stamp duty applies, the duly stamped instrument as required under Section 35 of the Indian Stamp Act, 1899; (b) the registration certificate and document or book number where the instrument falls under Section 17 of the Registration Act, 1908 (for example, a lease exceeding one year); and (c) a completed metadata record covering parties, effective date, expiry or renewal date, contract owner, and governing law. Access to the uploaded record shall be restricted according to the confidentiality classification assigned to the agreement."

What changed: it names the exact version required (stamped, not merely signed), turns registration from an afterthought into a checked field, sets a deadline and a named owner, and ties access to a classification rather than defaulting to "everyone can see it."

Building one on a budget, and when it stops being enough

None of this needs expensive software to start. A shared drive with a locked folder structure, a spreadsheet acting as the metadata index, and a consistent naming convention gets a small team most of the way there, and is genuinely free. A step-by-step build guide, including the exact metadata columns worth tracking, is here: how to build a contract repository. Before a document reaches the repository, it usually needs review and redlining, and that does not need to cost anything either: Weave, Adira's free browser-based markup tool, lets you comment on and mark up a draft with no account and no upload.

A plain repository stops being enough on volume and coordination, not headcount. Once more than roughly thirty to forty contracts a month move through review or renewal, or once a missed renewal has already cost real money, passive storage has run out of runway, and it is worth looking at contract management or full CLM instead of another spreadsheet column. The full comparison of what each tier adds is here: CLM vs contract management vs contract repository.

US and global contrast

A repository built around US or UK practice genuinely does not need the stamping and registration fields described above, because neither concept works the same way there. Most US states impose no general stamp duty on ordinary commercial contracts, and document registration outside real estate deeds and mortgages is rare. A US-built repository product, used unmodified by an Indian team, will happily store your lease with no field for stamp duty or registration status, not because the vendor is careless, but because the product was never asked to track something that, for its home market, does not exist. That gap surfaces only when an Indian lease or security document ends up in a dispute and someone discovers the "repository" never captured whether it was properly stamped or registered. It is the clearest reason a repository built for Indian contracts needs different fields from one built for a US audience, whatever the marketing page says about being "global."

FAQ

Is a contract repository the same as a document management system (DMS)? Close but not identical. A general DMS like SharePoint or a shared drive stores any kind of document. A contract repository is purpose-built for contracts, with fields for counterparty, value, renewal date, stamp duty, and registration status, and is searchable on those fields, not just the filename. A generic DMS can act as a rough repository if you configure these fields yourself, but does not have them by default.

Do I need to register every contract with a government office? No. Most commercial contracts, purchase orders, service agreements, and NDAs need no registration at all. Registration under Section 17 of the Registration Act, 1908 is triggered by specific categories, chiefly documents affecting immovable property, including leases exceeding one year. Check the specific instrument against Section 17, do not assume either way.

If a contract was under-stamped, is it void? Not automatically. Section 35 of the Indian Stamp Act treats an under-stamped instrument as inadmissible in evidence until the deficient duty and a penalty are paid, at which point it can usually be admitted. Getting stamping right at execution is safer than paying a penalty later under time pressure in a dispute.

Can a repository replace a lawyer's review of a contract? No. A repository, and even full contract management or CLM software, automates storage, search, and tracking. Whether a clause is enforceable, or a document was correctly stamped and registered for your situation, needs a person, usually a lawyer, applying judgement to facts the software cannot see.

What does Adira actually sell, is it a repository? No. Adira is a full contract lifecycle management (CLM) product, drafting, workflow, negotiation, obligation tracking, and reporting, not just storage. Its paid plans (Practice USD 89 to 109 per seat per month, Firm USD 179 to 219, Enterprise on custom pricing, all with a 7-day trial, as published on adiralaw.com, last verified 4 September 2026) sit well above the repository tier described on this page. The free Weave markup tool mentioned above is useful on its own, whether or not a repository is eventually all you need.

This page gets you to a working picture of what a contract repository needs to function, including the stamping and registration fields most repository advice never mentions because it was not written for India. It does not tell you whether a particular contract in your own repository was correctly stamped or registered, or whether it would hold up as evidence in a dispute you are facing, that depends on facts this page cannot see, and is not legal advice. Talk to a lawyer before relying on any specific document's stamping or registration status in a live dispute.