Blog

Compliance Register Spreadsheet: Owners, Evidence and Renewals

Structure a compliance register spreadsheet to track obligations, accountable owners, evidence, review dates, renewals and sign-off, with guidance on when a managed upgrade may help.

By Spreadsheet Upgrade 11 min read Published 6 Oct 2026

A compliance register spreadsheet gives your team one place to track obligations, accountable owners, evidence, review dates and sign-off status. It can be a useful operational tool for a growing business when it is designed for ongoing review rather than treated as a list completed only before an audit.

The aim is not to put every policy, certificate and requirement into one oversized workbook. It is to make clear what applies, who owns it, what action is required, where the evidence sits and when the next review is due.

Excel is often a sensible starting point. It is flexible, familiar and useful for filtering, reviewing dates and producing ad hoc reports. It can become harder to manage when several people need to update records, approvals need separation from updates, evidence accumulates, or missed renewals create operational risk.

What a compliance register spreadsheet should do

A useful register helps an operations or compliance lead answer practical questions quickly:

  • Which obligations apply to the business, site or process?
  • Who is accountable for each requirement?
  • What control or recurring activity supports compliance?
  • Where is the current evidence stored?
  • Which reviews, renewals or actions are approaching?
  • Which items are overdue, awaiting approval or subject to an exception?
  • What changed when a requirement, owner or control was reviewed?

This is different from a risk assessment spreadsheet. A risk assessment identifies and evaluates risks. A compliance register manages the lifecycle of obligations, controls, evidence and renewals.

It is also related to, but distinct from, an audit trail. An audit trail concerns the history of changes and decisions. A compliance register needs that history where appropriate, but its main job is to manage each obligation from applicability through review, evidence and renewal. Read more about the separate record-history problem in this Excel audit trail guide.

Start with one row per obligation

Each register row should represent one obligation that can be assessed, assigned, reviewed and evidenced. Avoid combining unrelated requirements in one row simply because they sit under the same policy or regulatory heading.

For example, a row for a certificate renewal, a row for a periodic control review and a row for a staff-training requirement may all relate to the same business area, but they can have different owners, dates and evidence.

Use a stable identifier for every obligation, such as COMP-001. That identifier should not change when the owner, status or next review date changes.

Suggested compliance register columns

Field group Column Purpose
Reference Requirement ID A stable identifier for the obligation
Reference Requirement title A short, clear description of the obligation
Reference Source Legislation, regulation, contract, customer requirement, policy or standard
Applicability Applies to Business entity, site, team, process or jurisdiction covered
Applicability Applicability rationale Why the obligation applies, or why it does not apply
Accountability Accountable owner Named person responsible for the outcome
Accountability Supporting team Team or role that carries out the work
Control Control or activity What the business does to meet the requirement
Evidence Evidence location Link or controlled location for the supporting record
Evidence Evidence period The period, version or date covered by the evidence
Review Review frequency Monthly, quarterly, annual or event-driven
Review Last review date Date the record or control was last reviewed
Review Next review date The next required review or renewal date
Workflow Status A controlled status such as active, in review, overdue, exception or not applicable
Approval Sign-off status Pending, approved, rejected or not required
Approval Approver Person responsible for approving the outcome where needed
Exception Exception detail Reason, action owner and review date for an agreed exception
Notes Change notes Short explanation of a material update or decision

Use an Excel Table rather than a loose range of cells. Tables make it easier to filter, add records, apply consistent formats and extend formulas without accidentally excluding new rows from a report.

Separate status from evidence

A status value is a conclusion. Evidence is what allows another person to check that conclusion.

A row marked as complete should not be the end of the record. It should point to the document, report, certificate, meeting record, approval or other source that supports the status.

Where the register covers several kinds of obligation, add columns that make evidence easier to interpret:

  • Evidence type
  • Evidence owner
  • Evidence date
  • Evidence expiry date
  • Evidence link or document reference
  • Reviewer comments

This avoids a common problem in shared workbooks: a free-text notes field containing several filenames, folders and informal comments that nobody can reliably interpret later.

It is also useful to separate obligation status from control effectiveness. An annual review may have been completed on time, while that review identified a weakness that still needs action. If both conclusions are combined into one status column, a completed review can hide an unresolved issue.

Use validation before building reports

Reports are only useful when the underlying data is consistent. Set allowed values for fields such as status, review frequency, priority and sign-off before creating dashboards or summary formulas.

For example, choose one controlled list for status rather than allowing variations such as “Done”, “Closed”, “Complete” and “Finished”.

Useful Excel controls include:

  • Dropdown lists for status, review frequency and sign-off state
  • Date validation for review and renewal fields
  • Protected formula cells
  • Clear input cells for users to update
  • Conditional formatting for overdue and upcoming reviews
  • Filters by owner, business area, status and next review date

Conditional formatting can highlight records that need attention, but it should not be the only reminder mechanism. Someone still needs responsibility for reviewing the register and acting on overdue items.

Build an audit-week view without rebuilding the workbook

A register should be useful throughout the year, not only when an audit, customer review or renewal deadline is close.

Create filtered views or pivot summaries for questions your team expects to answer regularly:

  • Obligations due for review
  • Items with missing evidence
  • Records awaiting approval
  • Open exceptions
  • Requirements by accountable owner
  • Requirements by site, business unit or jurisdiction
  • Expired certificates or upcoming renewals

Keep the detailed register as the source of truth. Use a separate reporting sheet for summaries rather than asking users to edit records through a dashboard.

