A per-year member survey can't tell you whether a member is slipping away. Here is how to carry each member forward on one record across renewals — recurring survey, cycle-over-cycle coding, and at-risk flags surfaced before renewal.
In short: Track members over time by giving every member a persistent Contact ID that survives renewals and email changes, running a short recurring survey coded against their prior response on the same record, and surfacing at-risk members before the renewal date. Report member value and engagement as a longitudinal trend, not a per-year snapshot. In Sopact Sense the persistent ID is what lets this year's answer sit beside last year's for the same member — so you see movement, not a fresh survey each cycle.
Membership data usually resets at every renewal — a new form, a new row, no thread back to who this member was last year. The fix is one persistent Contact ID per member that survives joins, renewals, lapses, and email changes, so the whole lifecycle sits on a single record. Assign it at first contact, and flag duplicates — the same person under a different email or name — so the history stays on one ID instead of splitting into two half-records.
Assign every member a persistent Contact ID that survives renewals and email changes, and flag any member appearing more than once under different names or emails so we can merge to one record.
You do not need a long annual questionnaire; you need the same short survey every cycle. Ask four things — perceived value, satisfaction, likelihood to renew, and one open "what would make you stay?" — and keep the wording and rating scale identical each time so answers stay comparable. Because every response writes to the member's persistent ID, this cycle's answer can be read against the last one.
Design a short recurring member survey with four items: perceived value, satisfaction, likelihood to renew, and one open question "what would make you stay?" Keep the wording and rating scale identical to last cycle so answers stay comparable, and map each to the member's persistent ID.
Expected output. A four-item recurring instrument mapped to the persistent ID, with the rating scale locked to prior cycles so trend is real. Input: your current member survey and the persistent IDs. Output: a comparable, repeatable member survey.
The point of tracking is to act before a member lapses, not to explain it afterward. Read each cycle of feedback the week it arrives, code it against your indicators, compare it to the member's prior cycle on the same record, and score renewal risk — flagging disengagement with the source sentence so a named owner can follow up before the renewal window opens.
Read this cycle of member feedback [BATCH]. For each member, code the response against our indicators, compare to their prior cycle on the same record, score renewal risk, and flag disengagement with the source sentence — surfaced before the renewal window.
Expected output. A per-member renewal-risk score, the movement since their last cycle, and a flag list of disengaging members each with the source sentence and a suggested owner. Input: this cycle's member feedback on the persistent IDs. Output: a scored at-risk watch list surfaced before renewal.
GRADE: green | value + satisfaction trend | same scale, compared on one ID; amber | renewal risk | scored from a single cycle, no prior to compare; red | disengagement flag | member not yet on a persistent ID, history split
Green is a member whose value and satisfaction are trended on one ID against an identical prior scale. Amber is a renewal-risk score drawn from a single cycle because there is no prior response to compare. Red is a member whose history is split across IDs, so no real trend exists until the records are merged.
Finish by reporting member outcomes as a trend, not a per-year snapshot. On the persistent record, trend value, satisfaction, and renewal likelihood per member and per segment across cycles — and measure value, not just attendance, so the story is whether membership is worth it rather than how many events someone showed up to.
Report member outcomes longitudinally across cycles on the persistent record: trend value, satisfaction, and renewal likelihood per member and per segment. Measure value, not just attendance, and hold the rating scale constant so the trend is real.
Measure value, not just attendance. Showing up is not the same as getting value. A member can attend every event and still not renew — the open "what would make you stay?" often catches that long before the attendance count does.
Keep the same rating scale each year. A trend is only real if the scale never moves. If you change a 1–5 satisfaction question to a 0–10 scale mid-stream, this year's number cannot be compared to last year's on the same record.
Never re-ask what the record already holds. If a member told you their renewal driver last cycle, do not ask again from scratch — read it off the record and confirm what changed. Longitudinal tracking should feel lighter each year, not heavier.
Improve your coding accuracy with your own language. Point the Assistant at your program or membership page so it codes feedback against your value language and indicators rather than generic categories.
Read our membership page [URL] and code this cycle of feedback against our own value and indicator language, so at-risk flags reflect what our members actually said.
Track members over time by giving every member a persistent Contact ID that survives renewals and email changes, running a short recurring survey — value, satisfaction, likelihood to renew, and one open 'what would make you stay' — coded against each member's prior response on the same record, and surfacing at-risk or disengaging members before the renewal date. Reporting is longitudinal rather than a per-year snapshot. In Sopact Sense the persistent ID is what lets this year's answer sit next to last year's for the same member, so engagement and value show up as a trend instead of a fresh survey each cycle.
An annual member survey that starts fresh each year cannot show whether a specific member's satisfaction rose or fell, because this year's response is not joined to last year's. A persistent Contact ID that survives renewals and email changes keeps every cycle on one record, so movement — a member sliding from satisfied to at-risk — is visible before the renewal window rather than discovered after they lapse.
Spot at-risk members by coding each cycle of member feedback against your indicators, comparing it to the same member's prior cycle on the same record, scoring renewal risk, and flagging disengagement with the source sentence — all surfaced before the renewal window opens. In Sopact Sense the comparison runs on the persistent ID, so a drop in value or a lukewarm open answer is caught while there is still time to act, not at the annual review.
ChatGPT, Claude, and Gemini are fine for a quick test — but not for an answer you'll put in front of a funder or board. When it has to hold up, run it in Sopact Sense.
Try it in Sopact →
