Outside Plant Construction Software: Why Your Crews Are Ahead of Your Billing

Why outside plant construction breaks the tools that sold you on it

A fiber build is paid in units. So many feet of aerial strand, so many feet of directional bore, each handhole set, each pole transfer, each service drop. The crew produces those units in the field all day. The money only moves when the units are verified, the permit is closed, the restoration is signed off, and the as built package is delivered in the owner's format. Between those two events sits every dollar of working capital your business has.

The gap is measured in weeks and it is entirely administrative. Foremen report footage on paper or in a group chat. The permit is with a coordinator who is chasing a municipal clerk. The inspector signed the ticket but the photo is on somebody's phone. The redlines are marked on a printed plan sheet in a truck. The general contractor cannot invoice, so the sub does not get paid, so the sub slows down, so the program slips, and none of it is a construction problem. It is a records problem that shows up in a construction schedule.

What makes it worse is that the units the crew produced and the units the owner will pay for are not the same list. Owners pay against their own quantity schedule, at their own verification standard, with their own rules about when a partial run counts. If your production record and their pay record were never the same object, reconciliation is a manual exercise done under time pressure by whoever is available, and the errors go in one direction. Nobody ever accidentally over bills themselves into a bonus.

What actually happens on a Thursday

A directional drill crew bores 1,900 feet along a county road. Two of those hundred foot sections cross a driveway, which is a different pay item. They hit an unmarked service lateral at station 14, which becomes a damage ticket, which becomes a claim. The restoration crew will not be there for eleven days. The inspector walks the run on Friday and marks two handholes as not set to grade.

By the following Monday the foreman has moved to a different jurisdiction, the daily report says 1,900 feet with no split for the driveway crossings, the damage ticket is in the safety manager's email, the inspector's note is on a paper punch list, and the restoration is nowhere. When the pay application goes out at month end, that run is billed at a single rate, the driveway units are missed, the damage claim is not accrued, and the owner rejects the line anyway because the as built has not been submitted. Everybody involved did their job. The system lost the money.

What Sitetracker, Render Networks, Vitruvi and IQGeo actually fail at

These are real products and some of them are good. Sitetracker is strong at portfolio and site level program tracking, and it earns its place on carrier deployment programs where the unit of work is a site. Render Networks is genuinely built around production and works well where the design is complete and the work is broken into pre defined tasks. Vitruvi is aimed squarely at this space. IQGeo is excellent at network records and spatial data, which is a different job.

Where a contractor runs into their limits is nearly always the same three places. The first is the unit price schedule. Every owner program has its own pay item list with its own definitions, its own minimum measurement rules, and its own escalators. Configuring that inside a packaged tool works until an owner adds a bespoke item mid program or pays a different rate for the same work in a different municipality, and then you are back in a spreadsheet next to the system you bought.

The second is the as built package. Owners do not want a report, they want their format: their attribute names, their coordinate system, their file structure, their naming convention, delivered into their inventory or geographic information system. A generic export is a starting point for a week of manual rework. Contractors who build for three owners are maintaining three separate translation processes by hand.

The third is the multi tier subcontractor reality. Most fiber production is done by subs, often two tiers deep, each with their own rate sheet, retainage terms, and insurance and prequalification status. Packaged tools model a crew. They do not model a chain of commercial relationships where the unit you bill up is a different price from the unit you pay down, and where a sub's expired certificate of insurance should freeze their pay application automatically.

What a custom outside plant build has to include

Start with the pay item as the atom. A production entry is a quantity of a specific pay item, at a specific location expressed as a station range or a coordinate, on a specific date, by a specific crew, against a specific work order under a specific program. Everything else in the system is a view of that record. If the atom is right, billing, production reporting, sub payment and progress all come out of one place instead of three.

Field capture has to work offline and it has to be fast. A foreman standing in a right of way at the end of a shift will use a form that takes ninety seconds and will not use one that takes eight minutes. Photos attach with position and timestamp automatically because photos are what settle disputes later. Splits that matter for billing, such as a driveway crossing at a different rate, get prompted rather than remembered.

Permits and inspections have to gate the money, not sit beside it. Model each permit with its jurisdiction, its conditions, its expiry, and the pay items it authorises. A production entry in a location with no open permit gets flagged the same day, not at month end. Inspection sign off attaches to the specific units it covers, so a partial approval releases partial billing instead of holding the whole run.

Restoration deserves its own track because it behaves differently from everything else. It happens weeks later, often by a different crew or vendor, in a different weather window, and it is frequently the last thing standing between you and a closed permit. Give it its own backlog with an ageing view, because an unrestored trench in a municipality that is about to review your next permit application is a business risk and not a punch item.

As built assembly should be continuous rather than a phase. Redlines captured against the design in the field, joined with production records and inspection evidence, means the package is close to complete when the last unit is placed. The final step is a per owner export profile that maps your attributes to theirs. Build that as a translation layer you can add to, because you will win a fourth owner with a fifth format.

One integration is close to mandatory: the locate ticket system you already use for 811 requests, so that damage events attach to the run that caused them and your claim file assembles itself. The second worth costing is your accounting system, so that approved production becomes an invoice line without rekeying.

What it costs and how long it takes

In Digital Heroes delivery experience, a focused first release runs $70,000 to $150,000 and ships in 12 to 18 weeks. That release is offline field production capture against a real pay item schedule, permit and inspection gating, and a first as built export for your largest owner. Crews use it on live work in week one of rollout.

A full platform at $180,000 to $400,000 phased over 6 to 12 months adds redline to record drawing workflow, subcontractor pay applications with retainage and compliance holds, restoration and damage claim tracking, program level forecasting, and export profiles for each owner.

What drives the number up in this category: the count of distinct owner programs, since each brings a pay item schedule and an as built format. Geographic information system integration, because writing into an owner's inventory model correctly is a real piece of work and testing it requires their cooperation. The number of subcontractor tiers you pay. And design data, because if your plans arrive as PDFs rather than as structured data, capturing redlines against them takes more engineering than it should.

What holds it down: pick one owner program and your two highest volume pay item types for the first release. That covers most of the money and teaches you what the rest needs.

How to choose a developer for fiber construction software

Give them your actual unit price schedule in the first meeting and ask them to model three items on a whiteboard, including one with a conditional rate. A developer who has done this asks how partial units are measured, whether the rate changes by jurisdiction, and what evidence the owner requires before a unit is payable. A developer who models a task list with a percent complete field is going to learn unit price contracting on your budget.

Ask specifically how field capture behaves with no signal for six hours and a conflicting edit from the office. Offline is not a checkbox, it is a conflict resolution design, and the honest answer involves a queue, a sync log, and a rule for who wins. Vague answers here become lost production data in month three.

Ask what as built formats they have actually delivered into and to which owner systems. Writing into a network records platform is a different problem from producing a spreadsheet. Ask for the specific system and the specific attribute mapping, not a claim about supporting integrations.

Ask who owns the code and get it in the contract before kickoff. You should hold the repository, the infrastructure accounts, and the freedom to hire another firm. At Digital Heroes the client owns the code from the first commit, and any developer who is uncomfortable with that is designing a dependency rather than a system.