Everything Plumeform does.

A survey goes from nothing to collecting answers in about five minutes. From your dashboard:

1. 1Create it. Name a survey and hit create — or start from a template, paste an existing survey, upload a Qualtrics .qsf file, or describe your study to the AI drafter.
2. 2Write the questions. Add questions from the type picker, drag to reorder, split across pages. Everything autosaves; undo with Ctrl+Z.
3. 3Preview. Preview shows exactly what respondents see, stores nothing. Share a reviewer link if someone without an account needs to sign off.
4. 4Publish. Publishing snapshots the survey. Respondents always see the published version, so later edits can never disturb answers already collected.
5. 5Share. You get a link like plumeform.com/s/your-slug. No respondent account is ever required.

Edits to a published survey stay in the draft until you hit Publish changes again — so you can rewrite freely mid-study without touching live data.

Twenty types, all available on the free plan except file upload. Any type can be converted to another from the question editor.

Every question can be required, or soft-required — which asks once (“no answer, continue anyway?”) and never blocks. Ethics boards generally prefer soft-required.

Rules live in the builder's Logic tab and read as sentences: when some condition holds, then do something.

Conditions can test any question (answered, equals, contains, greater/less than) and combine with all or any. With an A/B experiment running, rules can also branch on which arm the respondent was assigned.

PipingPRO — drop {{q:question-id}}into later question text and it's replaced with that respondent's earlier answer. The question editor has a picker that inserts the token for you.

The controls that make data defensible. All Pro, all configured in the builder — per question or in Settings.

Quality flags — speeders, straight-liners, failed attention checks — are computed automatically on the results page. Speeder detection needs at least five timed responses before it will accuse anyone.

Prolific, CloudResearch Connect and MTurk are first-class. Each has a step-by-step setup reference with a live demo loop you can click through:

Prolific setup →Connect setup →

In short, what's handled for you:

• Participant IDs (PROLIFIC_PID, STUDY_ID, SESSION_ID, participantId, workerId, or any custom parameter) captured from the study URL onto every response.
• Completion by redirect — with the response id, score and captured parameters substituted into your completion URL — or an on-screen code.
• Screen-outs routed to their own redirect and code, so disqualified people return marked correctly.
• One response per participant, enforced server-side on the panel ID.
• MTurk preview traffic handled without storing anything.
• Clean and flagged participant IDs copyable in bulk for approve/reject.

The results page updates as answers arrive: a chart per question, click any value to filter the whole page, cross-tab any two choice questions, and browse individual responses with their timings and flags. Hide flagged removes low-quality responses from every summary and export in one click.

Public results links share a live, read-only aggregate page with anyone — charts and counts only. Free-text answers and individual responses are never shown there.

Group surveys into waves of a studyPRO and Plumeform links the same participant across them — by panel ID or a custom URL parameter you choose.

• Retention funnel: participants per wave, share of wave 1, and how many also completed the previous wave.
• Wave-over-wave trends: the same question tracked across waves — scale averages with up/down deltas, and option shares per wave.
• Linked CSV: one row per participant with each wave's answers in w1_, w2_ columns.
• Multi-wave import: paste or upload several waves at once and get a linked study.

Questions are matched across waves by their wording, so duplicating a wave and editing it still lines up in the trend view.

Add languages in the builder's Languages tabPRO. Each locale is a translation of every string in your survey; the surrounding chrome (buttons, validation, progress) is already localized for English, Spanish, French, German, Italian, Portuguese and Dutch.

Respondents get a language picker and are matched to their browser language automatically; adding ?lang=es to the link forces one. Answers stay a single dataset— you translate the words, not the data, so analysis doesn't fragment. AI can fill a locale in one click, and every string stays editable.

The API exposes your surveys and their responses read-only, scoped to your workspace. Revoke a key any time — it stops working immediately.

Your dashboard shows responses used this month. If you cross the cap, collection continues until midnight UTC so nothing in flight is lost. Upgrade or manage billing (card, invoices, cancellation) from Account — cancelling keeps Pro until the period ends, then drops to free with all your data intact.

Where data lives, who can reach it, retention and GDPR: security & data practices. Participant accessibility: accessibility statement.