Licence and Permit Application Tracker
Two documents and three sheets that compute the earliest day each licence or permit can actually be filed, not just its typical timeline.
Free download · No account needed
Sequencing with Dependencies
[New location] — every licence and permit, and what blocks what
Earliest Start is computed from the dependency it waits on, not guessed from a typical range.
| Item | Depends On | Lead Time | Earliest Start | Earliest Complete | Critical Path |
|---|---|---|---|---|---|
| — | — | — | — | — | — |
| — | — | — | — | — | — |
| — | — | — | — | — | — |
What a due-date checklist cannot show
| Independent item | Nothing blocks it. Start it day one and it never affects the opening date |
| Critical-path item | Cannot start until a specific predecessor finishes, and every day it slips moves the opening date by the same day |
A checklist lists both kinds of item the same way, with a fee and a typical timeline next to each. Only one of those two kinds sets the calendar.
Every licence and permit checklist online has the same shape: a list of what this kind of business needs, each with its own fee and typical timeline, read alone. That format is complete, and it is also misleading, because it presents every item as an independent timer a founder can start on day one. Several items on a real list are not independent. One application cannot even be filed as complete until a different permit already exists, and a due-date checklist has no way to say which ones those are.
Birchwood Kitchen Co., a fictional restaurant group, opened a second location with a first-time beer and wine licence attached to it. The state board's own published range for that licence was 60 to 90 days, and it was the single largest number on the checklist. Read as a list of independent timers, that made it look like the item to start moving first: file it on day one, let the 75-day midpoint run alongside permitting and construction, open in around eleven weeks once it clears.
The licence application could not be filed as complete until the health department permit already existed, which itself is not issued in most jurisdictions until construction passes final inspection for a Certificate of Occupancy. Sequenced correctly against Birchwood's own building permit and construction timeline, that chain did not clear until day 175. The licence's own 75-day clock started only then and finished on day 250, eight months after the lease was signed, not the eleven weeks its own quoted range implied on a checklist that never said what it was waiting behind.
What's in the pack
Requirement Register
Every licence and permit this activity and location actually needs, by authority, with the real trigger and the documents each one will ask for. An obligation triggered by headcount, revenue or a new state instead of a specific permit belongs in a separate register.
Sequencing with Dependencies
What blocks what, computed rather than guessed: the earliest day each item can be filed as complete, and which chain of dependencies sets the real opening date.
Status Tracker
What actually got filed and approved, checked against what the sequence predicted, so a slip on one item recomputes everything waiting behind it.
Requirement Summary
Plain-language notes on what each authority actually checks and why, so the register reads as understood rather than just filled in.
Application Narratives
The written narratives several applications require, drafted at the point each one becomes fileable rather than months in advance.
Permit Sequencing Milestone Sweep
A weekly agent that flags any critical-path item that is unblocked but still not started, and recomputes dates the moment something ahead of them slips.
How to use it
- 1
Open in River, or download it
Install the pack so the agent builds the register and the dependency graph from your own situation, or take the blank Word and CSV files away and fill them in yourself.
- 2
Describe the activity and the location
What the business will actually do, whether alcohol or construction is involved, and whether a lease is already signed and from what date.
- 3
See what actually blocks what
Sequencing with Dependencies works out which applications wait on which others, and computes the earliest day each one can genuinely be filed.
- 4
File each one only once it is ready
Status Tracker keeps the real dates next to the predicted ones, so a delay anywhere on the critical path shows up immediately instead of on opening week.
Frequently asked questions
Is this template free?
Yes. Two documents and three sheets download as Word and CSV files with no signup and no credit card. "Edit with AI" is a separate, optional path for founders who want the agent to build the dependency graph from their own situation. The rest of the packs sit in the template library.
What format are the downloaded files?
Word documents (.docx) for the two narrative and summary documents, and CSV (.csv) for the Requirement Register, Sequencing with Dependencies and Status Tracker, zipped together. They open natively in Word, Pages, Google Docs, Excel, Numbers and Sheets.
What does 'Edit with AI' actually do?
It creates a free River account and installs this exact pack as a private workspace. The agent asks what the business will actually do at the new location, builds the requirement list from that, then works out which applications block which others before any filing date gets suggested.
Why does sequencing matter more than the checklist itself?
Because the checklist's biggest number is not always the one setting the pace. A licence quoted at 60 to 90 days looks like the item to start first. Where it actually sits behind a health permit, which sits behind a Certificate of Occupancy, which sits behind construction, its clock only starts once that chain clears, adding to the wait rather than running alongside it.
What if my state's or city's process looks different from the worked example?
The specific authorities, fees and lead times vary by state, county and city, and the pack is built from your own answers rather than the example. What does not vary is the method: find what each application actually requires as a precondition, then compute the earliest day it can be filed from there.
Do I still need a lawyer or a permit expediter?
For a complex build-out or a contested licence, often yes, and this is not legal advice. What changes is what you hand them: a dependency graph with computed dates, rather than a due-date list nobody has checked against what actually blocks what. A deficiency notice back from an authority is different work: answering it inside its own window matters just as much.
How is this different from the compliance calendar pack?
The compliance calendar tracks recurring obligations you are already registered for: filings, renewals, and the licences you already hold. This pack runs before that one exists, for a one-time set of new applications with real dependencies between them, and hands off to the calendar once everything is open.
Find out which applications are actually waiting on which others
Download the blank pack as Word and CSV files, or open it in River and have the real dependency graph built from your own situation first.
Edit with AI