How Fieldwork Management Software Improves Research Delivery Across CAWI, CATI, and CAPI

Fieldwork management software helps market research teams manage data collection, track survey progress, monitor interview quality, and control costs across different research methods. Whether a study uses online surveys (CAWI), telephone interviews (CATI), or face-to-face interviews (CAPI), effective fieldwork management is important for delivering reliable results on time.

Problems identified before a study launches are usually easier to fix. Once fieldwork ends, correcting those problems may require additional interviews, extra costs, or changes to the final research report.

During fieldwork, research teams must manage response targets, timelines, data quality, and budgets together. The sooner they identify an issue, the more opportunities they have to correct it before it affects the project.

In market research, fieldwork management software refers to systems used to manage survey data collection. It is different from field-service management software, which is generally used to schedule technicians and service appointments.

For online studies, important fieldwork activities include synchronizing quotas with sample suppliers, managing survey traffic, and monitoring incidence rates during soft launch. OnGraph covers these processes in its guides to market research project management software and tracking quotas across multiple suppliers.

This article focuses on the additional challenges that arise when research teams manage CAWI, CATI, and CAPI together, including interviewer performance, survey outcomes, quality validation, and differences between data collection methods.

Where Fieldwork Delays and Problems Begin

CAWI, CATI, and CAPI collect and report fieldwork progress differently.

Online survey completions are usually received through supplier status codes such as complete, terminate, overquota, and quality terminate. These statuses are communicated through survey panel integration, and the redirect and callback processes are explained in OnGraph’s guide to key integrations required in a market research platform.

Telephone fieldwork produces different outcomes, including no answer, busy, appointment scheduled, refusal, answering machine, and wrong number.

Face-to-face interviews often depend on tablet synchronization. When interviewers work in areas with limited connectivity, completed questionnaires may not reach the central system until later that day or even several days afterward.

When these activities are managed in separate systems, field managers often combine reports manually to understand overall progress.

The bigger problem is how long it takes to identify an issue.

For example, an interviewer may not be following the correct process, respondents may repeatedly abandon a particular question, or one quota cell may be filling through only one interview mode.

These problems are easier to address during the early stages of fieldwork. If they are discovered near the project deadline, correcting them becomes more difficult and expensive.

A central fieldwork management platform helps teams monitor these activities together and identify problems while there is still time to act.

CAWI vs. CATI vs. CAPI: Key Fieldwork Differences

Each data collection method requires different monitoring and quality controls.

Although these methods work differently, research teams still need consistent reporting across the complete project.

That starts with using the same definitions for survey outcomes.

Use Consistent Outcome Codes Across All Modes

A mixed-mode research project becomes easier to manage when every interview outcome follows a consistent classification system.

The American Association for Public Opinion Research (AAPOR) provides this framework in its Standard Definitions, 10th edition (2023).

The standard groups sampled cases into four main categories:

1. Completed interviews: Cases where the required interview has been completed.
2. Eligible cases not interviewed: Eligible respondents who did not complete an interview.
3. Cases of unknown eligibility: Cases where the respondent’s eligibility could not be confirmed.
4. Ineligible cases: Cases that do not meet the study’s eligibility requirements.

AAPOR recommends using standardized outcome definitions when reporting survey methods.

For fieldwork managers, these categories make it possible to compare progress across CAWI, CATI, and CAPI without treating every system’s raw status codes as equivalent.

They also support important fieldwork performance measures.

Response rate, cooperation rate, and contact rate

Counting completed interviews is useful, but it does not always explain why a study is progressing slowly.

Three measures provide additional information:

• Response rate: Measures completed interviews relative to the relevant sampled cases, using the applicable AAPOR definition. Under RR1, unknown-eligibility cases remain in the denominator.
• Cooperation rate: Measures completed interviews among eligible cases where contact was established, according to the selected cooperation-rate definition.
• Contact rate: Measures the proportion of cases where contact was established, using the applicable AAPOR formula.

Consider a telephone study that is behind schedule.

If the contact rate is low, the problem may involve poor contact information, calling schedules, or insufficient dialing capacity.

If the contact rate is reasonable but cooperation is low, the research team may need to review the interviewer introduction, respondent engagement, or incentive strategy.

Both situations can produce low completion numbers, but they require different solutions.

Track survey break-offs by question

AAPOR also recognizes the value of recording where respondents stop participating in an interview.

Instead of tracking only the total number of incomplete interviews, fieldwork software can record the questionnaire section or question where a respondent leaves.

For example, if many respondents abandon a survey at the same question, the research team can investigate whether the question is confusing, too sensitive, or difficult to answer.

Identifying these patterns during fieldwork gives the team an opportunity to review the questionnaire before the problem affects more respondents.

CATI: Track Call Outcomes and Interviewer Performance

Telephone interviewing requires more than monitoring the number of completed surveys.

A CATI system must also manage calling schedules, callbacks, appointments, refusals, and interviewer productivity.

These activities directly affect delivery timelines, response rates, and research costs.

Manage callbacks and calling schedules

When a respondent does not answer, the system needs rules for deciding when another attempt should be made.

