Field data for utility inspectors, wetland scientists, geotechnical crews, foresters, ecologists, archaeologists and paleontologists

The whole field workflow.One product.

Set up, collect, QA, report, deliver — without moving data between apps.

  1. Start from the form you already use.
  2. Collect on iPad — no signal needed.
  3. QA on the web before you demobilize.
  4. Delivery-ready report, same day.

One survey shouldn’t need six apps.

Nobody chose that stack. It accumulated, one tool at a time.

Every seam between them is a manual handoff, and a place data goes wrong.

WHAT MOST TEAMS RUNSIX APPS · SIX LOGINS · COPIED BY HANDWHAT YOU RUN INSTEADONE PROJECT · ONE RECORD · NO HANDOFFSform builderFORMSFORMS + MAPmap appCAPTUREOFFLINE SYNCdesktop DBDATALINKED RECORDSweb GISSHARINGLIVE QA PORTALreport writerREPORTSAUTO REPORTSfile drivePHOTOSMEDIA ON RECORD

Build it once. Run it every project.

A Composition packages the schema, map symbology, and report templates into one reusable template.

Elsewhere this is a services engagement.

Cedar Run OutfallsPROJECTPROJECT AREAPHOTOS · 12OutfallASSETPointPhotosCulvertASSETLinePhotosInspectionMANY PER ASSETPhotosNo locationPROJECTAREA · PHOTOSASSETSPOINT OR LINEINSPECTIONON EITHER ASSETPHOTOS · NO LOCATION

01 Design it once: the project, its assets, their inspections02 Every new project starts from the same Composition03 Open a project and collect: records on the map and in the list, as one hierarchy

Real relationships. Not repeated rows.

Assets hold inspections. Inspections hold defects and photos. Every record rolls up the chain.

Form builders give you repeats inside one form. That is not a data model.

MOST FORM APPSASSETTYPEDATECONDITIONOF-014OutfallMar 02FairOF-014OutfallJun 11PoorOF-015OutfallMar 02GoodOF-015OutfallJun 11FairASSET ID RETYPED EVERY VISITCODIFISW-26 Cedar Run OutfallsProjectOF-014 OutfallAssetMar 02 · FairInspectionJun 11 · PoorInspectionOF-015 OutfallAssetMar 02 · GoodInspectionJun 11 · FairInspectionENTERED ONCE · NEVER RETYPED

“What took me days, weeks now takes literally seconds.”

Andrew Saatkamp · Archaeologist
A wooden soil screen resting on freshly sifted dirt, a boot print pressed into the pile beside it.
The work
Andrew Saatkamp, in a hi-vis jacket and cap, shaking a soil screen among pines.
Andrew Saatkamp, in the field

Offline. And offline together.

Crews with no signal split the work and see each other's records live, device to device.

Most apps mean work alone, sync at the truck.

NO SIGNALCLOUDCREW 1 · TABLETCREW 2 · TABLETOUTFALL 14INSPECTION 14·1DEFECT · CRACKPHOTOS × 3OUTFALL 14INSPECTION 14·1DEFECT · CRACKPHOTOS × 3NO INTERNETDEVICE TO DEVICEEVERY RECORD ON BOTH TABLETS — WITH NO SIGNAL

01 No signal: every record crosses device to device02 One tablet finds signal and uploads the whole crew's work03 Photos, GIS, the form: three people on one record, live

Catch it before you demobilize.

Data tables on the device, and rules that reject bad values as they're typed.

Map-first apps don't put a table in your hand.

Report and export, same day.

Collect it once. The data form, the sample point log, the GIS layers and the photos all come from the same records.

Your GIS stays your GIS. We're where the data is born.

COLLECTED ONCECEDAR RUN WETLAND DELINEATIONW-1 WetlandWETLANDSP-1SAMPLE POINTJuncus effususSPECIESSoil 0–8 inSOIL LAYER4 photosMEDIASP-2SAMPLE POINTUSACE data formDOCXWETLAND DETERMINATIONSAMPLING PT: SP-1Hydrophytic veg.Hydric soilWetland hydrologySample point logXLSXPOINTPIRESULTSP-11.52WetlandSP-24.00UplandSP-32.10WetlandSP-43.75UplandGIS layersSHP · GPKG · JSON · GDBW-1SP-1SP-2PhotosZIP · NAMED BY RECORDSP-1_01.jpgSP-1_02.jpgSP-1_03.jpgSP-1_04.jpg

The small things that save a field day.

11 features
  • A phone showing a photo's location and view cone on the project map.
    Mobile + Web

    Photos on the map

    Every photo lands where it was taken, with the direction it faced. Browse a site by where, not by filename.

  • A phone camera viewfinder with a heading-up map overlaid.
    Mobile

    A camera that knows where it's pointing

    Heading and a heading-up mini map right in the viewfinder, so every photo carries its direction.

  • A phone drawing a line from GPS as the user walks, with LiveTrack on.
    Mobile

    LiveTrack

    Walk the boundary or the transect. The line draws itself as you go, with GPS accuracy on every point.

  • A phone showing a connected external GPS receiver and its live position data.
    Mobile

    Bring your GNSS receiver

    Pair a Bluetooth receiver. Satellites, fix quality and raw NMEA ride along into every export.

  • A tablet listing nearby records, overlays and photos by distance.
    Mobile

    Nearby features

    What's around you right now: the closest records, overlays and photos, with distance and direction.

  • A tablet downloading an offline map area for a project.
    Mobile

    Offline map areas

    Download the project area's basemaps and imagery before you lose signal.

  • A phone measuring distance and bearing between points on the map.
    Mobile + Web

    Measure anything

    Distances, areas and bearings on the live map, and keep any measurement as an annotation.

  • A line being drawn on the map, snapping to a named shovel test point.
    Mobile + Web

    Magnetic snapping

    Vertices land exactly on the feature you mean, and Codifi tells you which one by name.

  • A polygon's previous outline shown behind the current one, above its shape history list.
    Mobile + Web

    Shape history and recall

    Every shape a location has had, with who changed it and when. Ghost an old one, or recall it.

  • A hillshade layer over the project map, with photo view cones plotted on it.
    Web

    Imagery on demand

    Hillshade, local relief, slope and historic imagery for any extent, kept as a layer and taken offline.

  • A tablet showing a record's history of edits and photos.
    Mobile + Web

    Record history

    Who changed what, and when, on every record. Review it before anything ships.

A surveyor in foul-weather gear standing on a boat's wheelhouse, scanning the water through binoculars.

Who built it

Built in the field, with field crews.

Codifi came out of cultural resource management and archaeology — deep record hierarchies, federal deliverables, and a long way from a cell tower. If it survives a Section 106 deliverable, it will survive your inspection form.

See it sync. Thirty minutes.

Bring a form you already use. We’ll build the Composition live.

01Your schema, standing up in the Composition Builder
02Two devices syncing peer-to-peer with the wifi off
03A report and a GIS export off the same records

We'll email you to set up a time.

Not ready for a demo? Email connect@codifi.com. Existing customer? Visit support.codifi.com.