HR & OperationsContent Creator

Compliance tracker: a record of obligations, owners and dates

A compliance tracker lists the obligations your organization has identified, who owns each one, when it must be renewed or reviewed and where the evidence is kept. It records status; it does not decide which rules apply to you or prove that you meet them. Ask counsel, your regulator or a qualified adviser to confirm the list of obligations before you rely on the tracker.

Example excerpt

Sample rows for a small restaurant group

Sample section

Illustrative example. The business, obligations and dates below are fictional, and they do not show which rules apply to any real business. Obligation: Annual inspection of portable fire extinguishers (example entry) Owner (role): Facilities lead. Backup: general manager. Source: Inspection contract, and the local fire code reference listed under Reference materials. Evidence location: Shared records folder, subfolder 'Inspections 2026', dated inspection certificate. Last completed: 11 March 2026. Next due: 15 March 2027. Status: Current. Review note: Confirm the due date with the inspector when the contract renews. Obligation: Food-safety training records (example entry) Owner (role): Kitchen manager. Backup: head chef. Source: Local health permit conditions. The source has not been confirmed for this entry. Evidence location: Training log at each location. Last completed: Not recorded. Next due: Not set. Status: Needs confirmation. Action: Ask the health department whether the training requirement applies, and set a due date once the answer is known.

Section outline

Columns and sections that make each obligation checkable

  1. Obligation

    One sentence naming the duty, the place it applies and the rule that sets it.

    60 words
  2. Owner and backup

    A role rather than only a name, plus a second role for cover.

    60 words
  3. Due and review dates

    The next due date, the last completed date and the trigger for an earlier review.

    80 words
  4. Evidence location

    Where the certificate, log or report is kept and how a reviewer can find it.

    80 words
  5. Status and notes

    Current, due soon, overdue or needs confirmation, with the next action.

    100 words
  6. Reference materials

    Links to the rule, contract or permit that sets each obligation.

    80 words
  7. Review of the tracker

    Who checks the tracker, how often, and who receives the summary.

    60 words

Total: 520 words

Quality checklist

Check that the tracker can answer a real question

  • Each row names one obligation, so a single status can be given for it.
  • Every row has an owner role and a backup role.
  • The next due date is a real date, or the row says the date needs confirming.
  • A reviewer can open the evidence without asking the owner where it is.
  • The source of each obligation is listed, so someone can check it later.
  • Overdue rows are reviewed on a set schedule, not only when someone remembers.
  • The tracker holds status and dates, not copies of personal records or sensitive details about employees or customers.
  • The page states who last reviewed the list of obligations and when.
Mistakes to avoid

Mistakes that make a tracker look complete when it is not

Tracking the status, not the duty

A green status on a row with no source or evidence says little. Link each row to the rule and to the evidence the owner keeps.

Assuming the list is complete

A tracker covers only the obligations someone wrote down. Review the list with counsel or your regulator when operations change, such as a new location, product or hiring practice.

Storing sensitive records in the tracker

A tracker that holds health details, identification numbers or bank data creates a risk of its own. Store the evidence where access is controlled, and keep only a reference in the tracker.

Leaving the due date blank

A row without a due date will never turn overdue. If the date is unknown, write needs confirmation and give someone the job of finding it.

Frequently asked questions

What should a compliance tracker include?

At minimum: the obligation, its source, an owner and a backup, the next due date, where the evidence is kept and a status. Add a review note when the requirement changes. Keep the list short enough that someone reads every row each month.

Is a compliance tracker the same as a compliance program?

No. A tracker records obligations and their status. A compliance program also covers how you identify obligations, train people, handle problems and review the whole system. A tracker can support a program, but it does not replace one, and whether you need a formal program depends on your industry.

Can a spreadsheet work as a compliance tracker?

Yes, for a short list. A spreadsheet is easy to filter, but it needs a clear owner, protected date columns and a rule for who updates it. When the list grows, set a fixed review schedule so overdue rows get attention before an audit or inspection finds them.

Should the compliance tracker be shared publicly?

Almost never. A tracker can reveal gaps and personal details. Share it through a team link meant only for the people who maintain or review it, and publish only summaries written for outside readers.

Browse by category

More reports in HR & Operations

How to build it

  1. Follow the eight-step wizard: type, assets and description, images, branding, contact and call to action, Atty Suggestions, blueprint, and generate. Atty generates one HTML page in the background. Review it, then publish and share the page link or download the HTML file.

Attain OS BETA