These rules may include the number of permitted attempts, calling hours, and the time between attempts.

Appointment management is equally important.

If a respondent requests a callback at 7 PM, the CATI system should schedule the call for the correct time and time zone.

Refusal handling also requires clear rules. Depending on the study protocol, some cases may be eligible for a follow-up attempt by an experienced interviewer, while others should be closed.

A properly configured CATI system helps ensure that these decisions are handled consistently and in line with applicable calling rules.

Monitor interviewer productivity and quality

Field managers need visibility into interviewer performance, not just overall quota progress.

Useful CATI metrics include:

• Completes per interviewer hour: Shows how many completed interviews each interviewer delivers relative to working time.
• Contact rate: Helps identify difficulties reaching respondents.
• Cooperation rate: Shows how effectively eligible contacted respondents are converted into completed interviews.
• Interview duration: Helps identify interviews that are unusually short or long.
• Disposition patterns: Shows how frequently interviewers record refusals, appointments, incomplete interviews, and other outcomes.

These metrics should be reviewed together.

For example, an interviewer with an unusually high completion rate and much shorter interview durations than the rest of the team may require additional quality checks.

That pattern does not automatically mean the interviews are invalid. However, it gives supervisors a reason to review the work before accepting a large number of additional completes.

Why Interviewer Quality Checks Should Start Early

Interviewer-administered research introduces quality risks that are different from those found in self-completed online surveys.

Interviewers may read questions incorrectly, use inappropriate probing techniques, or fail to follow the approved questionnaire.

These problems can affect the consistency and reliability of collected data.

The UK’s Interviewer Quality Control Scheme (IQCS), described by the Market Research Society, addresses interviewer recruitment, training, assessment, supervision, and validation procedures.

Its approach is consistent with the importance of interviewer quality controls in the fieldwork requirements associated with ISO 20252.

Common interviewer quality-control methods include live monitoring of telephone interviews, validation callbacks, supervisor reviews, and selected audio recordings.

What research says about audio-based validation

RTI International’s 2008 research on computer audio-recorded interviewing (CARI) examined how audio recordings could support interviewer monitoring.

The study evaluated 5,600 recorded cases.

Its findings included:

Most of the cases that initially raised authenticity concerns were cleared after investigation.

The findings suggest that audio monitoring is useful not only for detecting possible interview fabrication but also for identifying mistakes in how interviews are conducted.

A 2015 US Census Bureau paper also discussed CARI as a tool for checking interview authenticity and detecting potential falsification.

The paper described recording a small but important selection of questions rather than entire interviews. It also cited RTI’s observation that reviewers could assess interview authenticity within approximately three minutes.

How fieldwork software can support quality control

For research teams, the main benefit comes from performing checks while fieldwork is still active.

A fieldwork management platform can help supervisors:

• Select interviews for validation across individual interviewers.
• Review recordings or callback results.
• Identify interviewers who need additional supervision.
• Track whether quality checks have been completed.
• Record validation outcomes and required corrective actions.

Validation should be distributed across interviewers rather than concentrated only at the overall study level.

Checking each interviewer’s work early helps supervisors identify problems before they affect a larger number of interviews.

CAPI: Verify Location, Time, and Interview Data

Face-to-face interviewing presents a different operational challenge.

Interviews may take place in remote areas, and devices may not have reliable internet connectivity throughout the day.

As a result, completed questionnaires can remain on interviewers’ tablets before reaching the central project database.

This delay affects quota reporting and quality monitoring.

Use interview metadata for validation

CAPI systems can collect operational information, often called paradata, alongside survey responses.

Depending on the project design and applicable privacy requirements, this information may include:

• GPS coordinates: Help confirm where an interview was recorded.
• Start and end timestamps: Show when the interview took place and how long it lasted.
• Question-level timings: Help identify unusually fast responses.
• Device synchronization status: Shows which completed interviews have reached the central server.
• Selected audio recordings: Support interview validation when appropriate consent and permissions are in place.

For example, several unusually short interviews recorded at the same location within a very short period may require investigation.

However, these signals should not be treated as proof of fabrication on their own. Supervisors should review the context and use appropriate validation methods before reaching a conclusion.

Monitor offline interviews and synchronization

CAPI devices should synchronize completed interviews whenever connectivity and project requirements allow.

If a completed interview remains on a tablet for four days, the central team cannot immediately use that record for accurate quota tracking or timely quality checks.

A fieldwork dashboard should therefore show which devices have unsynchronized records and how long those records have been pending.

Research teams also need clear consent procedures for collecting location information or recording audio.

Where required by law, research codes, or project policy, informed consent should be built into the survey process rather than left to individual interviewer judgment.

Why Interview Mode Should Be Recorded With Survey Data

Combining CAWI, CATI, and CAPI is not only an operational decision.

The method used to interview respondents can also influence their answers.

Pew Research Center examined this issue in a 2015 experiment on survey mode effects.

The study randomly assigned 3,003 panelists to answer 60 questions either through telephone interviews or online surveys.

Differences between the two modes were fairly common, although they were usually not large.

