The First 24 Hours After a Borrower Entity Status Alert

Executive Summary: An entity status alert is one of the few monitoring events where the order of operations changes the outcome. Most of what a lender does in the first day is reversible. Two things are not: the record of what the state said before anyone touched it, and the moment the borrower learns you are looking. Getting those two in the right order costs nothing and is the difference between a clean file and an argument.

Why does the sequence matter more than the speed?

Because the first action most teams take is the one that destroys the evidence they will want later.

The instinct on receiving a status alert is to call the borrower. It feels responsive and it is the wrong first move. Once a borrower knows the lender has noticed, the situation begins changing: filings get made, fees get paid, and the state record starts moving. None of that is improper, and most of it is exactly what you want to happen. But it means the record you are looking at is the last version that exists independent of your involvement.

There is a legal reason this matters and not merely a tidiness reason. Florida's reinstatement statute provides that when reinstatement takes effect it "relates back to and takes effect as of the effective date of the administrative dissolution," so the dissolution is generally treated as never having occurred.^[1] The same statute carves out an exception: "the rights of a person arising out of an act or omission in reliance on the dissolution before the person knew or had notice of the reinstatement are not affected."^[1]

That carve-out turns on what you knew and when. Which makes the first hour of an alert an evidence-preservation exercise before it is a collections exercise.

• Documentation is cheap now and impossible later. The state record will not preserve its prior state for you.

• Outreach changes the facts. Necessary, and better done second.

• The alert timestamp is not the same as the filing date. Both matter and they are different.

• Reversible actions should precede irreversible ones. Calling is not reversible.

• A file assembled in the first day survives review two years later. One reconstructed afterwards generally does not.

What should happen in the first hour?

Preserve, verify, and classify. No borrower contact yet.

Preserve the record as it stands. Capture the current state record with a timestamp and an identifiable source. A dated capture showing the state's own record is a materially different artifact from a spreadsheet line reading "checked, dissolved." Cobalt's live lookups can return a timestamped screenshot of the state website alongside the data, which exists precisely for this kind of evidentiary use.

Confirm the alert is real. Re-run the lookup directly. Alerts can fire on normalization artifacts, and a status field that changed because of a formatting difference is not a status change. This takes one call and eliminates the most common false start.

curl -X GET "https://apigateway.cobaltintelligence.com/v1/search?searchQuery=Acme%20Holdings%20LLC&state=TX" \
  -H "x-api-key: YOUR_API_KEY"

Establish the effective date. The date the state acted is not the date you were told. Every statutory clock in this area runs from the state's date. Reinstatement windows run from "the effective date of such dissolution" in Georgia,^[2] and Texas measures its retroactivity limit from the date of termination.^[3] A gap of weeks between the state's action and your alert is normal and it consumes your window.

Classify the status precisely. "Not in good standing," "delinquent," "administratively dissolved," "revoked," and "terminated" are different conditions with different consequences, and states use the labels inconsistently. Our guide to entity status transitions covers what each one costs a lender.^[4]

What should happen in the first four hours?

Now establish exposure and check the clock that runs fastest.

Pull the current exposure. Outstanding balance, remaining term, collateral, guarantees, and whether any advance is pending. A status alert on a facility with a draw scheduled tomorrow is a different situation from one on a loan amortizing to zero next month.

Check the entity name against your financing statements. This is the highest-priority technical check and the most commonly skipped. If the debtor's name changed such that a filed financing statement became seriously misleading, the filing perfects collateral acquired "before, or within four months after" the change and stops perfecting later acquisitions unless an amendment is filed inside that window.^[5] Four months is far shorter than any reinstatement window, the clock runs from the change rather than from your discovery,^[6] and the governing name is the one on the state's formation record.^[7]

Determine the applicable reinstatement window. It varies sharply and the state of formation governs, not where the borrower operates. Texas allows reinstatement at any time but treats the entity as having continued in existence without interruption only if filed before the third anniversary.^[3] Florida permits application at any time.^[1] Georgia caps it at five years.^[2]

Look for co-occurring changes. Check whether the officer roster, address, registered agent, or name moved in the same window. A status change alone is usually administrative. A status change alongside two other field changes is a different pattern entirely.

Identify the probable cause. An unfiled report, unpaid franchise tax, and a lapsed registered agent point in different directions. Failure to maintain a registered agent and registered office is itself a documented route to involuntary termination.^[8]

The four-month UCC amendment window is the only clock in this situation that can close before a quarterly review cycle would even notice the event. If one thing gets checked on day one, it should be the name.

What should happen before the day ends?

Now contact the borrower, with the file already assembled.

Going in prepared changes the conversation. You know the effective date, the probable cause, the reinstatement window, and your own perfection position. That converts an open-ended question into a specific one, and specific questions get useful answers.

• Ask what happened and whether they knew. A surprising share of borrowers do not know, usually because state notices went to a stale registered agent address.

• Ask whether a cure is underway. Reinstatement is conditional. Texas requires a Comptroller tax clearance letter plus a certificate of reinstatement with a filing fee.^[3] A borrower who cannot obtain tax clearance is not reinstating soon, and that answer is diagnostic.

• Establish a date. Not "we are handling it." A specific filing date you can verify against the record.

• Record the conversation in the file. Including the time, because your knowledge timeline is legally relevant.

