Returned mail is not an address change request

When donor mail comes back, record the failed delivery before changing the address. Stop that address from entering the next mailing, then correct it only from a documented source. A returned envelope is evidence about one delivery attempt—not proof that the donor moved, died, or asked you to stop contacting them.

How to handle returned donor mail before editing the record

Keep the envelope long enough to preserve what your export actually produced. The useful record is small:

• donor or contact ID;
• exact name and address printed on the piece;
• campaign or appeal that produced it;
• return date and the carrier's nondelivery wording;
• source of any proposed correction;
• owner, disposition, and next action.

That snapshot matters because the address visible on a contact screen may not be the address used for the mailing. The export could have pulled an older household field, a stale report, or a source record you did not expect.

Address behavior also varies by system. Fundraise Up, for example, documents that its supporter address can be derived from recent donation or recurring-plan activity, and that later activity can replace a manual correction. The general lesson is not to copy that product's workflow. It is to identify which field drives your next export and record where the replacement address came from.

Give every return one of four dispositions

Do not make “clean up the address” a free-form task. Close each returned piece as correct, verify, suppress, or investigate.

Correct

Use this when you have a replacement address from a source your team accepts: the donor, a documented internal update, or an approved address-correction process. Save the source and effective date. Keep the previous address in history when your system supports it.

USPS describes Move Update as periodically matching mailing-address records with customer-filed change-of-address orders to reduce pieces that require forwarding or return. But a service may not return a new address in every case. USPS's current NCOALink provider information distinguishes services by the change-of-address data they receive; some can flag an older move without supplying the new address. Confirm the relevant mailing requirements and options with your mail provider.

Verify

Use this when you have a plausible correction but not enough evidence to replace the address. A missing apartment number, conflicting household information, or a donor-entered address that disagrees with a trusted record belongs here.

Assign a person and a next action. That might be a donor confirmation, a review of the source document, or a comparison with the address-correction output. Until then, keep the proposed address out of production.

Suppress

Use this when the current address is known to be undeliverable and no verified replacement exists. Suppress that address from direct-mail exports without deleting the donor or inventing a new address.

This is an address state, not a donor state. Salesforce's nonprofit address-management documentation provides one product example: an address can be marked undeliverable so it is excluded from mailings. If your system lacks an address-level flag, use a documented suppression field that your export can enforce.

Investigate

Use this when the pattern suggests a process failure rather than a single bad address. If a mailing produces an unusual cluster of returns, compare a sample of envelopes with the export, the contact record, and the file sent to the mail house. Check the report date, household logic, and whether address corrections were returned to your database.

Do not “fix” dozens of donor records until you know which handoff failed.

Keep the failure attached to one address

Returned mail should change only what the evidence supports.

A failed delivery does not create a donor communication preference. Keep the direct-mail suppression separate from the channel-and-purpose rules in your donor communication preference record.

It also does not prove that every person in a household moved. Review the person who received the piece before changing the shared view; a household can connect donors without combining their records.

Finally, returned mail is not evidence of death. A deceased-donor closeout requires verified information and a broader set of record changes. Until then, this remains an address case, not a deceased donor record.

Reopen mail only after one observable check

Before closing the task, preview the exact export that will feed the next mailing. The donor should either appear with the verified replacement address or remain excluded because the address is still suppressed. If the old address reappears, the correction was made in the wrong field or another source overwrote it.

That pass-or-fail check is the finish line. It turns a pile of returned envelopes into a controlled queue instead of a series of guesses.