The mean difference was 5.5 percentage points, with individual differences ranging from 0 to 18 percentage points.

Some questions showed larger differences.

For example:

• Family life satisfaction: 62% of telephone respondents said they were very satisfied, compared with 44% of online respondents.
• Difficulty affording food: 20% of telephone respondents reported being unable to afford food, compared with 28% of online respondents.

Pew linked these patterns partly to social desirability, where respondents may present themselves more favorably when speaking with an interviewer.

Why mode mix matters during fieldwork

Suppose a research team is collecting most responses online, but one difficult quota cell is progressing slowly.

To meet the deadline, the team decides to complete that cell through telephone interviews.

This may help improve delivery, but it also changes the interview mode used for that audience segment.

If telephone and online respondents answer certain questions differently, the final differences between quota cells may partly reflect the data collection method.

Research teams should therefore:

1. Record the interview mode for every completed case.
2. Monitor the proportion of CAWI, CATI, and CAPI interviews within each quota cell.
3. Review proposed mode changes with the analysis team before implementing them.
4. Use a controlled, versioned questionnaire across modes, with necessary mode-specific adaptations documented.
5. Consider possible mode effects when interpreting results.

These practices help research teams distinguish between actual differences in respondent groups and differences associated with how interviews were conducted.

OnGraph also discusses questionnaire and project coordination in its guide to survey project management software.

What a Fieldwork Management Dashboard Should Show

A useful fieldwork management dashboard should give project managers a complete view of CAWI, CATI, and CAPI activity without requiring them to combine reports manually.

The following seven areas are especially important.

1. Survey progress and quota tracking

The dashboard should show completed interviews against targets for each quota cell.

For mixed-mode projects, it should also display how many completes come from CAWI, CATI, and CAPI.

This helps managers identify quota cells that are behind schedule or becoming too dependent on one mode.

2. Interview outcomes and response rates

Every case should be mapped to consistent outcome categories.

The system should support response, cooperation, and contact-rate reporting using the selected AAPOR definitions.

This helps managers understand whether slow delivery is caused by difficulties reaching respondents, low cooperation, or other fieldwork issues.

3. Questionnaire break-off monitoring

Project managers should be able to identify the questions or sections where respondents stop participating.

Break-off reporting by mode can also help identify whether a particular question creates more problems in online, telephone, or face-to-face interviews.

4. Interviewer performance

For CATI and CAPI studies, the dashboard should track interviewer productivity, interview durations, and disposition patterns.

Unusual results should be flagged for supervisor review rather than automatically treated as evidence of poor-quality work.

5. Interview validation and quality checks

The system should show which interviews have been monitored, reviewed, or validated.

It should also track quality-control coverage by interviewer and record the outcomes of those checks.

This helps supervisors identify where additional training or review may be needed.

6. CAPI device synchronization

For face-to-face studies, the dashboard should identify devices holding completed interviews that have not yet synchronized.

Project managers should be able to see pending records and follow up before synchronization delays affect quotas or reporting.

7. Fieldwork costs by mode

The dashboard should compare actual costs per complete against planned costs for CAWI, CATI, and CAPI.

This helps research teams understand how mode allocation and delivery performance affect the overall project budget.

Many market research project management tools already support quota progress and cost reporting for online studies.

However, managing mixed-mode fieldwork also requires consistent outcomes, interviewer monitoring, validation, and device synchronization.

Connecting these activities through market research workflow automation can reduce manual reporting and help teams respond to fieldwork problems more quickly.

Where OnGraph Fits

OnGraph develops custom and white-label project management software for market research companies.

Its white-label market research platform describes capabilities for managing online survey launches and telephone fieldwork through a unified dashboard.

These include traffic sourcing, respondent qualification, quota management, supplier integrations, and real-time tracking of completes, call outcomes, and costs.

The platform information also describes one-click play and pause controls, interviewer validation checks, and verified samples for CATI.

OnGraph’s published information references 65+ global panel integrations and 40+ API integrations as part of its broader market research software development services.

For research agencies managing multiple fieldwork methods, custom software can be designed around their existing survey systems, interviewer workflows, validation requirements, and reporting processes.

OnGraph’s published capabilities cover online, telephone, and hybrid fieldwork. The CAPI practices discussed in this article are general guidance for face-to-face research teams and should not be treated as confirmed features of OnGraph’s existing platform.

Managing CAWI, CATI, and CAPI Across Different Systems?

Build a custom fieldwork management platform to track quotas, interviewers, quality checks, and research delivery from one dashboard.

Discuss Your Requirements

Final Thoughts

Managing research fieldwork across CAWI, CATI, and CAPI requires more than counting completed interviews.

Each method has different operational challenges, from online survey break-offs and telephone callback management to interviewer validation and offline device synchronization.

Research teams also need to understand how changes in interview mode may affect the data they collect.

Fieldwork management software helps bring these activities into one system, giving managers a clearer view of progress, quality, and costs while the study is still running.

For agencies managing complex or mixed-mode research projects, that visibility can help reduce delays, improve quality control, and support more consistent research delivery.