Survey builds
Send your questionnaire, logic notes, and field date. Get a Decipher test link and handoff notes for your team to review before launch.
Brief a buildFOR RESEARCH TEAMS
Decipher survey programming for research agencies. Hand off a new build, a tracker wave, or a survey issue your team needs fixed.
Fixed quote before work begins. Reply within one business day.
01 WHAT WE DO
Keep the study with your team and hand off the Decipher programming you need help with.
Send your questionnaire, logic notes, and field date. Get a Decipher test link and handoff notes for your team to review before launch.
Brief a buildShare the previous wave and what has changed. Get the next wave programmed with checks on the routing and data variables your reporting relies on.
Brief a tracker updateBring the symptom. A screener drops the wrong people, a quota stays empty, a redirect fails, or the export doesn’t match what respondents saw.
Describe the issue See a sample fix note02 THE RIDE
Tell us what you want built, updated, or fixed. Once the work can be scoped, you get a fixed quote and a proposed turnaround. Work starts after you approve both.
Confirm the questionnaire or changes, the deadline, and what your team needs back. For a live issue, check whether new responses are affected.
Build, update, or fix the agreed scope in Decipher. Test the relevant routes, quota behavior, and data fields before handoff.
Your team reviews the test link or tested changes and decides when to release them.
What comes back: the programmed survey or tested changes, a short note on what was checked, and any open points for your team. For a live fix, the note flags earlier responses that may need review.
03 SAMPLE FIX NOTE
Some respondents hit a fatal error when they click Continue and can’t finish the live survey. The team’s usual test route passes, and the error message gives them no clue where to look.
Fictional example of the note your team receives at handoff.
FIX NOTE BS-014 · ILLUSTRATIVE
None. The downstream scoring routine passed that value to float(), raising an unhandled TypeError that blocked the page transition.None check before numeric conversion. The derived score stays blank when the rating is absent. Recorded values, including zero, still go through the calculation.04 QUICK ANSWERS
What to send, what access is needed, and how the work is quoted.
Yes, subject to availability. Say whether new responses may be affected and when the issue started. Once the cause is understood, agree on how to test and release the change with your team.
Start with what respondents see or where they get stuck. An error message or a redacted screenshot can help if you have one. We’ll ask for any other details we need.
Start with a short description. For a build or tracker update, have the questionnaire or change list ready. If a project link, account access, or a test export is needed, we’ll agree how to share it.
Yes. You can hand off a module, a tracker wave, or a single fix. If the work grows beyond the agreed scope, you'll get a separate quote before it starts.
You get a fixed quote once the work can be scoped. Work starts after you approve it.
You get a first reply within one business day. Start dates and turnaround depend on the questionnaire or change, the access needed, and what has to be tested. You get a proposed schedule before approving the work.
That depends on what was recorded. The handoff identifies which responses may need review and what can be recovered from the available data.
05 YOUR PICKUP
Tell us what needs doing, where the study stands, and when you need it. Review the brief, then open it in your email app.
Use a redacted example and leave out respondent details, passwords, and private links.