Platform module

Renewals & Vendor Register

A renewal register is where governance risk becomes manageable: every vendor, SaaS tool, license, contract, domain, and certificate gets an owner, a renewal date, and enough context to make a decision before something lapses or renews unnoticed.

Why renewals become governance risk

Renewal risk is rarely only about money. It is about service continuity, client trust, handover, and whether the team can prove that someone reviewed the decision in time.

Silent lapse

A domain, certificate, vendor contract, or key SaaS tool expires because the renewal date lived in one person's inbox.

Unplanned renewal

A contract auto-renews before the team reviews ownership, cost, or whether the tool is still needed.

No accountable owner

A renewal exists, but nobody is named as the person responsible for making a decision before the due date.

What the register tracks

CertPilot is not trying to be a full procurement system. It keeps the fields that make renewal governance practical: what is renewing, when it renews, who owns it, and what needs action.

SaaS tools and software subscriptions
Vendors, contracts, and hosting plans
Licenses, plugins, certificates, and domains
Owners, billing contacts, renewal dates, costs, and notes
Review state: overdue, upcoming, renewed, or incomplete

CSV in, CSV out

Most teams already have a renewal spreadsheet. CertPilot supports CSV import so the first register can start from that file, and CSV export so the data remains portable.

The goal is not to trap data in a dashboard. The goal is to make the register reliable enough to feed a report without rebuilding the spreadsheet every month.

Spreadsheet vs maintained register

Spreadsheet

Flexible, but easy to fork, forget, and leave owner fields blank. It usually does not produce a report without manual cleanup.

Maintained register

Structured fields, owner visibility, overdue/upcoming views, CSV import/export, and report output from the same records.

How Renewal Risk reports use this data

The Renewal Risk Report turns register records into a plain-English view of overdue, upcoming, and incomplete renewals. Monthly Proof and on-demand Weekly Governance reports can summarize renewal risk alongside domain health and access-review counts.

Sample report

The public sample uses fictional data, but it shows the same report structure used by the live Renewal Risk report.

View Renewal Risk sample

Renewal register FAQ

What is a renewals and vendor register?

It is a structured record of tools, vendors, contracts, licenses, domains, certificates, owners, costs, and renewal dates so renewals do not live only in inboxes or spreadsheets.

Why do renewals become governance risk?

Renewals become governance risk when nobody can show what is due, who owns the decision, what it costs, or whether it was reviewed before lapse or auto-renewal.

Can I import an existing renewal spreadsheet?

Yes. CertPilot supports CSV import and export for renewal records, so teams can start from the spreadsheet they already maintain and keep a portable copy.

Does CertPilot detect unused licenses?

No. License waste detection is not live. The register tracks renewal records and risk; it does not connect to SaaS admin systems or measure usage.

What report uses renewal register data?

Renewal records feed the Renewal Risk Report, Monthly Proof Report, and on-demand Weekly Governance Report.

Is this only for domain renewals?

No. Domains and certificates can be tracked, but the register is broader: SaaS tools, hosting, contracts, licenses, vendors, and other renewal-backed records.