Field Purchases, Software Seats and Who Gets to Approve What

Design software licenses on an engineering project typically ramp up during the design development phase and drop off once construction documents are issued, but most firms provision seats once at project kickoff and never revisit them. A structural analysis tool licensed for four engineers during the design phase often still shows four active seats six months later, during construction administration, when only one engineer is actually still touching the model. That's not a small waste on a per-seat annual license, and it compounds across every active project running the same pattern.

Tying seat counts to project phase, not just to the project existing, is the fix, and it requires someone to actually own that review rather than assuming the software vendor's usage report will catch it.

A site engineer discovering a soil condition that requires immediate additional testing doesn't have time for a multi-step approval before ordering it, the client's construction schedule is often the thing at risk if that testing is delayed. Airbase's card-first model, with a spend limit scoped to field and testing categories, lets a project engineer make that call on-site and tag it to the project afterward. The tradeoff is the same one every card-first system carries: if the tagging step gets skipped in the field, someone in the office is reconstructing which project a testing invoice belonged to weeks later.

Because software seats are planned, known in advance, and tied to a specific project phase, they're a better fit for Procurify's request-first flow: a project lead requests seats for the design phase, names the project and expected duration, and the request routes to whoever manages the firm's software budget for approval before the license is provisioned. That upfront step makes it natural to also record when the seat should be reviewed for downgrade, at the phase transition, rather than leaving it open-ended.

Say a bridge design project moves from construction documents into construction administration, dropping from six active engineers to two. If software seats were provisioned once at kickoff with no phase tracking, the firm keeps paying for six seats through the entire construction administration period, often a year or more on a large infrastructure project. A request-first system that captured the original phase and duration makes the downgrade decision visible at the point it should happen, rather than relying on someone remembering to check months later. On a firm running a dozen active projects at different phases simultaneously, this single habit, reviewing seats at each phase transition, is usually the single largest source of recoverable software spend.

Most firms that get this right set a dollar threshold, often a few hundred dollars, under which a field engineer can buy testing supplies or rent equipment on a card without prior approval, tagging the project after the fact. Above that threshold, even urgent purchases route through a same-day approval request rather than an unlimited card, because a larger equipment rental or a specialized testing contract is exactly the kind of cost a project manager should see before, not after, it happens. The threshold itself matters less than having one explicitly set and understood by every field engineer, rather than leaving the line ambiguous and letting individual judgment vary project to project.

Set the field purchase rules like this:

• Pick a dollar threshold, often a few hundred dollars, under which a field engineer can buy on a card without prior approval.
• Have the engineer tag the project after the purchase, and review untagged transactions weekly so they do not pile up.
• Route purchases above the threshold through a same-day approval request instead of an unlimited card.
• Send new vendor relationships and larger equipment rentals through the slower request-first path.

A structural engineering firm working alongside a civil consultant, a geotechnical subconsultant and the client's own architect on the same project has to coordinate purchasing decisions that affect more than one firm's scope, a shared testing contract, say, that both the structural and geotechnical teams need results from. Neither Airbase nor Procurify manages cross-firm coordination directly, but naming the shared vendor and splitting the cost by discipline at the point of purchase, rather than after the invoice arrives, avoids the awkward conversation about who owes what on a joint cost weeks later.

This is where a request-first flow earns its keep even on a purchase that isn't urgent: the request itself becomes the record of which disciplines agreed to split a cost and in what proportion, which is useful documentation if a client or another consultant later questions how a shared expense was allocated.