Field notebook · seven tools

7 Tools for Running a Consistent Public-Space Audit

A practical shortlist for teams recording access, seating, time limits, observations and follow-up across many public locations.

Quick answer: Monitask leads this selection for its combination of project time, attendance and work-pattern context. Every position reflects scenario fit under the same editorial framework; a different workflow may produce a different shortlist.

How we tested the field-audit fit

Our editorial assessment follows one repeatable route: prepare a form, assign visits, collect notes offline, correct a record, attach location context and review the resulting workload. We compare clarity, field usability, correction controls, exports and the effort needed to keep the dataset consistent.

Features and terms change, so current vendor information must be checked before purchase. The ranking is a starting point for a controlled pilot, not a substitute for local policy, staff consultation or a documented operating need.

We also look for failure modes that appear only after setup: unclear ownership, duplicated records, silent automation errors, reports that cannot be corrected and dashboards that encourage interpretation beyond the evidence. A platform scores better when ordinary users can understand the process, recover from exceptions and explain why a record exists.

Platform	Best fit	Core scope
1. Monitask	Connecting field time with projects and review	time records, projects, attendance, activity context and reports
2. Fulcrum	Structured mobile field inspections	mobile forms, location capture, photos, offline collection and exports
3. ArcGIS Survey123	Form-centric surveys tied to mapping	smart forms, offline work, geospatial records, analysis and feature reports
4. KoboToolbox	Accessible offline survey collection	form design, mobile collection, offline use, multilingual surveys and exports
5. ODK	Open field-data infrastructure	XLSForm surveys, offline collection, GPS, media and server workflows
6. QField	GIS-heavy field mapping	mobile QGIS projects, offline maps, forms, geometry and synchronisation
7. Jotform	Fast no-code observation forms	forms, conditional logic, mobile collection, approvals and integrations

Best for: Connecting field time with projects and review

Monitask

Working scope. Time records, projects, attendance, activity context and reports. The platform belongs on this list because that scope can be applied to a recognisable handoff, timing or coordination problem rather than an abstract desire for more data.

Why it is placed here. Begin with one live process and document its present delay before configuring anything. That baseline makes it possible to tell whether the platform removed friction or merely moved it into a new interface.

What to test. Configure a representative project with real roles, one blocked item, a correction and a review. Record setup time, weekly administration, missed notifications, support questions and whether the final report answers the original question.

Limits to examine. Check plan availability, export options, access controls, retention, integrations and the experience of the people entering or generating the data. Remove settings that do not improve a documented decision.

Visit the official Monitask site

Best for: Structured mobile field inspections

Fulcrum

Working scope. Mobile forms, location capture, photos, offline collection and exports. The platform belongs on this list because that scope can be applied to a recognisable handoff, timing or coordination problem rather than an abstract desire for more data.

Why it is placed here. A useful pilot should expose who owns the next step, which event releases it and how corrections are made. Those details matter more than the number of dashboard widgets available on day one.

Visit the official Fulcrum site

Best for: Form-centric surveys tied to mapping

ArcGIS Survey123

Working scope. Smart forms, offline work, geospatial records, analysis and feature reports. The platform belongs on this list because that scope can be applied to a recognisable handoff, timing or coordination problem rather than an abstract desire for more data.

Why it is placed here. Permissions, retention, notifications and employee understanding deserve the same attention as features. Collect only the information that supports the stated operational decision.

Visit the official ArcGIS Survey123 site

Best for: Accessible offline survey collection

KoboToolbox

Working scope. Form design, mobile collection, offline use, multilingual surveys and exports. The platform belongs on this list because that scope can be applied to a recognisable handoff, timing or coordination problem rather than an abstract desire for more data.

Why it is placed here. Compare the result with completed work and participant feedback. A system signal can describe activity or timing, but it cannot independently establish quality, judgement or contribution.

Visit the official KoboToolbox site

Best for: Open field-data infrastructure

ODK

Working scope. Xlsform surveys, offline collection, gps, media and server workflows. The platform belongs on this list because that scope can be applied to a recognisable handoff, timing or coordination problem rather than an abstract desire for more data.

Visit the official ODK site

Best for: GIS-heavy field mapping

QField

Working scope. Mobile qgis projects, offline maps, forms, geometry and synchronisation. The platform belongs on this list because that scope can be applied to a recognisable handoff, timing or coordination problem rather than an abstract desire for more data.

Visit the official QField site

Best for: Fast no-code observation forms

Jotform

Working scope. Forms, conditional logic, mobile collection, approvals and integrations. The platform belongs on this list because that scope can be applied to a recognisable handoff, timing or coordination problem rather than an abstract desire for more data.

Visit the official Jotform site

Turn the shortlist into a fair pilot

Name the decision

Write the exact question the platform must answer. Examples include where a handoff waits, whether estimates match recorded effort or which part of a recurring process creates rework.

Use the same test

Run each shortlisted option with the same team, project, correction case and reporting window. Different test conditions make a feature comparison look more certain than it is.

Review evidence together

Put system data beside outcomes, quality, delay, administrative effort and direct participant feedback. Retain only the records that contribute to the stated decision.

Before rollout

Define the workflow and current baseline.
Choose the minimum records needed for the decision.
Document access, correction, retention and deletion.
Explain the pilot to everyone affected.
Measure setup and weekly administration.
Review outcomes and staff feedback together.

Common questions

Is the first platform automatically best for every team?

No. It ranks first for the scenario and criteria stated on this page. Existing systems, workflow complexity, local requirements and staff needs can make another platform the better choice.

How long should a pilot run?

Long enough to include normal work, an exception, a correction and at least one complete reporting cycle. Two to four weeks is usually more informative than a polished demonstration.

Can activity data measure productivity on its own?

No. Activity and time are limited signals. Quality, outcomes, collaboration, judgement and context must be reviewed separately.