The Spreadsheet Nobody Owned

Someone opens the tracking sheet on a Tuesday morning because a partner asked a simple question: did we ever publish anything about that verdict? The sheet has eleven tabs. Column F says "status" and contains the values Draft, draft, DRAFT — hold, w/ Ana, and one cell that just says ?. Column J is called "source" and half of it is blank. There is a conditional formatting rule turning rows orange, and nobody in the room can explain what triggers it.

The person who built the sheet left in March.

This is the leak. Not a bad ad campaign, not a broken form — a spreadsheet that started as a temporary fix and quietly became the only copy of important status and source data, with nobody owning its logic. Six months in, it is load-bearing. And because it is load-bearing and undocumented, the whole content operation slows to the speed of whoever is willing to reverse-engineer it that week.

How a temporary fix becomes infrastructure

Nobody decides to run a publishing pipeline out of a spreadsheet. It happens in three moves.

Move one: the firm starts covering legal news — verdicts, regulatory changes, statute updates, the things clients actually search for after they read a headline. There is no system yet, so someone opens a sheet to track what's assigned and what's live.

Move two: the sheet grows columns. Publish date. Who reviewed it. Which practice area. Which city it's relevant to. Whether it's been linked internally. Whether the schema was added. Each column is a reasonable response to a real gap in the workflow.

Move three: the sheet becomes the answer to questions the CMS can no longer answer. What's in flight? Only the sheet knows. What did we source this from? Only the sheet knows. Why is this row orange? Nobody knows.

At that point the spreadsheet is not a tracker. It is the system of record — a system of record with no owner, no audit trail, and no backup logic. That is a specific and expensive kind of exposure for a firm whose growth depends on publishing consistently.

The detour costs you indexation, not just time

Here is what firm owners usually miss. The spreadsheet problem looks like an internal-efficiency problem. It is actually a freshness problem, and freshness is the entire point of news content.

Legal news has a short window. A ruling lands, people search, and the pages that get indexed inside that window capture the demand. Pages that get indexed three weeks later capture almost nothing. When every publish requires someone to interpret an undocumented sheet, decode a status value, and chase down the original source, you don't lose an hour — you lose the window.

So the honest measurement question isn't "how many articles did we ship" or "how many features does our content tool have." It's fresh article indexation. How many of the pages you published this month are actually indexed and serving? Everything else is activity.

The spreadsheet doesn't cost you an hour. It costs you the window — and the window is the whole business case for news content.

The second failure mode: automating the wrong thing

The instinct, once someone finally audits the sheet, is to automate the detour instead of removing it. Bolt a script onto the spreadsheet. Auto-generate summaries. Fire pages out at volume and hope the freshness signal does the work.

That's the wrong direction, and Google has been clear about the line. Its people-first guidance says automation becomes a problem when the primary purpose is manipulating search traffic instead of helping users. Automation that reduces manual steps in a real editorial workflow is fine. Automation whose output exists only to be a page is not.

Which means the fix has two halves, and most firms only do one.

Half one: make every news page actually useful

A headline restated is not content. A news page earns its place when it answers the three questions a reader has after they finish the headline. Make these a required part of the template — not a suggestion, a field the page cannot ship without:

• What this means. Translate the ruling, filing, or rule change into plain consequence. Not the procedural history — the outcome.
• Who is affected. Be specific about the population. Which claimants, which employers, which policyholders, which counties, which filing deadlines shift.
• What happens next. The appeal timeline, the effective date, the action a reader should take now, the thing to watch for.

Those three sections are what separate a page that helps a user from a page that exists to occupy a search result. They also happen to be the fastest thing to write, because your attorneys already say these things out loud on every intake call.

Half two: replace the spreadsheet with a system that keeps receipts

Deleting the sheet without replacing its function just moves the chaos into Slack. What you need is a workflow that does what the sheet was pretending to do, properly: reduces the manual steps while preserving an audit trail.

That means status lives in one place with defined values. Source URLs are captured at intake, not reconstructed later. Review and publish events are logged with who and when. Schema and internal linking are applied by the system, not by whoever remembers. And when a partner asks "did we ever publish anything about that verdict," the answer takes eight seconds and doesn't require archaeology.

That is the job Legal News is built for — cutting the manual steps out of the publishing path while leaving a trail you can actually inspect, so freshness stops depending on one person's memory of what column F means.

What to do this week

You don't need a project plan. You need an afternoon and an honest look at the pipeline.

• Name the owner of every operational spreadsheet. If a sheet touches publishing and has no name attached, it's a leak. Firms in this situation usually find two or three of them.
• Find the data that exists nowhere else. Status and source are the usual suspects. Anything that lives only in a sheet is a single point of failure.
• Audit ten recent news pages against the three questions. Do they say what it means, who is affected, and what happens next? If not, you're publishing headlines, not help.
• Pull your indexation number. Of the pages you published in the last 60 days, how many are indexed? That's your real throughput. Everything upstream of that is process theater.

The spreadsheet nobody owned wasn't a mistake. It was a reasonable stopgap that outlived its purpose because it never got escalated to a real system. The cost only shows up as a number you're not looking at — fresh pages that never made it into the index while the demand was still there.

Fix the ownership, fix the template, measure indexation. In that order.