ODK Central

FieldOps integrates with ODK Central to bring field data collection into the operational workflows used by monitoring teams.

Instead of collecting data in ODK Central and managing follow-up work separately, teams can connect their ODK Central server, select and map forms to FieldOps operational structures, synchronize submissions, review visits, record findings, create follow-up actions, and track accountability from FieldOps.

What you can accomplish

With the ODK Central integration, you can:

• Connect an ODK Central server to FieldOps
• Test ODK Central connections before using them
• Connect to an ODK Central project
• Select existing ODK Central forms
• Map ODK Central forms to a FieldOps Programme, Project, and Site
• Optionally associate forms with Monitoring Templates
• Synchronize ODK Central submissions into FieldOps
• Convert synchronized submissions into FieldOps visits
• Track visits through the FieldOps visit lifecycle
• Review submitted field visits
• Upload and review visit evidence
• Maintain a visit history and audit trail
• Identify issues discovered during monitoring
• Record findings against project monitoring activities
• Define finding severity and lifecycle status
• Create follow-up actions from findings
• Assign responsibility for follow-up actions
• Track action progress and accountability
• Keep field data, monitoring findings, and follow-up activities connected

This allows ODK Central to remain the field data collection platform while FieldOps provides the operational workflow around the collected data.

How the integration works

The ODK Central integration follows these main steps:

1. Connect an ODK Central server to FieldOps.
2. Test the connection.
3. Select the ODK Central project.
4. Select an ODK Central form.
5. Map the form to a FieldOps Programme, Project, and Site.
6. Optionally associate a Monitoring Template.
7. Synchronize ODK Central submissions.
8. Review synchronized submissions as FieldOps visits.
9. Process visits through the FieldOps visit lifecycle.
10. Review monitoring responses and supporting evidence.
11. Record findings when issues are identified.
12. Create follow-up actions where required.
13. Track actions through to resolution.

ODK Central connections

A FieldOps organization can create ODK Central connections for the ODK Central environments used by its teams and projects.

Multiple connections can be useful when:

• Different programmes use different ODK Central servers
• Development and production environments are separated
• Different teams operate separate ODK Central environments
• Different partners manage their own ODK Central servers
• An organization works with multiple ODK Central deployments

Use descriptive connection names so that users can easily identify the correct server or environment.

For example:

• Production ODK Central
• Kenya Monitoring ODK
• Regional ODK Server
• Partner Data Collection ODK

ODK Central projects and forms

ODK Central organizes forms within projects.

FieldOps uses this structure when configuring an ODK Central integration.

After connecting an ODK Central server, users can select the appropriate ODK Central project and then select the form they want to bring into FieldOps.

This allows FieldOps to work with the forms already configured in ODK Central rather than requiring users to recreate the data collection form.

Form mapping

An ODK Central form must be mapped to the appropriate FieldOps operational structure before its submissions can be used within FieldOps workflows.

A form mapping associates the ODK Central form with:

• Programme
• Project
• Site
• Monitoring Template, if applicable

The mapping tells FieldOps where synchronized submissions belong within the organization's operational structure.

For example:

ODK Central Form

Facility Monitoring Visit

↓

FieldOps Programme

National Health Programme

↓

FieldOps Project

Immunization Strengthening Project

↓

FieldOps Site

Nairobi Central Clinic

This allows ODK Central submissions to become part of the appropriate FieldOps project and site workflow.

ODK Central submissions and FieldOps visits

When ODK Central submissions are synchronized, FieldOps can use the submitted data within its visit workflow.

The ODK Central submission provides the field information collected by the enumerator.

FieldOps provides the operational context around that submission, including:

• Project
• Site
• Visit
• Monitoring responses
• Evidence
• Review
• Findings
• Follow-up actions
• Accountability

This means the field data does not remain isolated in ODK Central.

Instead, it becomes part of the project's operational monitoring process.

Visit lifecycle

Synchronized ODK Central submissions can be managed through the FieldOps visit lifecycle.

The visit workflow provides states such as:

• Draft
• Submitted
• Reviewed
• Approved
• Rejected

The lifecycle allows teams to distinguish between field data that has been collected, submitted, reviewed, and approved.

For example:

Field collection

