How to Build a Source Folder for a Press Release Campaign

A source folder is a single organized place — one shared drive folder, one document, whatever your team actually uses — that holds the verified facts and signed-off permissions a press release needs before it goes anywhere near a newswire. Build it before you write a word of the release, not after a draft comes back with questions you can't answer. Most of the delay I see on release campaigns isn't writing time. It's someone scrambling on day three to find a source for a number, or realizing nobody actually confirmed a spokesperson was okay being quoted.

Why This Is a Distribution Requirement, Not Busywork

Newswire services aren't publishing your release as a favor. They're accepting it as a factual company announcement, and content standards say so directly. Marketing by Kevin's own press release service terms, which lay out ACCESS Newswire's content standards for submissions, describe the requirement this way: copy must read as “a factual company announcement, not an advertisement,” in “an objective, news-style tone,” and “facts, numbers, quotations, rights, and links are accurate, supportable, authorized.” That word — authorized — is doing real work. It means someone said yes before you quoted them, not after.

Google's search spam policies point at a related requirement from a different angle. Under its Site Reputation Policy, sponsored or promotional content needs “explicit acknowledgement of ownership or responsibility” and disclosed commercial character. Under its separate Link Spam policy, paid links inside that content need to be qualified with a rel=”nofollow” or rel=”sponsored” attribute rather than passing ranking credit. A release built on unverifiable claims or undisclosed sourcing isn't just a content-quality problem — it's the kind of thing that gets a release rejected at intake, or gets a domain's broader reputation flagged.

One more distinction worth being precise about: getting a release accepted and distributed by a newswire is a production and distribution outcome. A journalist or outlet independently deciding to cover your story afterward is a separate, unguaranteed outcome. A well-built source folder helps with the first. It has no bearing on the second.

What Goes in the Folder: Facts

The facts side of the folder is every claim in the release traced back to something you can point to. That includes:

• Numbers and data points — sales figures, dates, study results, survey stats — each one linked to its original source, not a secondhand summary of it.
• Product or service specifics — what something does, what it's made of, what it costs — pulled from your own current documentation, not last year's version or a competitor's marketing copy.
• Comparative claims — anything that says “first,” “only,” “leading,” or “more effective than” needs the data behind it sitting right next to the claim, because a newswire reviewer or a skeptical journalist will ask for it.
• Third-party references — a study, a news mention, an award — cited with a link to the actual source, not a paraphrase of what someone told you it said.

If a fact doesn't have a source you can produce on request, it doesn't go in the release yet. Either find the source or cut the claim. That's what “supportable” means in a content standard, and it's the difference between a release that clears intake on the first pass and one that bounces back with a request for substantiation.

What Goes in the Folder: Permissions

Permissions are the part teams skip, and it's the part that causes the most expensive delays. Before a release goes to production, confirm:

• Quote approval — every person quoted has seen their exact quote and signed off on the wording, not just the general idea of being quoted.
• Speaker authorization — the person quoted actually has the authority to speak for the company on that topic. A department lead commenting on a company-wide financial claim is a mismatch worth catching early.
• Media rights — any photo, logo, or video included has documented rights to use it in this context, including rights from a third-party photographer or agency if one was involved.
• Legal and compliance sign-off — for anything touching regulated claims, financial figures, or pending matters, confirm the release has cleared whoever handles that internally before it's treated as final.

A Simple Source-Folder Index

You don't need special software for this. A folder with a short index document works. For each release, track:

1. Claim or quote (exact wording as it appears in the release)
2. Source (link, document, or named contact who can confirm it)
3. Permission status (approved, pending, or not required)
4. Who confirmed it and when

Four columns. That's the whole tool. What matters is that every claim in the release has a row, and every row has an answer in the source and permission columns before the release moves to submission. If a row is blank, that claim isn't ready.

What's Known, What's Still Route-Specific

What's consistent across routes: newswires expect facts to be supportable and quotes to be authorized, and search platforms expect commercial content to be clearly disclosed. What varies is how strict a given route's intake review is, and that's not something to guess at — if you're working with a specific distribution route, confirm its current content guidelines directly rather than assuming one route's standard applies to another. Standards get updated, and the safest move is checking the live guidelines for the route you're actually using before you finalize a release.

The Next Practical Decision

Before you start writing, decide which category your release falls into: a straightforward company announcement, or something claim-sensitive — health, financial, or supplement-related content, for example — that needs a closer evidence review before it goes anywhere. That decision changes how much substantiation your source folder needs and how long the review step should take. Getting it right at the start is faster than finding out at intake.

At Marketing by Kevin, our press release service handles the search planning, production management, route preparation, and reporting once your source folder is ready — the facts, authorization, and supporting documents are the customer's responsibility to supply and confirm, the same as they'd be with any newswire route. Our press release service terms lay out exactly what's required and what isn't guaranteed, and I'd rather you read that in full than take my word for a summary of it.