A growing number of operators now mandate that subcontractors submit work through specific platforms — OpenTicket, SAP Fieldglass, IronSight, Ariba, or proprietary portals. These systems serve legitimate purposes: validating tickets against price books, automating AP workflows, and integrating with operator ERP systems.
But a common mistake among subcontractors is assuming these mandated systems can run their entire operation. They can’t, and the gap creates measurable inefficiency.
What Operator Portals Do Well
Mandated systems excel at their designed function: managing the operator’s side of the transaction.
They validate submitted work against contracted rates, route approvals to appropriate decision-makers, process invoices into operator accounting systems, and track compliance with procurement requirements.
For subcontractors, efficient use of these systems accelerates payment. Fighting them or submitting poor-quality tickets creates friction that delays revenue.
What’s Missing
The limitation is that these systems were built for operator accounts payable departments, not subcontractor operations. Key gaps include:
Dispatch and scheduling. Operator portals document work after completion. They provide no tools for deciding which crew goes where tomorrow, managing equipment assignments, or responding to urgent calls.
Job costing. Portals validate that submitted rates match the contract. They don’t track whether the job was profitable, compare actual costs to estimates, or flag scope creep before invoicing.
Quoting. When an RFQ arrives, mandated systems can’t pull historical data on similar jobs, calculate labor and equipment costs, or analyze which work is worth bidding.
Multi-customer management. Most subcontractors work for multiple operators, each requiring different submission formats. Portals solve the single-customer case but add complexity for companies managing dozens of customer relationships.
The Staffing Implication
One metric captures the operational gap: field-to-office ratio.
Companies running unified field operations platforms report ratios of 40:1 — forty field workers supported by one admin role. Traditional operations relying on manual processes and disconnected systems typically run at 10:1.
For a company with 200 field workers, that’s the difference between 5 admin staff and 20. At $65,000 per position including benefits, the gap represents nearly $1 million annually.
The Practical Approach
Industry observers suggest subcontractors should use mandated systems for what they’re good at — validation and approval — while running actual operations on systems designed for service companies.
This typically means maintaining two layers: operator-facing submission workflows that meet customer requirements, plus internal systems that handle dispatch, costing, and the operational decisions that mandated portals don’t address.
The full analysis is available on the Aimsio blog.
