Survey fieldwork metrics are the numbers produced while a survey is in field: incidence, screen-out, over-quota, drop-off, conversion, and the removal rate at each quality gate. Every one of them is a ratio between two points on the respondent journey. In practice, what gets reported covers the survey itself, from the first start to the delivered complete. The supply-chain half of the journey, everything the supplier routed and removed before the link, is left out of standard reporting even though the supplier holds the data. This page is the reference for the whole journey: the formula of each metric, what it tells you, and who can compute it in each of the four cases, by seat, buyer or supplier, and by who hosts the questionnaire.
Buyers and suppliers often read the same study differently, and part of the gap is structural: each side computes its numbers on the part of the journey it can see, and not always with the same formula. Improving how fieldwork is done starts with a common understanding of which metrics to look at, how to compute them, and who can actually get them.
This page draws the whole journey once, at one scale, and lets you pick a seat and a host. The diagram shows what your side measures directly, what reaches you as an outcome only, and what is never reported to you. The table says who can compute each metric in each of the four cases; the definitions under it say what each metric is, what it tells you, and where it moves with the seat. One thing to hold throughout: what is measurable is wider than what is reported. Fieldwork reports describe the survey window. The supply-chain part is almost always left out, not because the data does not exist, but because it opens conversations the supplier does not necessarily want to have.
One journey, four seats: what each side can measure
Use the two controls to pick who you are and who hosts the questionnaire. The journey never changes. The panel beside the diagram describes your line of sight and lists the metrics you can and cannot compute, with their values for the scenario and, on hover, the numbers behind each. Click any band for what it is, how the industry defines it, and the metrics it feeds.
The numbers are one scenario built on the Global Data Quality benchmark (Wave 2, H1 2026: 46 companies, 13 countries, about 1.8 million survey records), joined into one journey, with a few estimates marked as such in about the numbers. The supply side is deliberately drawn as one supplier with two gates; bands marked flatten something, and the note for each is on the respondent-experience page.
Buyer view · questionnaire hosted by you. The journey is identical in every view; only what is reported to your side changes.
1,363 respondents were routed to this study to put 1,000 at the survey link: 5.2 routed for every delivered complete. 37.3% of survey starts do not qualify or have nowhere to go. Bands marked are simplified; the note is on the respondent-experience page, linked from each band.
The four scenarios, in text
What each seat can measure, in the order the controls offer them. The metric lists match the matrix in the table below; the panel beside the map shows the same text for the scenario you select.
The buyer, hosting the questionnaire
From the moment traffic hits your link, everything is measured directly: your checks at the link, the screener, the quotas, the partials, the quality terminates, the completes and your own review. Nothing before the link is visible. What the supplier routed, what its quality checks removed and what its pre-screen terminated exist in its system, and reach you only if it shares them.
Computable from your own data: everything from the link onward. Buyer pre-survey removal, in-survey removal, post-survey removal, reconciliation (the same review, seen from the supplier's side), the bad quality rate and the good-to-bad ratio on the survey window, incidence from your seat, screen-out, over-quota, drop-off, conversion. Not reported to you: the supplier pre-survey removal rate, and with it the journey-wide versions of the bad quality rate and the ratio.
The routed count and the supplier's own quality removals before the link, per study. Which of your criteria the supplier actually received and pre-screened on, and on what profile data. Which sources were in the blend, and what each of them routed and removed.
The buyer, when the supplier hosts
You receive a data file and a count. The supplier routed, gated, hosted the survey and cleaned the completes before delivering. The one step measured on your side is your own reconciliation: what you accept and what you reject among the completes delivered to you. Every other band is happening, and none of it is measurable from your side; it reaches you only as the supplier's report.
Computable from your own data: the reconciliation rate. Everything else, from the routed count to the supplier's own clean-up, depends on what the supplier shares.
The full funnel as the supplier's platform logged it: starts, screen-outs by criterion, over-quota by cell, partials split between screener and questionnaire, quality terminates by check, completes, and its own removals. The definitions its platform uses for a start and a complete. The sources under the study.
The supplier, hosting the questionnaire
You route, gate, host and deliver, so every band is yours to measure, from routed to delivered, and you decide what reaches the client. The only numbers that come from the other side are its reconciliation: how many of the completes you delivered it accepted, and how many it rejected after its own review.
Computable from your own data: ten of the twelve, including the supply-chain half nobody else can see. Outcome only: reconciliation, which reaches you as the client's count without the reasons. The buyer's pre-survey gate does not exist when you host.
The reason behind each reconciled complete, per ID: it closes the feedback loop, and it is data to append to the panelist's profile so the next match is better. Whether the client's review repeats checks you already ran, so the two of you are not removing the same people twice for different reasons.
The supplier, when the buyer hosts
Everything before the link is yours: what you routed, what your quality checks removed, what your pre-screen terminated, how many you sent to the link. From the link onward, the survey exists to you as the exit redirect each respondent comes back on: complete, terminate, over-quota, quality, often a fraud or duplicate exit as well, or no redirect at all. Outcomes, never reasons. A terminate does not say which criterion failed; a session that never returns does not say whether the person left or the page broke. After fieldwork, the buyer's reconciliation tells you how many completes it rejected, rarely why.
Computable from your own data: the supplier pre-survey removal rate. Outcome only, from the redirects and the reconciliation: everything else, including the buyer's pre-survey removal as a count of fraud and duplicate exits, the bad quality rate and the ratio over your whole window, incidence from your seat, screen-out, over-quota, drop-off, conversion.
The screen-out split by criterion, so you can stop sending the people who fail it. The split of non-returning sessions into drop-offs and technical failures. The reason behind each reconciled complete, per ID.
The twelve fieldwork metrics: formula, and who can compute them
One table, in journey order: each metric with its formula, and for each seat and host whether it is measured directly (✓), reaches you as an outcome without the reason (◐), or is not reported to your side (✗). A dash means the step does not exist in that setup. What each metric is, what it tells you and its caveats are in the definitions under the table; the values for the scenario you select are in the panel beside the map, with the computation behind each on hover.
Three things to hold while reading it. Pre-survey and in-survey are about the signal, not the moment: in this mapping a removal is pre-survey when it rests on fraud or technical signals (identity, device, IP, duplicates), even if the platform only terminates the person a few questions in, and in-survey when it rests on the answers given during the questionnaire. Some reports label the first group in-survey fraud removal. Measurable is wider than reported: a supplier can compute every row, and most of the time reports only the survey window, the rows a buyer could see, because the others open conversations it does not necessarily want to have. And the survey-window rates on this page divide by survey starts, the number a fieldwork report actually carries; some benchmarks divide by all records at the door, and read lower on the same data.
| Metric and formula | Buyer hosts |
Buyer supplier hosts |
Supplier hosts |
Supplier buyer hosts |
|---|---|---|---|---|
| Quality: where bad respondents are removed | ||||
| Supplier pre-survey removal ratesupplier's quality terminates before the survey ÷ routed | ✗ | ✗ | ✓ | ✓ |
| Buyer pre-survey removal ratequality terminates at the survey link ÷ entrants | ✓ | – | – | ◐ |
| In-survey removal ratein-survey quality terminates ÷ survey starts | ✓ | ✗ | ✓ | ◐ |
| Post-survey removal ratebad-quality completes removed after review ÷ completes | ✓ | ✗ | ✓ | ◐ |
| Reconciliation ratecompletes the buyer rejects ÷ completes delivered to it | ✓ | ✓ | ◐ | ◐ |
| Bad quality ratebad-quality removals in your window ÷ everyone who entered it | ✓ | ✗ | ✓ | ◐ |
| Good-to-bad quality ratiogood-quality completes delivered ÷ bad-quality removals in your window | ✓ | ✗ | ✓ | ◐ |
| Performance: how the fieldwork runs | ||||
| Incidence rate (IR)completes ÷ (completes + terminates) | ✓ | ✗ | ✓ | ◐ |
| Screen-out / disqualification rateterminates for no profile match ÷ survey starts | ✓ | ✗ | ✓ | ◐ |
| Over-quota rateover-quota ÷ survey starts | ✓ | ✗ | ✓ | ◐ |
| Drop-off (abandon) ratepartials, screener + questionnaire ÷ survey starts | ✓ | ✗ | ✓ | ◐ |
| Conversion ratedelivered completes ÷ entrants at the link | ✓ | ✗ | ✓ | ◐ |
✓ measured directly · ◐ outcome reaches you, reason does not · ✗ not reported to your side · – the step does not exist in that setup
The twelve metrics, defined
Supplier pre-survey removal rate
QualityWhat it isThe share of the respondents a supplier routed to a study that its own quality layer terminated before the survey existed to them: duplicates, technical fraud (anti-detect browsers, proxies, automation), blocklisted or hyperactive accounts, failed traps in the pre-screener. Pre-screen terminates are not part of it: they are a fit decision, not a quality one, and they surface only in the supplier's incidence.
What it tells youWhether the supplier pre-cleans its traffic at all, and how hard. A high rate can mean a careful supplier, an aggressive one, or a supply defective enough to need it; the rate alone cannot say which. A rate near zero can mean clean traffic or no checks.
CaveatsOnly the supplier can compute it, and it appears in no standard report. A catch rate is not an accuracy rate: nobody measures the false positives, the honest people caught by mistake. It is not comparable across suppliers, because each runs its own fraud vendor, thresholds and upstream filtering. When the supplier hosts, its gate is the only pre-survey gate; when the buyer hosts, a second gate follows at the link.
Buyer pre-survey removal rate
QualityWhat it isThe share of entrants at the survey link terminated before the first question by the survey side's own quality checks, usually a fraud-detection tool plugged into the link: duplicates, including the same person arriving through two suppliers, technical fraud, blocklisted or hyperactive accounts.
What it tells youWhat the survey side's checks flag among traffic the supplier already passed. It is not a verdict on the supplier: the two systems see different signals, the supplier holding identity, account and IP history across many studies, the tool at the link seeing a device and a session, and they run different thresholds and disagree. It is the one number a buyer can compute alone about the supply side. A rate that climbs across waves, or differs sharply between suppliers on the same study, is a question worth asking, not a conclusion.
CaveatsIt exists only when the buyer hosts the questionnaire: the survey link is the buyer's door, and its checks run there. When the supplier hosts, there is no link and no second gate. Some reports call it in-survey fraud removal, because the termination is often executed after the first question; in this mapping a removal that rests on fraud or technical signals is pre-survey whenever it is executed, and in-survey is reserved for removals that rest on the answers. The supplier is not blind to it: most platforms return these people on a fraud or duplicate exit redirect, so it sees the count without the reason. Duplicates across suppliers are the one category only this gate can catch, since neither supplier knows the other is in the study.
In-survey removal rate
QualityWhat it isThe share of survey starts terminated by a quality check on the answers given during the survey, in the screener or in the questionnaire: speeding, straight-lining, failed red herrings or low-incidence traps, contradictions with stored profile data. A quality terminate is its own disposition, returned on a quality exit redirect. Removals that rest on fraud or technical signals belong to the pre-survey rates in this mapping, even when the platform executes them during the questionnaire.
What it tells youHow much of the traffic that started failed the survey's own quality checks. Catching it here is cheaper than after completion: a terminate costs a click; a bad complete costs an incentive, a replacement and a re-field.
CaveatsA high rate says something about the check before it says something about the people: a check that a large share of a sample fails may be badly calibrated. The split by screener and questionnaire, and by check, is more useful than the total. Some benchmarks divide by all records at the door rather than by starts, and read lower on the same data.
Post-survey removal rate
QualityWhat it isThe share of completes judged bad quality on review and removed before delivery: gibberish or AI-written open ends, straight-lined grids, internal contradictions, duplicates surfacing in the data file.
What it tells youThe clean-up bill: bad quality that survived every earlier gate, by the reviewer's own standard. Every point of it was already paid for once, and each removal restarts a journey at the far-left edge of the map, through the same chain that produced the problem.
CaveatsWho reviews depends on who hosts: the buyer when it hosts, the supplier when it does. When the buyer hosts, this review is also the reconciliation the supplier receives. Completes and delivered completes are different numbers; agree which one the CPI is priced on before fieldwork. B2B studies run far higher here than consumer studies.
Reconciliation rate
QualityWhat it isThe share of completes delivered to the buyer that the buyer identifies as bad quality and refuses to pay for: IDs it does not recognize, duplicates against its own records, completes its review threw out.
What it tells youWhere the two sides' counts meet for the first time, and how far apart they are. It is the number the CPI is finally settled on.
CaveatsA low rate is not a clean sample. It says the buyer found little to reject in what it received, which depends as much on the cleaning that ran before delivery as on the traffic: a supplier that removed 60% of its completes before delivering will show a low reconciliation rate on a sample that was anything but clean. Read it with the post-survey removal rate. When the buyer hosts, reconciliation is the whole post-survey review: the same completes, seen from the supplier's seat as completes it will not be paid for. When the supplier hosts, it is the buyer's second review, of a file it did not count itself. Agree the CPI base and the dispute rule before fieldwork, not in the post-field email.
Bad quality rate
QualityWhat it isEvery removal on quality grounds inside your window, over everyone who entered it. For the buyer the window opens at the link: the checks at the link, the in-survey terminates and the post-survey removals. For the supplier it opens at routing and adds its own pre-survey removals.
What it tells youHow much of the traffic aimed at a study was bad, wherever it was caught. The single number for the quality problem, before any question of who caught it.
CaveatsBoth sides can compute it, on different windows, so the two seats read different values on the same study. Suppliers usually report the survey window, because including their own gate opens conversations they do not necessarily want to have. A catch rate says nothing about accuracy, and one supplier's rate is not comparable to another's: different vendors, thresholds and upstream filtering.
Good-to-bad quality ratio
QualityWhat it isGood-quality completes delivered, over the bad-quality removals in your window: usable completes per bad entry caught. The window opens at the link for the buyer and at routing for the supplier, as for the bad quality rate.
What it tells youHow much bad traffic a study, or a source, made you absorb per usable complete. Computed the same way across sample sources on the same study, it is a direct way to compare them.
CaveatsThe two seats read different values on the same study, and below 1 is common once the pre-survey gates are counted. Ratios computed among completes only, good against bad among what was delivered, are a different measure with a different denominator; do not compare the two.
Incidence rate (IR)
PerformanceWhat it isThe share of screened people who fit the target. By definition, qualified ÷ (qualified + terminates), over-quotas and drop-offs excluded. The qualified point is rarely logged, so in practice most reports use completes ÷ (completes + terminates), which is what this page computes.
What it tells youHow well the sample that reached the screener matched the criteria, and therefore how much traffic a study will consume per complete. It drives feasibility, pricing and timing more than any other number.
CaveatsIt depends on the seat: the supplier counts its own pre-screen terminates among the terminates, the buyer cannot see them. It is measured on a population someone else already filtered against a copy of the same criteria, two or three times in a layered chain, which is why two suppliers report different incidence on the same study without either being wrong. Other formulas circulate, completes ÷ starts among them. Agree the formula before comparing two quotes: the gap between formulas is usually larger than the gap between suppliers.
Screen-out / disqualification rate
PerformanceWhat it isThe share of survey starts terminated because the answers did not match the target profile.
What it tells youHow much of what reached the screener did not fit, after the supplier had already pre-screened it for the same criteria. Split by criterion, it says which question is doing the terminating, which is the one thing a supplier can act on.
CaveatsIt moves with incidence but is not its complement: starts also contain over-quotas, partials and quality terminates. In some status vocabularies a screen-out and a drop-out come back as the same terminate code, so a rate read from redirects alone is overstated by the partials hiding inside it. The supplier sees the outcome, never the question that caused it, unless the buyer sends it back.
Over-quota rate
PerformanceWhat it isThe share of survey starts who qualified and were turned away because their cell was already full, closed mid-session, or throttled by pace controls.
What it tells youA pacing and quota-design problem, not an incidence problem: qualified respondents lost, and goodwill spent for nothing.
CaveatsKeep it out of the termination rate you track, so the pacing problem has its own line. Separate the commercial case, allocation full, a limit on one supplier's share, from the targeting case. Per cell is the useful unit.
Drop-off (abandon) rate
PerformanceWhat it isThe share of survey starts that never reached the end and never returned on any exit redirect: sessions that simply stopped.
What it tells youRead as respondent behavior, it measures the questionnaire: length against the promise, grid load, the device it arrives on. But the band mixes two populations with opposite fixes: people who left, and sessions that broke.
CaveatsOnly the party hosting the questionnaire can split the two; if you do not host, the drop-off rate you receive is a mixture. A partial in the screener means something different from a partial in the questionnaire: the first never saw your questions. Some platforms report a partial as a terminate, and some benchmarks divide by records at the door rather than starts, so agree the definition before comparing two numbers.
Conversion rate
PerformanceWhat it isThe share of entrants at the link that ended as a delivered complete: the whole survey window in one number.
What it tells youWhat a study costs in traffic per usable complete, from the survey side. It is the number the supplier is paid on, so it is the one both sides watch.
CaveatsThe supplier often divides by what it routed instead of what arrived, which alone explains many disagreements about how a study went. Neither entrant nor start has a standard definition, first page load or first answered question, so agree the event before comparing conversion across suppliers. It says nothing about what the chain discarded upstream to produce it.
Why the two sides never get the same number
The redirect is the boundary. When the buyer hosts, a respondent leaves the supplier's system at the link and comes back on an exit redirect: complete, terminate, over-quota, quality, often a fraud or duplicate exit as well. Or does not come back at all. The supplier learns the outcome, never the reason. A terminate does not say which question failed; a session that never returns does not say whether the person left or the page broke. The buyer, for its part, learns nothing about what happened before the link unless the supplier chooses to report it, and standard reports do not.
The result is an asymmetry of information that limits both sides. The supplier knows how many people it routed and removed, but not which question terminated its respondents or why a complete was rejected. The buyer knows every disposition inside its survey, but not how the sample that reached it was selected and filtered. Neither side sees the whole performance of the study, and neither has a direct incentive to share more: for the supplier, the supply-chain numbers open conversations it does not necessarily want to have; for the buyer, sending back the reason behind each terminate and each reject is effort with no immediate return. Improving the performance requires exactly that exchange, which is the argument of the roadmap on the respondent-experience page.
Three formulas move with the seat even when both sides are honest. Incidence: the supplier counts its pre-screen terminates among the terminates; the buyer cannot see them. Bad quality rate and good-to-bad ratio: the supplier's window opens at routing, the buyer's at the link, and suppliers usually report from the link. Conversion: the supplier divides by what it routed, the buyer by what arrived. And two definitions vary by platform before any formula runs: what counts as an entrant, and what counts as a start. Three things are worth agreeing in writing before fieldwork, so the numbers can be compared afterwards: which incidence formula will be used; how quality will be assessed, meaning the pre-survey, in-survey and post-survey removals and the good-to-bad quality ratio, and on which window; and whether several suppliers are plugged into the same study, since that decides who can catch duplicates and how the blend will be reported.
Survey fieldwork metrics: questions people ask
Short answers, each drawn from the sections above.
How is incidence rate calculated in market research?
By definition, qualified ÷ (qualified + terminates): the share of screened people who fit the target, over-quotas and drop-offs excluded. In practice the qualified point is rarely logged, so the formula most reports use is completes ÷ (completes + terminates), which is what this page computes. The result also depends on the seat: a supplier counts its own pre-screen terminates among the terminates, a buyer cannot see them, which is why the GDQ Wave 2 benchmark reports 59.1% for research agencies and 45.9% for suppliers as the mean incidence its contributors provided. Agree the formula before comparing two quotes; the gap between formulas is usually larger than the gap between suppliers.
What is the difference between screen-out rate and incidence rate?
Screen-out (disqualification) rate is terminates ÷ survey starts: the share of starts terminated for not matching the profile. Incidence rate is the share of screened people who fit: completes ÷ (completes + terminates) in practice, qualified ÷ (qualified + terminates) by definition. They move together but are not complements, because starts also contain over-quotas, partials and quality terminates, which belong to neither side of the incidence formula.
Which fieldwork metrics can a buyer compute without the supplier's data?
It depends on who hosts the questionnaire. A buyer that hosts can compute everything from its own link onward: its pre-survey removal rate at the link, the in-survey and post-survey removal rates, reconciliation, the bad quality rate and the good-to-bad ratio on the survey window, incidence as seen from its seat, screen-out, over-quota, drop-off and conversion. It cannot compute the supplier pre-survey removal rate, and therefore not the journey-wide versions of the bad quality rate and the ratio, unless the supplier shares what it routed and removed. A buyer that does not host receives a data file and a count, and can compute one thing itself: the reconciliation rate. A supplier that does not host sees the survey as exit redirects (complete, terminate, over-quota, quality, often fraud or duplicate): outcomes, never reasons. The controls above the map show each case; the table has the full matrix.
Why do two suppliers report different incidence on the same study?
Because incidence is measured on a population someone else already filtered. Each supplier pre-screens its traffic against a copy of the targeting criteria, on stored profile data of different ages and quality, before the survey's screener runs. In a layered chain a respondent can be pre-screened two or three times. Two suppliers can therefore report very different incidence on the same study without either being wrong, or lying, and neither number tells you which supplier's routing was better.
What is the reconciliation rate in sample fieldwork?
The share of completes delivered to the buyer that the buyer identifies as bad quality and refuses to pay for. When the buyer hosts the questionnaire, reconciliation is the whole post-survey quality review: the completes the buyer removes from its data are the ones the supplier is told it will not be paid for. When the supplier hosts, the supplier cleans the completes first, and reconciliation is what the buyer rejects afterwards from the file it received. A low reconciliation rate is not a clean sample: it depends as much on the cleaning that ran before delivery as on the traffic. Either way it is the first point where the two sides' counts meet, so the CPI base and the dispute rule belong in the contract, not in the post-field email.
Do fieldwork reports cover the whole respondent journey?
No. A standard fieldwork report covers the survey window, from the first survey start to the delivered complete: starts, screen-outs, over-quotas, partials, quality terminates, completes and removals after review. The supply-chain half of the journey, everything the supplier routed and terminated before the survey link, is left out, even though the supplier holds that data. It is rarely reported because it opens conversations the supplier does not necessarily want to have, so the metrics a buyer receives describe a population that was already filtered against a copy of its own criteria. The left half of the map is that missing part.
The journey band by band: what each is, how the industry names it, and what to exchange
Every band of the map, in journey order: what it is, the industry term where one exists, the metrics it feeds, and, where it matters, what would have to be exchanged between the two sides for its number to be seen from both seats. The notes hold for all four scenarios. Counts are the benchmark-based scenario with the buyer hosting; the two merged or client-side bands only appear when the supplier hosts. Band names and volumes are the same as on the respondent-experience page, which carries the longer note on each, and what the person experiences there.
Respondents the supplier routes to the study1,363
Everyone the supplier put in front of this study: panelists who clicked an offer (a stated length, a stated reward) and were sent here by a router choosing the destination with the highest expected earnings per click, or who received an invitation for this study specifically. Either way they reached the supplier's own screening layer, and most of them see a few pre-screening questions there, to pre-check their eligibility and their quality before the survey. This is where the map starts, and it is already a long way downstream of the person deciding whether to answer a survey at all.
What happened before this (how the panel was recruited, who was invited, who never opened the invitation) is out of scope here. It matters, and it is invisible to everyone downstream of the panel that owns it.
Terminated by the supplier for pre-survey quality173
Terminated by the supplier's own pre-survey quality layer before the survey existed to them: duplicate entries, technical fraud (anti-detect browsers, proxies and VPNs, automation), known fraudsters on blocklists, failed quality traps inside the pre-screener, and hyperactive accounts answering implausible volumes of surveys. Suppliers often rely on an external fraud-detection provider for the technical signals, with a proprietary layer or score of their own on top.
Terminated for pre-survey quality: single merged gate (supplier hosts)305
When the supplier hosts there is no link and no second check: its quality layer is the journey's only pre-survey gate, and what it misses walks straight into the survey. Because every source's traffic passes one door, duplicates across sources can all be caught here.
Terminated by the supplier at pre-screening190
Qualified as a person, terminated as a fit: pre-screened against the buyer's targeting criteria, through pre-screening questions that often collect new answers or ask again for information the supplier already holds, or turned away because the supplier's own allocation for this study was already full.
Entrants at the survey link1,000
Everyone who cleared the supplier's checks, qualified on whatever pre-screeners it ran, and arrived at the survey link. It is the only number both sides can really agree on.
Everything to the left of this node happened in systems with no shared identifier, no shared status vocabulary, and no obligation to report. Everything to the right is the survey side's to instrument.
Terminated at the link for pre-survey quality132
Entrants terminated by the survey side's own pre-survey quality layer, before the first question, usually a third-party fraud-detection tool plugged into the link: duplicates, including the same person arriving through two suppliers, technical fraud, blocklisted and hyperactive accounts. These checks run after the supplier's, on different signals and thresholds, so the band is where the two systems disagree, not a verdict on either. Most platforms return these people to the supplier on a fraud or duplicate exit redirect, so the supplier sees the count, not the reason. Some reports call this band in-survey fraud removal when the termination is executed after the first question; here it is pre-survey because it rests on fraud and technical signals, not on answers.
Survey starts868
Everyone who sees the first question of the survey. The standard denominator for completion rate. It is not always tracked properly: where it is not, entrants at the link are used in its place. It is also the denominator for every rate on this page that describes the survey window: screen-out, over-quota, in-survey removal, drop-off. And a start is defined per platform, first page rendered or first question answered, the two differing by several points on a mobile-heavy sample, so every rate with starts in the denominator moves with both the definition and whether it is tracked at all.
Terminated in-survey for quality (screener)110
Removed by a quality check on the answers while still inside the screener: speeding, contradicting stored profile data, failing a red herring, tripping a low-incidence trap set for people who qualify for everything. Built mostly to catch respondents who misrepresent themselves to qualify. Returned to the supplier on a quality exit redirect. Removals that rest on fraud or technical signals count as pre-survey in this mapping, whenever they are executed.
Terminated for qualification: no profile match269
Started the screener and did not qualify: the answers do not match the target profile. This is the terminate the participant experiences as being thrown out.
Over-quota55
Qualified, but the cell they belong to was already filled, closed mid-session, or throttled by pace controls.
Partials (screener)45
Started the screener and never reached its end. Two different populations share this band: true drop-offs, which are a decision, and technical failures: broken sessions, incompatible devices, lost redirects. Most disposition systems cannot tell them apart, because in both cases the respondent simply stops sending signals.
Qualified389
Passed the screener, inside a quota with room, now answering the main questionnaire.
Buyers and suppliers rarely track this point directly, and it is the one input the strict incidence formula needs, which is why reports fall back on completes instead. Tracking it also gives partials a meaning: someone who leaves before this point most likely felt they would not qualify; someone who leaves after it genuinely disliked the experience.
Terminated in-survey for quality (main survey)43
Qualified, then removed mid-questionnaire by a quality check on the answers: speeding, straight-lining a grid, a failed open end, a trap question. Respondents usually have to fail more than one check before they are terminated. It is done mid-survey rather than after so that the supplier does not pay an incentive to someone the buyer would reconcile later. Returned to the supplier on a quality exit redirect, like the screener's.
Partials (main survey)60
Qualified, started the main questionnaire, and never reached the end. The same two populations as in the screener: true drop-offs, which are a decision, and technical failures.
Completes286
Reached the last page. Counted as a complete by the survey platform and, usually, already paid by whichever panel in the chain owns the participant. Not yet judged: the split into good and bad quality happens next.
Not everyone in this band answered the survey. Some people find the exit redirect, the URL that marks a session as complete, and call it directly: the supplier's system records a complete that the survey data does not contain. The industry calls that a ghost complete.
Bad-quality completes: removed after review25
Completes judged bad quality on review and removed before delivery: gibberish or AI-written open ends, straight-lined grids, internal contradictions, in-survey duplicates surfacing in the data file. When the buyer hosts, this review is the reconciliation: the supplier learns these completes will not be paid for.
Delivered completes: good quality261
What is delivered as good quality: the completes that raised no flag at all, and the ones that raised a flag but were kept after review. Keeping a flagged complete is a judgment call, and the size of that flagged-and-kept share is worth knowing. When the buyer hosts, delivered and accepted are the same count, made by the same side.
Accepted by the client (supplier hosts)251
Delivered completes the client accepted and paid for, after its own review of a file it did not count itself. Only a distinct step when the supplier hosts, and the count the CPI is finally settled on.
Reconciled: rejected by the client (supplier hosts)10
Delivered completes the client rejected after the supplier's own cleaning: IDs it does not recognize, duplicates against its own records, completes its own review threw out. PureSpectrum's status for it reads “buyer reconciled transaction; complete now considered termination.” A reconciled complete can cost the person a reward that was already credited.
About the numbers, and sources
About the numbers. The volumes are one scenario built on the Global Data Quality Benchmarking report, Wave 2 (H1 2026; data collected October 2025 to March 2026 from 46 companies in 13 countries, about 1.8 million survey records, 87% of them general consumer studies). The survey half uses the research-agency cut, per 1,000 records at the link: 13.2% removed before the first question, 15.3% removed in-survey (11.6% of it for fraud), 10.5% abandoned, 59.1% actual incidence, 8.9% removed after completion. The supplier half uses the supplier cut: 12.7% removed by its own quality checks, and an actual incidence of 45.9%. Three liberties to know about. The benchmark's removal and abandon rates are over all records; this page divides in-survey removals and drop-offs by survey starts, the number a fieldwork report carries, so the same scenario reads 17.6% and 12.1% here. The benchmark's incidence is the mean incidence its contributors provided, whatever formula they used; the scenario was sized so that the strict formula, qualified over qualified plus terminates, reproduces 59.1% from the buyer's seat and 45.9% from the supplier's, the supplier counting its own pre-screen terminates, which is what sizes those terminates at about 190 per 1,000 people who reach the link, an estimate; the practical formula on the same people gives 51.5% and 38.4%. And the two cuts come from different companies' records, not from the same studies; the map joins them as if they were one study. Four things the benchmark does not report are estimated: over-quota (set at 6.3% of starts), how quality removals and partials split between screener and questionnaire, every sub-branch split, and the client-side reconciliation when the supplier hosts (10 of 261). The supply side is drawn as one supplier with two termination gates, a deliberate simplification marked on every band it affects. What no band can show is what every check missed: that share is real, sits inside the delivered completes, and can only be sized with a validation study on a known-good subsample. The same scenario from the respondent's side is on the respondent-experience page.
Sources. Volumes and benchmark rates: Global Data Quality Benchmarking, Wave 2, H1 2026 (Insights Association / GDQ), global research-agency and supplier cuts. Definitions marked GDQ are quoted from the Global Data Quality glossary; band names follow it wherever it has a term, and where it has none (complete, terminate, over-quota, partial, the depth of a supply chain), the words are the industry's. Disposition and status vocabulary otherwise follows the Cint Exchange respondent-journey documentation and the PureSpectrum supplier status codes, the two most complete public disposition-code lists. Supply-chain vocabulary follows the ESOMAR 37 questions on sample sources, source transparency, and blend; for who sits between a panelist and a survey, the GDQ / MRS presentation of the sampling ecosystem is the best public map.
Corrections and suggestions welcome: or contact@enlightn.io.