Why member data fragments, and what connecting it makes possible. See how existing records, member identity and written feedback connect to a useful answer. Then work through the examples below.
Working with independent member organizations? You will also follow a network example: combine recurring reports without rebuilding them by hand, keep local ownership clear and return a useful view to each contributor.
Work at your own pace. No coding or software purchase required.
Choose one question and work it through
Follow either the individual-member example or the independent-organization example. Use your chosen records to define the question, bring in your member list from your AMS, connect the evidence, ask members a question on the same record and review their comments. Then return a useful answer, test permissions, corrections and the next reporting cycle, and follow up on what members said. A separate, optional benchmark exercise covers comparisons and a potential paid report. Existing Academy methods appear when they help you complete a specific task.
You leave with a question brief, your member list brought in from your AMS, a checked record map, a survey on the same member record, reviewed themes, a member-report prototype, a pilot checklist and a follow-up list. Together they define your data strategy and the requirements your tools need to meet.
Why connect your AMS instead of replacing it?
In short: your AMS already does its job. The gap is what members tell you.
An AMS runs the member record, dues, events and billing. Applications, assessments, survey answers and event comments usually sit in other tools, with no lasting link back to the member. Your team fills that gap by hand: exporting, re-keying and matching names across files. Every new survey adds another file, and nobody can see one member across a year.
At ASAE Annual 2026, associations described exporting spreadsheets, re-keying information and reconciling between their AMS, events, learning and email tools, and asked how to use their own data more intelligently. This course shows a way to close the gap without changing the system you already run. Your AMS stays the system of record for who your members are, plus dues, events and billing. Sopact adds what members tell you, on the same person.
What is different about this approach?
- You keep your AMS. Nothing to replace and no migration. You bring in a copy of the member list and keep the member number beside each member.
- One lasting ID per member. Every form, survey and event adds to the same record, so a second wave is a comparison, not a new spreadsheet.
- AI reads the comments no one has time to read. You choose which fields it can see, and each finding points back to the comments behind it.
- Each chapter or role sees only its own data. The organization sees the whole, and the AI Assistant follows the same access.
- You start small. One member list and one event, with no IT help.
How does this compare with what you do today?
| What you use today | Where it stops | What changes here |
|---|---|---|
| A survey tool and a spreadsheet | Each survey starts a new file with no lasting link to the member. | Every response lands on the member's record. |
| An AMS on its own | It holds the member record well. Comments and repeat survey waves usually end up in other tools. | The AMS stays as it is. Comments and repeat waves sit beside the member. |
| Building your own | Some organizations tell us that building their own registration and data tools took more time than they expected. | You start from the member list you already have. |
Your eight lessons
- 1Pick one question. Keep every system you have.A one-page question brief: who needs the answer, what they will do with it, and where the evidence lives.
- 2How do you build a membership database from your AMS export?Your member list entered once, matched on email and member number, and checked against your export.
- 3Connect the same member across systemsA small connected history and an exception list showing what you can—and cannot—join.
- 4How do you run an event feedback survey that lands on the member record?A short survey and a repeat wave that both land on the same member record.
- 5Make sense of member commentsA short coding guide, reviewed comments and a finding with its evidence and limits attached.
- 6Build a useful member benchmarkA one-page member report with a defined comparison, a methods note and a plan to test its usefulness.
- 7Run a small pilot with clear access rulesA requirements brief and a test log for deciding what to keep, repair or expand.
- 8How do you follow up on member feedback to support retention?A follow-up list built from the survey results, ready to send from your own email tool.
Download the practice pack (ZIP)
Synthetic CSVs, a coding guide, worked answers and a printable workbook. Choose the individual-member example or the member-organization example; no real member data is included.
What the course adds to the video
The video shows the destination. The lessons make you test the connections: a stable ID does not permit every join, a theme needs supporting words, and a shared definition does not guarantee a correct AI answer. Named and anonymous feedback stay distinct. A minimum group size alone does not guarantee safe publication.
You can also develop a benchmark report as a potential member benefit. The course helps you test its usefulness and demand; producing a report does not establish that someone will pay for it.