Collect chapter updates, event records, member feedback and interviews in one connected history. Compare participation and renewal while keeping the local explanation behind each result.
WHO IT’S FORAssociation and federation operations, membership leaders and chapter-support teams coordinating recurring data collection across a network.
WHEN IT MATTERSMember lists, event records and local updates do not line up when a renewal or board-reporting cycle begins.
Where did participation fall, what do local notes explain, and what happened after the chapter changed its program?
| Chapter | Event files | Unique attendees |
|---|---|---|
| North | 4 / 4 complete | 84 |
| Central | 3 / 4 incomplete | 61 observed |
| South | 4 / 4 complete | 72 |
Unique attendees: distinct permitted person IDs with evidenced attendance during Q2. Repeat attendance counts once in this measure. Unmatched IDs and missing event files are disclosed separately. Affiliation is evaluated at each event date.
Choose a stage to explore its data, context and next decision. Examples use illustrative data.
Collect chapter updates and interviews alongside membership-system exports and event attendance. Preserve the original files and reporting periods.
A registration file and an attendance list are separate sources.
Link people to their organizations, chapters and programs for the dates each affiliation applies. Keep events and renewals in the same history.
Q1 events retain the earlier affiliation; later events use C-03.
Define active membership, attendance and renewal centrally while retaining chapter-specific questions. Show missing data beside the comparable result.
A low observed count may reflect incomplete records, not disengagement.
Use AI to group comments and flag themes for review. Read participation counts with chapter notes before deciding how to respond.
Illustrative note. The team reviews whether the explanation fits the attendance evidence.
Compare the next complete event cycle with its comments. Examine attendance and renewal separately to see what changed after follow-up.
Which chapters recovered participation, and which still need follow-up?
Collect partner updates in Sopact and bring in agreed source-system exports. Keep the original records, their relationships and access rules clear.
Agree the fields with your data owner. Retain original submissions, source references and definition versions so each result can be checked later.
| Record | Fields to agree | Rule that preserves context |
|---|---|---|
| Member identity | person_id · organization_id · membership type | Keep an individual member distinct from a member organization. Store affiliations separately to avoid double counting. |
| Affiliation history | chapter_id · role · valid_from · valid_to | Use the affiliation valid at the event date, not just the member’s current chapter. |
| Participation | event_id · registration · attendance · evidence | Registration is intent; attendance requires an agreed evidence rule. Report unique people separately from total attendances. |
| Renewal cohort | due_date · eligible_count · renewed_count · cutoff | Use members due for renewal in the period as the denominator, with a fixed reporting cutoff. |
| Local explanation | cycle · original language · note · author / role | Preserve local narrative and source access. Version shared questions so changing forms does not silently change comparisons. |
| Access & aggregation | chapter scope · approved purpose · reporting level | Configure local and central views explicitly; aggregate when identifiable detail is unnecessary. |
ASCE describes connecting local events, communications and membership data to support chapter leaders. The story identifies Acumen AI as a planned next phase.
Read the source ↗Which chapter reports, interviews and program updates are missing from the membership record? Agree identity, definitions and access before comparing chapters.
Read the source ↗Members, languages and event cycles
WorldSkills International and Sopact are building a long-term data foundation for a 90-Member network—connecting teams, languages, and learning across event cycles.
Read the case study ↗
Qualitative stakeholder evidence
How ASME turned qualitative data it had only ever used as impact stories into analysed stakeholder insight.
Read the case study ↗FAQ
Yes. Agree a small shared dictionary for comparable network reporting while retaining chapter-specific questions and context.
Keep event, reporting period, submission status and chapter context together. Review coverage and local explanations before treating a lower reported total as a fall in participation.
Define access by role and purpose during setup. Network summaries and authorized member records can serve different needs without assuming every local response should be visible to everyone.