View Categories

Phase 4: Initial Survey Programming: A Seamless Handoff

Once the questionnaire is finalized, it’s time for a survey programmer to script it for data collection. This is where the AI solutions within the Survey Creator step in to automate and minimize the manual survey programming. Kalever streamlines this phase by turning the Survey Creator and the TrackEntry into a shared workspace for all stakeholders, ensuring consistency, clarity, speed and quality.

Scenario: The ‘Luxury Brands’ questionnaire is approved. The Project Manager now brings the Survey Programmer into the project to script the project and deliver a survey test link.

Note: For this scenario we will use Decipher as data collection platform example, but keep in mind that the Survey Creator tool is platform agnostic and could be connected to your preferred data collection platform.

Step 1: Grant the Programmer Direct Access #

The foundation of this workflow is collaboration. Instead of emailing files back and forth, the Project Manager should add the Survey Programmer as a member of the internal project within Kalever.

This gives the programmer direct access to the Survey Creator, TrackEntry, and all project files, making Kalever their central hub for the project.

Step 2: The Programmer’s Workflow in Kalever #

Now working within the same project, the programmer can take over.

A. Edit elements and Leverage Pre-Built Custom Modules
Before exporting, the programmer can review the survey structure. If edits are needed, the programmer could easily apply them within the Survey Editor.
More information: Editing Your Survey.
It you are using Decipher, you could also use the Decipher Editor as alternative of the Classic Survey Editor.
More information: A Deep Dive into Adding and Editing Survey Elements

If the survey includes complex exercises like MaxDiff, Conjoint, Gabor Granger, or VanWestendorp, their work is already simplified. Because these were added as Custom Modules, the complex, structured XML required for these exercises is already generated and standardized according to your company’s templates. This saves hours of manual scripting. More information: Using Custom Modules

B. Apply Template and Export the XML
The programmer’s first step is to export the initial survey for scripting.

  1. Inside the Survey Editor, open the Editor Options (cog icon) and apply the correct Company Template to standardize the output.
  2. Click the Download icon and select Survey Output (e.g., Decipher XML), choosing the desired template.

More information: Advanced options

This provides a clean, validated XML file that is ready to be loaded directly into the Decipher platform.

C. Collaborate with the Project Manager
If the programmer discovers an issue or needs clarification (e.g., on a complex logic condition), they should not leave the platform.

  • Best Practice: Use the integrated TrackEntry feature. By clicking the TrackEntry icon on the specific survey element in question, the programmer can ask the Project Manager for clarification. This keeps all project communication organized and contextually linked to the relevant part of the survey, eliminating confusing email chains.

More Information: How to Create, Edit, and Manage Entries

Step 3: Maintain Synchronization with Back-Import #

It is critical that the Kalever platform remains the “single source of truth”. If a programmer makes an urgent or critical change directly in the Decipher platform, they are responsible for bringing that change back into the Survey Creator.

  1. After editing the XML in Decipher, the programmer exports the updated file.
  2. Back in the Kalever Survey Editor, they open Editor Options (cog icon) and use the “Import from XML” feature to upload the new file.

This action updates the survey in the Survey Creator, ensuring that all project members are always viewing the most current version. This creates a reliable, closed-loop process managed directly by the person closest to the code.