Skip to content
DatumPro
Book a demo

The product

One record, from the first stake to the final sheet.

Crews collect on a map that works without a connection. The office decides what may be collected and what it must carry. Reporting turns both into the deliverable. It is one data set the whole way through.

Book a demoCompare plans
The client and project administration screen listing clients, projects and jobs.
Drawing
Project, jobs and status
Captured
2026-09-22

How a job runs. Each stage hands the next data it can rely on.

  1. 01

    Configure

    Office

    Author the catalogue: tools, attributes, connections, visuals, quality and automation rules. Give it to the project.

  2. 02

    Dispatch

    Coordinator

    Create the work and its work items with the fields you track. Share each job with the crew working it.

  3. 03

    Collect

    Field crew

    Draw features against the job, capture and mark up photos, work offline. Edits replay in order when signal returns.

  4. 04

    Verify

    Office

    Quality rules and the inspector surface what is wrong while the crew is still nearby. Automation fills in what can be derived.

  5. 05

    Deliver

    Reporting

    Build the report, produce CSV, XLSX, KMZ or the georeferenced map book, and hand over the record.

In the field

A map that works where the signal does not

Crews draw points, lines and polygons on the project map, on a tablet or a laptop in the truck, with or without a connection. Map edits land locally first and sync when there is signal — nobody waits on a spinner in a ditch.

Drawing a line feature on the map with the tool palette open and the attribute panel filling in.
Drawing
Drawing a feature
Captured
2026-09-22

  • Local-first editing

    Every map edit, geometry and attributes alike, is written to a local feature store and queued in an outbox. Close the app, lose the signal, drive out of the county — the work is still there, and it replays in order when the connection returns. Photos are the exception: they upload while there is a connection.

  • Draw what the catalogue allows

    Crews draw only with the tools in the project’s catalogue, so nobody invents a feature type that the office has to clean up later. A toolset narrows the palette further, to the work in hand.

  • Photos, marked up on the spot

    Capture a photo against a feature, then draw on it — pen, arrow, box, text, and the project’s own tool icons as stickers. The markup is baked into the image that gets handed over.

Before the crews roll

Configure the job once, in Catalog Studio

A catalogue defines the tools a project can draw, the attributes each one must carry, which tools may connect to which, and how all of it renders on the map. Projects use their catalogue live, so every project on it keeps the same discipline, and one that needs its own version can be detached.

Catalog Studio with the tools tab open, listing the tools, categories and attributes of a catalogue.
Drawing
Catalog Studio — tools
Captured
2026-09-22

  • Tools, categories and attributes

    One catalogue owns the feature types, the attribute definitions behind them, and the option lists those attributes pick from. Toolsets, defined alongside them, let each person narrow the palette to the task.

  • Connection and visual rules

    Connection rules decide which tool pairs may be joined. Visual rules decide what the map draws — badges, line crossings, colour by attribute — so a field map reads like the plan set it will become.

  • Quality rules that can say no

    Thresholds, scopes and severities are authored alongside the tools. For line ends left unconnected, zero-length lines and polygons whose border crosses itself, the strictest severity does not report the problem after the fact — it blocks the edit that would create it.

Rules, not reminders

Problems caught while they are drawn

Quality rules are authored on the catalogue with their own thresholds and severities. Warnings and errors are reported on the device while the crew works; for a few geometry mistakes the strictest severity refuses the edit. Automation rules go further and write the values that can be derived.

The quality tab of Catalog Studio, listing checks such as unconnected line ends and stacked points with their severities.
Drawing
Quality rules and severity
Captured
2026-09-22

  • Checks with a severity you choose

    Unconnected line ends, stacked points, missing required fields, prohibited connections, failed snaps — each on or off, each a warning or an error, per catalogue.

  • Restrict blocks the edit

    On unconnected line ends, zero-length lines and self-crossing polygons, the strictest setting does not report the problem afterwards: the edit that would create it does not save.

  • Automation fills in the rest

    When an attribute changes, a rule sets, copies or clears another — drawn on a flow canvas with conditions, switches and scopes, running after the write so it can never block a crew. Every run keeps a replayable trace.

Planning the work

Work orders with the fields you track

Work is what a coordinator manages; work items are what a crew does. Both carry the fields your organisation tracks, added without a release.

The work list for a client, showing work orders with their own configured fields.
Drawing
Work orders on a project
Captured
2026-09-22

  • Your fields, not ours

    Entity definitions let a client add typed, validated fields to work and work items — and they turn up in forms, grids and the report designer as ordinary data.

  • Labor codes with dated prices

    Each client keeps its own labor codes, each with a unit and prices that take effect on a date, so a new rate starts when it should and the old one stays on record.

  • Jobs on the same map

    A job is an area on the project map with a status, a priority and a due date, and it moves to In progress by itself when the first feature is recorded in it.

The deliverable

Exports the client will actually accept

Build a report against the project’s own fields, filter it with nested AND/OR groups, and export it as the format the receiving party asked for — including a georeferenced PDF map book, at a fixed scale, with detail sheets wherever work has been drawn.

The export drawer open over the project map, with scope, format, node count and footage.
Drawing
Export — scope and format
Captured
2026-09-22

  • Reports over your fields, not ours

    The attribute fields your catalogue defines and your own entity fields are first-class in the designer, alongside pivots and join paths across the domain.

  • CSV, XLSX, KMZ — in your formats

    Date style, decimal and thousands marks, unit conversion and Yes/No booleans follow the requesting user’s preferences, so a spreadsheet does not have to be re-cut by hand.

  • A map book, not a screenshot

    An overview, then a detail sheet wherever work has been drawn, with an index when there is more than one — georeferenced and at a fixed scale.

Who sees what

Access that follows the work, not the org chart

A role is assigned to a user or a team, at a scope: one resource and everything beneath it, or the whole organisation. Share a single job with a subcontractor and the features on their map are bounded to that job’s area.

Role-based access control administration showing roles, teams and scoped assignments.
Drawing
Roles, teams and scopes
Captured
2026-09-22

  • Roles, teams, scopes

    Each permission is a set of actions the server checks for clients, projects, jobs, map features, catalogues and exports, rather than a button the interface hides.

  • Restricted scopes

    A share at job level reaches the project it belongs to, with the map’s features bounded to that job’s area — enough context to work.

  • An audit trail that is append-only

    Who changed what, when, on which resource — recorded as events, never edited in place.

Watch it work. Four short clips from a running environment, silent and captioned.

Drawing
Drawing a route on the map
Captured
2026-09-22

Pick a tool, draw the route, and the attributes it must carry are asked for on the spot.

Drawing
Configuring a catalogue
Captured
2026-09-22

Catalog Studio decides what crews can draw, what it must record, and how it looks on the map.

Drawing
Exporting the record
Captured
2026-09-22

Turn the live map into the deliverable: a report, a spreadsheet, or a georeferenced PDF map book.

Drawing
Granting scoped access
Captured
2026-09-22

A role, assigned to a team, at a scope — and the map shrinks to exactly what that crew may touch.

See it against your own build

A demo runs on your data shape: your tools, your attributes, one of your projects. Thirty minutes, no slide deck.

Book a demo