Why is survey training required?
Training requirements depend on the support track for the project. The Standard Service support track requires survey training be completed. The Self-Service track does not have a training requirement. Please see the Model of Support page for more details.
Training is intended to help survey project builders jump start their learning. We review the foundational survey functionality that everyone building a survey project needs to know. We demonstrate the most commonly used survey related features. And, we share the best practices that have evolved from the many years the REDCap Team has been helping builders set up and manage their survey projects. We cover this material for general research use, so you can learn how to use survey functionality in the context of your research project.
If you haven't already completed training and will be building or managing a survey project, sign up for training.
Should I wait to complete survey training before I start building my project?
Brand new to REDCap: If the first project you build in REDCap is a survey project, it's helpful to take a break between completing Basics training and starting Survey training. We recommend you give yourself sometime to absorb the basic training material and get practice applying it in real-time, as you learn to build your first REDCap project.
Building Your First Survey Project: For everyone building their first survey project, both brand new and experienced builders, we recommend you work on the following kinds of building activities to move the project forward until you complete survey training.
- Develop, test and validate all your data collection forms, including those that you'll be enabling as surveys, which we call survey/forms.
- On the survey/forms, require a response for each question/field that captures data required for analysis.
- Determine if you need to set up a longitudinal project to repeat collecting data at discrete timepoints for any of your data collection forms or survey/forms.
How do I know which survey features to use?
One of the most important things all builders should do before they start setting up a project is to develop requirements. By requirements, we mean what are the kinds of things you want REDCap to do to help you get your survey links out to your participants and collect their responses. You'll be able to get the most out of our training and other learning resources, if you have some requirements in mind.
Let's break down the following survey use case into some requirements (i.e. example of how a research study wants to use surveys.)
Use case for surveys | Initial Requirements |
---|---|
Your participants need to complete a group of 4 surveys every 30 days for 3 months after enrolling in your study and every participant has different enrollment date. | 1. Participants complete the same survey 3 different times. |
2. Group together 4 different surveys. | |
3. Track the participants enrollment date and remind the participant to complete survey each month. | |
4. Remind participants to finish any surveys they didn't complete before their visit. |
While it's not unusual to discover some hidden or unexpected requirements as you start working in REDCap, that's largely because you discover REDCap can do something you hadn't know you could do that would help sending out and collecting your surveys. To be successful at building a survey project, it's critical to start with a list of requirements, even a short list, specific to your research study.
We will help you
We know that building a survey project steepens the REDCap learning curve. The software is feature rich in survey related solutions, but survey functionality is not always intuitive, can sometimes be confusing, and even an experienced builder needs someone to check their work. This is why we provide drop-in support to help builders use the survey functionality to set up their projects to get their survey links to their participants and collect their responses per the requirements of their project's data collection plan. We also know that because of the complexity, details and nuances of survey functionality there is a higher risk of configuring a setting in such a way that it would create a regulatory issue or technical failure, which is why we require and conduct a pre-production survey review for all surveys projects.