For Funders
Fund backbone reliability: warm handoffs, language access, and measurable follow-through without surveillance.
The 6-week cohort unit
CISAMN delivers in a contractable 6-week cycle that pairs practical learning with accompaniment and closure discipline so referrals become completed actions, not lists.
Procurement-ready cohort unit
Each unit is scoped with explicit inputs, auditable outputs, and a reporting cadence suitable for grant and procurement workflows.
Inputs
- Navigator time allocation and supervision cadence.
- Language access routing plan and escalation pathways.
- Verification cadence for partner resources and contact pathways.
Outputs
- Warm handoffs with documented statuses and completion checks.
- Step 3 follow-ups with barrier/action/checkpoint records.
- Friction logs and barrier register updates for partner action.
Reporting
- Monthly System Insight Brief (public edition).
- Partner-facing brief with operational recommendations.
- Aggregate metrics by default, with privacy-first controls.
Cohort structure
- •Weekly practice sessions (plain language, real scenarios, one-next-step design).
- •Navigator office hours for warm handoffs and preparation.
- •Step 3 follow-ups to confirm connection (and respond when connection did not happen).
- •System learning loop: friction logging -> barrier removal actions -> closure tracking.
Cohort outcomes
- •Higher referral completion (connections that actually happen).
- •Improved language access routing (what support is needed, when).
- •Fewer bounce-backs across systems (clear doors + closure loops).
- •Belonging loops: durable ties and a reliable point of return.
Outputs and impact
We report operational reliability using aggregate, privacy-forward signals focused on what changed in the system, not surveillance of individuals.
Warm handoffs
Counts and completion rates of warm handoffs (by channel), including language-access needs, reported in aggregate.
Barrier removal
Top barriers to connection and the actions taken to remove them, tracked as system frictions.
Friction logging
Where systems are hard to use under stress (forms, scheduling, language access, transport), captured as short observable notes.
Closure tracking
Whether a barrier changed, partially changed, or did not change and what will happen next.
What your funding enables
Funding supports Navigators, language access planning, and verification work that turns information into completion.
Consistent follow-up and closure loops so members have a dependable point of return.
Interpretation routing and translation of conversion-critical content, with a request path for long-tail languages.
System Insight Briefs: top frictions, what changed, what did not, and partner actions to improve reliability.
Trust and risk controls
Funders can review our public guardrails for privacy, operations, safeguarding, and scope before supporting implementation.
How funding scales
Choose the implementation tier that matches your scope and reporting needs.
Pilot cohort (single site)
One partner site, one 6-week cycle, with baseline reporting and process calibration.
Multi-site implementation
Partner network rollout with shared workflows, aggregate reporting, and barrier response routines.
Infrastructure support
Language access, verification, and measurement backbone to sustain reliability across sites.
Ways to support
Choose the pathway that matches your goals and reporting needs:
- •Fund a 6-week cohort cycle (delivery + language access).
- •Sponsor a partner implementation (libraries, adult education, municipalities, NGOs, employers).
- •Support verification + measurement (resource updates, dashboards, System Insight Briefs).
