When to use this
Use this before uploading confidential data, when learning the research workflow, demonstrating Surv.lytics, or checking how saved analyses become project findings and report documents.
Why it matters
A realistic worked example makes the connection between questionnaire mapping, constructs, data quality, statistical evidence, hypotheses, and reporting visible without presenting invented real-world findings.
Step-by-step instructions
1. Select Explore Sample Project from the landing page or Project Dashboard.
2. Choose Start from the beginning, Partially completed, or Completed showcase.
3. Confirm the project contains 280 fixed-seed synthetic responses and two immutable versions.
4. Inspect Research Intelligence for the approved design, questionnaire mapping, constructs, model paths, and hypotheses.
5. In the completed showcase, open Results & Findings to review saved descriptive, reliability, correlation, regression, and hypothesis evidence.
6. Select Download sample evidence to obtain the raw and prepared datasets, questionnaire, codebook, framework, computed reference outputs, thesis chapter, professional report, and illustrative manuscript formats.
7. Use the starting or partial version to repeat the missing stages and compare your saved evidence with the completed showcase.
Expected outputs
Three owner-scoped sample projects; 280 synthetic responses; documented raw and prepared data; four constructs; three hypotheses; saved statistical evidence; a reviewed Results Notebook; and a ZIP package containing generated DOCX, PDF, JSON, CSV, XLSX, SAV, and SVG examples.
How to interpret the results
Every numerical example is computed by Surv.lytics from the fixed-seed sample. Use it to understand workflow and presentation, not as empirical evidence or as support for claims about a real population.
Common mistakes
Do not describe synthetic respondents as real participants, copy sample interpretations into an unrelated study, or submit a publisher-inspired file without adapting it to the current journal instructions. Starting and partial states intentionally omit later analyses.
Was this article helpful?
Your response helps the methodology team improve this documentation.