Compliance tracker for a small firm: one owner, one renew-by date and a weekly Slack check for every license, certificate and policy

A working compliance tracker for a small firm is one sheet with a row for every license, permit, insurance policy and certificate, a named owner on each row, and a renew-by date, which is the expiry date minus the days the renewal takes. The ExpiryEdge template calculates exactly that and defaults the lead time to 30 days. Then a weekly check in Slack reads the dates and posts what is late, due soon or ownerless.
The failure this prevents is quiet. PermitDue puts a late fee at 10% to 50% of the license fee in most cities (a vendor figure), and says an expired license can bring an order to stop operating and that the insurer may deny a claim made while it is lapsed. A firm of 10 to 60 people usually finds a lapse when the issuer, the insurer or a client says so. The payoff of the setup below is that you find it on a Monday, with weeks left, instead.
What does a compliance tracker for a small firm need?
It needs ten columns and one rule. Every row has a person's name and a date, or it is a problem. The SBA notes that some licenses and permits expire after a set period and advises keeping close track of renewals, because renewing is often easier than applying again. It says nothing about how.
Keep the sheet in Google Sheets, one row per item:
| Column | What goes in it | Why it is there |
|---|---|---|
| Item | "General liability policy", "State contractor license", "Food handler certificate, J. Rivera" | One row per thing that can lapse |
| Type | License, permit, insurance policy or certificate | Lets you set lead times by type |
| Issuer | The agency, insurer or training body | Tells the owner who to call |
| Owner | One named person | The row that has no owner is the row that lapses |
| Manager | Who decides when the owner is silent | Needed for the escalation step below |
| Expiry date | The date printed on the document | Everything else is calculated from it |
| Lead time (days) | How long renewal takes | Forms, inspections, fees and broker processing all take time |
| Renew-by date | Expiry date minus lead time, as a formula | The date the check actually watches |
| Document link | The certificate or policy in Drive | So nobody searches email at 5 pm |
| Status | A short note, such as "filed 3 Nov" | For humans only, never read by the check |
ExpiryEdge's template uses the same logic: an owner per row, a lead time to cover forms, inspections, fees and continuing education, and a renew-by date derived from it. DocsReminder lays out a similar Google Sheets structure and says the weak point is that a sheet only helps if someone remembers to open it. That weak point is what the weekly Slack check removes.
Try Kipwise Agent free in Slack: mention it once in a thread and it does the repetitive work, with your permissions.
Why do spreadsheet trackers fail even when the dates are right?
A spreadsheet tracker fails at the moment of renewal, not at entry, because the new document goes to an inbox nobody watches and the Status cell stays put until someone edits it. PolicyHold describes this pattern for subcontractor insurance (a vendor's account, not a study): a broker sends the renewal certificate to an inbox nobody monitors daily, and the expiration column stays unchanged until someone edits it.
The same page describes a second failure that is easy to copy by accident. A sub was marked "cleared" in March, the general liability policy expired in August, and the sheet still said cleared because nobody ran a weekly expiration export. The word in the Status cell had outlived the policy. The weekly check should recompute status from the dates and ignore the Status column, because a typed status can say cleared long after the policy has lapsed.
Three rules for building the sheet follow from that:
- Make the renewal path end in the sheet. Whoever receives the new certificate or license, whether the broker, the issuer's portal or an assistant, is the Owner on that row, and the row is not finished until the new expiry date is typed in.
- Do not let Status carry any logic. Dates are facts; a typed status is an opinion that goes stale.
- Put the Owner's name where the check can read it, so an unwatched inbox becomes a named person on a Monday post.
Who should own each renewal?
One named person per row, and the type of document usually decides who. RenewOps says small teams typically assign ownership to operations, finance or legal depending on the document type, and keeps one named owner per record. A workable split for a firm of 10 to 60 people is a recommendation, not a rule from a source:
- Insurance policies: whoever deals with the broker, usually finance or the owner.
- Business licenses and permits: operations, because they involve forms and sometimes inspections.
- Staff certificates: the person's manager, not the person, so a departure does not orphan the row.
- Vendor certificates: whoever approved the vendor. If you collect those once at intake, our piece on vendor onboarding in a small team covers the first collection; this tracker covers every renewal after it.
An owner who is also the person most likely to be on leave is a risk, which is why the sheet has a Manager column. If one person holds most rows, you have a different problem: see bus factor for a small firm.
How far ahead should the renew-by date be?
Pick the lead time by what the renewal involves, then add the reminder points on top. The sources give ladders rather than one answer: PermitDue's own reminders run at 90, 60, 30 and 7 days before expiry, and RenewOps shows ladders of 60, 30 and 14 days in one place and 90, 60, 30 and 14 in another. Those are product defaults from vendors, so treat them as starting points.
| Item type | Suggested lead time (recommendation) | Reason |
|---|---|---|
| Insurance policy | 60 days | Broker quotes and underwriting do not happen overnight, and RenewOps recommends 60 to 90 days for insurance for that reason |
| License or permit with an inspection or continuing education | 60 to 90 days | PermitDue notes that some health departments require a new inspection after a missed window, and that some professional licenses need continuing education finished before a late renewal |
| License or permit that is a form and a fee | 30 days | ExpiryEdge's default |
| Staff or vendor certificate | 30 days | Short to renew, but easy to forget |
Set the lead time per row, because a single number for the whole sheet is wrong for at least one type.
How does the weekly Slack check work?
It is one request, made once. In your #ops channel, with Google Drive connected under your own login, you mention the Kipwise agent and ask it to run every Monday at 8 am in your Slack timezone. The agent can run a request on a schedule in plain language and post the result in the channel. Creating the scheduled request needs one Approve; later runs do not ask again.
A request that works, written in your own words, looks like this:
> Every Monday at 8 am, open the "Compliance tracker" sheet. For each row, work out the renew-by date as the expiry date minus the lead time. Ignore the Status column. Post the rows that are past their renew-by date, within 30 days of it, or missing an owner or an expiry date, grouped by owner, with the item, the expiry date and the days left. If a row cannot be read, say so by name.
Here is the made-up example, to show the output. A 25-person staffing agency has these rows on a Monday, 3 March:
| Item | Owner | Expiry | Lead time | Renew-by | Check result |
|---|---|---|---|---|---|
| General liability policy | Dana (finance) | 30 April | 60 days | 1 March | Past its renew-by date, 58 days left |
| State staffing license | Omar (operations) | 15 June | 45 days | 1 May | Not flagged, its renew-by date is 59 days away |
| Food handler certificate, J. Rivera | (blank) | 12 March | 30 days | 10 February | No owner, 9 days left |
| Workers' compensation policy | Dana (finance) | blank | 60 days | n/a | No expiry date, cannot be checked |
The agent posts the first, third and fourth rows, grouped by owner, and names the blank ones as problems. The person reading the post does not need to open the sheet.
The agent does not file the renewal, pay a fee or check the issuer's public record. It does not tell you the firm is compliant. It reads the sheet you maintain and reports what the dates say.
What happens when the owner stays silent?
The check posts the row again with the owner's manager named, and the manager decides. The agent never decides anything. A table fixes the steps so nobody improvises:
| Week | What the post says | Who acts |
|---|---|---|
| Renew-by date reached | Row posted under its owner's name | Owner starts the renewal |
| Two weeks after, no reply | Row posted again, manager named from the Manager column | Manager reassigns or chases |
| Four weeks after, or under 14 days to expiry | Row posted at the top, with days left | Firm owner decides: renew now, replace the policy or accept the risk in writing |
| Expiry date passed | Row posted as expired | Owner calls the issuer or broker the same day |
The week numbers are a recommendation. Adjust them to your longest lead time, but keep the manager step, since the source for the reminder ladders, RenewOps, describes who owns each record but not what happens when that person does not answer.
When the owner files the renewal, they reply in the thread. The agent can add the new expiry date to the sheet, and that change waits for an Approve card, because editing a Google Sheet is a separate connection and each change needs your approval. To ask a broker or vendor for a new certificate, ask the agent for a Gmail draft. It writes the draft in your Drafts and shows the recipient, subject and preview on an Approve or Deny card before anything is sent. Only the person who asked can use the card, and it expires after 30 minutes.
Why is a renew-by date not enough for insurance?
A certificate of insurance proves coverage only on the day it was issued, and the certificate holder is generally not told when the policy is cancelled mid-term, so a renew-by date alone does not make an insurance row safe. An opinion from the New York Department of Financial Services on the ACORD certificate says the form is issued for information only and confers no rights, and that a certificate not filed with the department cannot expand the insurer's duty to notify additional parties of a mid-term cancellation. It is a New York opinion, so check how it applies in your state. PageCrawl makes the same point in plain terms: a certificate reflects coverage on its issue date, and holders are generally not notified of a cancellation unless an endorsement puts them on a list (a vendor statement).
What to do differently, as a recommendation:
- For your own policies, ask the broker for the policy dates, not only the certificate, and enter the policy expiry in the sheet.
- For a vendor's or subcontractor's certificate, add a second date: the day you last confirmed the coverage with the broker or insurer. Make the check flag any certificate not confirmed in the last 90 days, even if its expiry is far away.
- Ask the broker to add the firm as a notice recipient where the policy allows it, and note the answer in the row.
The agent cannot do the confirmation for you. It can only make sure the question gets asked on a schedule.
What can go wrong with the weekly check?
Four things, and each has a fix.
- The sheet cannot be opened. The agent should name the sheet as not read, not return a clean report. A clean post and a failed read look the same in Slack unless the request tells it to say so, which is why the request above asks for unreadable rows by name.
- A date is typed as text. A row with "next March" or a mistyped year is a row the check cannot trust. Make the Expiry column a date column and flag blanks, as in the example.
- The agent's arithmetic disagrees with the sheet's formula. For the first month, compare the posted renew-by dates against the Renew-by column. If one differs, fix the request wording or the formula before relying on it.
- A row does not exist. No check can find a license nobody listed. Once a year, ask each manager for the licenses and policies their team depends on, and add what is missing. The SBA point that requirements vary by state, county and city is the reason the list has to be built by a person who knows the firm.
The tracker is the firm's own record. It does not replace the issuer's records, and the agent does not check them.
How do you know the tracker works?
Check three numbers after the first month, then quarterly:
- Rows with no owner or no expiry date: this should be zero by the second Monday.
- Rows that reached their renew-by date with no reply: each one should have gone through the manager step.
- Renewals filed before the expiry date: every renewal should land before its expiry, and any that does not tells you which lead time is too short.
Then test it once. Add a made-up row with an expiry date 20 days out and a lead time of 30 days, no owner, and wait for the next Monday. If the post names it as late and ownerless, the check works. Delete the row afterwards.
Compare it with your contract tracker if you have one: contract management for a small team sorts contracts the firm signed by notice date. This sheet holds things the firm must keep valid itself, so keep them in separate sheets with the same owner and escalation rules.
What to do next
This week, start your compliance tracker: build the sheet with the ten columns above and fill in only the insurance policies and the licenses you cannot operate without. Then, in #ops, connect Google Drive and make the Monday request. The install trial is $2 for 7 days on the fast model only; saving a card (not charged) or being on a paid Slack plan makes it $10 for 14 days with all models. After the trial, the agent is $10 per user per month with a minimum of 3 users, including $5 of personal credit per user and $2 per user of shared team credit. Run it for four Mondays, compare the posts to the sheet, and only then add the Gmail drafts for certificate requests.



