Distribution & Targeting

Once a survey is published, the author opens the distribution workspace and assembles an audience from layered filters: tenant-wide (every active member), an org-node subtree (a district and all its clubs), role-based (referees, club admins, license holders), demographic (age band, gender, license type, discipline, region), an explicit list pasted or uploaded, or any combination joined with set operations. As filters are added the audience estimator runs against the live member directory and shows the projected reach, eligible-but-opted-out counts, and channel coverage (how many have a verified email, SMS, or in-app device token). Authors then pick one or more channels — in-app push and inbox, transactional email, SMS, a public shareable link with optional Turnstile, or an embeddable iframe with a snippet for federation and club websites — and schedule the launch immediately or for a future window.

A reminder policy is attached at launch: none, a single nudge after three days, weekly until response or close, or every three days, with quiet-hours respect per recipient locale. The system writes one invitation row per (user, survey, channel) tuple so engagement can be tracked granularly: dispatched, delivered, bounced, opened, clicked, started, completed, opted-out. Reminders fire only against rows that are eligible (not yet completed or opted-out) and respect channel-specific throttles to avoid SMS fatigue.

Public links and iframe embeds bypass the invitation table for anonymous fieldwork but still capture campaign attribution via UTM parameters. Federation administrators with cross-tenant rights can hand off the audience to F20.06 for opt-in distribution to member nations, while tenant admins retain channel-level kill switches and can revoke invitations mid-campaign without losing already-collected responses.