Enhancing field operations efficiency through smart tools

Eric Helitzer

September 30, 2025

Procurement Practices

The field is where the work happens. It's also where the most information gets lost.

A superintendent writes down what materials they need. That note has to get to the right person in the office, who has to understand what's being asked for, confirm whether it's been ordered before, place the order with the right vendor, and communicate back to the field about when it's coming. At every step in that chain there's an opportunity for something to get lost, miscommunicated, or delayed.

When it does, the job pays for it. Crews waiting on material that's stuck somewhere in an approval chain. Reorders placed for items already confirmed because nobody told the field. Delivery tickets that don't make it back to the office until the invoice is already a problem. None of this is a failure of effort. It's a failure of the tools available to support the way field operations actually work.

What the problem looks like from the field

Field teams aren't sitting at desks. They're moving. The super who needs to request materials is the same person managing the crew, coordinating with the GC, and solving whatever problem surfaced that morning. Stopping to write a detailed requisition, wait for confirmation, and then follow up when nothing comes back isn't how anyone's day actually runs.

So requests go out by text. Or by phone. Or by writing something on a delivery ticket and hoping it makes it to purchasing. The information eventually gets there, usually — but late, sometimes incomplete, and without a record that connects back to the original request.

From the office side, the picture is just as fragmented. Purchasing doesn't always know what the field has already received. Accounting doesn't know what's been ordered until the invoice arrives. The PM is working off a budget that was accurate last week but may not reflect what went out the door yesterday.

That gap between field and office is where projects lose time and money.

What changes when the field has the right tool

The shift isn't complicated. It's about giving field teams a way to submit material requests that goes directly into the purchasing workflow — from their phone, in a format that contains the right information, without requiring a phone call or a follow-up.

With SubBase, a field superintendent submits a request using the company's own material catalog. The description is standardized. The cost code pre-fills. The request is visible to purchasing immediately, with no translation required. The field can see the status of what they've requested without calling the office to ask. When the material arrives, they confirm the delivery in the platform on the spot. That confirmation is visible to the office in real time.

That last step matters more than it might seem. A delivery confirmation in the system at the moment of receipt is the record that makes three-way matching work. It's the data point that tells accounting the material actually arrived before they pay the invoice. Without it, the match is always incomplete and someone has to chase it down manually.

Douglas Orr Plumbing processed 3,000 POs through SubBase in a single year and saved $189,000 in labor hours as a result. A significant part of that saving came from field teams using the platform properly — requests going in clean, deliveries getting confirmed in real time, and the back-and-forth between field and office dropping sharply.

What good adoption looks like

The technology only delivers if the field uses it consistently, and that doesn't happen automatically.

The biggest driver of adoption is simplicity. If the tool requires more steps than the current workaround, people won't use it. SubBase is built for the field specifically because of this: minimal typing, dropdown selections, phone-first design. A request that used to require a phone call takes thirty seconds.

The second driver is visible payoff. When field teams can see the status of their requests in the app rather than calling the office, that's an immediate, tangible benefit they feel on the job. When deliveries get confirmed and problems get flagged without anyone having to follow up, the friction they've been absorbing daily starts to disappear.

Getting the material catalog right before rollout is the foundation. If the items field teams need are in the catalog with accurate descriptions and the right cost codes, requests go out clean from day one. If the catalog is incomplete or poorly organized, the field defaults back to typing free-form descriptions — and the consistency that makes everything else work breaks down.

Field efficiency isn't just about what happens on site. It's about how cleanly the information generated on site flows back to purchasing, to accounting, and to the budget. When that flow is broken, the whole operation runs behind. When it's working, the job runs the way it was planned.

That's what SubBase is built to support.

Book a demo to see how it works: https://www.subbase.io/subbase-demo