The below outlines when you might want to publish a survey or form and what you should consider when doing so. The (technical) process of setting up a survey or form is described in detail here.

EHQ's Surveys & Forms tool is the most popular of all tools. The beauty and effectiveness of a well-designed survey surely is a contributing factor. That does not mean that is is easy to design a great survey. On the contrary, many surveys you will see are either too long, too complicated and convoluted or simply do not make sense.

When should I use this tool and not any other?

This is not an easy question to answer. There are lots of reasons why you might want to use a survey and not any of EHQ's other tools.

In general, a survey is best used if you need to collect lots of data quickly and efficiently. Surveys are often used if an organisation is looking to quantify results for a decision. It is also a good tool to use if you do not require to get involved yourself, or if you do not want/require participants to engage with each other. In most other tools, people can see if and how other people have engaged. A survey does not have this kind of transparency and is very 'one dimensional'. All engagement is 'hidden' from the public and only visible to you, the administrator. This might be a pro or a con to using surveys, depending what you want to achieve.

Please Note: 'Take Survey' or 'Submit Form' Buttons

  1. When a survey allows Registered Participants only and the button will say 'Take Survey'.
  2. When a survey allows Anonymous contributions, it is by default considered a form, and the button will say Submit Form.

The button itself is not customizable.

Another scenario :

  1. When a Survey allows 'Single Submissions'/Registered Participants - 'Take Survey' button appears
  2. When a Survey allows 'Multiple Submission'/Registered Participants - 'Submit Form' button appears

What should I consider when setting up a survey?

The most important part of a survey set up is giving consideration to the survey logic and the overall design. Don't design long surveys just because you can. A short survey is always better than a long survey.

Once you have designed your survey it is crucial to give it a good test. Make sure you do so thoroughly BEFORE you publish it. When you test a survey within EHQ before publishing it, the responses will NOT be saved in the reporting. This means you can test the survey fully without having to worry about cleaning up reporting later.

Read more about testing a survey here.

Testing is important in particular if you have a survey or form that uses conditional questions.

If you have a very long survey, consider splitting your survey into multiple parts via the page element 'Pages'. Not only will the survey appear to be shorter, but participants can come back at a later point and submit the previously incomplete survey. This works for both anonymous users, as long as they come back via the same browser on the same machine, or participants who are logged in.

What do to after I published my survey?

Sit back and see the submission roll in. If the survey is well designed and you have pushed marketing to increase incoming traffic to your project, you should see a decent engagement rate.

One thing to consider is to NEVER change an already published survey. Although the option to do this is present in EHQ, we strongly recommend to keep away from this. Read here why.

Did this answer your question?