Use Questionnaires Across Enrollment, Training and Onboarding - Article
Summary
The same questionnaire can support several journeys, but its placement changes what submission means. Feedback evaluates training; an enrollment requirement gathers information before joining; an application gives an approver evidence; an on-demand request starts a planning conversation.
Choose the route for the business outcome, not simply because it displays the same form. Preserve the relevant activity or onboarding relationship when you need that context in reporting, and explain any remaining approval, payment or participation step.
Use this article to:
- Select a delivery route that matches the business requirement
- Configure feedback, enrollment and confirmation at the appropriate level
- Offer questionnaires through onboarding, Course pages or email
- Distinguish submission from approval, payment, enrollment and certificate collection
- Check reporting context, notifications and repeat-response behavior
Choose the route before linking the form
Create and save the questionnaire under Course administration → Questionnaires first. Configure any rules or privacy policy that the intended journey needs. Then connect the saved form to the appropriate feature.
| Requirement | Configuration location | What submission means |
|---|---|---|
| Evaluate a whole learning programme or a Course/Event module | The activity or eligible module's Questionnaire feature | Feedback for the selected training context |
| Collect required information before self-enrollment | Activity features → Self enrollment → Restrict self enrollment until the criteria are met | Completion of that enrollment criterion, not an approver's decision |
| Collect an application for review | Activity features → Self enrollment → Participation approval | Evidence attached to a participation request |
| Confirm participation after approval | The participation-approval feature's after-approval questionnaire option | Applicant confirmation before continuing the enrollment journey |
| Request a custom delivery | Activity features → On-demand | A training request for operational or commercial follow-up |
| Ask targeted questions at login | Settings → Onboarding | Completion of the configured onboarding step |
| Collect input at a particular Course page | The page editor's Button tool, linked to a Questionnaire | An in-course response through the button route |
| Reach an external or unregistered audience | Questionnaire list → More → Copy link | A URL response, without an inherited training context |
| Ask through an automated email | The workflow email editor's button, with Questionnaire as its link type | An authenticated questionnaire response through the automation route |
Configure activity and module feedback
Open the activity under Course administration → Activities and edit its features. Enable Questionnaire at the level you want to evaluate and select the questionnaire. For a specific Course or Event module, use that module's settings/features rather than assuming the activity-level form evaluates only that module.
Use activity-level feedback for the combined experience and module-level feedback for a particular delivery or learning component. In the single-module activity workflow, use the module's Questionnaire feature. Avoid asking the same evaluation twice at both levels without a reason.
Choose whether Feedback can be sent anytime or Feedback can be sent only after completing training. This determines when the feedback action becomes available; it does not make the content of the answers an assessed learning result.
Where appropriate, enable Sending feedback is required to receive the certificate. If the learner otherwise meets issuance criteria but has not submitted the required feedback, the certificate-collection route leads them to the questionnaire. This is a learner-facing collection requirement, not a blanket prevention of every authorized administrator certificate-download action.
Where instructor evaluation is enabled, use Enable feedback for instructors and the relevant instructor questionnaire configuration. This captures the delivery team's perspective separately from participant feedback. Do not assume every instructor can edit forms or view every respondent merely because they can submit an evaluation.
Require information before self-enrollment
In the activity editor, enable Self enrollment, select Restrict self enrollment until the criteria are met, then Add criteria → Complete questionnaire and choose the form. Save the activity and verify that it is published and available through the intended Storefront route.
When the questionnaire is the only unmet criterion, the learner can be taken directly into it from the enrollment action. With several unmet criteria, the enrollment-requirements experience presents the remaining requirements. Submission satisfies this questionnaire requirement for the relevant activity; completing the form somewhere else is not a substitute for that enrollment context.
For a paid activity, submission can lead to checkout. A stored response does not prove that payment succeeded or enrollment was completed. If a registration associated with this enrollment-restriction route is canceled, the related response is removed and a later enrollment requires another submission. Do not apply that specific cancellation behavior to every kind of feedback response.
Collect an application before an approver decides
Under Self enrollment → Participation approval, configure the approver and enable Require users to complete a questionnaire before enrollment. Select the appropriate application questionnaire and save the activity.
The learner submits the required information while requesting enrollment. The responsible approver reviews the request and its evidence. On the activity's Enrollment requests page, the available column controls can add questionnaire answers to the comparison view. This helps assess applicants consistently without reviewing unrelated spreadsheets.
Submission does not automatically approve the application. The designated person must make the decision, and other participation conditions may remain. For the wider approver, waiting-list and enrollment workflows, see Enroll and register participants.
Request participation confirmation after approval
Where the process requires a second step, enable Require users to complete a participation questionnaire after approval within the participation-approval configuration. Select the questionnaire and configure the available confirmation deadline as appropriate.
The approver uses Approve and request confirmation. The request becomes Approved (confirmation pending), and the learner can confirm or decline using the available activity-page or email actions. Confirming leads to the questionnaire; after submission, the request can move to Approved and the learner continues through the applicable enrollment route.
Approval pending confirmation is not the same as confirmed enrollment. Payment and seat availability can still determine the next step. If a configured confirmation deadline expires, the request can become Approved (confirmation expired). An authorized approver or administrator must reset it to Pending to restart that flow; telling the learner simply to submit another ordinary questionnaire will not repair the status.
Use on-demand intake for a training request
Open the activity's On-demand feature and select the questionnaire as its request form. Ask about the audience, intended outcome and practical requirements needed to assess a custom delivery. The Request training journey is not an enrollment confirmation or reserved seat.
On-demand can accept requests from unregistered people where that route is enabled. The configured training-request recipient receives the request information; anonymous answers are also available through the applicable questionnaire report. Arrange ownership and response expectations so a valuable customer inquiry does not stop at form submission.
Offer a targeted questionnaire at login
Open Settings → Onboarding and create or edit a questionnaire-based rule. Define the intended audience and delivery conditions, then select the questionnaire. Open on a separate page provides a standalone experience instead of the default popup, which can suit a longer needs-intake form.
Review the onboarding rule's completion behavior as well as the questionnaire's settings. Where optional AI questionnaire recommendations are enabled, the applicable Generate AI-powered recommendations outcome can turn stated needs into training suggestions. Suggestions remain different from a configured Assign activity rule or required enrollment.
Useful intake asks about genuine goals and responsibilities. For example, distinguish someone seeking a general introduction from a service partner who needs fault-finding training. Avoid collecting unnecessary confidential or sensitive information to make the guidance appear more sophisticated. The wider conversation and training-discovery experience is covered in Find Answers and Training with Saga.
Place a questionnaire in a Course or an email
In the native Course page editor, add or edit a Button, choose the Questionnaire link/action type and select the saved questionnaire. This is useful for a reflection, facilitator check-in or evaluation placed at a deliberate point in the content.
In an Automated email workflow rule, use the email editor's button tool, choose Questionnaire as its link type and select the form. Respondents must be logged in for that questionnaire-button route. If the requirement is anonymous external distribution instead, use the questionnaire's copied URL as a URL link deliberately.
A manually pasted URL does not gain an activity relationship merely because it appears in a Course or email. The native Questionnaire button route and a generic HTML/URL link are not equivalent reporting choices. Check the stored usage type and source context with a real test response.
Share a standalone URL deliberately
From the questionnaire list, use More → Copy link. The link can be shared externally and can accept answers without login. Explain the purpose and collect only the context genuinely needed; a public form is not an authenticated profile-update route.
URL responses do not automatically provide Activity, Module, Schedule or Instructor context. If you need those relationships, select an appropriate native activity or Course-button configuration rather than trying to recover them from a generic shared link later.
Check repeat submissions and notifications
Repeat behavior depends on the route and platform configuration. URL and Course-button questionnaires can be submitted more than once. Activity/module feedback normally has a once-only flow, but an enabled repeat-feedback configuration can allow additional submissions and retain each response. Onboarding recommendation workflows can offer a retake action; do not assume all onboarding rules repeat in the same way.
This affects interpretation: several response rows do not necessarily mean several people. Review the actual route, filters and repeat configuration before drawing conclusions from response totals.
For training-feedback emails, an authorized administrator can use Settings → General → Questionnaires → Send email about training feedback, configure recipients and optionally Send email on low ratings only. The latter supports a Value or Percentage threshold for the applicable Linear scale and Rating scale questions. Exclude from low rating notification email on a scale question prevents that question from triggering the low-rating alert; another included question can still trigger it.
Review Submitted activity questionnaire - admin under Settings → Email sending → Questionnaires for its message. Where enabled on a questionnaire, Send an email with replies to submitter uses its separate user template. An enrollment confirmation, on-demand request email and feedback notification are different messages with different triggers. System Email Notification Overview and Email Sending cover the broader configuration.
Troubleshooting
| Problem | What to check |
|---|---|
| A learner submitted but is not enrolled | Check approval, confirmation, payment, waiting-list status and other requirements; submission alone is not the whole process |
| The application needs information after approval | Use the participation-confirmation route instead of overloading an ordinary feedback form |
| An expired confirmation cannot be retried | Ask an authorized approver or administrator to return the request to Pending and restart the flow |
| A URL response lacks training details | Use the native route that establishes the relationship; a generic URL does not infer it |
| The feedback button does not reappear | Check the once-only or repeat-feedback configuration and whether feedback was already completed. Anonymization is not a reset |
| No low-rating email arrives | Check the feature, recipients, Value/Percentage threshold, relevant scale direction, question exclusions and email configuration |
| Preview looks correct but nothing was recorded | Preview is not a submitted response. Test the actual delivery route with an authorized test account |
FAQ
-
Does submitting a questionnaire approve an enrollment request?
Not by itself. In a participation-approval flow, submission supplies information for the appointed approver. A questionnaire used as an enrollment restriction instead satisfies that requirement within the relevant activity's enrollment flow. Approval, confirmation, payment and seat availability can still be separate steps.
-
Can a questionnaire recommend training instead of assigning it?
Yes, where the optional AI questionnaire recommendation capability is enabled and the relevant completion outcome is configured. Generate AI-powered recommendations provides guidance from the questionnaire journey. It is different from an Assign activity rule and does not itself complete enrollment or bypass participation conditions.
-
Why is a learner not enrolled after completing an enrollment questionnaire?
Check which route was used. An application can still need approval; an approved request can still need participation confirmation; a paid activity can still need successful checkout. Other criteria or waiting-list conditions can also remain. A stored response is not proof that all enrollment steps are complete.
-
Can the same questionnaire be submitted more than once?
It depends on the route and platform configuration. URL and Course-button routes can accept repeat submissions. Activity/module feedback normally follows a once-only flow, but an enabled repeat-feedback configuration can allow more replies. Some onboarding recommendation journeys offer a retake. Submission totals therefore need not equal unique people.
-
Why does a shared questionnaire link not include activity details in the report?
A generic URL does not infer a relationship to the activity, module or schedule where somebody happened to paste it. Use the native activity feature, Course Questionnaire button or other appropriate connected route when that context is required. Review the resulting usage type with a test submission.
-
Why did an enrollment-restriction questionnaire response disappear after cancellation?
For a questionnaire used as a self-enrollment restriction, canceling the associated registration removes that related response. The learner must submit again for a later enrollment. This route-specific behavior is different from the usual retention of ordinary training feedback after a registration is canceled.