Media & Publishing · News & Digital Publishers
Breaking news isn't a publish. It's a story that keeps moving.
We build the live file, the wire matching, and the correction flow that let one story absorb every new fact in place, read by people who never have to reload, and fixed everywhere it ran when the figure turns out to be wrong.
Incoming
Appeals board confirms hearing date for the Harbour Street ruling
Filing published: full judgment, 84 pages
Statement issued by the planning office
Two named appellants withdraw
Harbour Street ruling: what the appeals board decided
Hearing date confirmed
Full judgment published, reading now
Planning office issues a statement
First report: board rules against the development
New agency line matched to LIVE-0114. Take appended, app push sent, no republish needed
Which story on your desk republished five times this week?
What a breaking day costs
Five things that go wrong between 15:20 and 16:02
Breaking means republishing the same page five times
Every new fact becomes a fresh publish cycle, and the readers already on the page have no idea anything moved.
The wire arrives faster than anyone can read it
Agency, court, and council feeds all land in different inboxes, and the line that matters is buried among forty that don't.
A correction reaches the web and stops there
The push notification, the newsletter, and the partner who syndicated it are all still carrying the wrong figure.
The paywall treats every story identically
A two-line council brief and the investigation that took four months meet the reader with the same meter.
Traffic spikes at exactly the wrong moment
The story that finally breaks is the one the site can't serve, because nothing was built for the day it mattered.
// five republishes, one story
Desks we build for
Every beat runs at a different clock
News
Breaking, running files, live updates
Politics
Results nights, votes, tracked pledges
Business
Markets, embargoed results, filings
Investigations
Long files, documents, legalling
Sport
Live scores, minute-by-minute, results
Culture
Reviews, listings, archive features
What we build
The newsroom software a breaking day actually needs
Live files & running stories
One story that keeps updating in place: takes appended as facts land, and every open reader sees them without touching reload.
LIVE-0114 · one URL
Hearing date confirmed
Full judgment published, reading now
Planning office issues a statement
Wire ingestion & matching
Agency, court, and council feeds land in one queue and get matched to the story they belong to, with no five separate inboxes.
Paywall & subscriber metering
The meter reads what a piece is actually worth to a reader, where a flat count to five just hopes.
Built against the CMS, paywall, and push tooling you already publish through. It works with them and replaces none of them.
Breaking-day infrastructure
Caching, edge delivery, and push built so the day the story lands is the day the site holds up.
Built against the CMS, paywall, and push tooling you already publish through. It works with them and replaces none of them.
First report filed
Board rules against the Harbour Street development. Published to web and app.
Statement appended
Planning office responds. Take added to the running file: no republish, no new URL.
Judgment published
Court feed matched to this file automatically. Document attached to the story.
Correction folded in
The appellant count was wrong in the 15:20 take. Corrected once, on the record.
Everywhere it ran
App push, newsletter block, and two syndication partners all updated from the same correction.
Flagship · the running file
Forty-two minutes, four takes, one URL
A story that's still happening doesn't need five publish cycles and five URLs. Facts append to the file as they land, the wire matches itself to the right story, and when the appellant count turns out to be wrong it's corrected once, then pushed to the app, the newsletter, and both partners from the same action.
- Appends a new take to a running story without a republish or a second URL
- Matches an incoming wire line straight to the file it belongs to
- Folds a correction into the record once and pushes it everywhere the story ran
- Keeps every reader currently on the page in sync as the file moves
An offer from the desk
Bring the story that broke badly last month
The file above is illustrative. Point the same live file, wire matching, and correction flow at a story your desk actually ran, and see where the five republish cycles would have collapsed into one.
Connects to your stack
It reads your feeds and publishes through your systems
Sources we read
Systems we connect
CMS
The live file is a first-class object in the CMS you already publish from.
Push & app
A take, a correction, or a breaking alert reaches the app from the same action.
Paywall & subscriptions
Metering and offers read the piece, the reader, and the moment together.
Syndication
Partners receive every update and correction, along with the original file.
How it runs
From a breaking day we watched to a file that runs itself
Follow a breaking day end to end
We watch a real story break: every republish, every inbox, every place a fact had to be retyped.
Make the running file a real object
One canonical story that takes append to, with a URL that never changes and readers who stay in sync.
Wire in the feeds and the matching
Agency, court, and council sources land in one queue and route to the desk and the file they belong to.
Turn on corrections and the meter
A fix propagates to every destination that ran the piece, and metering starts reading the story instead of the count.
What changes
A desk that stops republishing the same afternoon
A story updates instead of republishing
Facts append to one file, so readers already on the page see the news move without reloading anything.
The wire stops being an inbox
Lines arrive matched to the story they belong to, so the one that matters isn't buried in forty that don't.
Corrections reach everyone who saw it
The push, the newsletter, and the syndication partner are all corrected from the same action.
The big day doesn't break the site
Edge caching and push are built for the traffic the story actually brings, well beyond the average Tuesday.
Bars are illustrative. They show relative emphasis, not measured results.
Questions
What news teams ask first
Q.Does a live file need a new URL each time it updates?
No, and that's the point of it. One canonical story keeps its URL and its position in search while takes append to it, so links shared at 15:20 still work at 16:02 and show the current state.
Q.How does a wire line get matched to the right story?
Incoming feeds are parsed for entities, place, and subject, then matched against open files on the desk. Anything unmatched waits in the queue for a human, so nothing gets dropped.
Q.What happens to readers who are already on the page?
They stay in sync. New takes and corrections reach open pages without a reload, so nobody sits reading a version that was superseded ten minutes ago.
Q.Can the paywall behave differently for breaking news?
Yes. Metering can read the piece as well as the reader, so a public-interest breaking story can sit outside the meter while an investigation stays behind it.
Q.Will the site survive the day the story actually breaks?
That's what the infrastructure work is for. Edge caching, push at scale, and graceful degradation are built and load-tested against the traffic the biggest story would bring, far above the daily average.
Related services
The systems underneath the wire
Elsewhere in media
More of Media & Publishing
Let's talk
Running a large platform, shaping a first MVP, or getting a product ready for a funding round? Tell us where you are. We'll shape the process around it, and stay with you after launch.
