← Back to Church & Community Trust Hub
WSI/CES Church & Community Trust Hub

Partner Readiness Self-Assessment Checklist

Source: km-base · Partner-Readiness-Self-Assessment-Checklist-v0-2026-07-02 · Effective: 2026-07-02

Use this checklist to assess your organisation's readiness before requesting a briefing. Completing it does not authorize any program, data collection, system access, matching, exchange, CES transaction, local church MCP, or federated MCP deployment. It is preparation only.

0. Organisation Information

Organisation name
Location / city
Type of organisation
church / ministry / NGO / community partner / other
Named steward (accountable contact)
Backup contact
Date completed
Current readiness level (select one)

1. Overall Declaration

Complete all sections first, then select one:

2. Biblical AI Governance Boundary

Question PASS WARN STOP
We understand AI/digital systems are servant instruments, not masters.
We understand AI may not replace God's authority, human conscience, pastoral discernment, consent, or protection of the vulnerable.
We will not represent AI output as pastoral, legal, clinical, financial, eligibility, or matching authority.

3. Organisation and Role

Question PASS WARN STOP
Our organisation has a clear local role and defined community it serves.
We can name an accountable steward and backup contact.
We understand readiness is preparation, not program enrollment or operational approval.
We will not claim WSI/CES matching, exchange, CES transactions, or MCP federation are live.

4. Eligibility

Question PASS WARN STOP
Our mission aligns with community wellbeing and SDG 11/16/17.
Leadership can review governance, privacy, safeguarding, and consent boundaries.
We can participate in periodic review and accept suspension or rollback if needed.
We can prepare non-identifying evidence without participant data.

5. STOP Conditions

Any YES answer means the result is STOP. Contact [email protected] before proceeding.

Condition YES NO
We need AI/digital systems to decide about people or programs.
We cannot name a responsible human steward.
We intend to collect participant data before approval.
We cannot define safeguarding or escalation contacts.
We cannot accept privacy, audit, renewal, suspension, or rollback controls.
We need live matching, exchange, CES transactions, or MCP deployment now.

6. Consent and Privacy Readiness

Question PASS WARN STOP
We can explain what data would be collected in a future approved pilot and why.
We can explain who would review it and how consent would be obtained and withdrawn.
We understand consent must be informed, specific, and withdrawable.
We can support data minimization, retention limits, and suppression or removal.
We understand participant data remains not authorized now.

7. Vulnerable-Person Protection

Question PASS WARN STOP
We can identify vulnerable-person contexts in our community (children, elders, people in crisis, financially vulnerable people).
We can protect children, elders, people with disabilities, people in crisis, and financially or socially vulnerable people.
We will not use AI for profiling, eligibility, clinical inference, pastoral inference, or automated decisions about people.
We have a human escalation path for harm, coercion, complaint, or consent uncertainty.

8. Safeguarding and Escalation Contacts

Safeguarding lead (name / role)
Backup safeguarding contact
Privacy concern escalation path
Pastoral / community concern escalation path
WSI/CES steward contact path
Incident notes can avoid sensitive details: PASS    WARN    STOP

9. Data Classification Readiness

Data class PASS WARN STOP Notes
Public (published mission, service hours)
Governance metadata (steward name, review dates)
Internal partner notes (non-sensitive)
Community-sensitive (needs, risks, vulnerabilities)
Participant data (names, contact, health, care, pastoral, financial, legal)STOP unless separately approved
Secrets (credentials, tokens, keys, private infrastructure)PROHIBITED

10. Local Evidence-Pack Readiness

Do not include: participant data, pastoral notes, prayer requests, secrets, raw submissions, databases, Qdrant/n8n payloads.

Evidence item PASS WARN STOP
Partner identity and steward roster
Mission and community context
SDG 11/16/17 alignment note
Governance meeting record
Consent / privacy readiness notes
Safeguarding and escalation map
Data classification table
Human reviewer roster
Rollback / withdrawal path

11. MCP / Federation Boundary

Question PASS WARN STOP
We understand WSI/CES central MCP is a read-only governed context layer.
We understand this checklist does not authorize local church MCPs.
We understand this checklist does not authorize federated MCP deployment.
We understand any future MCP step requires the Federated MCP Standard and separate Founder approval.

12. Final Self-Assessment

Decision (select one):
Rationale / notes:
Prepared by (name / role):
Review requested from WSI/CES (what you need / what questions remain):

Contact: [email protected]  ·  WSI/CES Community Cloud  ·  SDG 11 / 16 / 17

Source: km-base · Partner-Readiness-Self-Assessment-Checklist-v0-2026-07-02

Completing this checklist does not authorize any program, data collection, system access, matching, exchange, CES transaction, local church MCP, federated MCP, or runtime change. Preparation only.

How to Submit for Briefing Review

  1. Complete all sections — work through sections 0–12, marking PASS / WARN / STOP for each item.
  2. Save or print — click Print / Save as PDF below and save a copy for your records.
  3. Email your submission — use the button below to open a pre-addressed email to [email protected]. Include your final self-assessment result and attach the PDF if possible.
Submit Self-Assessment — [email protected]

Submitting does not authorize any program, pilot, data collection, system access, matching, exchange, CES transaction, local church MCP, or federated MCP. It opens a briefing conversation only.

Use your browser's Print dialog and select "Save as PDF" to download.