Product

Live Quotas and Fieldwork Visibility: Why Boards Need a Control Room

Why qualitative bulletin boards need live visibility into who is on, how far they are, and where completes are stalling.

11 min readPublished 2026-06-01· Updated 2026-10-29
Productfieldwork · quotas

Fieldwork is the period when participants are actually answering your questions. A quota is a target for how many of each type of person you need, such as a set number of parents or a set number of heavy users. In a multi-day board you will not hit those targets by hoping. You need to see what is happening while there is still time to act.

If you only learn completion rates at close, you are managing archaeology, not fieldwork. Live visibility lets you nudge, re-invite, and probe while the study can still be saved.

Qualitative quotas are not survey quotas

In a survey, quotas are about statistical balance across hundreds of people, and software closes a cell automatically when it fills. In qualitative work you recruit a small group on purpose, often 15 to 40 people, and every person matters. Losing three out of eight in a key segment is not noise; it can mean you cannot tell that segment’s story at all. That is why qual quotas are watched by a person, in real time, rather than enforced by a counter.

What good visibility includes

  • Who is currently on the board
  • Progress by day and by person
  • Bounce / invite failure signals
  • Support escalations needing humans

‘Bounce’ means an invitation never reached the person, for example because of a bad email address. Without a signal, you may think someone ignored you when they never got the message. ‘Escalation’ means a participant asked for help the automated support could not solve and a researcher needs to step in.

Why it matters day by day

On Day 1, you want to confirm that invited people can actually get in. On Day 2 or 3, you want to see who is slipping behind. On the last days, you want to know whether every segment has enough finished voices to support a story. Each of these decisions is cheap early and expensive late.

MomentWhat you want to seeWhat you can do
LaunchWho has joined, who has notResend invites, fix bad addresses
Mid-boardWho is behind on the current daySend a friendly reminder
Final daysWhich segments are thinRecruit a replacement or probe harder
AnytimeOpen support requestsReply before the person gives up

A decision framework for stalled fieldwork

  1. 1Diagnose first: is the problem access (cannot log in), friction (task too hard), or motivation (forgot or lost interest)? Each needs a different fix.
  2. 2Fix access issues immediately with resent links or manual help, because these are the cheapest to solve and the most frustrating for the participant.
  3. 3For friction, simplify the task or offer an alternative way to answer, and tell people it changed.
  4. 4For motivation, send a short personal reminder and, if allowed, confirm the incentive terms again.
  5. 5Decide a cutoff for replacement recruits early. A replacement who joins on the last day cannot give you a multi-day perspective.

A scenario

An agency runs a four-day board with two groups of shoppers. By midday on Day 2, the dashboard shows one group has far fewer people active than the other. The researcher sees several invite failures, fixes the contact details, and sends fresh invitations. Without that view, the gap would have appeared in a closing report with nothing left to do about it.

FAQ

Common questions (tap to expand)

fieldworkquotasresearch ops

Keep reading

More from the journal

Ready to field?
Live this week.

Import a guide from your discussion guide, publish a multi-day board, and walk into the debrief with themes already forming.