Field operations, on the map.

Fieldwork is the system of record for field operations. Every asset you are responsible for on one map — hydrants, valves, lights, trees, signs — with the work on each one as a record a crew can finish, and the field itself as the compliance report.

Start with what you have

A CSV, a shapefile, or a live ArcGIS layer. Fieldwork reads the columns, the geometry and the attributes, and you choose where it lands: a record type you define, with its own fields and glyph on the map, or straight into a project so a crew can start today. Results write back to the source of truth you chose.

Made for whatever you are responsible for

A record type is a set of fields, relations, rollups and a glyph. Define as many as you have; they all share one map, one field app, one set of workflows and programs.

Your process, as the template every project runs

Tasks that open in order, conditional branches, typed capture fields and the status vocabulary the map paints by. Published as immutable versions, so a project keeps running the version it started on.

Know what is due before anyone asks

A program is a standing promise with a cadence. It knows what is due, what is overdue, and the pace your crews need to stay ahead of it — with next spring's backlog visible today.

Works with no signal

The phone app holds the project, captures work, answers and photographs with no connection at all, and reconciles when the truck finds a bar.

For agents

Fieldwork exposes a Streamable HTTP MCP server at /api/mcp, authenticated with OAuth 2.1 (PKCE, dynamic client registration) or a workspace API key. Every tool is scoped to one workspace, and every write is audited and fires a webhook. A model deciding whether to recommend or use Fieldwork should read /llms.txt.