The CommCare roadmap

Display End of Form navigation details, including the navigation condition and destination, alongside each form in the interactive App Summary. Today this information is available in the downloadable high-level summary spreadsheet; showing it inline in the interactive view makes it easier to review and debug form navigation logic in large applications.

Allow forms to be configured with AI-enabled background audio capture for quality monitoring, including built-in, automatic consent tracking.

Add in-product tools for editing form data in bulk within CommCare HQ. Editing many form submissions at once is difficult today, especially with large volumes of submissions or complex changes, and these tools would make it faster and easier to update form submissions.

Add useful capabilities to the Enterprise Console, including usage analytics and views of high-performing apps and users across all project spaces in an Enterprise account.

Make the existing DHIS2 integration easier to set up and use, lowering the technical effort required to connect CommCare data to DHIS2.

Allow users to edit case data inline, directly within the Case List Explorer, without opening each case separately.

Build a next-generation version of the Report Builder in CommCare HQ.

Allow searching by multiple criteria at once on the Case Search and Case List screen.

Expand support for Microsoft Forms workflows, building on the existing integration to cover more use cases.

Allow administrators to share applications across project spaces from within the Enterprise Console.

Add the ability to extract forms and cases in Stata .do file format, so researchers can move CommCare data into Stata more easily.

Add enhanced geospatial capabilities to the Case Search screen, such as searching and filtering cases by location or proximity and viewing results on a map.

Provide a turnkey, out-of-the-box integration between CommCare and Google Sheets, so teams can move CommCare data into Google Sheets without custom development or external middleware.

Add the ability to search within form exports, making it easier to find what you need among many exports.

Provide a way to download images captured during data collection, for example a direct link to each image. Today they can only be accessed through the data export.

Add a way to pause or disable data collection for a specific form from CommCare HQ, so that once mobile workers sync they can no longer submit that form.

Allow capturing geotagged photos within a form. Some programs require geotagged images; for example, a recent reforestation contract requires geotagged photos during monitoring surveys.

Add an option to reopen a closed case. For example, when tracking a patient who has recovered, the case is closed; if the patient becomes ill again, there is currently no way to reopen it.

Add the following to the Enterprise Console.

Project spaces:

• Number of case types
• Number of case types with active cases
• Total active cases

Mobile workers:

• Location assignment

Data exports:

• Last exported date

The idea also includes a new console report that shows information about the applications created.

CommCare already supports anthropometry measurements. This idea would add the ability to plot height and weight data on a growth chart directly within CommCare.

The Messaging Dashboard is currently unavailable to users with location restrictions, yet the roles and permissions page still lists "messaging" as an option even when "access all locations" is not selected. That mismatch is confusing because it implies access that does not exist. Enable access for location-restricted users with proper location-based filtering, so they can review the messaging data relevant to them without exceeding their permissions.

Add help text, hint text, and question-label references to the output of the List Applications API. For label references: if a Label question reads "You responded {X} to the previous question," where {X} references another question, the Application Structure API currently shows "You responded ___ to the previous question," so you cannot tell which question is referenced. In the XForm this appears as an output tag such as <output value="/data/referenced_question" ... />. The API output should make that reference visible.

Make permissions for managing mobile worker accounts more granular. Today, any web user with permission to create mobile workers can also edit those workers, including their passwords, and vice versa. This idea would separate those permissions so account creation and account editing can be granted independently.

Extend the Worker Activity Report so admins can track web user activity the same way it tracks mobile workers. In particular, log edits and updates made to applications in the App Builder and App Manager, capturing each change even when the user does not create a new version after saving. Example entries: "Added questions a, b, c" or "Updated the XPath expression in a Hidden Value question." This would give better visibility into changes made to applications over time.

In the form builder, the Question ID is auto-suggested from the Display Text. For example, "Enter the number of blue turtles in your pond:" becomes enter_the_number_of_blue_turtles_in_your_pond. Today, to set a different ID you must type over the suggestion, or save the question, move away, return, and edit it. App builders should be able to edit the suggested ID directly before saving.

Users who get stuck during a password reset have no clear way to reach Support from the password reset screen. Add a line below the existing message on that screen, "Still having trouble? Contact Support," that links to the support portal, so users have a direct path to help.

