COMMUNITY PARTICIPATION · Workflow idea

Understand participation without turning community conversations into surveillance.

For a community that has been clearly informed and has agreed to the activity measure, prepare limited participation counts for an explicit program such as an opt-in reward. Confirm group scope and participant preferences, avoid retaining message text or sensitive content, explain how counts affect eligibility, let people question or opt out of tracking, and set a short retention period with a responsible owner.

A Roman aqueduct taking shape from architectural sketch to marble.
A little structure. A clearer outcome.
Starts with
A community owner requests an opt-in participation summary
Produces
A limited activity summary with count definitions, participant choices, retention date, and owner review.
Category
Operations

01 / The starting point

A clear request.
A useful direction.

A group with clear notice, participant choice, and an approved purpose

“Measure agreed participation fairly without collecting more conversation data than the program needs.”
An example request · Make it specific to your team.

02 / The work

5 tasks.
One useful outcome.

Helps community organizers understand participation in a group program using disclosed, limited activity counts.

  1. Confirm the group and approved program purpose

    Limit measurement to the community and activity participants were told about.

  2. Explain participation measurement and choice

    Make clear what is counted, who sees the result, and how to opt out.

  3. Collect only the agreed activity count

    Avoid storing message text, media, or unrelated participant details.

  4. Review count accuracy and eligibility rules

    Check duplicates, exclusions, accessibility needs, and program criteria.

  5. Approve retention and any reward decision

    Have a community owner verify the outcome and delete data on schedule.

03 / The result

Something useful.
Something to build on.

A limited activity summary with count definitions, participant choices, retention date, and owner review.

AmbactiWorkflow folio · 5 steps

Measure consented community participation

Operations · Example outcome

The handoff

A limited activity summary with count definitions, participant choices, retention date, and owner review.

Keep in mind

Message counts reveal behavior and may be inaccurate or unfair when people have different access needs. Obtain informed consent, follow group and platform rules, avoid collecting message content, provide a correction and opt-out path, and do not use counts for unrelated profiling or discipline.

04 / Make it yours

Set the brief.
Set the standard.

A few choices shape the work around your team.

Document notice, consent, and opt-out choices

Explain the measure before participation is tracked.

Define minimal fields and count rules

Record only identifiers and activity details required for the stated program.

Set access and short retention periods

Keep participation records private and delete them when no longer needed.

Assign a community review owner

Name who handles corrections, opt-outs, and reward decisions.

Keep exploring

Put your next idea to work.

Start with your brief. Make the process your own.

Explore more workflows ↗