Keep Survey Percentage Points Separate from Percent Change
A response rate rising from 30 to 40 percent moves ten percentage points, not ten percent. Give each survey wave its own denominator before discussing a change.
1 · survey wave | invitations delivered | completed responses
FIRST-LOAD
Research prototype — checkout unavailable. Input is processed locally and a draft is saved automatically in this browser profile when storage is available. Reset to sample clears that draft; Pro history has its own clear button. A state link encodes your inputs in its URL: share only non-sensitive rows. Browser history, clipboard and anyone receiving the link may retain it. Optional AI use below leaves this device; it is not required.
Data note: Everything runs in this browser tab on the response-rate index card: your survey wave | invitations delivered | completed responses stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.
Perspective: Before: A rate using delivered invitations is not directly the same measure as one using a mailing-list size. After: the response-rate index card shows the working beside each named row so the reader can change the assumption and inspect the consequence.
2 · Read the response-rate index card
Descriptive arithmetic, not statistical inference or research ethics advice. Use anonymous aggregate counts; no respondent data is needed.
Paid layer: response-rate index card print and history
one-time step · the free reading above stays complete
Free tier
- one complete response-rate index card run in the app
- three samples plus unlimited article-demo runs
- unwatermarked result text and an explicit, user-triggered state link
What $4 one-time adds
- print the response-rate index card with its row workings
- CSV of percentage-point difference and row explanations
- last five reading summaries saved in this browser profile
$4 once for repeated filing of the response-rate index card, not for a better answer. Illustrative time basis: avoiding one five-minute manual reformat per saved reading; no market-price or guaranteed-savings claim.
Local history (this device)
- No saved runs yet — your first run files here.
Checkout is unavailable until a payment link is configured. The optional unlock is browser-local, profile-scoped and best-effort, not server-verified access. Clearing browser data can remove it; there is no account or cross-device recovery.
Boundary and sources
Descriptive arithmetic, not statistical inference or research ethics advice. Use anonymous aggregate counts; no respondent data is needed.
- Method: Compute 100 × completions ÷ invitations minus the reference. A 50 percent response rate against 40 gives +10 points; a 30 percent rate gives −10.
- All sample records are invented examples. The app does not fetch measurements, policies, files or personal records.
- Google’s official pricing page, fetched 2026-09-29, lists free-tier access including AI Studio. Optional formatting only; limits and availability can change. Free-tier content may be used to improve products. Never paste private records there.
Mechanism: competence-autonomy-loop
Optional AI formatting, not calculation
For this response-rate index card, use the free AI Studio interface only if available to you, with no paid API key. Manual entry completes the same workflow for free. Supply only fictional or non-sensitive notes. Review its output against the source; never paste unresolved questions into the numeric rows.
Format my non-sensitive notes for a response-rate index card. Return plain rows only: survey wave | invitations delivered | completed responses. Preserve supplied quantities exactly. Do not guess missing values; list questions separately. Do not calculate or add advice. I will check every row before pasting into the local tool.
Accepted schema: survey wave | invitations delivered | completed responses. No AI response is executed as code.