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 payment clock, the one that already runs net 30 to net 60 in this industry, has not started. The work is done. The money is not moving.

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 one-page 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 weeks disappear.

The Checklist

Six groups. If any item 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. Proof of work

• The as-built: the map marked with what was actually placed, with codes and quantities on it, and revisions dated
• Footage and unit counts per code (LF for cable and conduit, EA for drops, splices, locates, pedestals) that total to the as-built
• Photos: before, during, and after. Pit or trench before backfill, splice case open and closed, pedestal or handhole, restoration. Time and GPS stamped where the ISP asks for it
• Test results where the spec requires them: OTDR traces, light levels, in both directions if the ISP's spec says both

3. 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

4. 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

5. Sign-off

• Crew lead completion, with the date the work actually finished
• ISP, prime, or customer acceptance where the contract calls for it

6. The invoice itself

• 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

Why the Package Is Late, and It Is Not the Crew

"We dug the footage. We just cannot prove we dug it." Every fiber owner has said some version of that sentence.

The crew did the work and captured most 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 to the next job.

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. If a quantity changes, the whole thing gets done again. The as-built is where most closeout packages lose their days, because it is the document that turns field proof into billable quantities, and it is the one still being 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 in three weeks.

Build It While the Job Runs, Not After

The shops that invoice the same week the work finishes are not assembling a better package in the office. They stopped assembling it in the office at all.

The crew captures the codes, the quantities, the photos, and the ticket numbers once, in the field, against the job record. The map they mark is the same map the office bills from, so the as-built totals and the invoice lines are the same numbers by definition. The office reviews the package. It does not rebuild it.

Three things change when it works that way. The invoice goes out the day the work is complete, which means net 60 starts this week instead of three weeks from now. Nothing that was built goes unbilled, because nothing is waiting on a photo somebody forgot to send. And when a damage claim shows up months later, the proof is where it was captured, not in a chat thread nobody can find.

You are already waiting 30 to 60 days for the ISP to pay. The question is whether you add another two or three weeks in front of that, building a package the crew already had in their hands on Tuesday.

The Printable Checklist

One page. Print it, put it in the truck, and run the next closeout against it.

Download the checklist (PDF)

No form, no email required. If it saves your PM a Wednesday, that is the point.