
Read Fulcrum blog posts for field operations teams, covering mobile data collection, inspections, and daily workflows across all industries.

Fixed trimming schedules and top-down satellite imagery leave utilities guessing about where vegetation is closing in on their lines. In this demo, Woolpert and Fulcrum show how three-dimensional lidar data replaces that guesswork with precise, prioritized work.

Overhead imagery shows which trees threaten your lines, but it misses the spans crews cleared this morning. It also can’t show the dead oak a crew found that the imagery never caught. Until field results reach the model, your vegetation management program runs on a risk picture that lags the work.

The video showcases how Fulcrum’s Audio FastFill feature allows users to effortlessly fill out information using voice dictation. By simply pressing the record button, users can input details such as pole ID, classification, and accessibility without manual entry. The AI technology behind Fulcrum intelligently processes the spoken information, automatically selecting the correct values for the form fields. This innovative approach streamlines data entry, making it easier for users to manage their tasks efficiently.

AI can now turn an environmental agency’s paper form into a digital field app in minutes, speeding up form digitization. Speed has a catch, since agency forms depend on unwritten rules and an AI draft can miss them. Six practical checks and one test record help environmental teams digitize paper forms without losing what reviewers expect. A short routine in Fulcrum then takes each environmental inspection checklist from AI draft to field-ready app.

A soil boring log can get the geology right and still fall apart in an environmental audit. If a reviewer can’t tell who recorded a value, when, or with which meter, the log starts to wobble. Many of those answers exist only at the boring and vanish once the rig pulls out. See what a defensible log needs, and how Fulcrum captures every entry at the rig with its trail intact.

Issue 66 of the Fulcrum Insider rounds up our latest environmental and vegetation management resources, each one a click away. The common thread this month is field records that hold up from the first site visit to the final review. You’ll find links to a live webinar, two blogs, an infographic, an on-demand webinar, and three environmental reads from around the industry.

Years after an environmental remediation project wraps, someone will open its closeout file and start asking questions the field team is no longer around to answer. Some of those answers exist only if they were captured on site, on the day of the work. Find out which records a reviewer will ask for, and how teams use Fulcrum to build a file that holds up long after closeout.

Permits, sampling plans, and stormwater pollution prevention plans all expect a complete field record whenever an auditor asks for one. For many environmental compliance teams, that record still lives in paper forms, generic form apps, spreadsheets, and email threads. The Fulcrum Field Operations Management platform delivers every inspection and sample to the office complete, located, and correct before teams leave the site.

A corrective action can be signed off on schedule, and the same finding can still turn up at the next inspection. In the corrective and preventive action (CAPA) process, the trouble often starts at the evidence step, when a root cause gets built from memory and scattered photos. A stormwater example walks through the 5 whys and shows how Fulcrum keeps field evidence attached from the first finding to the final check.

After Fulcrum acquired Wildnote, we began planning how to move our customers and their environmental project data to the Fulcrum platform. That meant deciding what information to bring with them.

Clients and regulators judge an environmental consultant’s findings by the field record behind them, sometimes years after the baseline survey. Findings break when methods drift between visits or evidence scatters across files, and the right environmental reporting software closes both gaps at collection. See how Fulcrum helps consulting firms build impact records that can head off added studies and permitting delays.

Environmental teams know the feeling of finding a field mistake weeks after the crew has demobilized. By then, a return trip to the site is expensive, and sometimes it’s off the table entirely. Our infographic maps the five most common environmental field data problems against the moment each one finally comes to light.

Your AI can already build on Fulcrum. You just haven’t told it to yet. Join us to see what happens when you do.

Utilities looking to put AI to work already hold much of what it needs in their field operations. Asset management, vegetation management, linear construction, and emergency response generate records ranging from inspection findings to proof of work. Getting those records ready for AI has long been a struggle, since they come from separate tools, spreadsheets, and paper forms.

Issue 65 of the Fulcrum Insider follows good field data from water audit records to AI-built apps. You’ll also find a live AI webinar, a demo video, a data sheet, and a field service infographic.

