Testing and Activating the Project, Exporting Results
Activating the Project
Before starting the feedback process, the basic settings of the project have to be adjusted in the Survey menu.
Specify beginning and end of the project. Confirm with Save.
In the āStatusā line, you can see that the project has been created and is currently in the status āsurvey compiledā. But it is not activate yet (āin the fieldā). Click on the active button: the status will change to āactiveā.
The interval specified in the survey menu is the field time of the project itself. Individual feedback waves may have shorter field times, but these must be inside the overall project field time.
Testing the Project
Before entering into the field, you have to test questionnaire and feedback center.
You have repeatedly used the preview while creating the questionnaire to check completed questions or pages. After completion, the whole questionnaire needs to be tested.
As the preview does not support all features, you should test the questionnaire in the productive mode, too, before publishing it. For this purpose, a test wave with participants is used.
With a test wave and test participants, you can test the feedback center, too.
Testing the Questionnaire in Preview Mode
In the āDistributionā section of the survey menu, click on the Questionnaire preview icon and check the survey from the point of view of a participant. Go through the questionnaire and try whether filters, hiding conditions and plausibility checks really work.
Testing Questionnaire and Feedback Center with Test Participants
A test wave and test participants allow to test all features of questionnaire and feedback center under real-live conditions.
Create a test wave in the menu Participant administration ā Waves.
Create participants manually and define a feedback constellation. Alternatively, you can import a list of test participants into the test wave. Please take care to use only e-mail addresses for the test participants
which you can access and which you are permitted to use for e-mail tests!To access the questionnaire from the perspective of a feedback provider, please proceed as follows:
ā Open the feedback provider overview: Participant administration ā {Selected wave} ā {Selected focus person}.
ā For the desired test feedback provider, click on the code link in the āCodeā column.
ā The questionnaire is opened and you can now check wildcard replacement, routing etc. from the test feedback providerās perspective.To access the feedback center from the perspective of a focus person, please proceed as follows:
ā Open the focus persons overview: Participant administration ā {Selected
wave}.
ā For the desired test focus person, click on the Edit focus person icon.
ā In a second browser window, open the menu Process configuration ā Feedback center. Click on the feedback center URL: the login will be opened.
ā Copy e-mail address and initial password of the test person into the login form (right mouse button ā Copy or Strg+C).
ā You can now check the feedback center from the test focus personās perspective.
Based on the test wave, you can thus check the complete feedback process from all possible participant perspectives and in all possible feedback phases. E.g. you can check how feedback center functionalities change depending on the feedback status. Or you can invite test particiapnts to test the wildcard replacement in e-mails.
If you have completed all tests, go to the menu Participant administration and remove the test wave by clicking on the icon Delete wave in the āActionsā column. Then, please delete all remaining test persons from the Participant pool.
Resetting the Project
All data created e.g. by tests in productive mode must be deleted before the start of the feedback process. Go to the menu Test and validation ā Reset survey. Select ā...reset survey completely...ā and click on Reset survey. Now the database is cleaned and all test data deleted.
If you have created superfluous questions, pages or answer options, please delete them before resetting the survey and inviting participants.
If you delete pages, questions or answer options or change codes in a live survey, already stored information will be lost or it will no longer be possible to interpret it correctly. Filters and other features that reference variables and codes might be damaged, as well. Please do the clean-up before launching the survey, then reset and check again if all questionnaire features are working properly.
Exporting Results
EFS includes a variety of export features which allow to download participant data, results and other information for analysis and presentations.
This Chapter covers export features which allow you to download MSF-specific data (provided you have the necessary access rights).
Participant data
Return statistics
Results with and without participant data
For detailed information on the export features of EFS, please see āEFS Surveyā.
Exporting Participant Data
An export of participant data may be necessary if, for example, the same participants are to be invited to a follow-up project, or if someone without access to the EFS admin area needs to check and update the data.
Two exports are dedicated to participant data:
Participant data of the whole participant pool: Participant administration ā Participant pool ā Excel export / CSV export
Participants of an individual wave: Participant administration ā {Selected wave} ā Excel export / CSV export
Exporting Return Statistics
To download the return rates of one or several waves, go to the menu Participant administration ā Waves, mark the desired wave(s), select āExport return rateā in the drop-down list and click on Execute.
Exporting Results
In addition to the usual EFS result exports, two dedicated MSF-specific result exports are available.
MSF participant export with result data:
The familiar EFS Survey result data, the feedback identifier (u_link_id), all master data and some selected process data.
Requires read rights to āloft_export_combinedā.
MSF export with anonymous result data:
The familiar EFS Survey result data, the feedback identifier (u_link_id), and merely the process data feedback role (role) and wave (u_group).
Requires read rights to āloft_export_anonymā.
Appendix
Access Control for Multi-Source Feedbacks
The following table lists all MSF-spezific ACL rights.
Ā
Right | Read | Write |
---|---|---|
access_restrictions | Ā | With write permission, you can access the Access restrictions tab. |
leadership_report_manager_download | With read permission, you can download reports on the Report manager tab. | Ā |
loftpartadm | With read permission, you can view the participant list in multisource feedbacks. | With write permission, you can edit the participant list in multi-source feedbacks. |
loft_detail_view | With read permission, you can access the statistics of current and completed feedback processes. It shows for each process how many | Ā |
loft_export_anonym | With read permissions, you can export anonymous result data in multi-source feedbacks. | Ā |
loft_export_combined | With read permissions, you can export address and result data in multi-source feedbacks. | Ā |
loft_fbcenter | With read permission, you can change the type of the external view. | Ā |
loft_peergroups | With read permissions, you can edit peergroups. | Ā |
loft_report_extern | With read permission, you can open the Report definition menu and edit external reports. | Ā |
loft_report_intern | With read permission, you can open the Report definition menu and edit system-generated reports. | Ā |
report_360_dl | With read permission, you can download reports in multi-source feedbacks. | Ā |
view_loft_passwd | With read permission, you can view passwords in the participant administration of multi-source feedbacks. | Ā |
Mail Template Types
When selecting mail templates via the EFS mail forms, only those templates will be available that are appropriate to your current operation. For example, if you are inviting participants, only templates for invitation mails will be offered for selection. This is controlled by assigning the templates to certain mail template types. The following table provides an overview of those types which are used in multi-source
feedbacks and their respective applications.
Mail template type | When it is used |
---|---|
Default mail | Is available in all non-automated dispatch processes. |
Invitation mail | Used to invite participants to provide feedback. |
Reminder mail | Used to remind participants of feedbacks they have not completed yet. |
Notification before end of survey | Used to notify EFS admin area users of the upcoming end of their survey.
|
Notification by exchange platform | Only on installations with EFS Secure Exchange activated: Mail template used to notify project staff of changes on the exchange platform. For more information on the optionally available platform refer to the special documentation āEFS Secure Exchangeā. |
Ā© 2024 Tivian XI GmbH