How to Create a Survey Audit Trail
Keep a practical record of design, launch, fielding, exclusions, and final exports.
The Short Version
Keep a practical record of design, launch, fielding, exclusions, and final exports. A practical way to begin is to save the pre-launch design summary, then record the launch date and respondent source. Finish by making sure you store methods text, codebook, and analysis scripts together. The full walkthrough below explains each part in order.
Is This Guide for You?
Researchers preparing replication files, appendices, or internal project records.
Follow These Steps
Work through these 6 steps at your own pace. The wording is intentionally practical, and you can return to the checklist at the end when you are ready to review your work.
- Save the pre-launch design summary.
- Record the launch date and respondent source.
- Archive pilot and main survey versions separately.
- Export raw and analysis data after fielding.
- Save exclusion settings and final sample counts.
- Store methods text, codebook, and analysis scripts together.
What This Helps You Accomplish
An audit trail helps explain exactly what was fielded and how the final dataset was produced.
A Quick Confidence Check
- Archive before and after launch.
- Keep raw data separate from cleaned data.
- Record exclusion rules.
- Store codebook and scripts with exports.
Common Questions
Can I use this guide if I am new to this?
Yes. Researchers preparing replication files, appendices, or internal project records. Follow the steps in order, start with a small test, and use the final checklist before you field or report anything important.
What is the simplest way to get started?
Begin by save the pre-launch design summary. Next, record the launch date and respondent source. You do not need to perfect every setting before running a small preview or pilot.
How do I know when I am ready?
Use the confidence check above. In particular: Archive before and after launch. Keep raw data separate from cleaned data. Record exclusion rules. Store codebook and scripts with exports. When the decision is consequential, keep your study documentation and ask a qualified colleague or methods reviewer to examine the design as well.
Related Guides
Research artifact: sample data, codebook, and scriptsResearch Pathways
Product names and fielding platforms mentioned in this guide belong to their respective owners. Conjoint Survey is an independent academic research tool and is not affiliated with, sponsored by, or endorsed by those services.