A contract repository is the place executed agreements live along with the facts about them. The distinction that matters is between a repository and a folder: a folder holds files, and a repository holds files plus the fields that make them answerable. Somebody asking which agreements renew this quarter, or who signed the supplier contract and when, is asking a question a folder cannot answer at any speed. This page sets out what a repository has to hold, why those particular fields, and where the different names in this category point at the same thing.
The nine fields that turn a folder into a repository
Counterparty. What the agreement covers. Effective date. End date. Renewal term. Notice days. Value. The person here who owns it. The executed file itself. Nine fields, the same nine on every agreement, and the sameness is the point: comparing two contracts stops being an act of reading and becomes a matter of looking. Add fields beyond these only when every agreement will have one, because a field only some records carry cannot be sorted or counted.
Why the dates have to be fields and not clauses
An end date in clause 14 of a PDF cannot be counted forward, sorted, filtered or warned about. Lifted into a field it can be all four, and the difference is the difference between knowing what needs deciding this quarter and finding out afterwards. This single change accounts for most of what a repository is worth, which is why a spreadsheet with the dates in it is already most of the way there.
Contract database, repository tools, agreement tracking software: the same thing
These names come from different vendors describing the same product. Repository emphasises storage, database emphasises the fields, tracking emphasises the dates and obligations. A product using any of the three should still be judged on the nine fields, on whether it warns before a notice window closes, and on whether it exports everything in one action. The label predicts nothing.
What a repository should never become
It should not become the place drafts live, because drafts churn and the record needs to be stable. It should not become a general document store, because then finding a contract means filtering out everything else. And it should not become one person's system, because a repository only two people can open has not solved the problem it was bought for.
Questions people ask about contract repository
What is a contract repository?
A single store of executed agreements together with the facts about each one: counterparty, dates, notice period, value, obligations and the signed file. The facts are what separate it from a folder.
What is the difference between a contract repository and a contract database?
Nothing substantive. Repository emphasises the stored documents and database the structured fields, and any usable product has both.
Should drafts go in the repository?
No. Keep the repository to executed agreements so the record is stable and unambiguous. Drafts belong wherever the negotiation is happening.
How many fields should a contract record have?
About nine, and the same nine on every agreement. Fields that only some contracts carry cannot be sorted or counted, which is most of the value gone.