// Wireless tower contractors · Closeout packages
Site closeout packages built from the field records, line by line against the customer's list.
A tower job is not done until the customer's closeout checklist is answered. In a free AI proof of concept, AI sorts the records of 20 to 30 finished sites against the checklist each customer wrote and names every line with nothing behind it. Your reviewer, whoever knows your closeouts best, lays each draft beside the package your team actually sent.
- Finished sites
- 20 to 30
- Packages submitted
- None
- Systems touched
- None
// The one job
From a crew's folder to a package a project manager can submit
A closeout starts with what the crew turned in: photos off a phone, sweep files from the test set, redlines on a drawing set, torque and grounding records, and the lien waivers the office collected. Somewhere there is the customer's written list saying what the package must hold, and often what each photo must show. Someone in the office walks that list, renames files, chases what is missing and builds the package.
For the test, AI reads copies of a finished site's records and drafts the package index: each checklist line, the file that answers it, photos renamed to the wording on the list, test results carried over exactly as supplied, and a separate list of every item on the checklist with nothing behind it. It never decides a result passes and it submits nothing. Your project manager reviews the draft and submits every package.
the customer's list
// What makes it hard
The checklist belongs to the customer, and some lines can't be shot twice
A public buyer's list reads like a contract. Missouri's highway commission, specifying a 150-foot radio tower near Branson, names its final tower documentation: as-builts if anything changed, a certification that the tower is plumb, coax sweeps, a guide to the cable marking, a grounding resistance report, concrete cylinder results and construction photographs. Conway, Arkansas, in a 2015 addendum, wants at least four sets of as-builts before final acceptance, with the tower maker's engineering documents and the foundation concrete results folded in. Lincoln County, Montana, asked for three sets within fourteen working days plus a legible PDF, and tied final payment to its own inspection. The draft works from the list that came with that site and never carries one customer's line onto another's job.
Some photos only exist once. Missouri's photo list opens with the site grounding before backfilling and the foundation forms and rebar cages before concrete. Leon County, Texas, in a 2026 tower RFP addendum, won't let a trench be backfilled until the county has inspected the grounding, and wants installation photos of tower-mounted lights, control boxes, junction boxes and lightning rods. A shot of a finished antenna can be retaken on the next trip up. A shot of grounding under the backfill can't, so when one is missing the draft puts that line on the open list for someone to deal with.
A sweep only means something with its setup. Missouri asks for a return loss sweep before the final antenna connection is made and a distance-to-fault sweep on the finished installation with the antenna in place, and every result goes to the state for approval before final acceptance. Both sweeps are plotted with distance along the bottom, so to someone opening two files cold they look alike. The draft carries each file as supplied, with its line label, its date and whichever test condition the file states, and leaves every pass or fail to a person.
The engineer may only ever see your photos. Connecticut Siting Council files show why. In one, an engineering firm's desktop review of a mount change says it never visited the site and worked from the contractor's close-out photos. In another, inspectors reported that antennas and radios sat in a different mount position than the drawings showed and that the general contractor had redlined the change. The Council's conditions there called for documentation certified by a Professional Engineer within 45 days of finishing the installation. A redline that never reached the package leaves an engineer staring at a mismatch.
What your reviewer will watch. Conway wants ground resistance reported for the as-installed system with plan drawings showing where it was measured, so a number on a page answers only half the line. Torque and grounding records come through as the crew wrote them, and lien waivers show as present or missing against the checklist, with their legal effect left alone. Did each file land on the right line? Was each photo renamed to the list's wording rather than dropped in as any shot of that sector? Did any test value change on the way over? Is every open item on the open list? None of this is legal or engineering advice.
// What you send
Finished sites, as the crew left them
20 to 30 finished sites
Each closed job's field records as they came in: photos, test files, redlines, torque and grounding records, and the waivers the office collected. Include a site that came back for rework.
Each customer's checklist
The written closeout list that carrier, tower owner or public agency gave you for that job, in the version your team worked to.
The package you actually sent
The submitted package for each site, so your reviewer can compare it with the draft line by line.
NDA first, then copies
Sign the NDA, then send copies. Nobody logs in to your project system or a customer's portal. If a customer's files can't leave your office, we build look-alikes with your team.
// Before it starts
Agreed before any file leaves your office
Your owner settles each of these first.
- Your reviewer
- Named by the owner, often a senior project manager or closeout coordinator
- Success criteria
- Written down: which lines must land on the right file, and what counts as open
- Sites
- Your reviewer's pick, across at least two customers' checklists
- Who submits
- Your project manager, every time
- Test results
- Carried over as supplied, never judged
- Price
- A range for the live month, given up front
// How the test is judged
The package you submitted, beside each draft
| Across the same 20 to 30 sites | Your submitted package | Draft from the test |
|---|---|---|
| Checklist lines answered with the right file | Filled in on your sites | Filled in on your sites |
| Photos renamed to the list's wording | Filled in on your sites | Filled in on your sites |
| Sweep and test values carried over unchanged | Filled in on your sites | Filled in on your sites |
| Redlines and as-builts matched to the site | Filled in on your sites | Filled in on your sites |
| Torque and grounding records placed on their lines | Filled in on your sites | Filled in on your sites |
| Lien waivers present or marked missing | Filled in on your sites | Filled in on your sites |
| Every line with nothing behind it, listed | Filled in on your sites | Filled in on your sites |
// After a yes
About 30 days on sites closing now
If your reviewer says yes, the same job runs on sites closing over the next 30 days or so.
A person approves each item before it goes anywhere. Your project manager still reviews the draft and submits every package, by whatever route that customer uses.
Monthly support follows if you continue, and any further job is its own decision at its own price.
// Next, if you choose
What could follow the closeout index
- 01Next
Structural modification scopes
A report and its drawings laid out as a draft scope sheet, with their conflicts listed for your estimator.
- 02Then
Condition assessment write-ups
A climb's notes and photos drafted in the owner's report format, deficiencies by elevation.
- 03After that
Returned package comments
A customer's comments on a rejected package turned into a list of what the crew or the office has to fix.
// One hard limit
Your project manager submits every package.
The test never touches your project management system, a carrier portal or a live closeout. It never decides that a sweep passed, that a waiver is good or that a checklist line is truly satisfied, and it submits nothing. It never interprets a structural analysis or decides that a rigging plan is safe; your engineer of record owns every structural call. It reads copies and lists what it found and what is missing, and a person decides.
Priced per job. You get a range before the proof of concept and a fixed price before you sign.
Rob gives the range on the call, once he knows how many closeouts you send in a month and how many customer checklists you work to.
// Questions
Closeout questions
Can it tell us whether a sweep or a ground test passed?
What if a photo is missing or the crew named files badly?
Does the test run on our live closeouts?
Does this cover FCC or FAA paperwork?
Our carrier customers use their own portals for submission. Does that matter?

Rob Eason, founder
// Book a proof of concept call
Start with one finished site and the list it was closed against.
Half an hour with Rob about your crews, the checklists you work to and roughly how many closeouts go out each month. Keep the folders until the NDA is signed.
- Co-owned a 60-employee financial services firm and sold his share to his partner.
- Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
- 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
- 4.3/5 from 6 Google reviews of Massmarket AI.
- Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
- Takes every proof-of-concept call himself.
