Dark Fiber IRU Management: Can You Prove Those Strands Were Never Resold?

Why an IRU is an asset problem wearing a contract costume

An indefeasible right of use is not a service agreement. It is closer to a property interest: a counterparty prepays capital for the exclusive use of specific physical fibres along a specific route for twenty or thirty years, pays a recurring maintenance charge for the term, and holds rights over what happens if that route has to move or gets cut. The money arrived a long time ago. The obligation is still running, and the person who negotiated it has almost certainly left.

Here is the moment operators discover the gap. A wholesale customer asks for twelve strands on a route between two markets. The sales engineer checks the inventory system, sees available fibres, and quotes. Somewhere in a contract folder is a 2011 agreement that assigned specific strands on part of that route to another party, described in an exhibit as a written segment list rather than as a record in any system. Nobody checked, because checking means reading contracts, and reading contracts is not part of the quoting process. Now you have either sold something twice, or you spend a fortnight proving that you have not.

The structural cause is that two things which must agree are held in two places that cannot see each other. The contract is a document, filed with other documents. The fibre is a record in a GIS or inventory system, filed with other fibres. There is no object that says this strand, on this segment, from this splice point to that one, is encumbered by this agreement until 2041. Until that object exists, every assurance you give about availability is a person's recollection.

Problem 1: the obligation is a strand and the contract describes a page

IRU exhibits describe fibres in prose and tables: strands 25 through 36 on the segment from the Elm Street handhole to the north side of the interstate crossing, subject to reassignment on relocation. That description was accurate when written. Since then the route has been spliced, a section has been relocated for a highway widening, a regeneration site was added, and the fibre counts on one span changed during a cable replacement. The contract's description no longer maps cleanly onto the plant as it exists.

VETRO FiberMap and 3-GIS both model fibre plant properly, down to strands, splices and segments, and they are the right tools for that job. What neither is built to do is carry a commercial encumbrance with a term, a counterparty, an escalating charge and a set of rights. Agiloft and Icertis are capable contract lifecycle platforms and will manage the document, its clauses and its dates well. What they do not do is understand that a clause refers to a physical strand whose identity changed when the cable was replaced. Between those two categories sits the thing you actually need, and nobody sells it because it is made of your plant and your agreements.

What a custom build does: create the encumbrance as a first class record that references the inventory system's own strand and segment identifiers, and that survives plant changes because it is versioned. When a segment is relocated or a cable is replaced, the encumbrance moves with a recorded reassignment rather than silently detaching. Then availability checking becomes a system function: before any quote, the segment returns its total fibre count, its lit usage, its encumbered strands and their expiry dates. That is the whole point of the project, and everything else is built around it.

Problem 2: the maintenance charge leaks quietly for twenty years

The recurring operations and maintenance charge is the part everyone underestimates because each individual amount is small next to the original capital payment. It is usually computed per fibre mile or route mile, adjusted annually by an index or a fixed percentage, sometimes with a cap, and it runs for the life of the agreement. Over a twenty five year term compounding matters enormously, and the escalation is applied by whoever remembers to apply it.

What we see in practice: escalators that were never applied for several years because the person who did it left, indices applied from the wrong month, agreements where the counterparty was invoiced at the original rate for a decade, and a handful where the operator was overcharging and had to issue credits after a counterparty audit. All of that is invisible in a folder of PDFs. None of it is visible in the general ledger either, because the ledger records what was invoiced, not what was owed.

What a custom build does: hold the charge as a formula rather than as an amount. Rate basis, unit count, escalation method, index source, effective month, cap and floor become structured fields, so the annual adjustment runs automatically and produces both the invoice and a notice document with the calculation shown. Where you are on the paying side of an IRU, and most operators are on both sides, the same engine checks incoming invoices against the agreement and flags a mismatch before it is paid. Operators who ship this typically find the first year's recovery on incorrectly escalated charges is a meaningful fraction of the build cost, which is a rare thing to be able to say honestly about a contract system.

Problem 3: relocation and restoration are argued from a folder

A state highway agency orders a relocation. Your route moves. The cost is shared between the parties on the route, usually pro rata by fibre count or by some formula negotiated in each agreement, and each agreement's formula is different. Assembling the cost share means reading every contract touching that segment, computing each party's proportion, and issuing invoices that the counterparties' own asset managers will challenge because they are also reading from PDFs.

Restoration is the same shape under time pressure. A cut happens. The maintenance obligation, the response time commitment and the liability position differ per agreement, and the operations team fixing the cable at two in the morning has no visibility into any of it. Afterwards, somebody works out who is owed what and whether a service level credit applies, from a spreadsheet built for that incident.

