A tower closeout package gets treated as an afterthought on a lot of jobs — something assembled at the end because the contract requires it, rather than something built as the work happens. That order of operations is backwards, and it shows in the quality of the package. A closeout document assembled from memory a week after the crew left site is thinner and less useful than one built photo-by-photo and record-by-record as the work was performed.

Here's what belongs in a closeout package, organized by the scope it covers, and why each piece exists — not as a compliance checkbox, but as something a GC, tower owner or carrier actually uses.

Photo documentation — tied to specific work, not generic site photos

The baseline of any closeout package is photos, but there's a meaningful difference between "photos of the site" and photos that document specific completed work. Useful closeout photography is tied to what was actually done: a foundation's rebar and anchor bolt cage before the pour covers it, a torqued connection with the torque wrench reading visible, a completed sector install from multiple angles, a removed piece of equipment and the resulting site condition.

This matters most on work that gets physically covered up or removed once it's complete. Concrete covers the rebar cage. A removed antenna leaves no trace of what was there before. If the only record is a general site photo, there's no way to verify the specific work afterward — which becomes a real problem if a foundation needs to be evaluated years later, or a dispute comes up about what was or wasn't installed to spec.

As-built records — what was actually installed versus what was planned

Drawings and data sheets describe intent. As-builts describe what's actually in the ground or on the structure, and the two aren't always identical — field conditions, approved field changes, and installation reality can diverge from the original plan in small ways that matter later.

Depending on the scope, as-built records typically include:

  • Antenna position records — azimuth, downtilt and mounting height as installed, checked against the RF data sheet. This is what a carrier's RF engineering team actually needs to confirm the sector performs as designed.
  • Torque logs — structural and mount connection torque values recorded at the time of installation, not estimated afterward. This is the record that proves a connection was made to spec, since you can't visually verify torque after the fact.
  • Foundation and anchor records — anchor bolt pattern verification against the tower manufacturer's template, concrete mix and pour date, cure schedule.
  • Grounding system records — continuity and ground resistance test results, confirming the system was verified, not just installed.

Test results — sweep, PIM and electrical verification

For antenna and equipment work, line sweep and PIM (passive intermodulation) test results belong in the closeout package for every sector touched. These results are what confirm a sector is actually clean before it goes live — a visual inspection can't catch a PIM issue, but a test will, and the result needs to be documented, not just verbally reported as "it tested fine."

For grounding and electrical work, resistance and continuity test results serve the same purpose: proof of verification, not just installation.

Sign-off and scope confirmation

A completed closeout package should include a clear statement of the scope that was completed, matched against what was originally contracted — not just a stack of photos and records with no summary tying them together. This is what a GC actually needs to hand up their own chain to a tower owner or carrier: confirmation that the specific scope of work is done, supported by the documentation behind it.

Why this matters more on tower work than most trades

A lot of construction trades can be re-inspected relatively easily if documentation is thin — pull a panel, open a wall, look at a connection. Tower work doesn't offer that luxury as often. A foundation's anchor cage is buried in concrete. A removed piece of equipment can't be un-removed to check what was actually there. A connection torqued eighteen months ago can't be re-verified without redoing the work.

That's the actual argument for insisting on thorough closeout documentation, independent of any contract requirement: it's often the only record that will ever exist of specific work that physically can't be re-checked later. A GC holding a thin closeout package on tower work is holding more risk than they realize, because the gap often doesn't show up until there's a problem — a foundation inspection years later, a dispute over what was installed, an insurance claim that needs proof of what condition the site was in.

Who actually uses each piece of this documentation later

It's worth being specific about who downstream actually opens a closeout package, because it explains why "we'll get you photos" isn't really the same commitment as a structured package:

  • Carrier RF engineering uses antenna position as-builts to confirm a sector performs as designed and to plan future modifications without resurveying the site from scratch.
  • Tower owners and landlords use foundation, anchor and structural records when evaluating a site for additional colocation load, or when a future subcontractor needs to know what's already in the ground before a new scope.
  • Insurance and risk management rely on dated, specific documentation if a claim ever needs to establish site condition at a point in time — a generic site photo with no date or context is far weaker evidence than a tied, timestamped closeout record.
  • The GC's own closeout obligation up the chain to the carrier or tower owner is usually only as good as the documentation handed up from the subcontractor who actually did the work — a GC can't produce records a sub never generated.

Common gaps GCs find during an audit

A few patterns show up often enough when a closeout package gets scrutinized after the fact that they're worth flagging in advance, before they become a problem on your project:

  • Photos exist but aren't tied to specific work items — a folder of general site photos with no indication of what each one is documenting is close to useless if a specific question comes up later (was the anchor bolt pattern actually verified against the template, or just photographed from a distance).
  • Torque logs are summarized rather than itemized — "all connections torqued to spec" is not the same record as a logged value per connection, and only the latter can actually be checked against a spec after the fact.
  • Test results are referenced but not included — a closeout narrative that says a sector "passed sweep testing" without the actual test result attached isn't verifiable.
  • No clear scope boundary — a package that doesn't state what was and wasn't included in the completed scope leaves room for disagreement later about what the subcontractor was actually responsible for.

None of these gaps are necessarily intentional — they're usually what happens when documentation gets assembled from memory after the crew has already moved to the next job, rather than captured in real time as the work happens.

What to ask for before the job starts, not after

If you're subcontracting tower work, the closeout package format should be confirmed before the scope is awarded, not requested after the crew demobilizes. Ask specifically:

  1. What photo documentation is standard for this scope, and is it tied to specific work items?
  2. What as-built records will be provided (antenna position, torque logs, foundation/anchor records, grounding tests — whichever apply)?
  3. What test results are included for antenna, equipment or electrical work?
  4. Is there a written scope confirmation/sign-off, or just a stack of unorganized files?

A sub who can answer this specifically and consistently — the same answer whether you ask the project lead or the office — is a sub who runs this process as standard practice, not as a special request. If you're also evaluating the subcontractor more broadly before award, see our checklist for vetting a tower subcontractor.

Want to see our standard closeout format before you award a scope? Request crew availability and we'll walk you through exactly what you get back on your project type.