Skip to content
MLNetworks
Talk to an Expert

Sites & Tenants

Lease and tenants on the site record.

Sites & Tenants is the part of MLNetworks that keeps a site's leases, tenants and colocation requests on the same record as its equipment and power.

The lease, the tenants and the colocation requests sit on the same site record as its assets and its alarms.

Talk to an Expert
Landlords & LeasesLSE-0417

LSE-0417

Ridgeview RDG-0417

Tower site, 36 m

Active
Agreement type
Ground lease
Tenure type
Leasehold
Version
v2, effective 01 Mar 2024
Tenants on site
2

At a glance

Next critical date
Notice window - 30 Apr 2027
Open disputes
None
Renewal case
None open

Tenants

  • Tenant AIn service
  • Tenant BRequest open

From the lease to the tenant on the tower

  1. 01

    The lease, with its critical dates

    Each site carries its lease: terms in force, version history, notice windows and renewal options. Every date has a status and an owner.

    Landlords & LeasesLSE-0417

    LSE-0417

    Ridgeview RDG-0417

    Tower site, 36 m

    Obligations and critical dates

    • Renewal notice windowUpcoming
      Notice window30 Apr 2027
    • Renewal optionUpcoming
      Renewal option31 Oct 2027
    • Access to the compoundOpen
      Access obligation15 Dec 2026
    • Termination clause reviewMet
      Termination clause12 Jun 2026

    Source: v2 - signed lease document

  2. 02

    Tenants, and who is holding things up

    The tenant portfolio lists each tenant on the site and its footprint. For each one you see whether the next step is with the tenant, with your team or waiting on a decision.

    OverviewTenant Portfolio

    Tenant Portfolio

    Ridgeview RDG-0417

    TenantAttention

    Tenant A

    TEN-0001

    Nothing open

    Tenant B

    TEN-0002

    Colocation request

    Who the next step waits on

    Needs decisionWaiting on tenantWaiting on us

    Billing and accounting stay in your ERP. This view shows context, not invoices.

  3. 03

    A colocation request, stage by stage

    A request is checked against what the tower can still take, held while terms are agreed, and converted once signed. A person makes each call.

    ColocationCapacity Reservations

    REQ-0417-B

    Colocation request

    Tenant B - Ridgeview RDG-0417

    Active

    1. Requested

      Tenant B asks to add equipment on the tower

    2. Capacity checked

      Tower EPA, ground space and power checked

    3. Held

      Capacity held until the agreement is signed

    4. Agreed

      Hold converted to an agreement

    Check against the site

    • Tower EPA
    • Ground space
    • Power
    Waiting for a person to decide

    Expires 28 Oct 2026

    Convert to agreementRelease hold

Read from the registers you already keep

Integration scope is defined for each deployment, and each source is validated with your team before it is named as supported.

  • Site and asset registers
  • Lease and contract documents
  • Tenant and customer records
  • ERP and billing systems, for reference only

Lease dates and spare capacity

  • Dates on lease LSE-0417

    202620272028

    Critical dates, before they pass

    Notice windows and renewal options sit on a timeline for each lease, so nobody finds out after the date has passed.

  • Capacity at Ridgeview RDG-0417

    Tower site, 36 m

    Active
    • Tower EPARoom left
    • Ground spaceRoom left
    • PowerRoom left

    Held by active requests

    Capacity checked before a promise

    A request is compared with the site as built: tower EPA, ground space and power. The commercial team can see which sites are full before promising anything.

From the agreement to the equipment on site

Once a request is agreed, the site record is updated. Operations sees the new tenant and its equipment on the same site and the same lease.

Assets & Inventory

Hand-off to operations

Tenant B colocation

REQ-0417-B - Ridgeview RDG-0417

Equipment to record

  1. Agreement recorded

    Linked to lease LSE-0417

  2. Hold converted

    Capacity no longer open

  3. Site record updated

    Tenant B added to the site

  4. Equipment to record

    Installed items added to the register

Open site record

Commercial and operations work from one site

  • One record per site

    The lease, the tenants and the requests sit with the site, not in a file kept by another team.

  • Dates are owned

    Each critical date has a status and an owner. If nobody owns it yet, it says so.

  • Billing stays in your ERP

    MLNetworks shows the commercial side of a site. Accounting and invoicing stay in the systems you already use.

FAQ

Common questions

Does it replace our ERP or billing system?

No. Billing and accounting remain in your ERP. MLNetworks shows the commercial context of a site, such as its lease, tenants and requests, beside the operational record.

Where do the lease details come from?

From the lease documents and registers you already hold. How they are loaded and checked is defined for each deployment.

Who approves a colocation request?

A person. The product prepares the capacity check and holds capacity for a time. Converting or releasing the hold is a decision for your team, and it is recorded.

Can we track more than one tenant on a site?

Yes. The tenant portfolio lists each tenant with its footprint and what its next step waits on. How tenants are grouped depends on your records.

Which source systems can it read from?

That is defined for each deployment. We validate each source with your team before we name it as supported.

Sites & Tenants

Which site decision needs both records?

Bring a real case. An MLNetworks expert will walk through it with you.

Talk to an Expert

More of the platform

Every part uses the same sites and assets. Start where the need is greatest and add the next when you are ready.