Field-Data Apps for Reforestation Teams

A planting survey, a map of restoration sites, and a nursery-to-monitoring workflow need different tools. Start with the work your team does, then decide who will configure and maintain the system.

This guide compares five starting points, with three alternatives for more specific needs. It is an editorial shortlist, not a scored ranking or a hands-on benchmark of every app. Product documentation reviewed September 9, 2026.

Disclosure: Restoration Scope publishes this guide and is included below. The same questions about setup, cost, support, and data export apply to our platform.

Compare the main options

App	Start here when…	Plan for…
KoboToolbox	You need structured surveys with photos and GPS.	Someone to design forms, review submissions, and maintain reporting.
QField + QFieldCloud	Your team works in QGIS and needs those maps in the field.	A capable QGIS owner to maintain projects and synchronization.
ArcGIS Survey123	Your team uses ArcGIS and the work starts with a form.	ArcGIS administration, survey design, and licensing.
ArcGIS Field Maps	Your team uses ArcGIS and the work starts with a map.	Layer design, permissions, and offline map preparation.
Restoration Scope	You need a configured restoration workflow across field and office teams.	Scoping, onboarding, an internal owner, and an agreed support arrangement.

The form-led and GIS apps above document offline field collection; Restoration Scope also offers offline capture. That does not make their offline behavior interchangeable. Test the actual forms, maps, attachments, and update cycle your team needs. Sources and tradeoffs follow each option below.

Forms and surveys

KoboToolbox

Good fit: Plot assessments, household interviews, planting records, and other work that can be expressed as a structured form. KoboCollect supports offline collection on Android; browser-based web forms are another collection option. Data can be exported for analysis and mapping.

Think twice if: Your main need is maintaining a shared map or coordinating many linked operational records. First prove how revisits, identifiers, review, and reporting will work; collecting a submission is only one part of that system.

Team commitment: A form owner and a clear process for checking data. Include cleaning and reporting time when comparing cost.

Sources: collection options, KoboCollect, exports.

ArcGIS Survey123

Good fit: Form-led collection in an existing ArcGIS organization. Survey123 connects survey records to ArcGIS Online or Enterprise and supports online and offline form completion in its mobile app.

Think twice if: You do not otherwise need ArcGIS, or collectors mainly need to browse and edit mapped features. Compare the total ArcGIS setup with a standalone form tool; compare the map-led workflow with Field Maps.

Team commitment: Someone to own surveys, accounts, and the downstream use of the data. Confirm the user types and licenses required for authors and collectors.

Sources: Survey123 overview, licensing and capabilities FAQ.

Maps and GIS

QField + QFieldCloud

Good fit: A team with QGIS skills and a dedicated person who can maintain its field system. QField takes QGIS projects into online or offline fieldwork; QFieldCloud provides a synchronization workflow for teams.

Think twice if: Nobody can own layers, forms, project packaging, and sync issues. Technical capacity matters more than a long feature list. A supported implementation may still be viable, but include that service in the comparison.

Team commitment: A named GIS owner with time to maintain the project. Test two people updating field data, sync failures, attachments, and handover to a replacement administrator.

Sources: getting started, QFieldCloud synchronization.

ArcGIS Field Maps

Good fit: Teams that already manage data in ArcGIS and need collectors to find, create, or update features on a map. Field Maps combines maps, forms, and field tasks, with prepared offline maps.

Think twice if: A straightforward questionnaire is the entire job, or adopting ArcGIS would introduce an ecosystem you do not otherwise need. Survey123 may suit the form-led part of the work better; the two can also share ArcGIS data.

Team commitment: A GIS owner to prepare layers, access, forms, and offline areas. Test changes to existing records as well as collection of new ones.

Sources: Field Maps overview, Survey123 and Field Maps.

Restoration workflows

Restoration Scope

Good fit: Restoration teams looking for help connecting field collection, data processing, and an operational app around their project. Restoration Scope offers configurable capture apps, a data platform, and an app platform, including offline photos and GPS collection.

Think twice if: An existing survey or GIS tool already covers the job, you want to configure everything independently, or a scoped implementation would add unnecessary cost and dependency. A simple collection need may not justify a broader platform.

Team commitment: An internal owner still needs to define the workflow and accept changes. Agree on implementation cost, ongoing support, data export, responsibilities, and what happens if you leave before committing.

Source: Restoration Scope products.

More options by workflow

ODK · configurable data collection

Consider ODK alongside KoboToolbox for form-led work. ODK Collect supports offline collection, location, photos, and complex forms; ODK offers managed hosting as well as a self-managed route. Compare the form design, administration, and support you actually need. Choosing managed hosting does not remove the need for a form and data owner.

Sources: getting started, ODK Collect.

Mergin Maps · another QGIS field workflow

Compare Mergin Maps alongside QField when QGIS is already part of your work. Its mobile app supports offline field surveys using projects prepared in QGIS. Use the same pilot for both tools, and compare project setup, synchronization, support, and total cost. You still need someone to maintain the QGIS project.

Source: Mergin Maps offline workflow.

Terraware · seeds, nurseries, and monitoring

Consider Terraware when seed banking, nursery inventory, and planting-site monitoring are central to your work. Its nursery records connect seedling batches to seed accessions, and its monitoring workflow uses scheduled observations. Check that its inventory and monitoring model matches your operations before trying to make it a general-purpose field app.

Sources: Terraware overview, seedling inventory, monitoring observations.

How to narrow the list

Start with your existing system. If your data and skills are already in QGIS, compare QField and Mergin Maps. If they are in ArcGIS, compare Survey123 and Field Maps. If the job is mainly a survey, start with KoboToolbox and ODK. For a restoration workflow spanning several teams, compare a configured platform with the cost of joining those tools yourself.

Separate technical ability from available time. A team may know QGIS but have nobody available to maintain it. A dedicated, capable owner makes a configurable tool more practical. Without one, compare implementation and support services as part of the purchase.

Ask who owns the work after launch. Who changes a form, fixes a failed sync, checks bad records, and trains new collectors? Wanting support does not select a single app: compare each provider's actual service scope and your team's remaining responsibilities.

Compare total cost and your exit path. Include subscriptions, implementation, devices, training, maintenance, and data cleanup. Ask for a sample export with identifiers, geometry, photos, and relationships. Confirm current pricing, plan limits, and device support directly with the provider.

Run the same small pilot in two apps

1. Use one real survey or site, your intended phones, and two collectors. Include photos, GPS, and a revisit to an existing record.
2. Prepare the devices, switch off connectivity, close and reopen the app, and finish the fieldwork.
3. Reconnect both devices. Check submissions, edits, attachments, and how conflicting updates are handled.
4. Have an office colleague review the results and produce the report or export you actually need.
5. Ask the future system owner to change a field and help a collector recover from a mistake.

Choose based on the work your team can complete and maintain. The most useful shortlist is the two tools that survive that pilot.