Running a contract register across multiple sites without losing track

Most cleaning contractors start with a workable, informal way of tracking their contracts — a spreadsheet, a shared folder, a manager who simply knows the details of each site. That approach genuinely works for a handful of contracts. Somewhere around the tenth or twelfth site, with different specifications, different renewal dates and different points of contact, it starts to quietly break down, usually before anyone notices.

What a contract register actually needs to hold

At minimum, a usable register needs the scope and specification for each site, the renewal or break clause date, the client contact, and any site-specific requirements that vary from the contractor's standard practice — a particular consumable brand, a specific access arrangement, an unusual reporting cadence the client insists on. The value isn't in any single field; it's in being able to see all of this for any given site in seconds, rather than reconstructing it from memory or old emails.

Where spreadsheets genuinely start to fail

A spreadsheet isn't inherently the wrong tool — plenty of contractors run a reasonable-sized operation on one for years. What it struggles with is scale and cross-referencing: flagging every renewal date coming up in the next quarter across dozens of tabs, or checking which sites share a particular specification requirement, tends to mean manually opening and scanning each one. That's a workable habit for six sites and a genuinely risky one for thirty, because it depends entirely on someone remembering to do the manual check regularly.

• –Keep specification, renewal date and key contact together per site, not spread across separate documents
• –Make renewal dates visible at a glance across the whole portfolio, not something that requires opening each record individually
• –Record site-specific deviations from standard practice explicitly, rather than relying on a supervisor's memory
• –Review the register at a fixed interval, not only when a renewal or issue forces attention to a specific site
• –Keep it accessible to whoever needs it — a register only one person can open isn't much better than no register during that person's absence

Renewal dates are where the risk concentrates

Of everything a contract register tracks, renewal and break clause dates tend to be the highest-consequence field — a missed notice period can mean losing a contract by default rather than by any commercial decision. A register that surfaces these automatically, well ahead of the date, removes one of the more avoidable ways a contractor can lose business.

Connecting the register to day-to-day operations

A register that sits separate from actual day-to-day operations — schedules, staffing, site visits — tends to drift out of date quietly, because nobody's routine work touches it. It holds up better when it's the same place staff and supervisors already work from for shift patterns and site information, rather than a compliance document maintained separately and updated only when someone remembers.

The month the register stops working

Spreadsheets hold up surprisingly well to around twenty or thirty sites. What breaks them is not row count but concurrency and memory: two people editing different copies, a renewal date that only one person knows is wrong, a column whose meaning depends on knowing why it was added. The register does not fail visibly — it develops quiet inaccuracies that nobody can date.

The practical signal is when somebody asks a simple portfolio-wide question — which contracts expire in the next six months, which sites have a supervisor vacancy — and the answer requires an afternoon and a phone call. At that point the register has stopped being a source of truth and become a filing artefact.

Common mistakes

• –Multiple copies in circulation with no agreed master
• –Holding renewal dates without notice periods, which is the date that actually matters
• –Columns whose meaning lives in one person's head
• –Updating the register on contract signature and never again
• –No link between the register and the operational data that shows how the contract is performing
• –Discovering an error only when a renewal is missed