Is This a New Development or Last Week's Story Repackaged? A Four-Change Test

A story is new only if a fact, document, party or number changed.

Before you forward an item to your team, check whether a fact, a document, a party or a number changed. If none did, it's repackaging.

Three emails, one story

Picture a familiar morning. Three items land in your inbox before nine on a Tuesday, and all three lead with the same company's expansion plan. One says the company "announces." One says it "doubles down." The third calls itself an exclusive. Each has a new headline and a timestamp from the last twelve hours.

Read them side by side and the facts match. Same site, same timeline, same executive quote, lifted from the press release that went out last Wednesday.

So which one do you send to your team? Probably none.

Anyone following a specific field runs into this constantly. A story can be re-headlined for days after anything about it actually moved, and the cost lands on the reader: time spent rereading, and worse, a repeat forwarded to colleagues who now trust your forwards a little less.

The four-change test

We use a blunt rule. An item is a new development only if one of four things changed since you last saw the story: a fact, a document, a party or a number. If none did, the item is repackaging, however fresh the headline looks.

A fact changes when something true stops being true, or something unknown becomes known: the deal closed, the hearing was postponed, the product shipped. A document changes when a new primary record appears, like a filing, a permit application, a court order or a published rule. A party changes when someone enters or leaves: a new buyer, a regulator opening a review, a partner walking away. A number changes when a figure that matters moves, such as a price, a headcount, a capacity estimate or a deadline.

Four boxes. Tick one and the item earns a line in your notes.

The test is deliberately narrow, so it leaves out tone, commentary, fresh quotes restating a known position and analysis of what the story means. Those can be worth reading, and they still don't count as developments.

The four-change test. One ticked box makes an item a development.

Fresh headlines are packaging

Most readers judge newness by surface signals, and nearly every one of them can be produced without anything changing. A timestamp tells you when an item was published, which says nothing about when its information was. Verbs like "reveals" and "unveils" are headline choices. An exclusive label can sit on an interview with someone repeating what the company already said in public.

Quotes are the hardest call. A spokesperson saying the timeline is "on track" for the third time adds words and no information. A spokesperson saying the timeline slipped is a changed fact. Same speaker, opposite verdicts, and the test sorts them in seconds.

The usual advice for news overload is to cut sources or skim harder. Both treat volume as the enemy, and neither tells you which item to keep. A definition does. Without one, every reread feels like diligence and every forward feels like help.

Where the repeats come from

Repackaged items come from a few predictable places, and knowing them speeds up the test.

Syndication is the plainest: one wire report republished across many outlets, each copy with its own URL and headline. Press-release rewrites come next, with several outlets working from the same announcement on the same day. Then there are follow-ups that open with a full recap and add one line of reaction at the bottom, and roundup newsletters, which restate what ran elsewhere by design.

Roundups are useful when you missed the week. But the overlap adds up, and readers notice. Anyone subscribed to a handful of newsletters in the same field has probably seen the same story show up in several inboxes.

This test answers one narrow question: did anything move? If you need to trace where a story first appeared, use our prior-coverage check. If you're checking whether five outlets are really five sources, use the independence check. Whether a development is worth writing about right now is the job of the news peg guide.

A week on a hypothetical trade beat, logged

Here's the test applied to one week. Everything below is hypothetical: the field is battery recycling, and the company, which we'll call Northline, doesn't exist.

Monday is the baseline. A trade outlet reports Northline plans a second processing plant. First sighting, so it's logged as new.

Tuesday brings a newsletter recap with a punchier headline and the same details. Repackaged.

On Wednesday a county planning office posts a zoning application for the site. That's a new document, and arguably worth more than Monday's report, because it names a parcel and a filing date you can check yourself.

Thursday, a columnist argues the expansion signals confidence across the sector. Maybe interesting. No fact, document, party or number moved, so it's repackaged.

Friday, Northline names a construction partner and revises its capacity estimate upward. Two boxes: party and number.

Five items, three developments. The team gets three forwards instead of five, each with one line saying what changed. Copy the columns below into your own log. The verdict column is the point.

Changed-fact log. Hypothetical example: Northline is a fictional company. Leave 'What changed' blank on repackaged rows.

A quiet day is a result

Run the test honestly and some days every item comes back repackaged. That's a finding. The field held still, and now you know it held still, which your team can use.

On a quiet day the pull is to forward something anyway, because silence can look like you weren't paying attention. Resist it. A note saying "nothing moved on the Northline plant this week; the next document to watch is the county hearing" beats a sixth recap, and it teaches colleagues to open your forwards when they do arrive.

Quiet days also protect the log. Pad slow weeks with repeats and the record gets noisy, so later you can't reconstruct when the story actually moved.

A quiet day is a finding. The field held still, and now you know it held still.

Before you forward anything

Write one line first: what changed, and which of the four boxes it ticks. If you can't fill the line, don't send it. That single habit does more for a team's attention than any filter setting.

The same rule shapes how we think a field should be followed. A useful briefing tells you what changed and says so when nothing did. Niche follows a defined niche, merges syndicated copies of the same story, drops weak citations and keeps the supporting sources attached, so you can open the record yourself. You can read how we check sources. When there are no new stories, the briefing page records a quiet day and the email is skipped.

Source checking narrows the pile. It doesn't guarantee every claim is true, which is why the links stay with each story and why the final call stays with you. Run the test on what lands, keep the log and let the quiet days stand.

Frequently asked questions

Does a new quote make a story a new development?

Only if the quote changes one of the four boxes. A spokesperson repeating that a project is on track adds nothing. A spokesperson saying it slipped, or naming a new partner, changes a fact or a party.

What if an analysis piece adds a new number?

If the figure wasn't in the record before and you can trace it to a source, tick the number box. Commentary about figures already reported stays repackaged.

Is a quiet day a sign I'm missing something?

Not if you ran the test on what landed. A day where everything comes back repackaged means the field held still. Record it, and note the next document or date to watch.

How is this different from checking prior coverage or source independence?

The prior-coverage check finds where a story first appeared, and the independence check asks whether several outlets are really separate sources. The four-change test asks one question: did anything move since you last saw it?