Enumerator completes the ODK Central form.

↓

Synchronization

FieldOps receives the ODK Central submission.

↓

Submitted

The visit is available for review.

↓

Reviewed

A monitoring officer reviews the visit and its responses.

↓

Approved

The visit has passed the required review process.

If a visit does not meet the required standards, it can be rejected and handled according to the organization's review workflow.

Note

The visit lifecycle is managed by FieldOps. ODK Central remains the source of the original field submission.

Review field monitoring data

FieldOps allows monitoring teams to review synchronized visits rather than relying only on the original ODK Central submission.

During review, users can examine:

• Monitoring responses
• Required questions
• Submitted information
• Supporting evidence
• Visit status
• Visit history
• Previous changes and review activity

This gives supervisors and monitoring officers a structured way to review field work.

Evidence and audit trail

FieldOps supports operational evidence and history around visits.

Teams can use the visit workflow to maintain a record of:

• Visit status changes
• Review activity
• Supporting evidence
• Changes made during the operational workflow
• Historical versions where applicable

This helps organizations maintain accountability around field monitoring activities.

Findings and follow-up actions

ODK Central data can become the starting point for the FieldOps findings and accountability workflow.

When a monitoring officer identifies an issue from a synchronized visit, the issue can be recorded as a finding in FieldOps.

A finding can capture the issue identified during monitoring, including its:

• Severity
• Status
• Description
• Required follow-up

Users can then create a follow-up action for the finding.

Actions allow the organization to move from identifying a problem to assigning responsibility and tracking the required response.

The workflow is:

1. ODK Central collects field data.
2. FieldOps synchronizes the submission.
3. The submission becomes part of the FieldOps visit workflow.
4. The monitoring team reviews the visit.
5. An issue is identified.
6. A finding is recorded.
7. A follow-up action is created.
8. Responsibility for the action is assigned.
9. The action is tracked through its lifecycle.
10. The team reviews the outcome and closes the issue when resolved.

For example:

ODK Central submission

Facility monitoring visit identifies that required medicines are unavailable.

↓

FieldOps visit

Submitted and reviewed by the monitoring officer.

↓

FieldOps finding

Essential medicines were unavailable at Nairobi Central Clinic.

↓

Follow-up action

Confirm stock availability and implement a corrective replenishment plan.

↓

Accountability

Assigned to: Facility Manager
Due date: 30 Aug 2026
Status: Open

This creates a continuous workflow from field data collection to operational accountability.

Tip

ODK Central provides the field data. FieldOps provides the operational workflow for reviewing that data, recording findings, assigning actions, and tracking accountability.

From field submission to accountability

The value of the integration is not simply moving data from ODK Central into another system.

It connects the field data collection process with the operational processes that happen after data is collected.

The workflow can be summarized as:

ODK Central submission → FieldOps visit → review → finding → action → accountability

This allows monitoring teams to close the gap between collecting information and acting on what the information reveals.

What FieldOps adds to ODK Central

ODK Central is designed for collecting and managing field data.

FieldOps adds the operational layer around that data, including:

• Project management
• Site management
• Monitoring workflows
• Visit lifecycle management
• Review workflows
• Evidence management
• Findings
• Finding severity and status
• Follow-up actions
• Assigned responsibilities
• Action tracking
• Accountability
• Visit history and audit trail

This means organizations can continue using ODK Central for data collection while using FieldOps to manage what happens after the data has been collected.

Recommended setup workflow

For a new ODK Central project, use the following order:

1. Create an ODK Central connection.
2. Test the connection.
3. Select the ODK Central project.
4. Select the ODK Central form to use.
5. Map the form to the appropriate Programme, Project, and Site.
6. Optionally associate a Monitoring Template.
7. Synchronize ODK Central submissions.
8. Review the resulting FieldOps visits.
9. Process visits through the required review lifecycle.
10. Review monitoring responses and evidence.
11. Record findings for issues that require attention.
12. Create follow-up actions where required.
13. Assign responsibility and track the actions through to resolution.

ODK Central documentation

Use the following guides to configure and manage the ODK Central integration:

• Connect ODK Central
• Map a Form
• Troubleshooting

What to do next

Connect ODK Central

Map an ODK Central Form