A tenant addition is not a license to redescribe an entire macro site. The useful engineering question is smaller: which antenna, radio, mount, line route or compound reservation changes and which existing assets does that change actually touch? Treating the application as a whole-site redesign makes the package longer while making responsibility harder to see.
This article uses a tenant-delta ledger tied to the tower owner’s accepted baseline. It excludes coverage planning, broad RF modernization and wholesale antenna replacement. Structural, property, carrier and regulatory decisions remain with their authorized reviewers. Our job is to keep the proposed tenant change coherent across the schedule, analysis, drawings and installed record.
Define the Tenant Change Before Analyzing the Tower
1 ledger controls each tenant delta. It names every proposed addition, removal and relocation before co-location engineering cell tower work begins. The ledger ties each item to the owner baseline, mount position, line route and compound interface, so reviewers can clear the tenant change without reopening unrelated sectors or implying authority they do not hold.
Our object under review is the tenant change, not the tower in the abstract. Existing equipment enters the package only when it shares a mount, attachment, load path, cable route, power interface, grounding point or reserved compound space with that change. A remote cabinet label may need correction, but it should not delay the application unless it changes the proposed power, grounding or cable interface under review.
Our request establishes tenant identity by freezing manufacturer models, quantities, centerlines, azimuths, mount positions and ancillary equipment before analysis starts. The model anchors the request. Any dimension not confirmed in the current cut sheet or field record becomes an assigned field question. The ledger records the missing value and its owner instead of inserting a likely dimension into the schedule. Broader modernization belongs in a separate package under our wireless engineering services.
Each delta item can be proposed, held, approved, rejected or installed and accepted. Those states run in parallel by discipline. RF approval does not clear structural loading. A passing structural result still does not grant lease space or installation access. Lease consent remains separate. The ledger shows where the item is actually stopped and who can move it.
Scope test. If the request changes coverage strategy, several tenant sectors or the site’s broader architecture, open a macro-upgrade package. The co-location record can reference that work, but it should not disguise a larger redesign as a routine tenant addition.
The ledger also fixes the elevation datum and the naming rule used across carrier, owner and structural documents. A centerline quoted from the wrong datum can make the same antenna appear to occupy two elevations, while a generic model name cannot distinguish identical radios on different mounts. Recording the owner ID, tenant ID and any drawing alias together lets the team reconcile those differences before loads or line lengths are calculated. That identity crosswalk remains with the installed delta.
Use the Owner Baseline
The tower owner identifies the accepted structural model, current appurtenance register, modification drawings and relevant lease exhibit. We check revision coherence only where the tenant delta depends on those sources. Mixed revisions stop the tenant review. A newer antenna schedule attached to an older controlling model is not permission to recreate a whole-site baseline from assumptions.
Field verification targets delta-sensitive gaps in the named mount, accessible connection geometry, proposed line route, centerline datum and shared compound interfaces. Photos carry orientation and asset references. Unrelated appurtenances remain in the owner baseline unless evidence shows they affect the proposed load path or shared route; this focused method avoids converting one tenant application into an unbounded tower survey.
Discrepancies enter a tenant exception register with affected ledger row, consequence and next owner action. An unrecorded radio on the same mount can alter demand. A line-route conflict can block installation. By contrast, an unrelated label issue can remain in the owner’s broader record program without delaying the tenant delta; the antenna installation project management guide covers field release after design.
Existing, removed and proposed states remain distinct. Removal credit is allowed only when the approved installation sequence makes that removal enforceable, the responsible analysis accepts the sequence and the owner can verify the dependency before release. We use this three-state view as project guidance only for equipment connected to the tenant delta; it is not a universal structural rule.
One ID follows each delta item. It appears in the tenant schedule, analysis input, drawing callout and closeout evidence. Manufacturer model alone is not enough when several identical radios or antennas occupy the site. The identifier lets reviewers isolate one substituted, relocated or removed item without reopening unrelated tenant equipment. It also prevents a photo of the correct product at the wrong centerline from being accepted against a generic schedule row.
Baseline uncertainty is graded by decision impact rather than hidden in a general note. A missing bolt detail on the affected mount can block structural release; an unverified label on a remote, unrelated cabinet may not. The responsible discipline decides the technical consequence, while the owner decides whether broader verification is warranted. That separation keeps the delta focused without dismissing a discrepancy that genuinely reaches the proposed load path.
Build One Evidence Ledger for Tenant-Specific Interfaces
The following matrix is not a macro-upgrade checklist. It maps each tenant-addition interface to the evidence and decision owner needed to clear that single delta.
| Tenant-delta lane | Controlled question | Evidence attached to the ledger | Decision owner |
|---|---|---|---|
| Antenna and radio delta | Which models, quantities and centerlines change? | Frozen tenant schedule and manufacturer data | Carrier and tower owner |
| Mount interface | Which mount members and connections receive demand? | Verified geometry, mount analysis and disposition | Responsible structural professional and owner |
| Tower load delta | How does the tenant change alter the accepted model? | Delta load case and modification reference | Responsible structural professional and owner |
| Line-path occupancy | Which approved attachments and transitions are used? | Route sketch, line schedule and conflict record | Tower owner |
| Compound interface | Which cabinet, power, grounding and access spaces change? | Tenant overlay and discipline approvals | Tower owner plus applicable disciplines |
| Accepted tenant state | What installed delta becomes current? | Closeout comparison and exception dispositions | Tower owner and carrier |
ANSI/TIA-222-I is identified by TIA as the Structural Standard for Antenna Supporting Structures and Antennas. That source establishes the standard’s identity, not the governing edition for every site. Adopted codes, jurisdiction requirements and owner contracts define the project basis and the responsible structural professional records that basis in the tenant analysis.
Mount evidence stays distinct from the tower-level result. A tower can have global capacity while an existing sector frame, platform or connection cannot accept the tenant demand. Proposed ancillary equipment therefore carries accurate projected area, weight and offset. Unknown steel is measured, replaced or held; it is not hidden behind a whole-tower utilization statement.
Resolve Shared-Asset Collisions, Not Macro Design
RF authority supplies the tenant antenna models, azimuths, centerlines and tilt requirements. Structural engineering receives the corresponding loads but does not approve coverage performance. The delta ledger records the interface and any conflict. It does not develop a broader RF modernization plan or optimize other tenant sectors.
Line-path review asks whether the proposed tenant route can use the identified attachments, transitions and entry point without displacing accepted shared assets. Hybrid trunks, coax or fiber jumpers follow approved manufacturer practice and owner criteria. The fiber backhaul design for cell towers guide covers ring, spur and transport choices beyond the accepted demarc.
Power and grounding appear as interface evidence, not as a complete electrical redesign. The tenant supplies demand through the responsible discipline. Existing breaker labels, cabinet positions and grounding points are checked against owner records. An available position is not proof of upstream capacity and a drawing note does not become a universal bonding method.
Compound review keeps shared assets distinct by overlaying only the proposed cabinet, access path, cable entry and maintenance envelope against accepted reservations. A cabinet can fit geometrically while blocking another tenant’s route. The owner decides lease and space availability. We can identify the collision and propose a technical alternative but cannot grant property rights.
Temporary states enter the ledger only when the tenant sequence differs materially from the accepted final state. Hoisting, staged removal or partial installation can alter mount or tower demand. The construction planner supplies the sequence and the responsible structural professional decides which temporary cases require analysis. Final-state acceptance cannot be used to infer temporary capacity.
One equipment schedule controls tenant RF, structural and construction references. Any model, quantity, elevation or disposition change updates the delta ledger. A late radio substitution returns only the affected rows to review. This is narrower and more traceable than rerunning a generic end-to-end upgrade narrative after every change.
Alternates stay outside the released state until their interface evidence is complete. If procurement proposes a different antenna, radio or mount, the ledger compares the exact weight, projected area, offset, connector and pathway consequences with the accepted item. Similar dimensions do not prove equivalent demand. The responsible reviewers can clear the affected rows while leaving unrelated tenant evidence intact, which makes substitution control faster without making it informal.
Shared-mount sequencing deserves its own dependency record. A tenant removal may create space for the addition, yet the owner cannot credit that space or load reduction until access, sequence and acceptance are enforceable. The ledger links the removal evidence to the proposed installation row and states which operation must occur first. This is tenant-addition coordination, not a redesign of every appurtenance attached to the tower.
Limitation: A delta-ledger approach depends on a usable owner baseline. If the accepted record cannot support the tenant interfaces, the owner may commission broader verification or a macro-upgrade package. We will not label that expanded work a routine co-location review.
Attach Regulatory and Property Decisions Without Claiming Them
47 CFR 1.6100 implements review rules for certain eligible facilities requests involving existing wireless towers or base stations. Eligibility is a legal and fact-specific determination. The delta ledger supplies dimensions and modification facts, then records the determination and decision maker. We do not declare eligibility or bind a state or local authority.
FCC environmental and historic-preservation materials, including the Nationwide Programmatic Agreement for collocation, contain criteria and exceptions. Existing-structure use is not a blanket exemption. The tenant file references the applicable determination rather than repeating a full regulatory workflow. Counsel, the owner and reviewing authorities control legal conclusions.
FAA obstruction evaluation under 14 CFR Part 77 depends on structure height, location, alteration and nearby aviation conditions. We provide accurate existing and proposed elevation data to the designated reviewer. The resulting notice or determination state is attached to the tenant ledger and does not replace local approval or tower-owner acceptance. If that notice path also triggers FCC registration, the antenna structure registration ASR filing process is a separate owner duty from the tenant delta.
Lease, zoning, access and owner-application records remain separate from structural analysis. The ledger records current status and exact attachment without treating a reviewer comment as an engineering defect. This page does not advise on property rights. It makes the handoff visible so technical drawings do not imply legal authority they cannot provide.
Tenant Delta Release Depends on Shared Interfaces
For tower owners: Release begins with one packet: the approved tenant schedule, affected structural references, mount or modification details, line-route overlay, compound notes and every open condition. The tower owner controls access and site release. A field redline with structural consequence returns to the responsible professional, while an RF substitution returns to the carrier and only the ledger rows touched by that change reopen.
For carrier teams: Closeout compares the installed model, quantity, centerline, mount position and shared-interface use with the released delta. Photographs and survey records follow owner requirements and carry the same stable item IDs as the drawings. An expected photo list is not acceptance evidence when the image cannot establish which antenna, route or mount position was installed.
The handback index names each delta ID, controlling drawing, analysis reference, approval attachment, installed evidence and final disposition. It also lists superseded tenant schedules. That small detail matters on the next application because an old equipment list should not drift back into the owner baseline simply because it remains in a familiar folder.
We keep tenant engineering in-house and, for a package that includes construction, we deliver the work full turnkey through our managed subcontract crews under our QA/QC and safety oversight. The tower owner still controls access, the carrier retains RF authority and responsible professionals and agencies keep their own acceptance roles. Our accountability model and vendor qualification process describe those boundaries.
A useful intake for co-location review is the owner baseline reference plus the frozen tenant schedule, not a request to make the site generally current. Technical corrections to this protocol may be sent to info@draftech.com. The first review should expose the exact delta rows that still need evidence.
The go decision is narrow on purpose. Release only when every load-bearing or shared-asset delta has a verified basis, the correct decision owner has cleared it and the schedule, analysis and drawings describe the same proposed state. Otherwise hold the affected item or commission the broader package that the evidence shows is actually needed.
