Use cases for Communities
See how organizers can structure a Space, operate trustworthy Missions, and build repeat participation around real outcomes.
A Community owns the distribute, verify, and report stages of one shared program lifecycle, and hosts every other stage in its Space.
Launch one clear Mission
Scenario. An organizer wants Members to complete a specific local, learning, service, or contribution action.
Problem. Broad goals are difficult for Members to understand and difficult for reviewers to judge consistently.
How ZYNC works. The team defines a Space boundary, assigns only the access each teammate needs, and publishes one Mission with explicit eligibility, timing, proof, decision, reward, capacity, and challenge terms. The planning guides cover how to structure a Space, prepare a first Mission, and write proportionate verification rules.
Expected outcome. Members and reviewers work from the same visible definition of success, reducing avoidable ambiguity before submissions begin.
Relevant capabilities. Spaces, team permissions, Mission authoring, verification policies, capacity, and reward terms.
Next step. Draft the decisions listed in Your first Mission.
Turn a useful action into a repeat rhythm
Scenario. A community has found an action Members value and wants to repeat it weekly, monthly, or as a series.
Problem. Streaks and reminders can create shallow activity when they are not tied to a meaningful community habit.
How ZYNC works. The team keeps the qualifying action stable, chooses a predictable cadence, and uses reminders, milestones, invitations, and recognition to support the action. Each cycle can be reviewed through separate measures for discovery, completion, decision quality, return, and reviewer load. See the guide to recurring rituals and the principles for trustworthy discovery.
Expected outcome. The community gets a repeatable operating rhythm that can be improved without hiding terms or pressuring Members to remain active.
Relevant capabilities. Recurring Missions, discovery, invitations, streaks, milestones, and Community insights.
Next step. Use the insights and reports guide to attach each measure to a decision.
Operate a Sponsor-funded outcome
Scenario. A Sponsor wants to support an outcome that already fits the community’s purpose.
Problem. Funding, Member terms, verification, reporting, and refunds can drift apart when they are negotiated as separate promises.
How ZYNC works. The Community and Sponsor agree on an outcome, eligible audience, Missions, proof, budget, flat fees, evidence access, and exception rules before launch. The community keeps ownership of its Member experience while the Sponsor receives the agreed, privacy-safe evidence. Follow the documented sponsorship operating cycle, reward-funding decisions, and Sponsor proof-pack structure.
Expected outcome. The campaign has one accountable path from terms and funding through verified outcomes, exceptions, and closeout.
Relevant capabilities. Campaign terms, reward funding, Mission verification, Sponsor access boundaries, reports, reversals, and refunds.
Next step. Map the full cycle in Run a sponsorship.