The Fiber Closeout Package Checklist: What the ISP Expects Before It Pays
The crew finished the run on Tuesday. It is Friday, and the office is still building the closeout package.
The foreman has forty photos on his phone. The as-built is a printed map with three colors of highlighter on it. The footage is in a text thread with the project manager. The 811 ticket number is on a clipboard in the truck. The ISP's portal will not take the invoice until all of it is in one place, in the order the ISP wants it.
So the invoice has not gone out. The work is done. The money is not moving.
A fiber closeout package is the proof an ISP or prime needs before it accepts an invoice: the as-built with codes and quantities, photos, test and splice records, locate tickets, variances, and sign-off. If the invoice lines do not tie to the package, the invoice waits.
This is the checklist for what goes in that package, why it slows your billing, and how the shops that bill the same week build it differently. There is a printable version at the end.
What a Closeout Package Is, in ISP Work
A closeout package is the proof bundle that turns finished fiber work into an accepted invoice. Every ISP and every prime asks for a slightly different version of it. Some want it in a portal, some want a PDF per ticket, some still take a folder of photos by email. The shape underneath is the same: identify the job, prove the work, show you followed the rules, explain anything that changed, and get it signed.
If your invoice lines do not match what the package proves, the invoice comes back. That round trip is where the time goes.
The Checklist
Eight groups. Requirements vary by ISP and prime, so check each item against your contract. If an item the ISP requires is missing, expect the package to bounce.
1. Job Identity
- Work order, ticket, or purchase order number, exactly as the ISP issued it.
- Job address, segment or route IDs, and the ISP project name.
- The authorized scope: the codes and quantities on the RFP or work order, so the package can be checked against them.
2. As-Built and Quantities
- As-built in the format the ISP specifies (PDF redline, CAD, KMZ, or GIS shapefile or geodatabase).
- Redlines show deviations from design, with stationing, GPS points, and sheet numbers where required.
- Structures identified where the ISP requires: poles (utility pole tag), handholes, vaults, pedestals, splice closures.
- Cable type and fiber count per segment; reel numbers if the ISP tracks them.
- Footage and unit counts per code (LF, EA) that total to the as-built.
3. Photos
- Before, during, and after; splice case open and closed; pedestal or handhole; restoration; time and GPS stamps where the ISP asks.
- Underground: depth, tracer wire, and warning tape before backfill.
- Aerial: attachment on each utility-owned pole where the ISP asks.
- Road crossings and bore entry and exit where required.
- Photos named or indexed to the job, segment, or address, not a loose folder.
4. Tests and Splice Records
- Splice report: closure location, splice count, and tube and fiber assignments, where the ISP requires one.
- OTDR traces in the native file format (.sor) plus PDF, where the ISP asks, named to the strand or span IDs on the as-built.
- Insertion-loss results (light source and power meter), or light-level readings where the ISP asks, with the pass/fail limits from the ISP's spec.
- Both directions if the spec says both.
5. Compliance
- 811 locate ticket numbers and locate mark photos for any underground work.
- Permits and traffic control records where the route needed them.
- Any safety or tailboard record the ISP requires with the package.
For more on locate and bore records, see dig documentation and damage defense and pre-bore documentation for boring crews.
6. Variances
- Over or under quantities against the authorized scope, with the reason.
- Change orders, approved and dated.
- Damage, utility hits, or restoration notes, with photos and who was notified.
- Design change or route change form filed for any deviation, where the owner requires one.
7. Sign-Off
- Crew lead completion, with the date the work actually finished.
- ISP, prime, or customer acceptance where the contract calls for it.
- Inspector or QC acceptance recorded, where the ISP runs a QC review.
8. The Invoice
- One line per code, quantities matching the as-built totals, rates matching the contract.
- One invoice per work order or ticket, if that is how the ISP pays.
- The package attached or referenced the way the portal expects.
- Files named and indexed the way the ISP or portal expects.
- Lien waiver, where the ISP or prime requires one.
For the invoice build itself, see telecom contractor billing.
The test that matters: can somebody who was not on the job open the package and tie every invoice line to a code, a quantity, and a photo without asking the crew a question? If the answer is no, the ISP will ask the question for them, and the invoice waits.
Drop Work vs Construction: What Changes
Drops: one package per address. Address, drop length and type, photos, and a light-level reading or ONT details where the ISP requires.
Aerial and underground construction: per segment or submittal. Redlines, structures, splice records, OTDR by span.
For the drop side, see drop bury work.
If the Job Is BEAD-Funded
If the job is BEAD-funded, the state program can set its own closeout requirements, such as GIS as-builts in a set format and coordinate system, location IDs on every item, service verification, and native test files. Requirements vary by state and can change. The state's current guidance, the ISP's subgrant agreement, and your subcontract govern. Ask the ISP for the state checklist before the job starts. Using this checklist does not make a package BEAD-compliant.
For the paperwork around the subcontract, see BEAD subcontract paperwork and BEAD by state.
Why the Package Is Late, and It Is Not the Crew
"We dug the footage. We just cannot prove we dug it." Fiber owners know that sentence.
The crew did the work and captured much of the proof. The problem is where the proof went. Photos on one phone, footage in a message to the PM, the as-built on paper in the truck, the ticket number on a clipboard, the change order in an email. Five places, five people, and the office has to pull it back into one package after the crew has moved on.
Then the map. Somebody prints it, highlights what was placed, tallies the codes by hand, scans it, and re-keys the totals into the invoice. The as-built is where a package tends to lose its days, because it is the document that turns field proof into billable quantities, and it is the one still done by hand.
Every crew also documents a little differently. One foreman shoots every pit, another shoots the finished restoration and nothing else. Reconciling that across crews is the PM's Wednesday, every Wednesday.
And when the package is incomplete, the ISP does not reject it loudly. It just holds the invoice. You find out when the Wednesday AR report has a line that has not moved. To see what those held days cost, run the cash flow calculator. More on why telecom contractors bill late.
Run Every Package by Status
Give every work order a package status the office can see at a glance: field complete, submitted, kicked back, accepted, invoiced. Log each kickback with its reason, and fix the top two reasons at the crew level.
Name files to the job, segment, or strand IDs on the as-built.
Build It While the Job Runs, Not After
The crew marks the codes and quantities on the map once, in the field, and gathers the photos and ticket numbers as the work happens. In TCS, the crew's marks become the tally, priced from your price book, ready for the invoice.
The office reviews the tally. It does not rebuild the map.
TCS Map Annotator lets the crew place billing codes and quantities on the as-built and gives the office the matching tally.
Two things change when it works that way. The invoice does not wait on the office retyping the map. And when a question comes up months later, the marked map and the submitted tally are still there, not in a chat thread nobody can find.
You are already waiting on the ISP's terms. The question is whether you add your own delay in front of them, building a package the crew already had in hand on Tuesday.
For how the marked map becomes a tally that's ready for the invoice, see map to invoice.
The Printable Checklist
Print it, put it in the truck, and run the next closeout against it.
Download the fiber closeout package checklist (PDF)
No form, no email required. If it saves your PM a Wednesday, that is the point.
Questions Contractors Ask
What is a closeout package in fiber construction?
The bundle of proof an ISP or prime contractor expects before it accepts an invoice for completed fiber work: the work order reference, the as-built with codes and quantities, photos, test results where required, locate tickets for underground work, any variances, and sign-off. The invoice lines have to match what the package proves.
Why does the closeout package delay the invoice?
Because it usually gets assembled in the office after the crew is gone, from photos on phones, footage in text messages, and a printed map marked with highlighter. Every item that has to be hunted down or re-keyed adds time before the invoice can be submitted. Payment terms usually count from the invoice, not from the day the work was done. Check your contract for when your clock starts.
Who should assemble the closeout package?
Nobody should have to assemble it after the fact. When crews mark codes and quantities on the map in the field and gather the photos and ticket numbers as the work happens, the office reviews the package instead of rebuilding it.
Why can't I invoice fiber footage until the as-builts are approved?
Because the ISP or prime usually pays against proof. If your contract ties billing to an approved as-built, the footage on the invoice has to match that as-built before the invoice is accepted. Check your contract for what has to be approved first, and submit the as-built with the rest of the package so review starts sooner.
When can I invoice footage if the as-builts aren't accepted yet?
It depends on your contract. Some contracts allow billing on submitted quantities, and others wait for as-built acceptance. Ask the ISP or prime how it handles partial acceptance and get the answer in writing. This is general information, not legal advice. Read your contract and talk to your attorney.
Is OTDR testing required on every fiber? Can insertion loss alone be enough?
It depends on the ISP's test spec. An insertion-loss test with a light source and power meter measures total loss end to end. An OTDR trace shows where along the fiber the loss happens, such as at splices and connectors, so it can locate a problem. Some specs ask for both, some for one, and some drop work is verified with a light-level reading. Follow the ISP's spec and keep results in the format it asks for.
What file formats should be in a fiber closeout package?
Whatever the ISP or prime specifies. Common requests are the as-built as a PDF redline, CAD, KMZ, or GIS shapefile or geodatabase; OTDR traces in the native .sor format plus PDF; splice and test reports; and photos named or indexed to the job, segment, or address. Name files to the IDs on the as-built so a reviewer can find them.
Can CAD or paper redlines satisfy a GIS as-built requirement?
Only if the ISP or program accepts them. When a contract or program asks for a GIS deliverable, it usually sets the format, the coordinate system, and the attribute fields, and a PDF or CAD redline may need to be converted. Ask for the spec before the job starts, not at closeout.
When should as-built documentation start?
Before the first footage goes in. Get the ISP's as-built format and file naming before the job starts, then mark codes and quantities on the map as the work happens, not on Friday from memory. The later the as-built starts, the more of it gets rebuilt from phones and text threads.
How do I know a fiber closeout package is complete?
Use the test that matters: can someone who was not on the job tie every invoice line to a code, a quantity, and a photo without asking the crew a question? If not, the ISP will ask, and the invoice waits. Then check the package against the ISP's own closeout requirements, item by item.
What is the difference between a redline and an as-built?
A redline is the field mark-up. The crew marks the design print to show what changed in the ground. The as-built is the final record the ISP accepts, in the format it asks for, such as PDF, CAD, KMZ or GIS. The redline feeds the as-built. Ask who turns one into the other before the job starts.
Who prepares the fiber as-built?
Your contract decides. Often the crew marks the redlines and GPS points. Then an engineer or drafter turns them into the final CAD or GIS file. Some contracts put the whole as-built on the contractor. Before the first footage goes in, find out who marks it, who draws the final file and who signs off.
What should an underground as-built show?
It depends on the ISP's spec. Specs often ask for the route as built, with GPS points or ties to fixed features. The depth of the conduit or cable, and the bore logs. Each handhole, vault and pedestal. Cable type and fiber count for each segment. Footage and unit counts for each code. Capture it while the trench is open.
Where does your closeout package lose its days?
Would it be a bad idea to spend 30 minutes tracing one package from the field to an accepted invoice? Free 30-minute Fit Call. We will tell you whether an Operations Audit is a fit.
Book a Fit CallGet this coverage first in Google