SRP Survey DSL

Surveys written by humans.
Understood by machines.

SRP is a domain-specific language for designing surveys — plain text files that are as easy to read as a Word document and as structured as a database schema. Write once, parse anywhere.

Try the Playground Read the Language Guide →

What it is

A survey is just a text file.

Most survey tools store your work as opaque JSON blobs, proprietary databases, or locked-in cloud formats. When you need to audit a question, track a change, or move your instrument to another system, you're stuck.

SRP is different. A survey is a plain text file with a .srp extension, a "syrup file". Open it in any editor. Put it in version control. Email it to a colleague. The language is designed to be immediately legible to anyone who reads it — no training required — while remaining fully parseable by software.

customer_satisfaction.srp

page "intro" do
  title "How did we do?"

  SingleSelect "overall_rating" do
    text  "Overall, how satisfied are you with your experience?"
    required

    option "Very satisfied" do
      action :skip_to "promoter"
    end
    option "Satisfied"
    option "Neutral"
    option "Dissatisfied" do
      action :skip_to "dissatisfied"
    end
  end
end

page "dissatisfied" do
  title "We want to make it right"
  # ... targeted follow-up for dissatisfied respondents
  action :complete
end

page "promoter" do
  title "Great to hear!"
  # ... follow-up questions for happy respondents
end

The branching logic is right there in the file, exactly where it belongs — adjacent to the question it governs, readable by a researcher who has never seen code before.

Why it matters

Form builders trap your work. SRP sets it free.

Typical form builder

Surveys live only in their cloud
Branching logic buried in a GUI
No version history
Export is an afterthought
Vendor lock-in by design
Hard to review or audit

SRP Survey DSL

Plain text — yours forever
Logic visible in the file
Native git version control
Parseable by any compliant tool
Portable across implementations
Peer-reviewable like source code

Capabilities

A full vocabulary for survey design.

SRP covers the full range of professional survey instruments — from simple feedback forms to complex multi-path studies with dozens of question types and conditional flows.

Rich question types

Single and multi-select, open-ended, ratings, rankings, matrix grids, constant sum, heat maps, media upload, and more — all with a consistent syntax.

Branching & skip logic

Route respondents through conditional paths using skip_to, include_if, and exclude_if — expressed inline, never hidden.

Human-readable syntax

Written to be understood at a glance by researchers, designers, and clients — no technical background required to read an SRP file.

Machine-parseable

A formal grammar means SRP files can be parsed, validated, transformed, and rendered by any compliant implementation — today or in ten years.

Tagging & piping

Tag responses for downstream branching. Pipe prior answers into later question text to create personalized, conversational flows.

Validation built in

Required fields, numeric ranges, selection limits, and custom constraints are part of the language — not bolted on after the fact.

Plans

Availability

Individual and enterprise plans.

Whether you're a solo researcher or a team running large-scale instruments, there's a plan for you. Contact us to learn what's available.

Individual

For researchers & designers

Build, preview, and share surveys using the SRP language. Full access to all question types, branching logic, and the interactive playground.

Ask about individual access →

Enterprise

For teams & organizations

Collaborative workflows, custom integrations, volume capabilities, and priority support. Built for organizations where survey quality is non-negotiable.

Talk to us about enterprise →

Surveys written by humans.Understood by machines.