Export Instruments, Codebooks, and Flow Diagrams

Response exports give you data. File exports give you documentation: the instrument, codebook, Flow diagram, security overview, review files, and other artifacts that help collaborators, reviewers, IRB staff, and analysts understand the study.

Use file exports before launch for review, during fielding for records, and after collection for reproducibility.

• Survey PDF or Word: share the instrument in a reviewer-friendly format. When the Flow splits respondents into conditions, every arm is printed — blocks that only some arms reach appear before the next block all arms share, and a page never mixes questions from two arms. Every question type shows its content, including reaction-time trials and tree-test tasks and menus, and piped answers show the source question's variable name. Every end screen's closing message is printed under its name, with a note when it redirects. Questions hidden in Flow are left out of every instrument format, including the Qualtrics TXT. The text, LaTeX, and HTML instrument downloads follow the same rules. The PDF and codebook PDF render Arabic and Hebrew (right to left), Chinese, Japanese, Korean, Greek, Cyrillic, and emoji text, fetching the matching fonts only when your survey uses those scripts, so the first such export can take a few extra seconds. Emoji print in black and white. If your instrument has non-Latin text, compile the LaTeX download with XeLaTeX or LuaLaTeX instead of pdflatex.
• Codebook PDF or Word: document variables, answer options, recodes, and analysis notes. If the survey uses a custom theme, turn on Apply custom theme in the Codebook card to style both files with the theme's accent color, text color, font, and logo. Pages stay white and very light colors fall back to black, so the codebook still prints cleanly. The PDF uses the closest built-in serif, sans-serif, or monospace face; Word uses the theme font itself when the reader has it installed. Uploaded font files and SVG logos are not embedded. The setting is saved with the survey, and it is off by default. Both formats end with Appendix A — Flow Variables, one entry per Flow variable: how its value is set (its recode table, the answer combinations it is built from, random outcomes with their probabilities, or its Python or R script) and where the survey uses it — the condition sets it assigns or stratifies, the questions and end screens it is piped into, and other variables built from it. Each question that pipes a Flow variable lists it under Piped Flow variables with its appendix number, so a reader can trace a piped or assignment-driving value back to how it was produced. Every replication package includes both formatted codebooks (Codebook.pdf and Codebook.docx), styled the same way, next to the machine-readable Codebook.csv.
• Security Overview: give reviewers a concise record of relevant security and handling information.
• Flow SVG or PNG: include routing diagrams in protocols, slides, or review packets.
• Flow PowerPoint: edit or annotate the routing diagram for presentations and team review.
• Replication package: bundle the study files for OSF or long-term research records.

1. Step 1: Name variables clearly. Question names become the vocabulary of your codebook and response exports.

   Step 1: Variable Names

2. Step 2: Check Flow. Make sure the diagram shows the intended blocks, branches, condition arms, and end screens.

   Step 2: Flow Diagram

3. Step 3: Preview at least one path. File exports are more useful when they reflect a survey you have already walked through.

   Step 3: Preview

4. Step 4: Export the files. Download the instrument, codebook, Flow diagram, or package you need from Export.

   Step 4: Export Files

• IRB review: include the instrument, consent materials, screeners, end screens, and Flow diagram.
• Team review: share a Word instrument or PowerPoint Flow diagram when collaborators need to comment outside Domandata.
• Analysis handoff: share the codebook and a test response export so analysts can confirm expected columns.
• Open science: use the replication package and OSF workflow when the project needs a reproducible public record.

• Export Research Survey Responses
• Pre-Analysis Plans and Survey Codebooks
• Prepare a Research Survey for IRB Review
• Preregister and Archive a Domandata Study