Understand the outcome
Audience and anonymity lock once anyone responds, so decide them first.
Surveys lets you build a questionnaire and decide who answers: members with their names attached, members anonymously, or anyone with the link. Share it by link, QR code, or notification, then read results as summaries or one response at a time. Internal surveys allow one response per member, even when anonymous.
This guide focuses specifically on “Build and share a survey.” Complete it from an account with the appropriate Surveys access, verify it from the affected member or operational view, and preserve existing records rather than repurposing historical configuration.
Before you begin
Make the decision before changing the screen. Record the current configuration when the department already uses this feature, and use a test record or test account when the change can affect active members.
- Decide named, anonymous, or public.
- Decide target roles and dates.
- Draft your questions.
Do not work around it from another member’s account. Confirm that Surveys is enabled, its dependencies are active, and your role grants the exact management action required for this task.
Where to work and what access you need
Start from the portal destination named in the procedure. Administrators normally need permission to view Surveys plus the specific create, edit, manage, approve, report, or all-record action used by the task. Visibility alone does not grant management access.
- Surveys
/officer-hub/surveys - My Surveys
/officer-hub/surveys/my - Survey workspace
/officer-hub/surveys/:id/:section - Public survey
/survey/:key
Required foundation
- Core must be enabled and correctly configured before this workflow can operate reliably.
If your department uses custom roles, test the procedure with that role—not only with a full administrator account. This confirms the people responsible for daily operations can complete the workflow without receiving unrelated access.
Complete the task
- Step 1Create the survey
Open Surveys in the Officer Hub and create one, or duplicate an existing one.
- Step 2Add questions
Use the nine question types and section headings.
- Step 3Add conditions
Show a question or section only when an earlier answer matches.
- Step 4Set the audience
Choose named internal, anonymous internal, or public, plus roles and open and close dates.
- Step 5Share
Copy the link, download the QR code, or notify members.
- Step 6Read results
Review summaries and responses, export CSV, and remove test responses.
Operational safeguards
Apply these module-level controls while completing the procedure. They prevent a technically saved configuration from becoming an operational or access problem later.
- Control point
Decide on anonymity before sharing; audience and anonymity lock once anyone responds. - Control point
Test conditional questions with a draft. - Control point
Set a close date so results are final. - Control point
Remember public surveys cannot limit people to one response. - Control point
Follow up manually; surveys do not send automatic reminders. - Control point
Duplicate a survey when you need a different audience.
Verify the result
Do not consider the setup complete merely because the save action succeeded. Confirm the behavior from the user-facing or operational view, then retain evidence of the test when department policy requires it.
- A test response appears.
- Conditional questions behave correctly.
- Anonymous responses show no names.
If any verification fails, return to the source configuration and correct it there. Do not edit a report or downstream record to conceal an incorrect setup.
Troubleshooting
Can’t change anonymity
It locked after the first response; duplicate the survey.
Public survey got duplicates
Public surveys can’t limit one response per person; remove bad responses.
Low response rate
Send a reminder yourself; there are no automatic reminders.
Connected modules and downstream effects
This workflow is primarily contained within its module. Verify its member-facing result and reporting output before department-wide rollout.
Continue in Surveys
Return to the Surveys module guide for connected workflows, dependencies, portal destinations, and additional procedures.