Live Fieldwork Monitoring: What to Watch, When to Act, and How to Keep a Survey on Track

Live fieldwork monitoring is the difference between a project that closes on time and one that is rescued at midnight before the client deadline. Once a survey launches, the numbers start telling a story straight away: who is arriving, who is qualifying, who is leaving, and which suppliers are delivering. This guide covers the metrics worth watching, how to read them together, and a monitoring routine that research operations teams can actually keep up during busy weeks.

Why fieldwork drifts without anyone noticing

Most fieldwork problems are not sudden. They build slowly while everyone assumes someone else is watching. A quota cell fills quickly with one demographic while another barely moves. A supplier sends plenty of traffic that mostly terminates. A routing change on day two quietly breaks the redirect for one country. None of these is a crisis on its own, but each one eats into the time you have left to fix it.

The usual causes are familiar to anyone who has run a busy field desk:

• Counts live in too many places. The survey platform, supplier portals and a tracking spreadsheet all show slightly different numbers.
• Nobody owns the check. The project manager assumes the field team is looking, the field team assumes the PM is.
• Raw totals hide the detail. A healthy overall complete count can mask a cell that will never fill.
• Changes are not logged. When a quota or screener is adjusted mid-field, the reason and the time are lost.

The core metrics, and what each one tells you

Every survey platform labels outcomes slightly differently, so agree the definitions with your scripting team and suppliers before launch. For reporting outcome codes formally, the AAPOR Standard Definitions report is the reference most researchers point to; for day-to-day operations, the working set below is usually enough.

Reading clicks, completes and terminates together

Clicks, completes and terminates only make sense side by side. Completes divided by clicks gives you the conversion you are actually achieving, and comparing it with the incidence assumption in the bid shows whether the costing still holds. If termination is far higher than expected, look at three things before blaming the supplier: whether the screener is stricter than the brief, whether the targeting sent to the supplier matches the screener, and whether a quota closure is being recorded as a terminate.

Drop-out rate as an early warning

A rising drop-out rate is often the first sign of a questionnaire problem rather than a sample problem. Break drop-outs down by the last question answered and by device. A grid that is unusable on a phone, a video that will not load, or an open-ended question placed too early can all show up as a sudden wall of exits. Catching it on day one means you can fix the script while most of the sample is still to come.

Build a monitoring plan before launch

The best monitoring starts before the first respondent clicks. A short plan agreed at kick-off removes most of the confusion that slows teams down mid-field.

1. Confirm definitionsAgree what counts as a complete, terminate, over-quota and drop-out with scripting and every supplier.
2. Load the quota planEnter each cell with its target and any minimum or maximum so progress is visible per cell, not just in total.
3. Set the pace curveDecide where completes should be at the end of each field day, allowing for weekends and time zones.
4. Name an ownerOne person owns the daily check and the decision log, even if several people look at the numbers.
5. Agree thresholdsWrite down what triggers action, such as a cell falling behind pace or a supplier's quality removals rising.
6. Test the redirectsRun test links for complete, terminate and over-quota for every supplier before going live.

Thresholds do not need to be precise formulas. A simple rule such as "if a cell is noticeably behind its pace by the end of day two, review targeting and supplier allocation" is better than no rule. The point is that the team agrees in advance what deserves attention, so nobody argues about it under pressure. If you need a refresher on structuring cells and limits, our survey quota management guide covers that in detail.

A daily fieldwork monitoring routine

Monitoring works best as a fixed rhythm rather than constant dashboard watching. The routine below suits a typical multi-day online project; compress it for a short field window.

First hours after launch

The soft launch is where you catch structural problems. Watch the first completes arrive and check them manually: open the data, confirm the routing behaved as intended, and confirm that each supplier's redirects are recording the right status. Hold back the full send until the soft-launch data looks clean.

Each field day

1. Morning check. Compare completes by cell and by supplier with the pace curve. Note anything behind or ahead.
2. Quality pass. Run your data quality checks on new completes and record removals by supplier. Our post on online survey data quality checks lists the usual tests.
3. Supplier actions. Ask suppliers to adjust targeting, increase sends or pause, based on what the numbers show. Record what you asked for and when.
4. Afternoon check. Confirm that the morning's actions are having an effect, especially in time zones that are just starting their day.
5. Status note. Send the client or internal stakeholders a short status note with accepted completes by cell, issues found and actions taken.

Final stretch

As cells approach their targets, close them deliberately rather than letting over-quotas pile up. Watch the hard-to-fill cells most closely, and decide early whether you need an extra supplier, a relaxed quota agreed with the client, or a field extension.

• Completes compared with plan by cell and supplier
• Quality removals recorded by supplier
• Drop-outs reviewed by question and device
• Supplier requests logged with time and reason
• Status note sent with accepted, not raw, completes
• Any quota or screener change written into the decision log

Acting on what you see

Monitoring is only useful if it leads to decisions. The common interventions, roughly in order of how often they are needed, are:

• Rebalancing supplier traffic. Move sends towards the suppliers that are converting cleanly for the cells you still need.
• Tightening targeting. If a supplier's traffic terminates heavily, share clearer profiling criteria rather than simply asking for more volume.
• Closing cells early. Close full cells promptly so respondents are not wasted and over-quota payments do not grow.
• Fixing the script. Where drop-outs cluster, fix the question or page and record the change time, since data before and after may need flagging.
• Agreeing changes with the client. Relaxing a quota or extending field is a client decision; bring evidence from the monitoring data rather than a general request.

Whatever you change, write it down. A decision log with the time, the change, the reason and who approved it saves hours later, both when the client asks why a cell looks different and when you reconcile with suppliers at close. Standards such as ISO 20252 set out service requirements for research providers, and a disciplined record of fieldwork decisions makes it far easier to show how a project was run.

Spreadsheet tracking versus a connected project record

Many teams run fieldwork tracking from a shared spreadsheet, refreshed by hand from the survey platform and supplier portals. That works on small projects, but it strains as soon as several suppliers, countries or cells are involved.

The gain is not just speed. When monitoring, status reporting and reconciliation all use the same numbers, there are fewer disagreements at close. That matters when you later have to agree complete counts and invoices with each supplier, which we cover in sample supplier reconciliation.

Where Sampledge fits

Sampledge was built by Frequent Research from day-to-day experience running research projects, and live fieldwork is at the centre of it. SampTrek holds the project's quotas, suppliers and fieldwork status in one record, so the team sees completes, terminates and over-quotas by cell and supplier instead of reconciling several exports. Because the same record carries through to close, status notes and supplier reconciliation start from figures the team already trusts. If you also buy sample directly, SampAudience lets you track audience projects from launch through fieldwork.

To see how fieldwork tracking fits the wider project flow, read how Sampledge works, or book a demo and walk through a live project with our team.