Skip to content

Creating a survey

Surveys are built and managed from the Surveys area (/survey/list). Building a survey needs the admin role (edit permission on surveys); viewing and submitting are open more broadly.

Steps

  1. From the survey list, create a new survey (or edit an existing one).
  2. Set the details: name, description, start and end dates (the window during which people can respond), and whether to allow multiple responses.
  3. Choose the survey type/template — a blank custom survey you build yourself, or the standing Data Collection Questionnaire (DCQ).
  4. Build the questions with the form builder — drag in field types (text, number, choice lists, matrix, etc.), or start from a template. For a DCQ, matrix questions carry one column per selected supplier.
  5. Set the organiser, co-ordinator, category/team, and any deal/company link as needed.
  6. Add recipients — pick contacts to invite. For a DCQ, recipients are derived automatically from the DCQ tag and product profiles in the chosen category, so you don't pick them by hand.
  7. Save.

Result

The survey is saved and indexed for the list and results views. Invited recipients are recorded against the survey.

Note two things, confirmed in code:

  • Saving does not email invitees — the automatic invitation email was disabled, so recipients are recorded but not mailed. Communicate the survey to them another way.

  • Delete leaves invitations behind — deleting a survey removes the survey but not its invitation rows.

Sending reminders

Use the reminder action to chase non-responders; it sends each of them an in-app task notification (not an email).

Answering and results

Respondents answer from the survey's detail view while it is open; a finished (past-end-date) survey shows as closed. The results view aggregates responses — a supplier-comparison matrix for the DCQ, or per-question results for a custom survey.

If it fails

  • You can't edit or create — you lack the admin role / edit permission on surveys.
  • Recipients you added didn't get an email — invitations aren't emailed on save; notify them separately or send a reminder.
  • Response counts look inflated — anyone logged in can submit (an invitation is created on the fly), and repeat submissions aren't blocked.