Newsletter teams spend hours on subject lines and minutes on permissions. That’s backward, and most of the time it doesn’t matter. Then one day it does: a photographer emails about an image, a partner objects to their logo appearing beside a promotion, or a customer is surprised to see their private message quoted to thousands of subscribers.
None of those problems can be fixed by better writing. They’re permission problems, and they’re preventable with a habit that takes about five minutes per issue: list every asset and give it a status before you write around it.
This guide explains the method, why it works and how to fit it into a weekly or monthly newsletter without slowing anything down.
What counts as an asset?
More than most people think. An asset is anything in the issue that you didn’t create from scratch for this issue:
- Images and illustrations, including stock, screenshots and photos taken by staff or customers.
- Quotes, whether from customers, partners, authors, employees or public figures.
- Logos and brand marks belonging to other organizations.
- Embedded content, such as videos, social posts or charts.
- Excerpts from articles, books or reports.
- Links, especially to partner pages or time-sensitive offers.
Each one carries a question: are we allowed to use this, here, in this way?
Why has permission always mattered in publishing?
The rules around using other people’s work have been developing for centuries, and a few landmarks show how seriously the question has been taken.
The Statute of Anne. Passed in Great Britain in 1710, it’s widely regarded as the first copyright statute, giving authors rather than printers rights over their works for a limited term. It established the principle that creators have a say in how their work is reproduced.
Mark Twain before Congress. In 1906, Mark Twain testified before a congressional committee in favor of stronger copyright protection for authors, famously appearing in a white suit. Creators have long cared, loudly, about how their work is used.
“Happy Birthday to You.” For decades, the song was treated as copyrighted and licensed accordingly. In 2015, a U.S. federal judge ruled that the company collecting fees did not hold a valid copyright to the lyrics. Even one of the most familiar songs in the world turned out to have a complicated permission history.
The lesson for a newsletter isn’t to become a copyright expert. It’s to treat permission as a real question with a real answer, recorded before you send.
What’s the Cleared, Needed or Cut method?
For every asset in the issue, assign one of three statuses:
- Cleared: you created it, you licensed it, or you have explicit permission for this use. Note the basis: “our photo,” “stock license,” “permission by email, date.”
- Needed: you want to use it, but permission or licensing isn’t confirmed yet.
- Cut: removed from the issue, with a short reason.
Then apply one firm rule: nothing goes out with a Needed status. If an asset isn’t cleared by your production deadline, it’s cut, and the issue is adjusted.
That rule is what turns a list into a safeguard. Without it, Needed quietly becomes “probably fine,” and “probably fine” is how surprises happen.
How do you write around a cut asset?
Usually easily, especially if you know early. Cutting is far less painful when you list assets before drafting, not after. Common substitutions:
- A customer quote becomes a paraphrased theme: “Several readers told us they want more weekend events” instead of a named quote.
- A stock image becomes your own photo, or no image at all.
- A partner logo becomes a plain-text mention, with a link if appropriate.
- An excerpt becomes a summary in your own words with a link to the original.
In the fictional Harbor Ledger #14 example included with the Newsletter Issue Production Kit, an author’s quote from an email is marked Needed and then Cut when permission doesn’t come through. The editorial rationale is recorded plainly: cut the uncleared quote rather than invent permission. The issue still works. Nothing was lost except a risk.
How do you ask for permission quickly?
Most permission requests stall because they’re vague. “Mind if we share your nice note?” invites a polite non-answer. A clear request names exactly what you’ll use, where and when, and makes yes easy. An illustrative template:
Hi Dana, thank you for your note about the Saturday story hour. We’d love to quote this sentence in our newsletter going out Thursday the 14th: “My kids now ask for the bookshop before the playground.” We’d credit it as “Dana, a regular at story hour.” Is that okay? If you’d prefer no name, or would rather we didn’t use it, that’s completely fine too.
That message takes a minute to write and usually gets a same-day reply. Note the reply in the basis column with its date.
Three habits speed things up further:
- Ask early. Request permission when the asset goes on the list, not the day before sending.
- Offer options. Name, initials or anonymous. More options mean more yeses.
- Keep a standing permission list. Partners and regular contributors who’ve given blanket permission for certain uses can be marked Cleared quickly, with a link to the original agreement.
For agencies producing newsletters on a client’s behalf, add one more column: who confirmed the clearance. Client-supplied assets should be cleared by the client, in writing, so the record shows where each permission came from.
Which assets cause the most trouble?
In practice, six categories account for most permission headaches:
- Images found through search. “It was on the internet” is not a license.
- Quotes from private messages. A customer’s kind email to you isn’t automatically permission to publish it.
- Screenshots of other people’s content, especially social posts.
- Partner logos and co-branded offers, where the partner expects approval.
- Staff and customer photos, where the people pictured may not have agreed to appear.
- Reused assets from old issues, whose original permission may not extend to new uses.
Treat these as automatically Needed until you confirm otherwise.
Where do links fit into the asset list?
Links aren’t usually a permission issue, but they are an accuracy issue, and the asset list is a convenient place to track them. Record each important link with its destination and status. Then, during testing, click every link from a real test email to confirm it goes where intended. Partner and offer links deserve particular care, because they’re time-sensitive and often change.
How does the asset stage fit into production?
It comes second, right after the issue brief and before drafting. That order matters. If you draft first, you write paragraphs around assets you may not be allowed to use, and cutting them later means rewriting. If you list assets first, you know what’s safe to build on before you start.
A full issue production line runs: brief, assets and permissions, production, subject line and CTA, tests and checks, handover, and learning. The asset stage is small, but it shapes everything that follows.
What should the asset record include?
Keep it simple. For each asset:
- Description: what it is and where it appears in the issue.
- Source: who created or owns it.
- Status: Cleared, Needed or Cut.
- Basis: how it was cleared, such as “own photo,” “license,” or “email permission from [name], [date].”
- Notes: any conditions, such as credit lines.
The basis column is the one that pays off later. When someone asks months from now whether you had permission to use a photo, you’ll have the answer, with a date.
How does the Newsletter Issue Production Kit support this?
The Newsletter Issue Production Kit gives asset clearing its own tab, Assets & Permissions, alongside an Issue Brief, Production tracking, Subject, CTA & Tests, a Handover sheet that marks the issue “Issue Ready” only when nothing earlier is on hold, and a Learning Log. Checks include honest alt text for images and links that point to their intended destinations. A five-page guide explains the workflow, and the fictional Harbor Ledger #14 example shows every stage filled in, including the cut quote.
Quick answers
Do I need permission to quote a public article?
Short quotes with attribution and a link are common practice, but norms and rules vary by context. When in doubt, summarize in your own words and link to the source.
Is a stock photo automatically cleared?
Only within the terms of its license. Note the license source in the basis column.
What if permission arrives after the issue is sent?
Use the asset in a later issue. Never send first and ask later.
Clear it, then write it
The best newsletters are remembered for their writing. The worst are remembered for the one image or quote that shouldn’t have been there. A five-minute asset list, with every item marked Cleared, Needed or Cut, keeps you firmly in the first group.
Get the Newsletter Issue Production Kit and put permissions before paragraphs in your next issue. List the assets, clear what you can, cut what you can’t and send with confidence.
You’ll find the Newsletter kit, including the Assets & Permissions tab, on Content & SEO Workflows.
Leave a Reply