A simple audit-week checklist can help:

  1. Filter for overdue and upcoming review dates.
  2. Check that each active row has a current owner.
  3. Check that evidence links open and point to the right record.
  4. Review items marked as exceptions or awaiting approval.
  5. Confirm that key changes have an explanation and decision record.
  6. Export or save a controlled copy if your internal process requires one.

Record ownership changes and regulatory updates

A register becomes unreliable when it silently preserves old ownership. If someone changes role or leaves the business, their obligations need a visible handover rather than an unrecorded name change.

Use a controlled owner list where possible, and review ownership during regular register reviews. For important obligations, record:

  • Previous owner
  • New owner
  • Handover date
  • Open actions
  • Evidence or notes confirming the handover

Regulatory, contractual and policy changes also need more than a new row added to the bottom of a sheet. Record what changed, which obligations are affected, who assessed the impact and what action was agreed.

A practical change log can include:

Change field Purpose
Change reference Identifier for the change record
Date identified When the change was recorded
Source update The relevant update, notice or internal change
Affected obligations Requirement IDs affected by the change
Impact assessment What the business considered and why
Decision No action, revised control, new action or exception
Action owner Person responsible for the follow-up
Target date When the agreed action should be reviewed
Approval record Who accepted the decision where approval is needed

Do not overwrite historic wording where it matters to explain a past decision. Preserve the earlier version or record the change separately, particularly where the register supports a controlled or regulated process.

UK GDPR and data-protection records

A compliance register may include data-protection obligations, but it is not automatically the same thing as a record of processing activities. Whether particular UK GDPR documentation duties apply depends on the organisation, its processing activities and the circumstances involved.

For UK businesses, use the Information Commissioner's Office as a starting point for current guidance on UK GDPR accountability and documentation. The ICO's guidance on documentation can help you identify the records relevant to your situation.

This article is about structuring an operational register, not legal interpretation. Where an obligation depends on legislation, regulation or contractual terms, record the source clearly and seek appropriate professional advice where needed.

Where Excel can become difficult to control

Excel remains well suited to modelling, forecasting, flexible calculations and exploratory work. It can also support a small, well-governed register.

The issue is not simply workbook size, company size or user count. A small register can still be business-critical if it controls licence dates, customer commitments, safety documentation, required approvals or evidence that the business may need to produce later.

Consider whether the workbook is starting to show these signs:

  • Several people need to edit records at the same time.
  • Owners need reminders or escalations without manual chasing.
  • An owner must not be able to approve their own work.
  • Each obligation has several evidence documents or review comments.
  • Users struggle to find the current version of a supporting record.
  • Staff changes leave unclear ownership.
  • Important dates rely on formulas that only one person understands.
  • The team must reconstruct history from emails, comments and saved copies.
  • Reporting requires manual consolidation before management reviews.

These are process-design signals, not proof that Excel has failed. In some cases, better register structure, validation and ownership discipline will be enough. In others, the workflow has become too dependent on manual coordination.

When a managed compliance application may be a better fit

A managed custom web application can be appropriate when the compliance register is no longer just a reference workbook and has become a repeatable operating process.

Instead of asking users to navigate a large grid of cells, a purpose-built workflow can present the tasks and fields relevant to their role. It can support structured submissions, role-based access, approvals, evidence records, review queues and controlled reporting.

For a compliance register, that may mean:

  • Individual user access rather than a broadly shared workbook
  • Guided forms for new obligations and updates
  • Controlled status transitions
  • Separate owner and approver actions
  • Central evidence links and document references
  • Task lists for upcoming reviews and renewals
  • A clearer history of workflow events and decisions
  • Reporting by owner, location, status or review period

The point is not to replace every spreadsheet. It is to move a business-critical workflow into a more controlled environment when spreadsheet governance is becoming difficult to sustain.

A practical next step

Review one live area of the register rather than redesigning everything at once. Choose a group of obligations with recurring reviews, several owners or frequent evidence updates. Check whether every row has a clear owner, current evidence, a next review date and a usable status.

If the workbook is becoming difficult to maintain, hand over or audit, a Free Fit Check can help you consider whether the current process needs better spreadsheet controls or a managed application designed around the workflow.

Start a Free Fit Check

Ready to look at your own process?

Start with a £295 Spreadsheet Assessment

We review the spreadsheet and the work around it, then define what should stay in Excel, what should change and what a sensible first app release would include.

Book the assessment

A human development team is included

You bring the workflow. We handle the software.

Your plan includes people who learn how your business works, design and build the app, check the important details and support it after launch. You are not left to configure a builder or make technical decisions alone.

You are buying a finished app, not a software-building tool

We agree the calculations, access, wording and workflow with you, then take responsibility for turning that into working software.

Human-led delivery Custom to your workflow Support after launch

Your development team

We turn your spreadsheet process into a real app. You explain the work; we handle the design, build and technical choices.

Built around the real process

Screens, calculations, approvals and terminology are shaped around how your business actually works, not forced into a generic template.

Checked before people rely on it

Important rules, access and workflows are reviewed with you and tested before launch instead of assuming a generated first pass is correct.

The same team stays with you

Managed plans include hosting, backups, maintenance, security fixes and ongoing support from people who understand the app they built.

Your spreadsheet, your workflow

Get a clear plan before committing to a build

The £295 Spreadsheet Assessment is the planning step. We review how the file is used, the people and hand-offs around it, the important rules and data, and the practical options for replacing or improving the process.

If you go ahead with a build, the full assessment price is credited before VAT.