What a custom build does: attach the cost sharing formula and the restoration terms to the segment through the encumbrance record, so a relocation project on a route produces the participant list and each party's share as an output rather than a research task. Splice and repair events from the operations side get logged against the segment, so the response time evidence exists without anyone reconstructing it. This is where the join between contract and plant pays off most visibly, because both of these events are fundamentally geographic and the contract system cannot see geography while the GIS cannot see terms.

Problem 4: diligence arrives and the answer takes six weeks

Fibre assets change hands constantly, and infrastructure funds do serious diligence. The question is always the same: show us the encumbrances. Which routes carry IRUs, for what terms, with what renewal or extension rights, what assignment and change of control provisions, what restoration obligations, and how much of the network is actually free to sell.

When that answer comes from reading a folder, two things happen. The process takes weeks of senior time, and the buyer discounts for uncertainty, because an inconsistent answer implies risk they cannot size. We have seen operators discover during diligence that an agreement contained a right of first refusal on adjacent strands that nobody had tracked, which changed the shape of the deal late.

What a custom build does: make the diligence pack a report. Every agreement's key terms structured, every encumbrance mapped to the plant, expiry and extension dates in a schedule, assignment and change of control clauses flagged, and an unencumbered capacity view by route. That report also serves the ordinary business, because the same view is what your wholesale team needs before quoting and what your finance team needs to value the asset base. Building it for diligence and using it daily is the correct order of operations, not the reverse.

What an IRU management build costs and how long it takes

From Digital Heroes delivery experience, a first release covering structured agreement records, strand and segment level encumbrance linked to your inventory system, the maintenance charge engine with escalators, and availability checking before quote runs $60,000 to $130,000 and ships in 12 to 16 weeks. A full platform adding relocation and restoration cost sharing, assignment and change of control tracking, counterparty portals, incoming invoice validation and diligence reporting runs $160,000 to $380,000 phased over 6 to 11 months.

What drives cost up in this asset class specifically: the number of legacy agreements requiring abstraction, since someone has to read each contract and encode its terms and that is the dominant line in the budget for portfolios with long histories. Whether your fibre records are actually strand level, because if the inventory only goes to cable level then the encumbrance cannot attach where it needs to and inventory work comes first. Acquired networks, where the agreements arrived without a clean schedule and the plant records use different conventions. And the number of counterparties who will want a portal rather than an emailed statement.

What keeps cost down: abstracting the twenty agreements that cover most of your route miles first, and leaving the small historical ones for a later phase. The distribution here is usually steep and you can get most of the risk covered quickly.

When Agiloft, Icertis, VETRO or 3-GIS is the right call

Buy the document layer and buy the plant layer. Agiloft and Icertis handle contract lifecycle, clause libraries, approvals and obligations at a general level and there is no reason to rebuild that. VETRO FiberMap and 3-GIS model fibre plant seriously, and rebuilding a fibre GIS would be an expensive mistake. If your problem is that contracts are unsigned and unfiled, or that your plant records are incomplete, fix that first with the products built for it.

Our position on when to build: when two or more of these are true. Your commercial team quotes availability without a system check against encumbrances. You have IRUs older than the people managing them. Your maintenance charge escalators are applied manually, or you cannot confirm they have been applied at all. Relocation or restoration cost sharing is computed by reading contracts. Or you are heading into a financing, a sale or an acquisition where encumbrance clarity affects valuation.

The tipping point is that a contract platform manages documents and a fibre GIS manages glass, and the risk lives precisely where a clause has to be enforceable against a strand. That join has never been productised because it is specific to how your plant is recorded and how your agreements were written. It is also, for the same reason, the part that carries the asset value.

How to choose a developer for fiber contract and asset software

Ask them to draw the encumbrance object. A developer who understands this will show a record referencing segment and strand identifiers from your inventory system, with a term, a counterparty, a charge basis and a version history that survives plant changes. Someone who draws contract with an attached document has built a contract repository and will not solve the double sold strand problem, which is the reason you are doing this.

Ask what happens to an encumbrance when a cable is replaced or a route is relocated. If they have not thought about it, the system will silently detach obligations from plant and you will trust it right up until the moment it is wrong.

Ask what they have integrated by name. 3-GIS and VETRO expose data differently, and an operator running an internal inventory built on a spatial database is a third case. A developer who asks which system holds strand level truth before quoting is asking the right question.

Ask who owns the repository and the hosting accounts, and settle it in the contract before kickoff. At Digital Heroes the client owns it from the first commit. A practical first step that costs nothing: pick one route where you are confident there is spare capacity, then have someone read every agreement touching it and confirm. Whatever that exercise turns up, and how long it takes, is your business case.