Guides
Part of Build compliance calendars from an obligation inventory
Why compliance calendars go stale, and the yearly fix that works
Compliance calendars go stale because the business changes, not the rules. The events that add or kill a row, and the yearly re-inventory hour.
The rules a business lives under change slowly. The list of obligations that business holds changes constantly, and nobody sends a notice about it. A calendar built accurately in one year is wrong by the next, not because anything was legislated, but because the business grew a service, moved a person, or signed something.
This page is about keeping the inventory current. Every deadline, fee and consequence belongs to the office that issued the obligation, and those offices have names: the city or county business license office, the state department of revenue behind a sales tax permit, the state licensing board behind a professional license, the Secretary of State that receives the annual report, and the IRS behind the employer identification number. What it gives is the list of events that add or kill rows in your compliance calendar, plus the smaller problem of a renewal whose own procedure changed without anybody being told.
What to take away
- Two things changewhat you hold, and how each thing is renewed. The first changes far more often and is entirely within your own knowledge.
- Operational events create obligations silently. The event list is short and worth pinning up.
- A row can also die, and dead rows left in a register are why people stop trusting it.
- Procedure changes at the issuing end are found by asking, on a schedule, not by being told.
The events that add rows
None of these announces itself as a compliance event, and every one of them can create something with a date attached. A new location can pull in a city business license and a sales tax permit for that state, a hire in another state can require a new withholding account there, and a new line of work can require a professional license from a state board.
Business events that add compliance rows
Event
- New service or process
- Permissions at any layer
- New material or equipment
- Handling, storage, inspection
- New location or move
- Local permissions, parcel questions
- New jurisdiction
- Registration and tax there
- First employee or new state
- Employment registrations, insurance
- New customer class or data
- Obligations scale with collection
- Entity, name, ownership change
- Filings, re-issues in old name
- Threshold crossed
- Scaled obligations and fees
What it can add
- New service or process
- New material or equipment
- New location or move
- New jurisdiction
- First employee or new state
- New customer class or data
- Entity, name, ownership change
- Threshold crossed
| Event | What it can add |
|---|---|
| A new service, product, or process | Permissions attached to the activity, at any layer |
| A new material, substance, or piece of equipment | Handling, storage, or inspection obligations |
| A new location, including a second site or a move | Local permissions, and a fresh set of questions about the parcel |
| Operating in a new jurisdiction | Registration and tax obligations in that place, separately |
| A first employee, or a first employee in a new state | Employment-related registrations and insurance |
| A new class of customer, or a new kind of data held | Obligations that scale with what you collect rather than what you sell |
| A change of legal entity, name, or ownership | Filings, and a re-issue of things held in the old name |
| Bringing a credentialled individual in or out | The firm's own position where its authority rests on theirs |
| Crossing a threshold in revenue, headcount, or floor area | Obligations and fees that scale, at whichever layer sets them |
| Signing a lease, a supply agreement, or platform terms | Notice and renewal dates, and obligations you accepted to hold |
Two of these stand out: a new location resets almost every local question, since authority follows the parcel, not the postal address. That reasoning appears in city and county licenses.
A credentialed individual leaving is an operational event with a very short fuse. A change of qualifying person requires the answer of the board that issued the license, asked before the last day, not after, as industry licenses sets out.
The events that kill rows
Registers grow and rarely shrink, and a register full of obligations that no longer exist is one nobody reads.
Closing a dead row properly
- Service discontinued
- Location closed
- Equipment gone
- Activity stopped
- Jurisdiction exited
- Agreement ended
- Close with date, reason, evidence
A service discontinued, a location closed, a piece of equipment gone, an activity stopped, a jurisdiction exited, an agreement ended. In each case the row does not simply get deleted. It gets closed, with a date, a note of why, and the evidence retained.
Some obligations have their own exit steps. Closing a location usually means telling the city or county that issued the business license, and stopping sales in a state usually means closing the sales tax permit with the department of revenue rather than letting it lapse. An obligation abandoned rather than closed can leave a filing running or a permission lapsing in a way that reads as a failure rather than a decision. The issuing office is the one to ask what closing looks like for that thing.
The other kind of change: how a renewal is done
The obligation stays the same and its administration moves. Portals get replaced, submission routes change, prerequisites are added, fee schedules are reset by a resolution nobody reads, and an office reorganizes into a different department.
Ask the issuing body each cycle
Is the submission route still as we have it?
record name and date
update the row and route
None of this reaches you reliably. Notices go to the address the agency holds, which is the mailing address on the license or the registered agent address the Secretary of State has on file, and that is why the address audit belongs in the same routine. The first sign of a changed process is often a renewal that does not work the way it did last year.
Ask, don't watch. Once a cycle, when the row comes up, the owner asks the issuing office two factual questions, whether that is the department of revenue, the licensing board, or the Secretary of State's business services desk. Record the answers with a name and a date.
Is the submission route still as we have it? Are the prerequisites still these? Two minutes on a call catches everything in this category.
The events that change a rule rather than your list
These are real and much rarer, and they are worth separating so they do not crowd out the work above. A legislature amends something, an agency adopts a rule, a local government adopts a new edition of an external code, a higher government moves the boundary of what a lower one may require.
You will usually hear about these from a counterparty rather than from a register. Turning a second-hand signal into an answerable question is the subject of business law basics.
Keep one habit: separate the adoption date from the effective date. The second is the one your calendar cares about, and reporting routinely collapses the two.
A re-inventory that takes an hour
Once a year, or after anything on the event list, do this in order.
The yearly re-inventory hour
- Read the business change log
- Scan bank and card statements
- Walk the register row by row
- Check ownership and access list
- Close dead rows, record the exercise
Read the business's own change log first: what did we start doing, stop doing, or move, and who joined or left. Operational change creates more new obligations for a small business than rule change does.
Then read the bank and card statements for the year, looking for payments to bodies that do not appear in the register, such as a state annual report filing, a sales tax permit renewal, or a licensing board fee. This finds what memory does not.
Then walk the register and ask, per row, whether it still describes what the business does, where, and who does it. The business entity search on the Secretary of State's site answers the entity-level version of that question in one page: still active, and who the registered agent is. Coverage drift is the failure that leaves a live permission attached to an operation that has moved.
Then check the ownership and access list against who actually works here now.
Then close the dead rows properly rather than deleting them, and record the whole exercise with a date, including "nothing changed" where that is the answer. The structure this all feeds is described in compliance calendars, and the cost of skipping the exercise shows up in the lapse patterns violations and renewals covers.
Where the answers come from
The body that issued an obligation answers every question about it: the city or county license office, the state department of revenue, the state licensing board, the Secretary of State, the IRS. The U.S. Small Business Administration's guidance on licenses, permits and staying legally compliant is a fair frame for the routine half, and its local Small Business Development Centers will walk the routine with you.
Reach a state's offices faster through USA.gov's state government directory than a search engine. If a change touches a contract, an insurance position, or the ability to trade, ask a lawyer early, while it is still hypothetical.
Common questions
How do we keep a change log without it becoming a chore?
One line per change, written when it happens, in whatever the business already uses. It only needs to say what changed and when. The reading of it is the scheduled part, not the writing.
Something changed a year ago and we never checked. What now?
Check now, and note the date the change actually happened rather than today. Offices ask when, and a straight answer with a date is a better position than a vague one.
Do we need to tell agencies when we change what we do?
Sometimes, and the requirement is theirs to state. That is a question for each issuing body about its own obligation, and it is one of the two questions worth asking on every renewal call.
Is a quarterly review better than annual?
Quarterly for the change log, annual for the full re-inventory. The event-triggered check matters more than either, because it happens when the risk is actually created.
