A clause library is the record of what the company has already agreed to sign: the confidentiality clause it uses, the limitation of liability it accepts, the governing law it insists on, the payment terms it gives and the fallbacks it has accepted under pressure, each kept by type with a note on when it applies. Organizing contracts around their clauses rather than their filenames is what turns a shared drive into a register, and contract metadata, the term, notice period, value, owner and counterparty recorded as fields, is what makes the register searchable. This page is about what the library holds, how contract clauses and metadata are organized, and why the library is the part of legal document automation that a small team should build first.
What the library holds
One entry per clause type the company negotiates: confidentiality, limitation of liability, indemnity, governing law, term and termination, payment, data protection, insurance, assignment. For each, the company's standard wording, the fallback positions it has accepted, the contracts they came from and a note on when each applies. That last part is the value: a clause without the note is a paragraph, a clause with it is a position. Contract clauses gathered this way are what a new contract is assembled from and what a negotiation is measured against.
Contract metadata, and organizing contracts so they can be found
Contract metadata is the set of fields recorded for every contract: counterparty, type, term, renewal term, notice period, annual value, owner, status, and the clause types it contains. Organizing contracts by those fields is what lets the register answer the questions it is asked: every contract with this counterparty, every contract renewing this quarter, every contract with an uncapped indemnity. The free contract tracking calculator on this site works from four of those fields as averages; the paid register holds them per contract.
Why the library is where automation starts
Legal document automation is assembling a document from clauses and deal terms, and it is only as good as the library it assembles from. A team that builds the library first, from the contracts it has already negotiated, gets automation that produces contracts it would sign; a team that buys the automation first gets a template generator with no positions in it. The library is also the record of the company's risk appetite, which is why it belongs to the legal team and not to a drafting tool.
Questions people ask about clause library
How many clause types does a small legal team need in the library?
Usually between ten and twenty: the clauses that are negotiated in most contracts, with their fallbacks. A library of every clause in every contract is a filing system, not a library; keep the ones the team argues about.
What metadata should every contract carry?
Counterparty, type, term, renewal term, notice period, annual value, owner and status at minimum, plus the clause types present. Those fields are what the register's questions are asked in, and what the deadlines are computed from.
Is the clause library part of the free tools?
No. The free tools work the register's arithmetic from figures you enter. The clause library, with the clauses, fallbacks and the contracts they came from, is part of Clauselane Pro at $49 a month for the whole legal team.