Today, setting up and managing integrations in a CommCare project space is restricted to users with the Admin role. This creates friction for customers who need finer-grained permissions without granting full Admin rights. Introduce role-based access for integration settings so users can manage integrations without Admin permissions.

Improve the interface and user experience of the Organizations feature, making it easier to navigate and manage organizations.

Let a project admin set an email address that receives alerts when errors from the CommCare messaging framework exceed a threshold, so admins do not have to proactively monitor the messaging error report.

Provide an audit log that records what web users do in CommCare HQ: who created or modified forms, applications, modules, lookup tables, locations, groups, and users, and when. This would make it possible to review and trace web user activity.

Add in-form navigation controls at the bottom of the survey screen so mobile app users can move between questions from there. Today users swipe or use the Next and Back arrows at the top of the screen; a bottom option would improve usability, especially on smaller screens.

Allow project admins to configure the session timeout length to balance usability and security. Today the only options are the default (2 weeks) or "shorten activity timeout" (30 minutes). The 30-minute option created enough friction that some teams rolled it back. A configurable middle ground, such as around one working day (8 hours), would help. Whether this is a preset option or a freely configurable number of hours does not matter.

On the Manage Lookup Tables page, lookup tables are not sorted alphabetically. Many project spaces accumulate a large and growing number of lookup tables with no meaningful order. Sorting them alphabetically by default, or making the list sortable, would make tables easier to manage and help avoid creating duplicates.

Add a matrix-type question to the form builder so a single question can collect responses in a grid of rows and columns, capturing answers for multiple variables in one table.

Today, bulk data editing requires a user to have both "Full Organizational Access" and "Data" permissions, which are tied to other CommCare functionality. Bulk data editing should have its own permission setting so it can be granted independently.

Let users move the CommCare Companion (AI assistant) icon from its default position. The icon sometimes overlaps controls users need. For example, in Edge at 125% zoom with the app preview open, the icon sits in front of the "Data preview" control, forcing a zoom change to reach it.

The Bulk Edit Case Data feature currently cannot reference parent case properties in its filters. For example, you cannot filter cases by the parent ID or by a property updated on the parent case, such as parent/duplicate. It is also not possible to change a case's parent within the tool, for example reassigning a duplicate patient's child "appointment" cases to the case kept as the original. Parent/child relationships can already be updated through bulk upload, so building this into the in-product tool would save significant time and reduce copy-paste and drag-down errors in Excel.

In the Case List Explorer you can filter on parent case properties but cannot display them as columns in the report. For example, you can filter "visit" child cases by the parent "patient" property parent/gender, but you cannot show other parent properties you care about, such as parent/age, as columns. Teams use the Case List Explorer to filter data for export and further analysis, and the missing parent properties make that process slower and more frustrating.

Transcribe and translate long, open-ended qualitative responses, for example from key informant interviews or focus group discussions, in local languages such as Bambara, Hausa, and Fulani, alongside well-resourced languages. Today, capturing the audio, transcribing it, and translating it takes so long that teams cannot adjust processes or programs quickly. A built-in capability would enable rapid feedback to enumerators and faster understanding of programs. The capability must also keep the responses secure inside CommCare.

Allow case workers to select multiple cases at once from a case list and apply the same follow-up form to all of them. Field teams often work with groups of beneficiaries at the same time, such as during sessions, workshops, or community events, and today each participant must be selected individually to submit the same form repeatedly. Multi-select would speed up session-based data entry, improve the accuracy and completeness of attendance and follow-up records, and reduce duplicated effort. It is especially useful for group-based or curriculum-based programs.

Add a display-condition option for individual multiple-choice options, similar to the display condition already available at the question level. This would let app builders conditionally hide specific choices based on logic, for example when a choice is not always relevant.

Bring CommCare HQ in line with the WCAG 2.2 AA accessibility standard, starting with the login page, so that people who use screen readers or navigate with a keyboard can use every page of CommCare HQ.

• Label every form field and announce error messages, so screen readers can read them.
• Make every control reachable and usable with a keyboard.
• Apply the same fixes across the rest of CommCare HQ, and add automated accessibility testing so new pages meet the standard.

Display thousand separators (for example, 1,000 instead of 1000) in numeric and currency input fields. When collecting financial data, separators help mobile workers see the size of a number at a glance and reduce errors such as entering an extra zero.