01
Design gate
Can this brief produce credible evidence here?
- Feasibility and incidence
- Sampling and sourcing risks
- Instrument logic
- Language and cultural fit
- Privacy and consent needs
QualityQuality is not a claim.
Quality is not a claim.
It is a visible system.
04 / CONTROL
We define how a study could fail, place controls where they matter, and keep a decision trail your team can inspect.
Discuss QA requirements ↗Our standard
Every material field decision should be explainable after delivery.
Controls vary by method and risk. The principles do not: prevent early, detect continuously, resolve clearly, and document what changed.
Four quality gates
Control before, during, and after field
02
Launch gate
Is the field team measuring what the study intends?
- Interviewer calibration
- Live or observed pilot
- Comprehension checks
- Survey and quota testing
- Pilot change log
03
Collection gate
Are emerging patterns real or operational?
- Quota and source tracking
- Duration and location review
- Audio and open-end checks
- Back-checks and recontacts
- Interviewer-level flags
04
Delivery gate
Can the client understand and use what happened?
- Data consistency and coding
- Exclusion decisions
- Evidence completeness
- Exception and limitation log
- Structured handoff
Evidence package
You receive more than a clean file.
A delivery is stronger when the team can see the fieldwork behind it.
01
Quality plan
Controls, thresholds, review frequency, and escalation ownership.
02
Progress record
Quota status, source mix, field notes, and daily risks.
03
Decision log
Flags, investigations, exclusions, replacements, and corrective action.
04
Closeout summary
What was checked, what changed, and limitations worth carrying forward.
Need an independent local QA layer?
Explore quality control ↗