Next month's calendar has 12 rows on it, and each one opens with a utility slug where the keyword used to sit. Three of the 12 call for a calculator. Two call for a comparison, one for a dataset, and the rest are still open.
That leaves you with three real questions. Which row gets built first. What building one actually involves. And what you say when the CMO asks where the keyword volumes went. A keyword tool can't answer any of them, because all three answers live inside your own blog.
I've watched team after team try to skip ahead and end up with a calculator graveyard instead: three tools someone built last year, none tied to a brief, none maintained, none cited. In every one of those cases the utility was an extra ask bolted onto a keyword-led brief, so nothing in the plan ever protected it. Shipping more tools into that plan changes nothing.
The Library Gap Audit
The utility-first content plan starts with an inventory of what your workspace has already shipped, sorted by what each page does for a reader rather than the query it ranks for. Page one of Google falls out of that list, downstream.
Here's the count to run. Pull your last 50 published posts and mark every one a reader would come back to use rather than read once. A calculator earns a mark. A live poll earns one on every vote. A dataset earns one for as long as its methodology page still checks out against the source. So does a comparison page, and so does a verifiable claim with a citation chain under it. A 1,400-word explainer with nothing embedded in it earns nothing.
Three out of 50 is the typical result.
Only a library-gap audit produces that shape. A SERP audit hands you competitors and a keyword audit hands you queries, and neither one can tell you what your own blog has and hasn't built. The case for making the switch at all, opening the brief with a utility instead of a query, is in replace keyword research with utility content. The volumes never moved when that switch happened. The brief above them did.
Five Utility Classes
The audit gives you a count. Shipping against the gap means choosing a class, because that count is spread across five kinds of utility and each one ages on its own schedule.
A live source renews with every interaction. A calculator converts an input into an output and ships once. A dataset publishes on a research cadence. A comparison page holds a contract on two products at the same time. A claim is an atomic, verifiable statement filed against a registered source.
Five classes means five different upkeep bills. The keyword follows from whichever bill you agree to pay.
Look at next month's calendar and pick the row your team is most likely to actually build.
The chart below is the running split across everyone who has answered.
It reorders on every vote, and the peak lands on whichever upkeep bill the room believes it can carry. A content planning framework built off the SERP reduces that choice to a different question, what Google already ranks, which says nothing about what your team will keep accurate. The poll you just answered is itself a live source, a poll that generates its own data. LiquiChart hosts and monitors assets in all five classes.
Maintenance Posture Sets the Cadence
Each class costs a different amount to keep accurate. Call that cost its maintenance posture. The default calendar runs the decision backwards, committing to a publish rate first and then hunting for something to fill the slots. Choose the class first and the cadence falls out of it.
So does compounding. A calculator's value tops out on ship day. A poll-backed chart gets a little more valuable with every vote. A claim costs exactly whatever keeps its source verifiable, and that last surface is the one Google's information gain score reads.
Treat a claim as its own class and it becomes the smallest thing you can maintain and the densest thing anyone can cite.
The selection question is which utility, once it ships, another publication would cite. Answer it from the SERP and the calendar points at what already exists. Answer it from the audit and the calendar points at the gap.
The Utility-First Content Brief
The standard content brief template opens with a keyword and produces a calendar. The utility-first brief opens with the utility and produces an asset registry. Six columns are enough; at 10 you've written a checklist. The row under the header is this post's own utility, filled in.
Column one names the utility. Column two names the contribution gap, the thing the audit showed your blog hasn't published yet. Column three picks one of the five classes. Column four records the maintenance posture, and no keyword-led brief has ever carried that column. The keyword sits still while the asset ranking for it decays on a schedule nobody wrote down.
Column five is the editorial frame, where the post around the asset lives. Column six is where the utility travels beyond it. When column three says claim, column six points at the claim registry, where every filed claim carries a verification record, a registered hash, and a citation chain other publications can pull from. Living content handles the same propagation for poll-backed sources.
The poll above is this draft's own column-one entry. The paragraph below is its column-four contract.
Column four is the contract the brief carries on whatever ships into column three. As readers weigh in above, the live vote is column four being filled in against the menu of five postures, and the entry the room commits to is the one the keyword-led brief never had a slot for.
Six columns is where the brief holds. Add a seventh and it drifts toward checklist. Cut to four and maintenance posture is the first casualty, and that's the one column I'd never give up. A keyword-led brief plans what you'll publish. This one plans what you'll keep true.
Triage the Existing Library
A calendar full of fresh utility slugs still can't tell you which row to build first. The audit can, because the same scan that produced the count also orders it by decay speed.
Calculators go to the top of the queue every time. Their decay is invisible right up until a number inside one stops being true. Comparison pages sit in the middle, their contract breaking whenever either product ships an update the page hasn't registered. Live sources sit at the bottom because they renew themselves.
The LiquiChart Content Health scanner reads any URL you've shipped and returns the staleness risk for every claim on the page, sorted by which numbers age fastest. Run it on the entries the audit flagged and you know exactly where to start. The longer arc, how the audit, the classes, and the scanner fit together, lives in the new stack for data-backed content.
Audit first. Rebuild after.
The triage queue also shows which existing posts are closest to graduating into maintained utilities and which are still sitting under keyword-led briefs. The calendar reads off the queue. The standup is where you defend it.
The Stake
Three of your 12 rows already carry a utility slug in column one. Nine still open with a keyword nobody has retired, and a quarter from now the CMO will ask whether they still do. The utility-first content plan is what you walk in with, because next quarter is when content strategy without keyword research has to defend itself outside the standup.
Run next month with the columns unchanged and you ship 12 more rows that look like everyone else's. You know the count. You have the brief that names the missing column. What the calendar looks like next quarter comes down to which one you defend on Wednesday.