How to Run a Contract Cleanup Project (Step by Step)

What is a contract cleanup project, and why run one? A contract cleanup project is a focused effort to find every live contract your organisation has signed, pull the important terms out of each one, and get them into a single place you can trust. Most teams need one because contracts pile up in email inboxes, personal drives, a shared folder nobody maintains, and a few filing cabinets. Nobody can answer simple questions like "which contracts auto-renew next quarter", "who are we committed to", or "where did we agree to that liability cap". A cleanup is usually triggered by a real event: a funding round or sale, a new general counsel, a move to contract management software, a data-protection audit, or a renewal that was missed and cost money. Whatever the trigger, the goal is the same. Turn a scattered pile into a reliable register, close the obvious gaps, and leave behind a habit that keeps it clean. This article is general guidance, not legal advice. ## Step 1: Set the scope and the goal Decide what counts as "in scope" before you start, or the project never ends. Agree on: - Which contracts. Customer, supplier, employment, leases, NDAs, licences. You may phase it, starting with revenue and spend contracts because they carry the most money and risk.

• Which time period. Only active contracts, or expired ones too? Expired contracts still matter for disputes and renewals.
• The one outcome. A complete register with key dates and obligations is a good first target. "Perfect metadata on everything" is not realistic in one pass. Write the scope down in a single page and get the sponsor to sign off. This is the document you point to when someone asks for "just one more contract type". ## Step 2: Find every contract You cannot clean up what you cannot find. Hunt in every place contracts hide: - Shared drives and document folders
• Email inboxes of people who sign or negotiate deals
• E-signature accounts (completed-envelope histories)
• Accounting and procurement systems (a payment usually means a contract)
• Personal laptops, old systems, and physical files Pull everything into one staging folder. Expect duplicates and several versions of the same agreement. Do not try to sort as you collect. Collect first, then sort. ## Step 3: De-duplicate and find the signed version Now reduce the pile. For each agreement, find the final signed version and mark it as the master. The signed copy wins over any draft. Watch for: - Multiple drafts named "final", "final2", "final-really"
• A signed PDF plus an editable Word version that do not match
• Amendments and side letters that change the original but live in a different folder Link each amendment to the contract it changes. A contract and its three amendments are one relationship, not four documents. ## Step 4: Capture the terms that matter For each master contract, record a small set of fields. Resist the urge to capture everything. The fields that earn their place are usually: - Parties and what the contract is for
• Start date, end date, and renewal type (fixed, auto-renew, rolling)
• Notice period to end or renew
• Value and payment terms
• Key obligations and deadlines
• Liability cap and indemnities
• Governing law
• Where the signed copy lives Put these in a spreadsheet or a contract register. This register, not the pile of PDFs, is the real deliverable. A reader with only the register should be able to answer "what renews next month" without opening a single contract. ## Step 5: Fix the gaps you find A cleanup always surfaces problems. Triage them into three buckets: - Fix now: a renewal due in weeks, a missing signature, an expired contract still being used.
• Fix soon: no liability cap, outdated data-protection terms, a party name that changed after a merger.
• Note and move on: cosmetic issues that carry no real risk. Assign an owner and a date to each "fix now" and "fix soon" item. A cleanup that finds problems but fixes none has only produced a longer worry list. ## Step 6: Set up the habit that keeps it clean The cleanup fails if the pile rebuilds in six months. Leave behind simple rules: - One home for signed contracts, and a rule that nothing is "done" until it is filed there
• A naming and folder convention people actually follow
• A standard set of register fields captured at signing, not months later
• A calendar of renewals and key dates with a named owner
• A quarterly check that the register still matches reality ## Common mistakes to avoid - Trying to capture every field on every contract in the first pass, so the project stalls.
• Cleaning up the documents but not the process, so the mess returns.
• No single owner, so nobody drives it to the end.
• Treating drafts and signed copies as equal, so you rely on the wrong version.
• Forgetting amendments and side letters, so the register shows terms that have since changed. ## Where a contract workspace helps Most of a cleanup is mechanical: reading each contract, pulling out dates, parties, renewal terms and risk points, and keeping versions straight. That slow work, along with drafting and reviewing the agreements you fix and governing the register once it is built, can live in one AI workspace tuned to how your company contracts, so a signed contract and its amendments stay linked and renewals stay in view instead of the register going stale the week after the project ends. Adira is one example of a workspace built around that single-home idea. A cleanup done by hand still works; a workspace mainly turns the one-off project into something that stays clean on its own.