Universities Sign Vendor Contracts in Every Department and Track Them in None

A university's vendor relationships do not belong to a single function. They are spread across at least six distinct procurement centres, each operating with its own authority and its own filing system.

Central IT

Student information systems, learning management systems, HR and payroll platforms, enterprise identity management, cybersecurity tooling, cloud infrastructure. These are typically the best-tracked contracts in the institution, simply because IT has the most developed vendor management practice.

The library

Journal subscriptions, database licences, e-resource platform agreements, interlibrary loan systems, archival access licences, discovery layers. The library's vendor list alone can run to hundreds of agreements. Publishers like Elsevier, Springer, and Wiley hold multi-year big-deal agreements that auto-renew unless the library serves notice - sometimes with lead times of 120 days or more.

Research groups and principal investigators

Every grant-funded research group runs its own software stack. Statistical packages, specialist analysis tools, data storage, participant survey platforms, domain-specific databases. The licences are purchased against grant budget lines with hard end dates tied to the funding period. When the grant ends, the software either gets renewed from another budget (if the research group is still active) or lapses (if it is not) - and central procurement usually finds out neither way.

Estates and facilities

Building maintenance contracts, cleaning and security, waste management, energy supply, catering. Facilities contracts often have the longest notice windows - 90 days is common, 180 days is not unheard of for large service agreements. They are also the contracts most likely to have been signed under a previous facilities director and never properly recorded in a central system.

Student services

Mental health and counselling platforms, disability support tools, careers software, accommodation management, student union agreements, sports facility management. These are predominantly signed by service heads who have significant operational autonomy and limited interaction with central procurement.

Faculty and departmental

Each academic department has its own software subscriptions, professional memberships, specialist datasets, and conference management tools. The Computer Science department and the Law faculty and the Business School all have vendor relationships that central procurement has never seen.

Central procurement exists at most mid-size and large universities. It has a mandate to manage vendor relationships. In practice, it manages the contracts that were signed through it. That is typically 20-40% of the actual vendor portfolio.

The rest of the portfolio was signed under delegated authority. Academic freedom and departmental autonomy are legally and culturally entrenched in higher education governance. The head of a research group who holds a £500,000 EPSRC grant has the authority to spend that grant budget on software without routing every purchase through central procurement. The library director who manages a multi-million-pound journal budget has specialist knowledge that general procurement cannot replicate. Estates directors have operational relationships with service contractors that predate the current procurement function by decades.

The result is not a failure of governance - it is a predictable consequence of how universities are structured. The problem is that devolved signing authority does not come with devolved renewal tracking. Departments sign contracts and then forget about them until the invoice arrives - or until the vendor sends a renewal notice to an email address that no longer exists.

Research software licences funded against grant budgets have a structural characteristic that makes them particularly prone to mismanagement: their end date is not a renewal decision. It is the grant closure date.

When a research council grant ends on 31 March, the software licences purchased against it should end on the same date. In practice, what happens is one of three things:

• The software vendor auto-renews the licence and invoices the department, which then scrambles to find a budget line to pay from or disputes the charge.
• The licence lapses on the grant end date, but the research group continues using the tool for months on an expired licence because nobody flagged the cessation.
• A successor grant is in progress, the software is needed, but nobody has thought to transfer the licence in time - so the new grant starts with a gap in tooling.

All three outcomes are avoidable. All three require knowing that the licence exists, knowing its end date, and knowing the date of the associated grant closure. That information sits in three different systems - the vendor contract, the finance system's grant ledger, and the research office's project register - and is almost never joined up.

Academic publishers have spent decades optimising their renewal terms. The big-deal journal bundle - a multi-year agreement covering a publisher's entire catalogue at a negotiated price - is the primary vehicle. Those agreements typically auto-renew unless the library serves written notice 90-120 days before the end of the current term.

The leverage is structural. A library that fails to serve notice in time has two options: accept the auto-renewal on the existing terms, or cancel and lose access to journals that researchers are actively citing. For most universities, losing access to Elsevier or Springer mid-term is not a viable operational outcome. The publishers know this.

The result is that universities disproportionately miss library subscription notice windows, because the consequences of missing them are serious enough to make the auto-renewal feel unavoidable. Libraries that do manage to serve notice and renegotiate report saving 15-30% on big-deal renewals. The ones that auto-renew every year because they missed the window pay the publisher's standard escalation - typically 3-5% annually on an already large base.

For a university with a £3-5 million annual journal spend, a missed notice window that prevents renegotiation costs six figures in forgone savings on that single contract alone.

Universities operate on an academic calendar that creates predictable blackout periods for renewal management. The summer break, in particular, is a procurement dead zone. University administrators take leave, departments are at reduced capacity, and the staff member who owns the vendor relationship may be completely unavailable.

Contracts whose notice windows open in June or July are at extremely high risk of lapsing unnoticed. The window opens, nobody flags it, the academic year restarts in September, and the vendor's invoice for the new year has already been processed.

The same dynamic applies at term boundaries. November is exam season for many programmes. December is the Christmas closure. January is a compressed re-entry. A notice window that opens in any of these periods is likely to miss the one person who holds the renewal decision authority.

This is not unique to universities - any organisation with predictable peak-load periods has a calendar reminder problem at those moments. What makes universities distinctive is the duration and regularity of their low-capacity windows. Summer break runs 8-12 weeks. That is long enough for a 90-day notice window to open and close entirely.

The solution is not to centralise procurement authority. That conversation has been tried at most universities and has consistently failed to get past the governance layer. Academic departments will not cede signing authority, and they should not have to. The goal is visibility, not control.

A visibility-only register works on a different principle: departments keep their signing authority, but every signed contract gets logged in a shared system, regardless of who signed it. The mechanics:

1. Start with the finance system. Every vendor payment leaves a trace. A one-time export of vendor names and payment frequency from accounts payable is the fastest way to build a draft inventory. It will not capture contracts with no recent payment, but it gets you 60-70% of the active portfolio in a week.
2. Add the library separately. Library subscriptions are typically well-documented within the library's own systems but not visible to central procurement. One meeting with the head of e-resources will produce a complete list. The library is highly motivated to have its renewal windows tracked - they bear the consequences of missing them most directly.
3. Contact research finance. The research office holds the grant portfolio. Most grants have associated software purchases. A query against the grant ledger for software spend in the past three years will surface the grant-funded vendor relationships.
4. Circulate to departmental administrators. A short survey to the administrator for each faculty, asking for any vendor contracts they manage directly, will pick up the remainder. Departmental admins know what they pay for even when central procurement does not.
5. Upload contracts to a central register. Once collected, each contract goes into a single system where notice deadlines are tracked forward, not just noted and filed.

This process takes 4-6 weeks for a mid-size university. It requires no change to procurement authority and no political fight with faculties. It just requires someone with the mandate to run it.

Renewly is a vendor contract register built for organisations with devolved procurement and a large, fragmented contract portfolio. Upload your contracts - from any department, in any format. Renewly extracts the vendor name, contract value, category, and notice deadline. Every renewal across every faculty and function appears in a single forward calendar, sorted by notice window. Alerts fire before the critical dates, not after.

Free for up to five vendor contracts.