A Practical Guide to Using Rsw Busted Newspaper for Investigative Research
Rsw Busted Newspaper has become one of those terms you hear in newsrooms but nobody seems to write a manual for. It is a workflow built around pulling together local newspaper archives, public records, and cross-referenced reporting to expose stories that were either buried or never fully developed. The name comes from the idea of "busting" open files that local papers handled incorrectly or dropped entirely. I started using it about four years ago when I was trying to verify a land development story that had been covered but not followed up on. The basic process involves three layers. First, you gather every mention of the subject across archived newspaper databases. Most people stop at the front page results. The second layer pulls from local government records, court filings, and municipal meeting minutes that newspapers reference but do not reproduce in full. The third layer is where the method actually earns its name — you compare what was reported against what the documents say and flag the gaps, misquotations, or omitted details. I use a combination of the NewsBank archive, county recorder searches, and a simple spreadsheet tracker. The tracker is the part most people skip and should not. My setup has columns for date of publication, headline, key claim, source document citation, and a notes column where I record discrepancies. Over time you build a timeline that shows whether a story was changed, pulled, or quietly rewritten without correction. A complete audit like this usually takes between 6 and 12 hours depending on how long the original coverage ran and how messy the public records are.
There is a specific edge case that caught me last year involving a zoning board decision that a local paper reported as unanimous when the meeting minutes showed a dissent. I found it because I had pulled the raw audio from the municipal recording system rather than relying on the transcript the paper had used. The workaround was downloading the .wav files directly from the city's open meetings portal and running them through a free transcription tool called Whisper. The audio made it clear the "unanimous" vote had a conditional objection that the reporter missed. Getting the original audio cost about 40 minutes of work and completely changed the story. Most beginners make two mistakes with this approach. They treat the newspaper coverage as the primary source instead of a secondary account. Newspapers summarize. The summary is where errors hide. The second mistake is not checking the revision history of online articles. Many local papers edit stories after publication without marking changes. I found an archive tool called the Wayback Machine useful here but also paid for a service called Media Change Tracker that alerts you when specific URLs are modified. The paid version runs about $15 a month and saved me two separate investigations last year. The method also has hard limits. It does not work well for stories where the original newspaper coverage was minimal or nonexistent because there is nothing substantial to compare against. It also struggles when the underlying public records were redacted or destroyed. I ran into a case where a city cleaned out five years of planning commission emails before anyone requested them. Nothing in the workflow can force retention of materials that were never preserved. If your target story relies heavily on internal communications rather than public documents, this approach will only get you so far before you need to pivot to FOIA requests or on-the-record interviews.
When it works, it works fast. A focused audit of a three-month news cycle with about 20 published articles typically yields 2 to 5 verifiable discrepancies. That is enough material to build a follow-up story or a corrections request. The process does not require expensive tools. Your main investment is time spent reading primary documents rather than headlines.
Get the Full Details
Step-by-Step Workflow
Start by defining the scope. Pick a single subject, person, or event rather than trying to audit an entire department. A narrow scope makes the archive search manageable. I recommend keeping it under 90 days of coverage unless you have a team handling the workload. Next, run your newspaper search across at least two archive sources. NewsBank and your state's digital newspaper repository will cover different papers. Some regional outlets are on one platform while local weeklies are on another. Cross-reference the dates and headlines to make sure you have everything. This step usually takes 30 to 45 minutes. Then pull the public records. Start with whatever was cited in the articles, then expand outward. If a paper mentioned a council vote, get the full agenda packet. If it quoted a permit number, pull the permit file. These documents are usually free through county or municipal websites. You may need to visit in person for older physical records. I keep a running list of which offices require appointments and which allow remote requests.
After that, you build the discrepancy log. Go line by line through each article. Every factual claim should have a matching document citation. Anything missing goes into the tracker. This is tedious work but the payoff is high because most errors are small and easy to miss without a systematic check. A typical session produces about 8 to 10 flagged items per hour. Finally, verify before publishing or submitting. Take your top discrepancies and have someone independent review them. I usually ask a colleague to spot-check three items. This catches confirmation bias where you convince yourself a discrepancy matters when it actually does not. In my experience, about 30 percent of flagged items turn out to be minor or explainable once a fresh pair of eyes looks at them. The method scales poorly beyond local journalism. Statewide or national stories involve too many outlets and too much volume for a single researcher to handle systematically. If your goal is broader, you would need to combine this approach with automated text analysis or hire additional help. For local beats, it remains one of the most reliable ways to find something that was wrong, incomplete, or deliberately understated in the original coverage.
I continue to use this workflow periodically. It is not flashy. It does not generate quick hits or viral moments. What it does is catch things that matter to the people who live in the community and read those papers every day. That tends to be enough.
