Compliance calendars policy template: what belongs in each section

A calendar is a list of dates. A policy is what makes the list true a year from now. This page is the second thing: a one-page internal document saying who owns the register, what puts a row into it, what has to happen before a row can be closed, and what triggers a review of the whole thing.

Fill in the brackets. Nothing here states what any authority requires, sets a deadline, or says what a lapse costs. Those answers belong to the offices that issued your obligations, they differ by place and by license type, and a lawyer settles anything where a contract or the ability to trade turns on it.

What to take away

The page

What the register covers

Every obligation with a date attached, at every level of government, plus every private agreement carrying a renewal or notice date. Concretely: entity filings, tax registrations, licenses and permits held by the business, credentials held by individuals whose work the business depends on, insurance policies and bonds, inspections, and agreements including leases, supplier terms, and software terms accepted by clicking.

If it can expire, lapse, renew automatically, or fall due, it is in scope. Notice deadlines inside agreements are in scope too, for the same reason as a license expiry: they are dates on which somebody has to act. The frame for reading the documents they come from is contracts and liability.

Who owns what

[Role] owns the register itself: its structure, its completeness, and the review. Each row has a named owner who is responsible for that obligation being met and its evidence filed. Ownership is a person, never a department, and it transfers explicitly, in writing, with the leaving person confirming what they handed over.

[Role] holds the ownership map: who owns which rows, who can access which portal, and who covers each owner in their absence. Portal accounts frequently belong to individuals rather than to the business, which makes this list load-bearing rather than administrative.

What creates a row

Three events, and each has an owner obliged to act within [period].

Acquiring anything with an expiry: a license, a registration, a policy, a bond, a certification. Signing anything with a date in it, at which point the dates are extracted the same day. And changing what the business does, where it does it, or who does it, which is the event that creates obligations nobody was told about.

The third one is the one that gets missed. The list of changes that should trigger a check is in compliance calendars, and it is short enough to keep beside this page.

What a row must contain before it counts

A row missing the prerequisite field or the evidence path is incomplete, and incomplete rows are the ones that fail.

What closing a row requires

Not a tick. The owner records the date submitted, the confirmation reference, the new expiry, and the location of the new certificate. Then the next cycle's dates are set from the new expiry rather than from the old ones.

Where something was paid automatically, the owner confirms the payment landed rather than assuming it. Silent payment failure is common and generates no alarm at your end.

Asking the issuing office

Once per obligation, and again after any change in how it is administered, the owner asks the issuing body two factual questions. Record the answer with a name and a date. The questions: what the current submission route and prerequisites are, and what happens if the renewal is late.

The second answer determines how much lead time this row needs. It is knowable only from them, which is the argument violations and renewals makes for asking before you need to know.

Contact details

[Role] audits, at least annually, which postal address, email address, and contact person each agency holds for the business, and corrects them individually. Agencies do not share updates. The register assumes notices will not arrive.

The review

On [date] each year and after any trigger list change, [role] and one other person walk the whole register and ask five questions.

Is anything held that is not on the list, and does each row still describe what the business does, where, and who? Did every autopay in the year actually succeed, and does each owner still exist and know they are the owner? Has any issuing office changed its process since we last asked?

"Nothing changed" is a valid outcome and is recorded with the date. An unrecorded review did not happen.

Making it survive contact with a real business

Two failure modes are worth naming in the document itself.

The first is a register that only its author can use. The test is not whether it looks complete but whether a second person can complete one real renewal from what is written, and that test is worth running once a year on a randomly chosen row.

The second is a policy that describes an ideal. If in practice one person does everything, either the page says so and names the cover arrangement, or the practice changes. A policy the business quietly ignores records that somebody knew what should have happened, which is worse than not having written it.

What this page does not do

It states no requirement, no deadline, and no consequence. It does not tell you which permissions you need, which is a separate exercise across the layers described in license fundamentals, and it does not interpret a contract clause, which is a legal question.

For the routine half of the work the federal guidance on staying legally compliant is a fair frame. The route to a particular state's own offices is quicker through an index of official state government sites than through a search engine.

Common questions

Is a policy overkill for a business with four obligations?

At four obligations it is half a page and takes twenty minutes. Its value is not proportional to the number of rows; it is proportional to how badly it would go if the person holding them all were unavailable.

Who should hold the register if there is no administrator?

Whoever will actually open it on a schedule. Ownership by the busiest person in the business is the most common reason a register goes stale.

Should the register record what a rule requires?

No. Record what the office told you, with the name and the date. A requirement written into your own document reads as a fact and goes stale silently; a dated answer from a named person reads as what it is.

What happens if the review finds something that lapsed months ago?

You have found it before somebody else did. Ask the issuing office what its process is now, and stop anything that makes it worse. Where a contract, an insurance position, or the right to be paid for completed work could be affected, take that part to a lawyer with the dates in hand.