• Decide on pending advances. Whether to hold a scheduled draw is the one genuinely urgent commercial decision, and it should be made deliberately rather than by default.

Most administrative dissolutions are curable and many borrowers cure them within weeks. Treating every status alert as a default event destroys performing relationships over $50 filing fees. The point of the preparation is not to escalate faster. It is to know which situation you are in before deciding.

Want to see how Secretary of State change detection fits into a portfolio monitoring workflow? Book a demo.

What happens after day one?

The first 24 hours establish the facts. The following weeks determine whether the situation resolves or drifts, and drift is the more common failure. An alert that gets a diligent first-day response and then no follow-up produces a well-documented file describing a problem nobody fixed.

Days two through seven: verify the cure is actually moving. A borrower's commitment to reinstate is not evidence of reinstatement. Shorten that borrower's monitoring interval so the record is being re-checked frequently enough to catch the filing when it lands, and hold the committed date as a hard checkpoint rather than a soft expectation. If the date passes without a filing, that silence is itself information, and it is more informative than the original alert was.

Week two: reassess whether the cause matches the story. By this point you generally know whether the borrower obtained tax clearance, filed the outstanding report, or replaced the registered agent. A borrower who said the problem was an overlooked filing and who still cannot cure two weeks later probably had a different problem. That divergence between explanation and behavior is one of the more reliable early signals available, precisely because it costs nothing to observe.

Weeks three and four: escalate or close deliberately. Either the entity reinstated, in which case document the reinstatement date and note that the intervening period has been retroactively re-characterized, or it did not, in which case the situation has moved from an administrative lapse to something requiring a credit decision. Letting it sit in neither state is the outcome to avoid.

Two things deserve tracking across the whole period rather than at a single checkpoint:

• The four-month name-change window, if a name change occurred. It is the only clock here that can expire during an otherwise well-managed response, and it does not pause because a reinstatement is in progress.^[5]

• Whether other fields move while the status issue is open. An officer change or address change during a dissolution episode is a materially different signal from either event occurring alone.

The closing discipline is the one most often skipped. When a borrower reinstates cleanly, the instinct is to mark the alert resolved and move on. Record the reinstatement date and the fact that relation back applies, because that period may need to be reconstructed later and the version of events preserved in your file is the only one that will not have been rewritten by the statute.

What should not happen in the first 24 hours?

Several common reactions make things worse, and they are worth naming because they are all well-intentioned.

• Do not accelerate on the status alone. An administrative dissolution is a compliance failure, not a payment default. Whether it constitutes a covenant breach depends on your documents, and reading them takes an hour.

• Do not assume the business has stopped operating. Dissolved entities frequently continue trading, often without knowing their status changed. Revenue and entity standing are independent.

• Do not assume liens vanished. Whether a perfected security interest survives dissolution depends on state survival statutes and the facts of the winding up. It is a question for counsel, and the four-month name-change window is the part that will not wait for counsel.

• Do not close the alert because the borrower says it is handled. Verify against the record. A reinstatement either appears in the state's filings or it did not happen.

• Do not skip documentation because the situation resolved. The clean resolution is exactly the case where nobody remembers to write it down, and reinstatement retroactively rewrites the period you just lived through.

What does monitoring give you, and what does it not?

Being precise here matters, because a runbook built on an inflated view of the tooling will have gaps at the exact moments it is needed.

Business Monitoring re-checks a borrower's Secretary of State record on a cadence you configure, from daily up to every 30 days, and reports what changed against the previous check, classified by severity.^[9] Each completed check costs 1 credit from the shared pool. What it delivers to this runbook is the trigger and the timing: you learn a status changed, and you learn it within one cadence interval rather than at annual review.

What it does not deliver:

• Scope is the Secretary of State record only. No OFAC or other watchlist screening, no UCC filings, no court dockets, no professional licenses. Sanctions re-screening stays a customer-side workflow, and the UCC check in the four-hour block above is your system's job.

• It does not tell you the cause. Status moved. Why it moved is a phone call.

• It does not tell you your reinstatement window. That is statutory and depends on the state of formation.

• It does not preserve your evidence for you. Capturing and storing the dated record at the moment of the alert is a step in your process, not an automatic byproduct of detection.

The value is the trigger and the interval. Everything after the trigger is a workflow you have to have written down before the alert arrives, which is the entire argument for having a runbook at all.

What does a good runbook look like on paper?

Short enough that someone follows it under pressure. The version above compresses to a single page:

Hour 0 to 1: Preserve the dated record. Re-verify the alert. Establish the state's effective date. Classify the exact status.

Hour 1 to 4: Pull exposure. Check the entity name against financing statements and start the four-month analysis if it moved. Determine the reinstatement window for the state of formation. Check for co-occurring field changes. Identify probable cause.

Hour 4 to 24: Contact the borrower with a specific set of questions. Get a committed cure date. Document the conversation with a timestamp. Decide explicitly on any pending advance.

Standing rules: Do not accelerate on status alone. Do not close on the borrower's assurance. Verify cures against the record. Document even when it resolves cleanly.

The reason to write it down in advance is that the first genuine Critical alert is the worst possible moment to be deciding who owns the response and what the escalation path is. Those decisions are cheap to make on a quiet afternoon and expensive to make with a statutory clock running. For the underlying statutory landscape, our guide to the administrative dissolution reinstatement window sets out how the state clocks differ and why the date you knew is legally material.^[10]