Survey123

Survey123 doesn't have generative AI features -- its "smart" behavior is rule-based form logic (relevant expressions to show/hide questions, constraint expressions to validate entries) authored explicitly in the form design, the same category of logic used in Field Maps Designer's smart forms, not a machine-learning layer.

Practical Details

This rule-based logic is genuinely effective for reducing bad data at the source -- catching an out-of-range number or an inconsistent answer combination before it's ever submitted -- but it requires the form author to anticipate and write each validation rule, rather than a model inferring what's valid automatically.

Actionable Considerations

1. Don't expect generative AI or automatic anomaly detection; Survey123's data-quality logic is rule-based and must be authored explicitly.
2. Invest form-design time in relevant and constraint expressions upfront, since that's what actually prevents bad data, not a post-hoc AI review.
3. Review submitted data periodically for patterns validation rules didn't anticipate, since rule-based logic only catches what it was written to catch.

Survey123 shares the same licensing model as Esri's other field apps -- staff who only submit surveys can be licensed as ArcGIS Field Worker users rather than a full Creator license, which is the main lever for controlling cost as the number of field respondents grows rather than any app-level performance setting.

Practical Details

The practical scale constraint is usually attachments, not submission count -- surveys with photo or file attachments on every record can consume hosted feature layer storage and ArcGIS Online credits quickly at high volume, and repeat questions (letting one survey capture multiple sub-records, like several trees observed on one site visit) multiply the underlying data volume per submission.

Actionable Considerations

1. License field-only respondents as ArcGIS Field Worker users rather than full Creator licenses to control per-seat cost.
2. Monitor hosted feature layer storage and ArcGIS Online credit consumption specifically where surveys include photo or file attachments.
3. Account for repeat questions multiplying record volume when estimating storage needs for a large-scale survey.

Data quality in Survey123 is enforced through XLSForm-standard expressions authored in Survey123 Connect -- constraint expressions reject invalid entries at data-entry time (not after the fact), relevant expressions show or hide questions based on prior answers, and pulldata functions can pull in reference values from another dataset to reduce manual entry errors.

Practical Details

Survey123 can auto-generate a formatted Word or PDF report from a template for each individual submission, which is genuinely useful for field reports that need to go to a client or regulator, separate from the raw tabular export (CSV, shapefile, or Excel) used for analysis.

Actionable Considerations

1. Author constraint and relevant expressions in Survey123 Connect using the XLSForm standard, not just the simpler web designer, for real validation logic.
2. Use pulldata to reference existing lookup values rather than relying on free-text entry for anything with a known valid list.
3. Set up a per-submission report template if individual survey results need to be shared as a formatted document, separate from bulk data export.

Form authoring happens through one of two tools: the browser-based Survey123 web designer for straightforward forms, or Survey123 Connect (a separate desktop application) for advanced logic using the XLSForm spreadsheet standard -- repeat sections, skip logic, and pulldata generally require Connect, not the web designer alone.

Practical Details

Publishing a form creates a hosted feature layer in ArcGIS Online or Enterprise, the same underlying data model Field Maps and other ArcGIS apps use, and distribution options include a shareable link, a QR code for the exact survey, or an anonymous public link for surveys that shouldn't require a named ArcGIS login.

Actionable Considerations

1. Use Survey123 Connect rather than the web designer if the form needs repeat sections, skip logic, or pulldata lookups.
2. Decide early whether the survey needs to be public/anonymous or restricted to named ArcGIS users, since that affects distribution setup.
3. Pilot a form with a small group before wide distribution, since publishing changes to a form already collecting data can require careful schema versioning.

Survey123's own website view shows live summary charts per question as submissions come in, which is often enough for simple stakeholder updates without building a separate dashboard -- for more polished or combined-data views, teams typically graduate to an Operations Dashboard built against the same underlying feature layer.

Practical Details

Because forms can include repeat sections and per-submission report generation, engagement with field teams benefits from showing them the auto-generated PDF or Word report for their own submissions -- seeing a clean, formatted output from data they entered tends to reinforce careful data entry more than an abstract data-quality reminder.

Actionable Considerations

1. Use Survey123's built-in results view for quick stakeholder updates before investing in a full Operations Dashboard build.
2. Share auto-generated per-submission reports with field staff to reinforce data-entry quality.
3. Set a regular cadence for reviewing submission trends with the team, rather than only checking in when something looks wrong.

Because Survey123 writes to a standard ArcGIS hosted feature layer, results are immediately usable by other ArcGIS tools without a separate export step -- an Operations Dashboard or ArcGIS Insights can be built against the live survey data, updating as new submissions come in.

Practical Details

Survey123 supports webhook-style integrations and email notifications triggered on submission, and for workflows beyond ArcGIS's own tools, ArcGIS's connectors for Microsoft Power Automate let a new survey submission trigger an action in another system without custom code.

Actionable Considerations

1. Build dashboards and analysis directly against the survey's hosted feature layer rather than re-exporting data manually for each report.
2. Set up submission-triggered email notifications or webhooks for time-sensitive survey types, like incident reports.
3. Use the Power Automate connector for workflows that need to reach outside the ArcGIS ecosystem, rather than building custom integration code.

Survey123 has no separate permissions system of its own -- like Field Maps, access is inherited from how the survey's hosted feature layer is shared in ArcGIS Online or Enterprise, and who can view results versus who can submit is controlled by ArcGIS group sharing and layer permissions, not a Survey123-specific setting.

Practical Details

A distinct choice specific to Survey123 is whether a survey is open (anonymous, no ArcGIS login required to submit) or restricted to named users -- open surveys are common for public-facing feedback or citizen-reporting use cases, while restricted surveys are the right default for internal data collection needing accountability for who submitted what.

Actionable Considerations

1. Decide deliberately between an open (anonymous) and named-user survey, since that choice can't always be changed cleanly after data collection begins.
2. Share the survey's results layer only to the specific ArcGIS groups that need to view or analyze results.
3. Enable editor tracking on the underlying feature layer if accountability for who submitted each record matters.

Survey123 is Esri's form-centric field data collection app -- distinct from its sibling app Field Maps, which is map-centric for navigation and asset editing, Survey123 is built around structured questionnaires, using the open XLSForm standard for advanced logic like skip patterns and repeating sections.

Implementation Details

Forms are authored once (in the web designer or the more capable Survey123 Connect desktop tool) and published as a hosted feature layer in ArcGIS Online or Enterprise, the same data backbone shared across the ArcGIS field apps, so survey results are immediately available to other ArcGIS tools without separate data wrangling.

Considerations

• Choose Survey123 specifically for structured, question-driven data collection rather than map-centric asset editing, which fits Field Maps better.
• Use Survey123 Connect and the XLSForm standard for any form needing repeat sections or conditional logic.
• Plan for offline data collection and sync behavior explicitly, since field connectivity is rarely guaranteed.