Rules
Part of Nonprofit marketing strategy: the choices behind public claims and donor trust
Write the charter first: nonprofit marketing strategy development
How to write a one-page charter for nonprofit marketing strategy development: audience, channels, budget, evidence and owner, with a worked example and the US email, text and charity-registration rules.
A nonprofit marketing strategy becomes actionable when the team records its choices before producing campaign material. The charter should connect the intended audience and mission outcome to objectives, channels, tactics, budget, evidence, donor-information handling, ownership, and review. Leave unknown entries open for a decision rather than filling them with assumptions.
Define the scope of the work
A charter is useful when it defines what the work is meant to accomplish and what the team has authority to do. Start with the program-related change, intended audience, and limits. Those decisions guide later marketing choices and prevent an incoming request from quietly changing the campaign.
| Weak version | Better version |
|---|---|
| Describe the work as broad awareness, without naming an audience, intended change, or limits. | Identify the audience by its situation, state the program-related change sought, and record what the campaign includes and excludes. |
| Let each new request redefine the campaign purpose. | Require an explicit scope decision before a request becomes part of the approved work. |
Use this fill-in charter as the working record. Complete the entries before copy is written; where a decision is not yet made, record that it remains open. This makes the strategy usable without inventing an objective, spending amount, channel, or tactic that the team has not approved.
| Charter field | Entry to complete |
|---|---|
| Objective | The intended mission or program outcome and how the campaign will recognize progress |
| Audience | The group and situation the communication addresses |
| Channels | The approved routes for reaching that audience |
| Tactics | The planned activities within each selected channel |
| Budget | The approved amount or a note that approval is pending |
| Scope | Included work, exclusions, and limits on claims |
| Evidence | Source, retrieval date, and verifier for each objective public claim |
| Donor information | Route from form to CRM to email platform, including where permission is captured |
| Owner | Named approver and person responsible for resolving scope questions |
| Review | Observations, evidence limits, and the decision to continue, change, or stop |
A completed charter, as an illustration
The following example is hypothetical, for a small food-pantry nonprofit, and every figure is invented to show the format. Replace each entry with your own approved decisions.
- Objective:grow monthly donors from 120 to 160 in 12 months, with retention at six months as the progress check.
- Audience:donors who gave twice in the last 24 months but not monthly.
- Channels:email, the donation page, one social channel, and follow-up after the annual event.
- Tactics:a four-email series explaining monthly giving, a monthly option set as the default on the donation page, and a thank-you call to new monthly donors.
- Budget:$12,000 for the year, split for illustration as 50 percent email and CRM tools, 25 percent paid social, 15 percent event follow-up and 10 percent held for testing.
- Review:at day 90, count new monthly donors, cost per new monthly donor and unsubscribe rate. The stop rule: pause a tactic if its cost per donor exceeds the first-year value of that donor's gifts.
Name the audience and its journey
An audience description should help the team decide what belongs in the campaign, not simply name anyone who might care. Tie the intended audience to the program purpose, then state which requests or activities fall outside the approved boundary. This gives writers and reviewers a consistent basis for judging proposed material.
Segment by donor stage: prospects who have never given, first-time donors, repeat donors, monthly donors and lapsed donors. Each stage needs a different message. See mapping the donor journey, donor acquisition and donor retention for how each stage is measured.
| Weak version | Better version |
|---|---|
| Address everyone who could have an interest and leave the purpose open to interpretation. | Describe the audience by its situation and connect the message to the program-related change the campaign supports. |
| Treat every later request as an automatic expansion of scope. | Record whether a request is included, excluded, or awaiting a decision from the charter owner. |
The charter and handoff checks shown below should travel with the approved scope. A saved file is not necessarily usable by the next role: specify what that role needs and record whether the supplied material meets those requirements. The common strategy questions can help surface choices that need an owner.
Charter and handoff completion checks
- Audience named
- Mission outcome named
- Evidence that changes plan
- Person who can halt work
- Owner signs the scope
- Each claim has a citation
Choose channels, tactics and budget
Objectives, channels, tactics, and budget are strategy decisions, not details to leave for whoever writes the first message. Connect the objective to the program outcome, then pick channels that fit the audience: email for existing donors, social media for reach, events and peer-to-peer fundraising for community networks, direct mail for older donors, and text for supporters who have opted in.
There is no universal budget split. Start from last year's net revenue by channel and your cost per donor, and record the approved budget. If a choice is unsettled, mark it as pending instead of implying approval.
| Weak version | Better version |
|---|---|
| Use a general objective and let each contributor choose a channel or activity independently. | State the intended outcome, then document the selected channels, tactics, and budget alongside the audience and scope. |
| Treat a participation figure or attention as proof that the mission outcome was achieved. | Review participation and cost alongside mission contribution, evidence quality, and the limits of the claim. |
Use the wider nonprofit marketing strategy guide to frame the choices, then keep this campaign charter as the approved record. The strategy checklist can support file review, but it does not replace a decision about objectives, channels, tactics, or spending.
Keep evidence beside public claims
Every objective public claim needs a source, a retrieval date, and a named verifier before publication. Agreement among colleagues or polished wording is not evidence. Record these details together so a reviewer can trace a number and remove a claim when its source cannot be produced.
| Weak version | Better version |
|---|---|
| Publish a factual statement without identifying its source or the person who checked it. | Keep the source, retrieval date, and verifier for each objective claim in the evidence record. |
| Retain a program figure when nobody can show where it came from. | Identify who supplied the figure and remove the claim if its source cannot be produced. |
Misleading appeals can draw scrutiny from state charity regulators, so keep proof for every figure. For example, if a draft says a gift feeds 40 families (a hypothetical claim), the charter must record who calculated that number, from which program costs, and when. Keep the source for each number beside its retrieval date and verifier; do not leave an untraceable program figure in donor-facing copy.
Claim substantiation before donor copy
- Claim drafted
- Source located
- Date pulled recorded
- Verifier named
- No source: claim removed
Trace donor information and the US rules that apply
For a US campaign, map the donor information route from the form through the CRM and email platform, and mark where permission is captured. A software setting alone does not show what permission was recorded.
Four US rules belong in the charter. First, CAN-SPAM governs commercial email: a plain fundraising appeal may fall outside it, but a message promoting event tickets, merchandise or paid services is covered, and many nonprofits follow it anyway with an honest sender line, a postal address and an unsubscribe honored within 10 business days. Second, the Telephone Consumer Protection Act (TCPA) treats nonprofit status as no blanket exemption: automated fundraising texts generally need prior express written consent.
Third, about 40 states plus the District of Columbia require charities to register before soliciting their residents, and an IRS exemption does not replace that. Check the registration status for each state where you solicit; see our guides for California, New York, Texas and state donor privacy laws.
Fourth, IRS substantiation rules shape the wording of the ask. IRS Publication 1771 explains the written acknowledgment a donor needs for a single gift of $250 or more, and the written disclosure a charity owes when a donor receives goods or services for a payment above $75. Have qualified counsel review the mapped route against these rules before launch. For Canadian donors, a different regime applies; see CASL consent rules.
| Weak version | Better version |
|---|---|
| Assume the team knows how donor information moves or that a platform setting proves permission. | Draw the route from form to CRM to email platform and mark the point where permission is captured. |
| Apply a Canadian checklist to a US campaign without checking which jurisdiction and requirements apply. | Identify the jurisdictions in scope, then have qualified counsel review the mapped route against applicable donor-information and permission requirements. |
Assign authority for changes
Name one person who can approve the scope and settle conflicts. A shared committee may contribute, but the record should still identify who has authority to resolve an exception. Keep the approved scope, exclusions, owner, and decision in a versioned file so later changes can be distinguished from the original authorization.
| Weak version | Better version |
|---|---|
| Treat the charter as an informal intention with no named approver or record of authorization. | Have the named owner approve the scope before copy is written and preserve the approved version. |
| Replace the original scope whenever a new request arrives. | Record whether the request was approved, excluded, or left undecided, and identify who will resolve it. |
| Count a file being sent as a complete handoff. | State what the receiving role needs and record whether the material meets that requirement. |
When the team reviews the file, record the correction needed and the person responsible for it before the next communication proceeds. This makes a missing input visible before it becomes a donor-facing problem. Protecting donor trust belongs in the decision record alongside scope and evidence, not as a substitute for either.
Record the decision after review
A review should end with a clear decision to continue, change, or stop. Consider participation, cost, mission contribution, quality, exclusions, and source limits together. None of these observations can make an unsupported statement acceptable or stand in for evidence about the program outcome.
| Weak version | Better version |
|---|---|
| Record results without saying what the team will do next. | State whether the work continues, changes, or stops, and record the reasons and evidence limits. |
| Favor attention when the underlying program claim remains uncertain. | Keep the mission outcome, source trail, approved scope, and limitations visible in the final review. |
Bring the approved scope, named owner, source trail, observations, and decision into one record. That makes it possible to distinguish authorized work from later changes and explain why the donor-facing message reflects the program. A charter that records choices before production can guide strategy development without turning assumptions into commitments.
