How Do You Upload Existing Contracts and Track Their Key Dates?

> Quick answer: Upload the signed file, tag it with the counterparty and contract type, then set its key dates: start, renewal, expiry and notice deadline. Choose your own reminder window for each date, assign a named owner, and the contract is ready to be shared or re-signed from the same record later. PDF uploads work on every tier. Word, Excel and PowerPoint uploads need the Business tier or above.

Fenwick Interiors had eighteen supplier contracts sitting across four people's inboxes when the operations lead decided to bring them into one place. None had been drafted in the platform. All of them had been signed on paper or through other tools, then emailed around as attachments for years.

The process took an afternoon, not a week, because uploading an existing contract and tagging its dates is a short, repeatable job once you know the steps.

Step 1: upload the signed document

Start with the file as it already exists, whether that is a PDF export of a signed agreement, a scanned paper contract, or an Office document. PDF uploads are supported on every tier, including Free and Pro, which covers the great majority of already-signed contracts, since most get shared and stored as PDFs regardless of how they were drafted.

Word, Excel and PowerPoint uploads are available from the Business tier upward. If Fenwick had a contract still living as an editable Word file with tracked changes, that upload needs Business or Enterprise. A signed PDF export of the same contract would upload on any tier.

Step 2: tag the contract

Once uploaded, tag the contract with the details that make it findable later: the counterparty's name, the contract type, and any internal reference you use. This is the difference between a file sitting in a folder and a record you can actually search.

Fenwick tagged each of the eighteen by supplier name and category, supplier, landlord, software vendor, so a search for "software" or for a specific supplier's name would surface the right contract immediately, instead of requiring someone to remember which folder it sat in.

Step 3: set the key dates

This is the step most manual systems skip, or only do partially. A contract record should carry four separate dates, not one:

• Start date, when the current term began.
• Renewal date, if the contract renews on a specific date rather than automatically.
• Expiry date, when the current term ends.
• Notice deadline, the last day you can act to change the default outcome, if the contract requires notice.

These are four different fields because they answer four different questions. Confusing the expiry date with the notice deadline is exactly how teams end up locked into a contract they meant to leave, a pattern covered in full in what contract renewal management actually gets wrong.

Step 4: choose your reminder windows

Rather than accepting one fixed reminder schedule for every contract, set the window yourself, per contract. A short, low-value subscription might only need a two-week warning. A twelve-month supplier contract with ninety days' notice needs a much earlier one, ideally well before that ninety-day cutoff, so there is real time to decide, negotiate or find a replacement.

Fenwick set a forty-five-day reminder on most contracts, and a full one-hundred-and-twenty-day reminder on the two contracts with ninety-day notice clauses, giving the operations lead thirty clear days of margin after the alert before the real deadline closed.

Step 5: assign an owner

Every contract record should carry a named person responsible for it, not "the team" in general. This matters most when that person eventually leaves. Because the ownership sits on the document record rather than in one person's calendar or inbox, a departure means reassigning a field, not reconstructing the contract's history from scratch.

Step 6: share or re-sign from the same record

Once a contract is uploaded, tagged and dated, it behaves the same way as one drafted directly in the platform. It can be shared as a tracked, revocable link, gated behind an NDA if it contains sensitive terms, or sent back out for a fresh signature if it needs to be re-executed, all from the same record rather than a separate export. If the counterparty goes quiet after that fresh copy goes out, how to chase a signature without starting the whole process again covers the follow-up.

If the document needs updating before it goes out again, for example replacing an expiring supplier agreement with a fresh one, drafting a consultancy agreement with AI shows how a new contract can be assembled from vetted clauses and then dropped straight into the same tracked record.

Uploading in bulk rather than one at a time

Fenwick's eighteen contracts did not need eighteen separate sessions. Most of the work was uploading the files in one batch, then working through the tagging and dates in a single sitting while the details were fresh. That order matters more than it sounds.

Doing all eighteen uploads first, before any tagging, meant nobody was switching back and forth between finding a file and filling in a form. It also surfaced duplicates early. Two of Fenwick's eighteen turned out to be an older and a newer version of the same supplier agreement, something that would have been easy to miss if each contract had been processed as a one-off task spread across different weeks.

The same approach works for a much larger backlog. Upload everything you can find first, even if some records are incomplete. A contract sitting in the system with its file attached but no dates yet is still a far better starting point than a contract still buried in an inbox nobody has opened in a year.

What this looks like end to end

How does 99 Data Rooms handle uploads specifically?

Uploaded contracts sit in the same rooms as documents drafted through the template library, searchable and dated the same way. Signed documents keep their audit certificate, recording signer IP, intent to sign, timestamps and a SHA-256 fingerprint, whether they were signed inside the platform or uploaded after being signed elsewhere; see what an e-signature audit trail actually records for the detail.

Reminder windows are set per contract rather than on a single fixed company schedule, which matters most on the contracts with unusually long notice periods. For the reasoning behind why the notice deadline deserves its own field rather than being folded into the expiry date, see what contract renewal management gets wrong. Once every contract is uploaded and dated, how to get reminded before a contract expires covers how the alerts themselves behave, and how to keep track of all your contracts in one place covers the search and index layer sitting above the individual records.

Frequently asked questions

What file types can I upload?

PDF uploads work on every tier, including Free and Pro. Word, Excel and PowerPoint uploads are available from the Business tier upward.

Can I upload a contract that was never signed through 99 Data Rooms?

Yes. A contract signed on paper, through another e-signature tool, or by hand, can be uploaded and given the same key dates and reminder windows as anything drafted in the platform.

How many dates can one contract have?

Four separate fields: start date, renewal date, expiry date and notice deadline. Not every contract needs all four, but tracking them separately avoids confusing an expiry date with the earlier notice deadline that actually decides the outcome.

Can I choose my own reminder schedule?

Yes. Each contract's reminder window is set individually, so a contract with a long notice period can warn you far earlier than one with a short one.

What happens if the contract owner leaves the company?

The contract record, its dates and its reminder windows stay in place. Ownership can be reassigned to a new person without losing any of the history already attached to the document.

Does an uploaded contract keep an audit trail?

If it was signed through 99 Data Rooms, yes, in full. If it was signed elsewhere and then uploaded, the document itself is stored securely with its key dates, though the original signing record depends on whatever tool was used to sign it.

Bring your existing contracts into one dated, reminded record

Uploading what you already have takes an afternoon, not a rebuild. Tag it, date it, choose your reminder window, and assign an owner who will still be findable a year from now. The free tier includes three rooms and twenty-five active links, forever, with no card required. Start for free and stop relying on memory to catch a notice deadline.

Sources

• General guidance on contract repositories and metadata tagging: Chartered Institute of Procurement and Supply, "Contract Management", https://www.cips.org/intelligence-hub/contract-management
• UK Government Commercial Function standard on contract management (GFS008): https://www.gov.uk/government/publications/government-functional-standard-gfs-008-commercial