A decade on Rose Street ended with a sentence nobody in this town wanted to type. A local restaurant was closing, and the reason given was a big drop in sales. I've written enough food stories here to know the usual rhythm: a soft opening, a first look, a farewell post with a nostalgic photo and a line about how much we'll miss the sandwich case. This one didn't follow the rhythm. This one had a number attached to it, and a number is where a restaurant feature stops being a restaurant feature.

That's the turn most food writers never train for. You spend years learning how to describe a ham without sounding like a press release, and then one day the owner you've quoted six times is explaining a rent dispute with her landlord, and your friendly profile is now a document that could end up in someone's file. You do not need to be a lawyer to report that story. You do need to know when to stop acting like a diner and start acting like a journalist. If the dispute escalates to a claim, the standard move is to route the legal questions to someone whose job is answering them, the way you'd hand questions to a lawyer personal injury specialists handle when they take over a case from a writer.

What follows is the process I actually use, the one that has kept me out of trouble across two decades of covering places that eventually close, get sued, get cited, or get rebuilt by new owners with a better lease. It's not glamorous. It's mostly about changing who you call first.

Why "Sales Are Down" Is a Quote, Not a Fact

When an owner tells you sales significantly, you have a decision to make in about four seconds. Print it as her claim, or print it as reality. Print it as reality and you've just made a statement about the health of a business you can't verify, which is the kind of thing that gets a correction request, then a retraction request, then a letter from someone's attorney who bills by the hour.

So you attribute it. "Owner says sales have fallen significantly this year, making it impossible to keep the beloved shop open." That's a completely different sentence. It's still a story. It's a better story, honestly, because it's honest about who supplied the number. You keep the texture, you lose the liability.

The same discipline applies to anything a restaurant tells you about its own closure. Health department records, liquor license status, court filings, all of that lives in public databases, but reading a filing correctly is its own skill. I've watched reporters misread a simple civil docket and turn a billing disagreement into a scandal on their own blog. If a dispute is heading toward litigation, the person who should be interpreting that paperwork is not the writer who knows how to make short rib sound good.

The Three Calls I Make Before I File the Story

This is the part you can actually use. It's a checklist, roughly in order, and it works for a closure, a labor complaint, a beef recall, or a beloved bakery that suddenly has a new owner and a new name.

1. The source call. Go back to the person who gave you the number and ask, out loud, "Can you show me where that came from?" Sometimes they can. A pos system export, a lease, a settlement summary. When they can't, you attribute the claim and you move on.
2. The records call. County clerk, state licensing boards, the health department. Cross-check the facts a reader can verify themselves so you're not the only source standing between a claim and the public.
3. The counsel call. This is the one people skip. When a story involves an active claim, a landlord dispute, or a business that's been served, I ask a lawyer to walk me through what's public, what's privileged, and what I shouldn't repeat even if someone hands it to me on a plate. You are not asking for a legal opinion. You are asking where the edges of the story are.

Most of the time, that third call costs me twenty minutes and saves me a month of email. I've learned to make it early, not after the letter arrives.

When a Restaurant Story Becomes a Public Records Story

There's a version of this where the food angle survives completely intact. The building gets a new tenant. The recipes get sold. The sandwich case finds a new home across town. Your farewell post runs. Fourteen years, fond memories, everyone's happy.

Then there's the version where the closure is actually the middle of the story and the beginning was a lease someone stopped paying two years ago. That version belongs to the news desk, not the dining section, and knowing the difference is your whole job. Public health records are a good example of the second kind. Inspection reports, citations, and follow-ups sit in state databases anyone can pull, and a bad inspection is often the earliest visible sign that a kitchen is in trouble long before the owner stops returning calls. Checking those records early gives you a factual spine for a story that would otherwise just be grief and a GoFundMe.

Here's the thing fiction writers get wrong about the restaurant business. None of it is about the food. It's about the lease, the labor, the margins, and the people who can afford to wait. A drop in sales is not a chapter in a cooking show. It's arithmetic, and arithmetic always arrives with paperwork. If you've ever wondered why the great local spots close while the mediocre ones survive, it's usually not talent. It's the boring stuff you don't see from the dining room.

What this means for a food writer in Sarasota, or anywhere with a real restaurant scene, is that you have to be comfortable in two rooms: the dining room, where the story is taste and memory, and the records room, where the story is numbers and signatures. The best local coverage lives in the overlap. When I get pulled into a story that has both, my rule is simple: keep the food writing in the food story, and hand the legal questions to someone qualified. That's not a failure of reporting. It's the reporting.

How I Decide Whether the Story Runs at All

Not every closure deserves a piece. Some are private, and pulling a dispute into the public eye because you happened to see a court filing is a way to hurt people who never asked to be in your story. I weigh three things.

Public interest. Did the business take deposits, sell gift cards, sign leases, or employ a staff that now can't get paid? If money changed hands and didn't come back, that's news.

Verifiability. Can I stand behind every sentence in the piece with something other than a single source's memory? If not, the piece gets shorter or it doesn't run.

Harm. Is the person who loses something here the same person who did something wrong? Usually not, and when I'm not sure, I wait.

None of this requires a law degree. It requires you to slow down at exactly the moment a good quote makes you want to speed up. That instinct, the one that says "this is a great line," is often the one that gets you corrected three weeks later.

What Keeps a Food Writer Out of Trouble

Write like the courtroom is a reader. Attribute aggressively. Keep your notes for a year. Get a second set of eyes on anything that involves a claim, a contract, or a person's reputation. And accept the fact that a closure story about a beloved shop is not, and was never, just about the cheese. I don't love that part of the job, but I've stopped pretending it isn't there.

If you're writing about a business that's closing under a cloud, stop asking what the cheese tasted like and start asking who's holding the lease. Where does your favorite local story actually end for you, at the last meal or at the paperwork?