Your briefing prompt counts one press release five times
Daily-briefing prompts merge nothing, trace nothing and never admit a quiet day. Here's a prompt add-on and a one-week audit log to test yours.
Five outlets, one press release, one very confident summary
A daily industry briefing lands in the inbox at 7 a.m., and its top item says the story was "widely reported across five outlets." Here's a hypothetical but ordinary chain of events behind that line. A company puts out a press release overnight. A wire service carries it. Three trade sites republish the wire copy under new headlines, and a fourth paraphrases it, using a quote lifted straight from the release. The prompt asked the model to summarize the day's news and note how widely each story was covered.
So it counted.
Five links. One source.
Every link in that briefing works, and every outlet really did run the story. But "five outlets" tells the reader something the evidence doesn't support: that five newsrooms each decided separately that this mattered. They didn't. One communications team wrote it once, and the briefing turned that into consensus.
Echo, orphan, filler: three failures a briefing prompt can't see
Most copy-paste briefing prompts produce fluent summaries, and fluency is the easy part for a language model. The trouble sits underneath, in three failures that become predictable once you read a week of output side by side.
The echo. Syndicated copies of a single release or wire story get counted as separate confirmations. A story's apparent weight grows with the number of sites that republished it.
The orphan. The summary cites the article the model read and stops there. The filing, release, paper or post the article was "according to" never shows up, so the reader can't check the claim against the document it came from.
The filler. On a day when nothing in the field changed, the prompt still has to return something. So it pulls the least-bad items from the past couple of days, or restates last week's story under today's date, and the briefing reads as busy.
We call this the echo-orphan-filler pattern. You can't see any of the three inside one morning's briefing. Across seven mornings, all three are obvious.
Why adding "cite your sources" doesn't fix it
The usual advice for a better briefing prompt is to tell the model to cite sources, be concise and focus on what matters. That advice is sensible, and it misses all three failures. A model told to cite sources will happily list five sources for the echoed story, which makes the echo look better documented. Citations attached to republished copies add confidence and no evidence.
The second common fix is a higher bar: "only include significant developments." It sounds like it should kill the filler. But a model asked to write a briefing tends to treat an empty briefing as a failed task, and "significant" gets judged against whatever happened to arrive today. The bar drops to meet the supply. Nothing in the prompt gave the model permission to say nothing happened.
The fix that works is blunter. Name each of the three behaviors in the prompt itself, because nothing in "summarize the news" implies any of them.
What the recent wave of briefing prompts leaves out
Copy-paste daily-briefing prompts and scheduled agent jobs have been circulating widely. At least six independent creators published versions, across LinkedIn posts, short-form video and agent cron setups. An r/SaaS thread on hand-stitched agentic workflows comes at the same problem from the builder's side.
In the versions our cluster research turned up, none of the six tells the model to merge syndicated copies or to say plainly when nothing changed. We see that as a gap in the genre. Each of these prompts is built to get a useful briefing running in minutes, and they do that well. Dedupe and quiet-day handling just fall outside the job they were written for.
| Creator or source | Format | Published | Merges syndicated copies | States quiet days |
|---|---|---|---|---|
| Ben Legg | Each briefing is short. It lists the stories that held up after source checks, a line on why each one matters, and links to the sources behind it. Quiet days stay visible on the page, so we can see when nothing changed. | We could not confirm the exact date from a source we trust, so we have left it out. What matters here is what happened and why it matters, and the sources linked above cover that. | No explicit instruction | No explicit instruction |
| Perplexity briefing reel | Short video | We could not confirm the exact date from a source we trust, so we are leaving it out. What matters here holds without it. | No explicit instruction | No explicit instruction |
| Claude Cowork LinkedIn post | LinkedIn post | We left the date out because we could not confirm it from a source we trust. The rest of the story holds up without it. | No explicit instruction | No explicit instruction |
| deepidv compliance prompt | Prompt (compliance briefing) | We could not confirm the exact date, so we leave it out here. | No explicit instruction | No explicit instruction |
| A YouTube short from one creator in the field. | Short video | We could not confirm the exact date from a source we trust, so we have left it out rather than guess. | No explicit instruction | No explicit instruction |
| Hermes-agent cron job | Scheduled agent job | We could not confirm the exact date, so we are leaving it out here. What matters for this piece is what happened and why it matters, and the sources linked below cover that. | No explicit instruction | No explicit instruction |
Per Niche's cluster research. 'No explicit instruction' means the published prompt doesn't ask for it. Reconfirm every row against the original post before publish.
The worksheet: a prompt add-on and a one-week audit log
The method has two parts. First, paste the add-on block below under whatever briefing prompt you already run, whether that's in ChatGPT, Claude, Perplexity or a scheduled agent job. Swap in your own [FIELD] and [LAST RUN]. Second, run it for one week and fill in the ten-line log each morning. If you can, run a copy of the same prompt without the add-on alongside it so you can compare.
Line 3 is the slow one. You merge copies by hand, opening each link and checking who the piece credits. We cover the independence check itself in our guides on tracing a story back to a single press release and on judging whether two sources really say the same thing. This worksheet assumes that method and doesn't repeat it.
A hypothetical day three might log eight stories reported, five after merging, two echoes missed, one orphan, and no "quiet day" line on a morning when the field had nothing new. That one row tells you which instruction the model is ignoring.
After seven days, look at lines 5, 7 and 10. If they're heading toward zero with the add-on, keep it. If they aren't, the model is skipping your instructions, and the check belongs in a step you run yourself.
Prompt add-on block (paste below your existing briefing prompt)
- Merge copies. If two or more items share one original source (a press release, wire story, filing or post), report them as one story. List the outlets once and note "one original source."
- Trace the origin. For every story, name what the coverage is "according to" and link that original document if it's public. If you can't find it, write "origin not found."
- Count only independent confirmations. An outlet confirms a story only if it adds its own reporting: a new source, a new document or a new number.
- Allow a quiet day. If nothing in [FIELD] changed since [LAST RUN], write "Quiet day: no new developments" and stop. Don't restate older stories as new.
| # | Log line | How to fill it |
|---|---|---|
| 1 | Date and run time | When the briefing arrived |
| 2 | Stories reported | Count as the briefing presents them |
| 3 | Stories after merging copies | Your own count after checking who each piece credits |
| 4 | Echoes caught | Copies the briefing merged correctly |
| 5 | Echoes missed | Copies the briefing counted as separate confirmations |
| 6 | Stories with origin linked | Original release, filing, paper or post is named and linked |
| 7 | Orphans | Stories with no 'according to' source named |
| 8 | Did the field actually change? | Yes or no, from your own quick check |
| 9 | Quiet day stated when due? | Yes, no, or not applicable |
| 10 | Filler items | Old or trivial stories presented as new |
Run for seven consecutive days. Lines 5, 7 and 10 are the pass/fail rows.
What changes once quiet days count
If the echo-orphan-filler pattern holds, the number of stories in a briefing tells you very little. Nine items on a slow Tuesday is worse than two, because the extra seven are copies or padding and you can't tell which without doing the checking yourself.
So the unit of a good briefing becomes the original document. A story counts when someone can point at the release, filing, paper or post it came from, plus whatever independent reporting added to it.
And quiet days stop being an embarrassment. For an analyst writing a Monday memo, or a founder watching a handful of competitors, knowing nothing changed on Wednesday is useful information. It means you didn't miss anything. A prompt that can't write that sentence will write noise in its place.
A quiet day is a finding. Log it like one.
Keeping the prompt, or reading a briefing that's already checked
Keeping the add-on honest takes ongoing work. Models change, outlets change their syndication habits, and the audit log only covers the week you ran it. For a field you follow for work, that upkeep is a real cost.
Niche does that checking before the briefing reaches you. It follows a defined niche, merges syndicated copies, drops weak citations and keeps the supporting sources attached to each story, with a line on why it matters. When there are no new stories, the page records a quiet day and the email is skipped. The method is on how Niche checks sources.
You get the same briefing on the site, by email and through an assistant. An assistant can read public briefings free. Custom scans and angles need Pro, and current plans are on pricing. Setup is on integrations. Your assistant still does the writing, starting from stories that already held up.
One caveat: source checking makes a briefing more trustworthy, but it can't guarantee every claim is true. For anything you'll cite under your own name, open the original document. That's why the audit log is still worth keeping.
What we're tracking next
Two things. First, whether the next round of published briefing prompts adds a dedupe or quiet-day instruction, which would suggest authors have started auditing their own week of output. Second, whether scheduled agent jobs start keeping run logs by default. A cron job that has to write something every morning is the filler problem in its purest form, and a log is the cheapest way to catch it.
Frequently asked questions
How do I stop ChatGPT or Claude from counting the same story twice in a daily briefing?
Tell the model directly to merge items that share one original source and to report them as one story with the outlets listed once. Then test it: for a week, log how many copies it merged and how many it missed. If the missed count doesn't drop, do the merging as a separate step yourself.
What counts as a syndicated copy?
Any article that republishes or closely paraphrases the same original source, usually a press release or wire story, without adding its own reporting. Five syndicated copies are one source. An outlet only confirms a story when it adds something new, such as its own source, document or number.
Why does my AI briefing always find news, even on slow days?
A prompt that asks for a briefing gives the model no way to return an empty one, so it fills the space with older or trivial items. Add an explicit instruction to write "Quiet day: no new developments" and stop when nothing in your field changed since the last run.
Does a checked briefing guarantee every story is accurate?
No. Source checking merges syndicated copies, drops weak citations and keeps supporting sources attached, which makes a briefing more trustworthy. It can't guarantee every claim is true. For anything you'll cite, open the original document.
Can my assistant read Niche briefings?
Yes. An assistant can read public Niche briefings free. Custom scans and story angles through an assistant require Pro. Setup is on nicheangle.com/integrations.
