VPre-Field Checklist

Pre-Field Checklist

Eight safeguards every instrument should pass before a respondent sees it. Use it on your own studies: mark what is true, print it, keep it on file. Nothing you enter here is recorded or sent.

Wisfield Survey Engineering

Pre-Field Checklist

Form PF-08

Study

Field date

Reviewed by

The questionnaire was final and signed off before programming began.Changes made during the build are the most common source of untested logic.
Every skip, filter and terminate condition is written down, not implied.Implied logic is interpreted differently by each person who reads it.
Someone other than the programmer will test the instrument.Programmers test what they intended, not what they built.
There is a written test plan, and its results will be kept.Without a written plan, “tested” can be neither checked nor repeated.
Quotas have been tested at their limits, not only in the middle.Quota faults appear at the edges: the last complete, the full cell, the overlap.
Every piped text and dynamic list has been checked on every path.Piping errors hide on the paths most testers never take.
The data map will be reconciled to the questionnaire before delivery.An unreconciled map breaks the tables, and on a tracker, the trend.
Any post-launch change will be logged and re-tested.Untested fixes after launch are where clean studies go wrong.

0 of 8 safeguards confirmed.

Any statement you cannot mark is a gap. A specified, independently audited build closes every one of them before the first respondent arrives.

Request a Written Scope