Deceased Donor Suppression

The last thing a grieving family should receive isa fundraising letter.

Breakwater is working with a small group of nonprofit design partners on an evidence-first workflow for reviewing deceased-donor risk before a mailing.

Invitation-only  ·  Assisted onboarding  ·  Human review required

She donated loyally for eleven years. She deserved better.

Invited
Approved workspaces only
CSV
Batch workflow
Human
Ambiguity stays in review
Audited
Decisions keep context
The Process

A careful, review-first workflow

Design partners start with a historical sample, validate the available evidence, and keep a person in control of every uncertain decision.

1

Upload your CSV

Prepare a constituent CSV using the template agreed during onboarding. The beta workflow checks required fields before a scan begins.

2

Review available evidence

Breakwater organizes the signals available for your pilot and explains the resulting classification. Conflicting or insufficient evidence stays visible:

High Confidence DeceasedNeeds Human ReviewLikely Alive
3

Record decisions & export

Your team reviews uncertain records and records its decisions before downloading a tenant-scoped suppression CSV for a controlled handoff.

Start Carefully

Prove the workflow before a live mailing

Design partners begin with a historical sample and known outcomes. Together, we examine where evidence is available, where it conflicts, and how much review your team should expect.

A pilot is scoped to one workflow and an agreed data set. Breakwater does not update your source systems or make unattended CRM changes.

Before any real campaign use, your team reviews the results and makes the final suppression decision.

Small
Invitation-only cohort
First
Historical sample validation
Always
Human approval before handoff
Not a Black Box

You see exactly why we flagged someone

Breakwater keeps each available signal with its source context and shows how evidence contributed to a classification. Your team retains control.

  • Source and observation context retained for available signals
  • Match details and evidence conflicts shown for record-level review
  • Conservative classifications when evidence is insufficient
  • Manual reviewer decisions retained in the audit history
  • Tenant-scoped suppression CSV for an explicit downstream handoff
Illustrative Review RecordNeeds Human Review
Example Constituent
Sample data  ·  Not a source-coverage claim
Evidence Signals
Customer-provided history

Name and address supplied

Context retained for review

Available
Returned-mail signal

Imported pilot evidence

Source date displayed

Partial
Reviewer decision

Conflicting evidence remains visible

Operator action required

Pending
Design-Partner Beta

A focused pilot, built alongside your team

Access is approved individually. Pilot scope, supported evidence, data handling, and commercial terms are agreed before a workspace is provisioned.

Pilot scope
One workflow
Historical sample first

Start with one mailing use case and learn where available evidence is useful before relying on a live campaign result.

  • CSV upload validation
  • Scan summary and warnings
  • Record-level evidence review
  • Explicit pilot exclusions
  • No automatic source-system changes
Discuss Your Use Case
Decision control
Human-reviewed
Conservative by design

Ambiguous and conflicting evidence remains visible so your team can make and document the final decision.

  • Review queue
  • Evidence context
  • Recorded reviewer decisions
  • Audit history
  • Suppression CSV handoff
Schedule a Walkthrough
Design partnership
Direct feedback
Small beta cohort

Partners share workflow feedback and discrepancies so we can measure what works before expanding the product.

  • Named operator and owner
  • Guided result review
  • Discrepancy feedback loop
  • Beta support channel
  • Controlled rollout
Apply to Partner
Request Access

Apply for the design-partner beta

Tell us about your nonprofit, your mailing workflow, and a historical sample you could use for validation. We review each request before provisioning access.