Scope
Specify the physical assets, exact strands or conduit sections, geographic endpoints, and include exhibits or maps to prevent later conflicts about what was granted.
A well-drafted Indefeasible Right of Use Agreement reduces ambiguity about who may use assets, when access begins, and who pays for maintenance; it protects long-term access, supports financing, and minimizes operational disputes among owners, operators, and financiers.
Typical parties to an Indefeasible Right of Use Agreement include asset owners, network operators, and institutional participants in long-term infrastructure deals.
Identifying each party’s commercial role early ensures the agreement allocates liabilities, performance obligations, and transfer rights consistent with regulatory and contractual needs.
The grantor is the legal owner of the physical asset (for example, the party that holds title to ducts or fiber). The grantor retains ownership while granting defined use rights, and must ensure accurate asset descriptions, authority to grant rights, and clear maintenance obligations.
The grantee is the party receiving the indefeasible right (for example, a carrier or ISP). The grantee needs clear capacity definitions, term certainty, transferability rules, and protections for service continuity and dispute resolution.
Specify the physical assets, exact strands or conduit sections, geographic endpoints, and include exhibits or maps to prevent later conflicts about what was granted.
State the effective date, fixed term length, renewal options, and the circumstances that allow early termination or acceleration of rights.
Describe the capacity allocated (strand count, wavelength, or bandwidth), performance expectations, and testing or acceptance procedures.
Detail fees, payment schedules, escalation or CPI adjustments, tax treatment, and remedies for late payment to protect revenue streams.
Allocate maintenance and repair responsibilities, response times, outage credits, coordination requirements, and access protocols for technicians.
Include default definitions, cure periods, indemnities, limitation of liability, and dispute resolution procedures to streamline enforcement and claims handling.
| Field | Configuration |
|---|---|
| Signer Authentication | Email plus SMS code or ID verification |
| Field Types | Signature, initials, date, checkbox, conditional fields |
| Routing Order | Sequential or parallel routing depending on approvals |
| Retention | Automated archival, export to PDF/A for long‑term storage |
Select a platform that supports legal admissibility, strong authentication, secure storage, and exportable audit trails for the IRU agreement.
Confirm the provider can produce signed PDFs with embedded audit trails, support HIPAA or 21 CFR Part 11 when required, and integrate with your document management system for secure retention.
Date when rights and obligations begin; ties to service provisioning.
Due dates, late fee triggers, and escalation timing.
Dates for installations, testing, and acceptance procedures.
Timing to record instrument with land records to perfect notice.
Deadlines for breach notices and available cure windows.
Parties finalize terms, exhibits, schedules, and technical attachments.
Internal approvals, counterparty reviews, and counsel sign-off are completed.
Signatures are collected; notarization or RON performed if required by parties.
Access provisioning, testing, and handover to operations for service start.
| Criteria | IRU Agreement | Easement |
|---|---|---|
| Transferability | transferable | often perpetual |
| Term Length | fixed term | often perpetual |
| Consideration | periodic payments | one-time payment |
| Remedies | contract remedies | property remedies |
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Trial available | Trial available | Trial available | Trial available |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |
A regional carrier secures long-term use of two fiber strands across a metropolitan route to expand capacity and wholesale services.
A city grants an IRU to an ISP for conduit space under public roads to support broadband deployment.
Export final signed copies as PDF/A for archival or as standard PDF with embedded audit trail for legal admissibility and portability.
Attach maps, strand inventories, technical schedules, insurance certificates, corporate resolutions, and recording receipts as exhibits to the agreement.
Keep an audit log of each revision and the party who approved it to avoid disputes about which draft became binding.
Number exhibits, cross‑reference clauses to exhibit items, and ensure each exhibit is signed or initialed where required for completeness.