Separate a finished field interview from a received submission

Give each count a precise completion meaning

Identify what the field team means by complete: the conversation ended, the collector finished entering answers, required checks passed, or the receiving system accepted the record. These are different milestones. Keep a restricted internal record reference and the minimum operational status needed to reconcile them. Avoid copying research answers or participant contact details into a widely shared progress tracker.

Agree which milestone supports each report. A schedule update may count interviews conducted, while an analysis handover must identify received records available for review. Record unresolved exceptions explicitly so neither team silently changes the meaning of the total. The closeout ledger should make an unmatched record findable by its authorized owner without requiring everyone to inspect the underlying research material.

Locate the record in the actual collection workflow

ODK Collect distinguishes draft, finalized and sent forms. Its documentation describes finalized as ready for submission and sent as received by the server. This supports separating local readiness from receipt; it does not establish that the received answers have passed research review.

Have the authorized collector or operations owner inspect the relevant record state and compare it with the receiving evidence. A missing row in one analyst export may reflect extraction scope rather than a failed send. Conversely, a local indication that work is ready does not prove arrival. Capture the observed state and time, retaining uncertainty when the two ends cannot yet be reconciled. Do not recreate a record merely to make the counts agree.

Resolve the unmatched state without losing evidence

Assign a specific route for each discrepancy. An unfinished record goes to the collector for the approved completion decision; a queued record goes through the permitted transmission process; an apparently received but absent record goes to the system or export owner. Preserve the original record and error evidence while the owner investigates. Avoid repeated manual submissions through alternate channels that could create competing copies or disclose research data outside its approved route.

If a record cannot be recovered, describe the loss and its known scope. Do not ask the collector to reconstruct exact answers from memory or automatically contact the participant again. Any recontact must follow the study’s permissions and participant arrangements. The research owner decides whether the gap affects the study deliverable. An operational deadline does not turn missing evidence into an acceptable inferred answer.

Close on verified receipt and carry limitations forward

Reconcile the final ledger against the receiving system using the agreed record references. Keep receipt separate from later quality approval and attachment review. A record can arrive successfully and still require a substantive review. Identify any records remaining on devices under the approved retention procedure, without treating closeout as authority to clear storage or change security settings.

Hand analysis staff the received count, the fieldwork count and a concise explanation of unresolved differences. State the cutoff time and whether further authorized submissions are expected. If a late record arrives, update its status and inform the dataset owner rather than quietly inserting it into an already frozen analysis. The accepted closeout is a traceable boundary between collection work and received evidence, not a promise that every interview necessarily produced an analyzable record.

Make the reasoning concrete.

A fictional service-design team conducts workshop-observation interviews at a business site with intermittent connectivity. Its schedule shows twelve conversations completed, but the analysis export contains eleven records and one device still shows a record awaiting transmission.

The team chooses reconciliation and does not repeat the interview merely because the transmission state is unresolved.

Take the questions into your next brief.

Use these prompts in your own notes. Nothing is submitted from this page.

1. Milestone

   What does complete mean in each operational count?

2. Reference

   Which permitted identifier connects the collected and received record?

3. State

   What do the device and receiving system actually show?

4. Owner

   Who can resolve the specific unfinished, queued or unmatched state?

5. Cutoff

   What remains outstanding at the analysis handover time?

Watch for the wrong conclusion.

• Counting finalized records as received without evidence.
• Recreating an uncertain submission through an alternate route.
• Treating successful receipt as substantive quality approval.

Sources & scope

Workflows, worksheets and fictional examples are original editorial analysis. Sources support only specifically attributed principles. Platform guidance can change; legal requirements depend on jurisdiction and context. No measured results or named human reviewer are claimed.

• ODK Docs: Helping data collectors take the right next step after filling a form →Primary data-collection documentation · Supports: Supports the draft, finalized and sent distinction in ODK Collect. The closeout ledger and escalation method are original analysis.