Environmental data management often breaks down at the handoff, where monitoring records pass through several hands before compliance review. Records reassembled in the office draw extra scrutiny during audits and permit renewals, and some gaps require another site visit to close. Capturing structure at the point of collection gives compliance leaders records they can defend from the start.

A useful field record helps someone who wasn’t there understand what you observed. Sometimes, a written note and a photo are enough. Other times, you need to show movement, point out a detail, sketch a relationship, or explain what you’re seeing as you see it.

Vegetation is the most common cause of power outages in the U.S., accounting for more than 20% of incidents, and vegetation management is the number one line item on most utilities’ annual budgets. Spending at that scale comes with a reasonable question attached: what did the year’s work change. Field organizations run good programs and document them carefully, and answering that question still means inferring a good deal.

Ask anyone who runs field work what they stopped requesting. They already knew what the job needed, and none of it was impossible. But building the workflow seemed too complicated. And something else always seemed more important.

Water infrastructure fieldwork happens in pieces: an inspection here, a GIS layer there, a safety record somewhere else. This infographic shows how water and wastewater utilities bring it all into one system.

FSM software earned its category by handling customer service calls well. Asset-driven field work runs on different logic, and the FSM vs. FOM distinction names the gap. Crews feel it on day one, when a job begins at an asset instead of a customer.

Every field organization carries a workflow nobody could justify building: too complicated, too expensive, or just never urgent enough to make it onto a developer’s calendar. Multiply that one shelved idea across every crew, and the backlog turns into the norm. AI-guided workflow creation exists to clear exactly that kind of backlog, without adding a developer to the queue.

Utilities manage vegetation across every mile of corridor they own, usually without a current picture of what’s growing into the lines. Work gets scheduled by calendar, so some spans get trimmed years early while encroachment builds somewhere nobody’s watching.

How AI-assisted development lets environmental firms encode their own processes into app extensions, data events, and custom reports — without a developer.

A regulated MS4 generates field records because its permit requires them, from outfall mapping through post-construction maintenance. Records held in separate, unlinked systems are difficult to turn into capital priorities or permit documentation. Consistent inspection forms tied to a GIS asset layer give a program one record feeding inventory, condition scoring, and capital planning. Federal rules already require permit terms to be clear, specific, and measurable, and records to be kept for at least three years. A program holding those records year-round has far less to reconstruct when a report comes due.

GeoAI runs in ArcGIS. Predictive maintenance runs in an EAM. Most AI investments have two things: a team doing the work, and a platform for AI to run on.

Water utilities have 60 days to identify and report storm damage to FEMA, and paper forms or verbal radio reports can leave that record built mostly on memory. Missing GPS coordinates, photos, and asset-level detail can put reimbursement at risk before that 60-day window even closes. Utilities running water utility management software before severe weather hits get a prioritized repair list, records that map cleanly to FEMA’s funding categories, and disaster recovery documentation built to stand up to federal review.

GIS reliability and EPA-driven inspection demand define this month’s field operations conversation. Issue 63 of the Fulcrum Insider tackles AI and data quality gaps while stretching your Esri investment further. We also build the case for a dedicated Field Operations Management platform. Three headlines close out the issue, each one tracing back to unreliable field data.

Every water utility faced the same LCRR deadline last October, but the results split fast. Utilities with a clean lead service line inventory verified pipe materials in the field before the crunch hit. Others defaulted unresolved lines to unknown and are still paying for it in notifications and lead service line replacement program queues. Here’s what separated the two groups, and what the 2027 LCRI deadline demands next.

Challenges
Map book creation for field dispatch took up to three days of GIS staff time.
Earth resistance testing required manual asset matching and paper map books for field dispatch.
Logging a new tree asset on site required multiple manual steps.
GIS staff spent a lot of time checking and cleaning field data.
Limited defect visibility made it difficult to track and act on field data.

Alpine Energy runs the electricity network across South Canterbury, New Zealand, where field safety carries real stakes. Getting tree and earth-bank data right catches hazards before they become outages.

Explore how Fulcrum eliminates manual handoffs, routes critical issues, and keeps projects moving.

