Know the next permit step on every job.

• The decision clock

  Four recorded windows — the completeness determination, the decision, and the applicant and affected-parties appeal periods — each carrying the instant somebody observed, the period a cited official-source revision states, and the date that period makes it due; a window nobody has started reads as not started, and a period no source states is left uncounted rather than filled in.

• The revision ledger

  Every revision item keeps the municipality’s own wording, the cited requirement it was raised against, the review round that raised it, an owner inside your company and the documents that answer it — and an item that comes back a second time is marked as a repeat, because a returning item is the expensive one.

• The pre-application meeting

  Where a published checklist asks for a pre-application meeting summary, the meeting is recorded with its date, its summary document and the additional requirements the authority identified there, so a condition found before the application is an item with an owner rather than somebody’s memory of a room.

• Decided is not released

  A permit whose decision is recorded and whose release is not sits in its own recorded state, with the prior-to-release conditions still listed and the two appeal windows counted from their own starts — the applicant’s from the decision, the affected parties’ from the public-notice advertisement — and a window whose start nobody has observed stays unknown in both directions.

• A read-only link for the architect of record

  One expiring, revocable link per professional per project shows them the open revision and prior-to-release items in the municipality’s wording, the cited requirement behind each, the same clock your team reads and the documents the municipality expects — and no client, property, financial or internal record, no file downloads and no other project.

• Developments, phases and launch readiness

  Group a site’s projects into a development with the phases your company already uses, then read one screen that says what each phase is waiting on, building by building, from recorded evidence — it projects no date, shows no countdown and estimates nothing.

Who does PermitLane replace? Nobody. The architect of record draws, the municipality decides, and your team files — through the permit expediter you already use, if you use one. What PermitLane holds is the space between them: which condition was raised, against which cited requirement, who holds it, what it blocks, and the date a cited period makes it due.

It cannot make a municipality decide faster, and it never says when one will. What it does is make the wait visible and keep the return trip short: fewer avoidable round trips, and no surprise on the date. Marking an item resolved records what your team did; it never says the municipality accepted it. Your inspections stay your own — your project managers run that roadmap, and nothing here changes how you run it.