Advanced versioning allows you to create, manage, and track multiple versions of the same survey. This powerful feature helps you distribute customized surveys while maintaining all responses in a single dataset.

Key capabilities of advanced versioning

With advanced versioning enabled, you can:

Label each version

Assign meaningful names to different versions (e.g., "Boston Office", "Chicago Office", "Remote Workers") for easy identification and analysis.

Print any version

Unlike standard mode where only the latest version prints, advanced versioning lets you print any previous version whenever needed.

Track version usage

Every response is tagged with its version name, allowing you to filter and analyze data by version.

When to use advanced versioning

Advanced versioning solves specific distribution and analysis challenges:

Location-based distribution

Deploy different versions to various sites while keeping all data together:

• Retail chains tracking store-specific feedback
• Multi-campus educational institutions
• Healthcare facilities with multiple locations
• Event feedback across different venues

A/B testing

Test different question wordings or survey flows:

• Compare response rates between versions
• Evaluate which phrasing gets better data quality
• Test short vs. detailed survey formats

Time-based studies

Track how responses change over time:

• "January 2024 Version", "February 2024 Version"
• Seasonal variations in customer feedback
• Pre/during/post intervention studies

Customized content

Maintain consistent questions with location-specific details:

• Restaurant names in satisfaction surveys
• Department names in employee surveys
• Product names in user feedback

How advanced versioning works

Setup process

1. Enable "Advanced Versioning" in survey settings
2. Create your base survey
3. Save and name your first version
4. Make changes and save additional versions
5. Each version gets its own print option

Version management

• Version list: See all versions with creation dates
• Active editing: Only modify the latest version
• Print history: Track which versions were printed when
• Version comparison: Review differences between versions

Real-world examples

Example 1: Restaurant chain feedback

A restaurant chain needs location-specific surveys:

• Version 1: "Downtown Location" - includes parking questions
• Version 2: "Mall Location" - includes shopping experience questions
• Version 3: "Airport Location" - includes travel-related questions

All responses feed into one dataset with location tags.

Example 2: Training evaluation

A training company runs different course lengths:

• Version 1: "Full Course (5 days)" - comprehensive evaluation
• Version 2: "Short Course (2 days)" - focused on core modules only

Both versions share core questions but have length-appropriate additions.

Example 3: Product feedback evolution

A software company refines their feedback form:

• Version 1: "Beta Launch" - detailed technical questions
• Version 2: "Public Launch" - simplified for general users
• Version 3: "Post-Update" - includes new feature questions

Historical data remains accessible across all versions.

Important considerations

Complexity management

Advanced versioning adds interface complexity. Enable it only when you genuinely need version tracking capabilities.

Data consistency

While versions can differ, maintain core questions across versions for meaningful comparisons.

Version proliferation

Too many versions can complicate analysis. Plan your versioning strategy before creating multiple variations.

Best practices

1. Name versions clearly - Use descriptive names that indicate purpose or location
2. Document changes - Keep notes on what differs between versions
3. Test before printing - Verify each version works as intended
4. Plan your analysis - Consider how you'll use version data before creating versions
5. Regular cleanup - Archive obsolete versions to keep the interface manageable

Technical notes

• Advanced versioning is disabled by default to keep the interface simple
• All versions share the same question IDs for unified reporting
• Version information exports with your data for external analysis
• You cannot edit previous versions - only the current version

Should you enable advanced versioning?

Ask yourself:

• Do I need location or time-specific survey variations? → Yes, enable it
• Will I analyze results by version? → Yes, enable it
• Do I need to reprint older versions? → Yes, enable it
• Is my survey consistent across all distributions? → No, keep it disabled

Most users don't need advanced versioning. Enable it when you have a clear use case that requires tracking multiple survey variations within a single dataset.