Water utility asset inspections often lack reliable photographic evidence. That leaves organizations vulnerable during contractor disputes, regulatory audits, and insurance claims. Visual inspection software like Fulcrum addresses this gap by using automation to embed asset IDs, GPS locations, and timestamps into photos at the moment of capture. Inside Fulcrum, custom AI models can also flag defects like corrosion or cracking in that same photographic evidence. Together, they create a centralized, searchable visual history that integrates with existing utility systems and the broader inspection workflow to provide immediate, defensible proof whenever it is needed.

Water utilities inspect hydrants, valves, and meters constantly, yet these water infrastructure records remain among the hardest to verify. GIS, CMMS, and field inspection software are often implemented separately, leaving records scattered across systems that don’t talk. Connecting those systems into one record keeps condition assessment data current and turns audit requests from a scramble into a routine pull.

The EPA is speeding up delivery of several major water infrastructure funding programs, including the Drinking Water and Clean Water State Revolving Funds, the WIFIA loan program, and the Emerging Contaminants grant. Together, these programs direct federal investment toward water systems and projects that protect water quality and public health. Faster funding means a faster-arriving wave of permitting, inspection, and reporting work for the environmental consulting firms that support water utility clients. Here’s what that shift means for field teams, and why documentation readiness decides which firms absorb it smoothly.

Pipeline integrity teams manage corridors spanning hundreds of miles under strict federal repair deadlines. Connectivity gaps and crew expertise gaps compound the challenge in the field. Most software wasn’t built to handle scale, regulation, connectivity, and crew skill gaps together. Here’s what pipeline integrity software needs to deliver instead.

Location data quietly shapes crew productivity, planning accuracy, and public safety, whether teams realize it or not. Issue 62 of the Fulcrum Insider covers reliable geospatial data, seamless GIS workflows, and where AI actually belongs in the field. Three real-world stories round it out, showing what happens when location records fail the people who depend on them.

Field Operations Management is the coordination of work that happens away from a fixed site: inspections, maintenance, construction, surveys and service calls. A Field Operations Management platform (FOM) is the single system that plans that work, puts it on a crew’s device, captures what they did and where, and closes the record out with the evidence attached. It replaces the mix of scheduling tools, forms apps, spreadsheets and paper most field organizations run on today. Our guide to Field Operations Management software covers the category in depth.

Field Operations Management (FOM) is the discipline of running, recording, and closing out the physical work field crews do, from the first site visit to the final compliance record. It covers the work orders, inspections, maintenance, and surveys that keep infrastructure in service, and it turns each one into a structured record the office can trust. This post defines the category, shows what it covers, and explains why the tools most field teams use today were built for something else.

Explore calculation fields you control, location data that fills itself in, and hierarchical artifact classification built for fieldwork.

Most GIS teams spend significant time maintaining field apps that should belong to the field team. The problem is structural and won’t be solved by better communication. Discover the ownership shift that fixes it and what both sides get back.

Water utilities run dozens of field programs generating water utilities field data that regulators, clients, and auditors will eventually demand to see. Most of it lands in spreadsheets or disconnected apps that were never built to produce defensible records. A dedicated field platform closes that gap, producing geolocated, timestamped, attributable records across every program a crew runs.

Using AI to vibe code a field tool sounds straightforward until you realize how much groundwork has nothing to do with the problem you set out to solve. Offline sync, spatial data, validation logic, consistent interfaces across devices: field operations demand all of it, and building it from scratch takes months. The smarter approach is extending a platform that’s already handled that work.

In the environmental sector, regulatory and operational shift is the norm. Evolving definitions of WOTUS and changing client demands leave many firms managing their environmental field workflows in survival mode. Getting reports out the door takes priority over building something better.

The video reveals how maintaining your own field operations platform gives you defensible records to protect your bottom line and move faster than your competition by eliminating those inefficiencies.

Many operations leaders blame scheduling or staffing gaps for missed SLAs, completely overlooking how poor field data accuracy quietly derails their daily workflows. This post explores how high-quality geospatial field data eliminates costly, hidden worker workarounds, improves data capture, and optimizes the entire operational lifecycle across planning, execution, and review. Discover how investing in location data quality transforms field operations performance from reactive firefighting into a compounding competitive advantage.