Side by side
| Question | Email distribution lists | RAID |
|---|---|---|
| Who receives a product? | Whoever is on the list today, plus anyone it gets forwarded to. | Members of the communities the analyst targets, and no one else. |
| Keeping the audience current | Manual list edits; transfers and retirements are easy to miss. | Vetted access requests, role-based membership, scheduled requalification, and automatic disabling of dormant accounts. |
| Did it arrive and was it read? | Not knowable. Read receipts are optional and unreliable. | Delivery and readership are recorded for each product and each recipient. |
| Finding an older product | Search your own inbox, if you still have it. | One searchable, access-controlled feed of every product. |
| Leaks | Every copy is identical, so the source is hard to trace. | Recipient watermarking deters sharing and helps attribute a leaked copy. |
| Access when someone leaves | They keep every product already in their mailbox. | Access is revoked centrally; with Microsoft SSO, immediately when their agency account is disabled. |
| Reporting to command and funders | Counts of emails sent. | Reach and engagement by product, community, and partner agency. |
| Audit trail | Mail server logs, if retained. | Access, membership, and security events logged and retained. |
Where email still fits
Email is good at notification. RAID uses it that way: recipients can get an email that a new product is available, or a daily briefing, and then read the product itself in RAID where access is controlled and readership is recorded.
What changes for analysts
Analysts stop maintaining contact spreadsheets. They publish a product once, choose the communities that should receive it, and can see afterwards who opened it and which partners may need a follow-up call.
What changes for stakeholders
Partners get one place for every finished product, on a phone or a desktop browser, scoped to their role and communities, instead of digging through forwarded messages.
Moving off email lists
A typical rollout loads your existing partners as users, organizes them into communities that mirror your current lists, and runs RAID alongside email for a short period. Welcome and reminder emails guide each person through first sign-in.