Contract renewal reminders and the files it handles | DocHive

What it handles

Contracts, policies, HR files, invoices, and the dates buried in them

Five kinds of document, and the fields that decide where each one belongs. If you recognise your own situation further down the page, that is the signal.

Document types

What gets read out of each one.

Contracts

Suppliers, maintenance, leases, licences, works agreements. The notice period is the field that pays for the product.

Filed as 2026-07-20_AcmeCorp_Contract_Maintenance.pdf

  • PartiesBoth sides
  • TermStart and end
  • Notice periodWith the clause
  • ValueAnnual or total

Insurance policies

Liability, property, business interruption, vehicles, group accident. Renewal dates cluster around the year end, which is exactly when nobody has time.

Filed as 2026-01-01_Helvetia_Policy_Liability.pdf

  • InsurerAnd policy no.
  • CoverWhat and how much
  • RenewalAnd notice date
  • PremiumPer period

HR files

Employment contracts, amendments, certificates, sick notes, references. Filed into the folder for that employee, under the access rights that folder already has.

Filed as 2026-04-01_Keller-M_Employment_Amendment.pdf

  • EmployeeMatched to file
  • CategoryContract, cert, note
  • RetentionClass and clock
  • Effective dateFrom when

Invoices

Purchase invoices waiting on approval, and the ones you sent that a client asks about six months later. Matched to the vendor and the amount, not just the file date.

Filed as 2026-06-18_SwisscomAG_Invoice_4471.pdf

  • VendorMatched by name
  • Invoice numberRead from the header
  • AmountAnd currency
  • Due dateWatched like a deadline

Quotes and cost calculations

The place where versions go wrong. Which calculation was the one you sent, and which one did the client actually sign? Version and author come out of the document, not out of memory.

Filed as 2026-05-02_Kunz_Quote_Halle-B_v3.pdf

  • ProjectAnd client
  • VersionOrdered, not guessed
  • AuthorWho prepared it
  • TotalAnd validity date

See how a proposal is built from these fields

When companies call us

If one of these is on your desk this quarter.

Nobody wakes up wanting to improve their filing. Something forces the question, and it is usually one of these four.

A due diligence

A buyer or a bank asks for every supplier agreement with a term over one year. Assembling that list by hand is the moment most people decide something has to change.

An audit

Two years of documents, requested in a week, spread across a drive, three mailboxes and someone's desktop. The work is finding them, not producing them.

A renewal that slipped

The contract rolled over for another year because the notice period ran out quietly. Usually the cost of that one miss is larger than a year of DocHive.

A key person leaving

The filing logic lived in one head, and that head is going. Rules written down and applied consistently are the difference between a handover and an excavation.

If none of these apply, there is a fair chance you do not need this yet. We will say so on the call.

Book a 20 minute call →

The fair question

Why not just SharePoint?

Because storing is a different job from reading. SharePoint keeps what you put in it, under the name you gave it, in the folder you chose. It does not know the notice period is three months, and it will not tell you in September.

Metadata columns can carry that, if someone fills them in on every document, for years. That is the part that stops happening around month four.

DocHive does not replace it. SharePoint stays where it is. DocHive reads the new document, proposes the name, moves it through the official API and watches the date. A good structure in SharePoint is an advantage, there is something to file into.

How to structure contracts in SharePoint Read the FAQ