New World Survival · Network design
Interfaith Disaster Network Charter Workbook
Define a shared purpose, member authority, verified capabilities and a practiced request process without creating authority over member institutions.
Purpose
1. Name the operating problem
Network name
Geographic area
Convening organization
Public emergency partner
One-sentence purpose
Explicit non-scope
Members
2. Record authorized representatives
| Institution | Representative | Backup | Authority limits | Confirmation date |
|---|---|---|---|---|
Participation and withdrawal rules
Charter
3. Agree on how the network operates
- Members retain their own governance and property authority.
- No member speaks for another tradition or institution.
- Offers require confirmation for each activation.
- The network name cannot be used for fundraising or public promises without approval.
- Private contacts and capability details have access and sharing rules.
- Assistance is not conditioned on belief or participation.
- Shared relief work is not used to proselytize or recruit.
- Concerns, corrections and withdrawal have a documented process.
Decision method and quorum
Capability directory
4. Verify offers and conditions
| Institution | Category (space, people, equipment, reach) | Possible offer | Authority | Conditions and limits | Last verified |
|---|---|---|---|---|---|
A directory entry is not permission to deploy it.
Confirm space, people, equipment and reach through the member's authorized representative for every activation. Ask every member to confirm its lines twice a year.
Customs page
What each member needs respected
| Institution | Days and times not available | Food | Spaces and dress | Forms of address and languages |
|---|---|---|---|---|
Ask, do not assume
Each member fills in its own line. Nobody fills in a line for another tradition.
Each member fills in its own line. Nobody fills in a line for another tradition.
Activation
5. Write the contact and decision sequence
| Step | Responsible role | Method | Time target | Backup |
|---|---|---|---|---|
| Verify incident and partner | ||||
| Notify representatives | ||||
| Collect status replies | ||||
| Route and confirm requests | ||||
| Issue shared update | ||||
| Close and review |
Request record
6. Make handoffs auditable
| What is needed | How much | Where | By when | Who is asking | Receiving institution | Conditions | Status and close time |
|---|---|---|---|---|---|---|---|
MOU discussion checklist
Settle material commitments before signature
- Purpose, parties, term, review date, amendment and termination
- Activation request, acceptance and authorized contacts
- Property, rooms, hours, keys, access and restoration
- Operator, staffing, supervision, safeguarding and credentials
- Licensure and certification
- Supplies, equipment, transportation and replacement
- Public messages, branding and representation
- Private information, records, retention and permitted sharing
- Costs, compensation, reimbursement, donations and financial reporting
- Insurance, liability, indemnity and required legal review
- Safety, accessibility, closure, transfer and dispute resolution
Questions requiring qualified review
Information controls
7. Protect contacts and institutional details
Directory custodian
Access approval
Review frequency
Deletion or archive rule
- Public and restricted information are separated.
- Contact lists are not forwarded outside approved roles.
- Building details are shared only for a defined request.
- Incident records contain no unnecessary personal information.
- Outdated copies are withdrawn and deleted.
Exercise
8. Test the network before relying on it
| Test | Expected result | Finding | Correction owner | Retest |
|---|---|---|---|---|
| After-hours notification | ||||
| Capability confirmation | ||||
| Request acceptance or decline | ||||
| Accessible shared message | ||||
| Public partner handoff | ||||
| Closure and record return |
Approval
9. Confirm readiness and review dates
- Purpose and non-scope are approved.
- Representatives have documented authority and backups.
- Capabilities include conditions and verification dates.
- The public emergency partner knows the network.
- Activation and request procedures passed an exercise.
- Information controls and public representation rules are active.
Convening lead
Date
Member approval method
Next review