The renewal you missdissolves the company.

No. It's the triage layer, not a registered-agent service. It computes where every obligation stands from the dates and consequences you enter, tells you what's current, due soon, past due, or blocked, and names what to fix first — but it files nothing, contacts no state, and tracks no live status. Its distinct value over a filing service is the honest read those dashboards don't give you: which of your obligations are existential versus annoying, and which licenses will structurally lapse because the entity they hang on is about to be dissolved.

Because a built-in deadline table would rot. Renewal dates, late fees, grace periods, and dissolution timelines are dated, state-specific, and change — Florida charges an immediate $400 the day after May 1 and releases your name after 12 months; Georgia dissolves after July 1; Delaware gives you two-plus years; Texas can revoke after 120 days. A shipped database would quietly go wrong. Instead you confirm each obligation's own due date and consequence from your Secretary of State or licensing authority, and the tool computes from exactly what you enter. That's the same honesty rule the rest of the catalog follows: it never invents a number you'd act on.

Because most licenses hang on an underlying entity — a contractor or professional license is issued to your LLC or corporation. If that entity is administratively dissolved, the licensing authority won't renew the license under it; you have to reinstate the entity first. So when a license's parent entity is past due, past its grace window, and facing dissolution or name-loss, the license reads BLOCKED regardless of its own date. The shipped sample shows a Florida contractor license 149 days from its own renewal reading BLOCKED, because the Florida LLC underneath it is 64 days past due. Fix the entity and the license goes back to reading by its own clock.

Urgency is when — the headline, from the due date versus the evaluation date: current, due soon, or past due. Severity is how bad — the consequence you confirm if it's missed, from a flat late fee up to loss of good standing, a lapsed license, name loss, or administrative dissolution. They're deliberately kept separate and never averaged, because a low-severity item due tomorrow and an existential item due in forty days are different problems, and a single blended score would bury which is which.

It's aimed squarely at the owner who's outgrown a spreadsheet but isn't paying a compliance service per entity — say three to fifteen obligations across a couple of states. If you have one LLC in one state, a calendar reminder is probably enough. The moment you add a foreign registration, a couple of licenses, or a second entity, the interactions start to matter: separate dates in each state, and licenses that can be taken down by an entity lapse you didn't notice. That's the mess this untangles.

The evaluation date is pinned rather than live so the workbook, engine, and demo always agree on the same reading — you set it to the day you run the review. The obligations themselves are yours to keep current: run it monthly, re-confirm any date that's changed, and the read updates. A mistyped or blank date is flagged as INVALID DATE rather than silently misread, so a bad entry can't quietly show you as current when you're not.