Structured, longitudinal programs inside your private network — named the way your community names them.
A mission is not an event — it lasts two years, has a cohort of participants, a coordinator, a location, and a status that changes over time. A language apprenticeship cohort is not a calendar entry — it has enrolled participants, a master speaker and an apprentice, a schedule that runs for months, and outcomes the community cares about tracking. A heritage summer camp has registration, roles, a curriculum, and a record of who attended and what they learned.
ECO's Community Programs feature is built for the structured, ongoing work that holds a community together across time — the kind of commitment that doesn't fit in a single event, and doesn't disappear when a single date passes. It runs alongside the Events feature: events are one-off gatherings; programs are sustained, enrolled, reported.
The vocabulary is yours. The system calls it a Program; your community calls it whatever is right — Mission, Cohort, Seva, Chantier, Ngā Kura, Campaign. The label is set by the program coordinator, not the platform.
Not a project management tool. The sustained work your community was already doing — now tracked, visible, and reportable.
Title, type, description, start and end date, coordinator name, and the number of spots available. If the program has a community-specific name — Seva, Mission, Cohort — that label is set here and used everywhere in the network instead of the generic "Program." The program appears on every member's events tab immediately.
Members tap Enroll and join the cohort. The coordinator assigns roles — participant, mentor, apprentice, elder guide, language keeper, observer. Each role can carry a custom label the community chooses. The program tracks who is in it, in what role, from when, and whether they've completed.
Unlike an event, a program has a sustained lifecycle — active, paused, completed. A youth mission might run for two years. A language cohort might run for a single season. A service program might recur annually. The program stays visible to the network throughout, accumulating the record of who participated and what was accomplished.
Programs marked grant-reportable contribute to the Metrics Dashboard — enrollment numbers, completion rates, participant counts by month. For TBCP Use & Adoption awards, tribal language programs, or any community receiving grant funding, the data that program officers ask for is collected automatically as the program runs, not assembled at the end in a hurry.
The Latter-day Saint community organises youth missions that span two years in a specific location — a person is called, serves, and returns. The Missionary Wall tracks who is currently serving, where, and since when. Returned missionaries are honoured. The community prays for those who are away. The program is not administrative — it is devotional, and the system treats it that way.
When a program completes, it doesn't disappear — it joins the community's archive. Who participated. What roles they held. What the outcomes were. The language apprenticeship cohort of 2026 becomes part of the record the community is building for the people who come after. The work is done; the evidence of the work is permanent.
ECO recognises eight program types — but the type is a structural hint to the system, not a constraint on your community. Every type supports the same core features: enrollment, roles, schedule, outcomes, and grant reporting.
Youth missions, service missions, community outreach programs. Tracks called, serving, and returned status. Used by Latter-day Saint communities, Catholic service organizations, and any faith community that sends members out on sustained service.
A structured group working to learn, document, or transmit an endangered or heritage language. Tracks master speakers and apprentices. Connects naturally to the Language Preservation feature and the Cultural Vocabulary Library. Ideal for tribal nations running TBCP-funded programs.
Recurring or sustained community service — a Habitat for Humanity build season, a community garden program, an elder care visiting program, a food pantry rotation. Different from a one-off event in that it runs over time, has enrolled participants, and produces reportable outcomes.
A structured program — often annual — where cultural knowledge, traditional skills, language, and practice are transmitted to younger members. Registration-based, with roles (elders, youth, facilitators), a schedule, and outcomes worth keeping in the community's record.
A structured pairing between a knowledge holder and a learner — a traditional skill, a trade, a cultural practice, a language. Works alongside the Mentor & Apprentice feature for matching; Programs tracks the cohort-level record.
A program specifically created to fulfil the Use & Adoption requirements of a grant award — TBCP, BEAD, AFCP, NEH, Mellon, or other. Grant-reportable flag enabled by default. Enrollment, participation, and completion data feed directly into the Metrics Dashboard for programmatic reporting. The work of running the program and the work of reporting on it are the same work.