Process & Documentation

# What Project Managers Should Expect from a Closeout Package

TLDR

A closeout package proves the work: signed **as-built drawings**, **OTDR traces** and splice loss records, permit and restoration signoffs, plus photo evidence tied to **stationing**.

Last updated October 20, 202613 min read

A closeout package is the evidence file that lets an owner accept, maintain, and locate the plant you built. Expect signed as-built drawings with measured depths and offsets, OTDR traces and splice loss records for every fiber, conduit and structure records, permit signoffs, restoration photos, and material documentation, delivered in one indexed set.

## What is a closeout package supposed to prove?

A closeout package answers three questions the owner will keep asking for the life of the plant: where is it, what is it made of, and does it perform. Every document in the file should map to one of those three. Anything that maps to none of them is padding.

Where is it drives locating, future design, and damage prevention. What is it made of drives spares, warranty claims, and maintenance planning. Does it perform drives acceptance, billing, and the baseline you will compare against when a span degrades three years from now.

That framing also tells you when a package is deficient. A folder of photos with no stationing proves nothing about location. A set of drawings with no test data proves nothing about performance. The package is only useful when the three legs stand together.

## What documents belong in a fiber closeout package?

Scope changes the volume, not the categories. A route with underground conduit, splice points, and a road crossing produces the same document families whether it runs a mile or fifteen. The table below is a working checklist, along with the failure mode that shows up most often in each row.

| Document | What it proves | Common failure |
| --- | --- | --- |
| Signed as-built drawings | Final horizontal and vertical position of everything installed | Field redlines never reconciled back to the design file |
| Bore logs | Pitch, depth, and offset recorded rod by rod at each crossing | Only entry and exit points recorded, nothing between |
| Splice records and OTDR traces | Continuity, splice loss, and end to end performance per fiber | Traces shot from one direction only |
| Conduit proofing records | Each duct is clear, round, and usable for a future pull | Proofing claimed but no mandrel size or result listed |
| Structure schedule | Handhole and vault type, load rating, lid marking, location | No load rating, so no one knows if the lid suits the setting |
| Permit and inspection signoffs | The agency accepted the work and released the permit | Package closed before final inspection was scheduled |
| Restoration documentation | Surface returned to the standard written in the permit | Existing condition photos never taken before mobilization |
| Material submittals | The cable, conduit, and hardware actually installed | Submittal shows an approved product, the field shows a substitute |

## How should as-built drawings be delivered?

Ask for the as-built in the same coordinate system and file format as the design, plus a portable copy. If the design arrived as a georeferenced CAD or GIS file with attributes, the as-built should come back the same way. A scanned PDF of a marked up plan sheet is raw material, not a deliverable.

Position should be recorded as measured values, not as design values with a note saying the work matched the plan. Depth of cover at each crossing, offset from the reference line, station of every splice point and structure, and measured separation from foreign utilities are the fields that get used later by someone you will never meet.

Deviations matter more than conformance. If a bore shifted eight feet to clear a storm line, that shift is the single most valuable fact in the drawing set. It belongs in the file as a dimensioned change, not as a cloud with the words field adjusted inside it.

## What test and splice records should you require?

For a fusion spliced route, expect a splice loss record for every fiber at every splice point and OTDR traces run in both directions on each fiber. A one direction reading can make a splice look better or worse than it is, so the averaged pair is the number that belongs on the record.

Fusion splices in matched single mode fiber land low, often close enough to the instrument's own uncertainty that a one direction reading is not a meaningful acceptance test. Keep the acceptance conversation on the bidirectional average against the number written in the specification, not on whichever single direction trace happened to read lowest.

The native trace files belong in the package, not just a summary table. Native files let the owner reopen the measurement with different markers when a fault appears later, and they establish the baseline that a future OTDR shot gets compared against. A PDF summary alone throws that away.

- Native OTDR files for both test directions, with a summary table a reviewer can scan.
- Splice loss per fiber at each splice point, identified by buffer tube and fiber color.
- End to end insertion loss with a light source and power meter where the specification calls for it.
- Launch and receive conditions noted, since events near a connector can otherwise be masked.
- Fiber and buffer tube assignment matching the splice diagram exactly.

## What proves the underground pathway is usable?

Conduit that was installed correctly and conduit that can be proved to have been installed correctly are two different deliverables. The package should include proofing or mandrel results for each duct, documentation that pull tape or rope was left in place, and duct assignment for every occupied and spare path.

Tracer wire deserves its own line item. A nonmetallic duct with no continuous, terminated, testable tracer wire is a locate problem waiting to become a damage claim, and the crew that finds out is the one that hits it. Record where the wire terminates, how it is accessed, and the result of the continuity test.

Structure records should list type, load rating, lid marking, and grade relationship. A box set proud of a sidewalk becomes a trip hazard ticket, and a lid rated for a green space does not belong in a driveway. Both problems are cheap to catch in a schedule and expensive to catch in a claim.

## How are restoration and permit closeout documented?

Restoration is closed by the agency, not by the contractor's opinion of the surface. The package should carry the permit number, the conditions attached to it, the final inspection result, and any bond or maintenance period that survives inspection and stays open afterward.

Photo evidence should be paired: a before image and an after image from the same position, with the location tied to a station or coordinate rather than to a filename and a timestamp. Unpaired photos are close to useless when a property owner reports damage that was there before the crew arrived.

Where restoration includes sod, asphalt, concrete, or irrigation repair, the record should name the material and method used. That is exactly what an agency compares against the permit condition when it decides whether to release the bond.

## When should the package be assembled?

Continuously, from the first production day. The most common cause of a weak closeout package is that data collection started after demobilization, when the only remaining sources are memory and photos that were taken for some other reason.

Daily production reporting is what makes continuous assembly possible. When each day's report already carries stationing, footage, depth notes, structures set, and photos, closeout becomes an editing exercise instead of a reconstruction project.

A middle checkpoint helps. Deliver a draft as-built and preliminary test data when the route is mechanically complete but before final restoration. Errors found at that point can still be corrected with crews and equipment on the ground rather than through a remobilization.

## How should a closeout package be organized?

By document family, with an index on top. The index lists every item in the package, its file name, the date it was produced and who prepared it. A reviewer should be able to confirm the package is complete from the index alone, before opening a single drawing.

File names should carry the route segment and station range, not just a date or a camera number. A trace file named for its fiber, splice point and test direction can be found in seconds. A file left with the instrument's default numbering has to be opened to be identified, and on a long route that adds up to hours of searching.

Deliver it as one set. Packages that arrive in pieces over several weeks, by email, file share and thumb drive, almost always have gaps, and nobody can tell which version of a drawing is final. Use one transmittal, one index and one version, and issue later corrections as dated revisions.

## What happens when a package comes back with gaps?

Treat gaps as a punch list, not a conversation. The reviewer lists each missing or deficient item, why it fails, and what would satisfy it. The contractor answers item by item and resubmits only the affected documents as a dated revision, not a whole new package.

Some gaps can be fixed in the office: a missing signature, a file in the wrong format, an index that does not match the contents. Others need the field, such as a missing depth at a crossing that has since been backfilled, or a structure with no recorded location. Those are the expensive ones, and they are the reason a draft review while crews are still mobilized pays for itself.

Keep the deficiency log with the final package. It shows what was questioned and how each item was resolved. That matters when an auditor or a future project team asks why a record looks the way it does.

## What should a project manager specify before award?

Write the deliverable into the contract with the same precision you use for the construction. Name the file formats, the coordinate system and vertical reference, the test method, the acceptance threshold, and the calendar days after substantial completion when the package is due.

Then tie a meaningful portion of retainage to the documentation rather than to the last splice. A closeout requirement with no commercial consequence is a request, and requests lose to the next mobilization every time.

- Deliverable formats: CAD or GIS with attributes, native OTDR traces, and a PDF set for field use.
- Coordinate system and vertical reference stated explicitly, not assumed.
- Test method and acceptance threshold, including bidirectional averaging.
- Due date measured from substantial completion, not from the final invoice.
- One named person responsible for the submission and for answering questions about it.

## Key takeaways

- Every document in a closeout package should help answer one of three questions: where the plant is, what it is made of, and whether it performs.
- Native OTDR trace files belong in the package because they let the owner reanalyze a fiber years later, which a PDF summary cannot do.
- A closeout package tied to a meaningful share of retainage arrives sooner and more complete than one tied to nothing.
- Reviewing a draft package while crews are still mobilized is the cheapest time to fix gaps that need field data.

## Key terms

**Closeout package**: The indexed set of records a contractor delivers at the end of a project so the owner can accept, locate and maintain the work. It usually includes as-built drawings, test results, permit closeouts, restoration records, photos and material documentation.

**Substantial completion**: The point at which the work is complete enough for the owner to use it as intended, even if minor items remain. Contracts often measure the closeout due date and the release of retainage from this milestone rather than from the final invoice.

**Native trace file**: The original data file saved by an OTDR, commonly in the standard .sor format, holding the full measurement rather than a picture of it. With the native file, an owner can reopen the trace, move markers and compare it against a later test.

**Retainage**: A portion of each payment the owner holds back until the contract is complete. Tying part of the retainage to an acceptable closeout package gives the documentation the same commercial weight as the construction work itself.

*Closeout package index: format and sign-off by document family*

| Document family | Delivered format | Prepared or signed by |
| --- | --- | --- |
| As-built drawings | Georeferenced CAD or GIS with attributes, plus PDF | Contractor, with a surveyor's seal where the contract requires one |
| Test results | Native OTDR files plus summary tables | The splicing technician who ran the tests |
| Bore logs | Rod by rod log tied to stationing | Drill operator and locator for each bore |
| Permit closeouts | Agency letters or inspection records | The issuing agency |
| Restoration records | Paired photos tied to station or coordinates | Contractor, confirmed by agency inspection |
| Material documentation | Submittals and delivery records | Contractor, checked against the approved submittal |

*What a closeout package contains*

## What this means for your project

The closeout package is the part of the project you keep. Crews leave and memories fade, but the package is what your locate team, your maintenance contractor and your next designer will rely on. A weak package pushes cost onto every future project in the corridor, usually in places where it is hard to trace back to the job that caused it.

Reduce that risk before award. Write the formats, coordinate system, test method, acceptance thresholds, due date and the retainage tied to the package into the contract. Then ask for a draft at mechanical completion. Gaps found while crews are still on the route cost a phone call. Gaps found after demobilization cost a return trip and schedule time.

## Related reading

- [As-built documentation servicesField capture and drawing preparation for the core closeout record.](https://strillacommunications.com/services/supporting-services/as-built-documentation)
- [Closeout and documentation standardsThe standards a complete closeout should meet, in one reference.](https://strillacommunications.com/resources/closeout-and-documentation-standards)
- [Closeout checklistA working checklist for confirming every record is in the package.](https://strillacommunications.com/resources/checklists/closeout-checklist)
- [Post-construction and closeoutHow restoration, inspection and package delivery are sequenced.](https://strillacommunications.com/about/our-process/post-construction-and-closeout)
- [Why as-built records matterWhat a real as-built contains and who depends on it later.](https://strillacommunications.com/blog/the-importance-of-as-built-documentation)
- [Closeout examplesWhat finished closeout deliverables look like in practice.](https://strillacommunications.com/projects/closeout-examples)

## Frequently Asked Questions

**How long after construction should a closeout package be delivered?**: Tie the due date to substantial completion and state it in the contract. The specific number of days matters less than the anchor point you choose. Packages tied to the final invoice tend to arrive after crews have moved to another project, at which point field questions can no longer be answered by the people who actually did the work.

**What file formats should as-built drawings be delivered in?**: Request the working format plus a portable one. A georeferenced CAD or GIS file with an attribute table lets the owner load the route into their own system without redrawing anything. A PDF set is what field technicians will carry. Delivering only the PDF forces someone to re-digitize the route later, which adds errors nobody can trace back to a source.

**Are OTDR traces enough on their own for acceptance?**: Often not. An OTDR characterizes the span and locates events, but many specifications also require an end to end optical loss measurement with a light source and power meter, because that measures total insertion loss including connectors rather than inferring it from backscatter. Read the specification, require both when both are named, and keep the native trace files either way.

**Who is responsible for permit closeout, the contractor or the owner?**: It depends on whose name is on the permit, and that should be settled before mobilization rather than after. When the contractor pulls the permit, the contractor carries the inspection and the bond release. When the owner holds it, the contractor still has to supply inspection dates, restoration records, and any agency required documentation on time.

**Should daily reports be part of the closeout package?**: Yes, as a supporting record. Daily reports show when each section was built, what conditions the crew found, which locate tickets were in force and what changed in the field. Few people read them cover to cover, but they answer questions the drawings cannot, especially about timing and site conditions, and they cost nothing extra to include when they were produced every day of the job.

**What if the owner's GIS uses a different coordinate system than the design?**: Settle it before construction. The contract should name the coordinate system and vertical reference the as-built will use, and field data should be collected in that system or one that converts cleanly to it. Converting after the fact is possible, but it adds a step where errors creep in, and a mismatched vertical reference can make every recorded depth look wrong.

**Can closeout be delivered in phases on a long route?**: Yes, and on long routes it often should be. A complete package for each finished segment lets the owner accept and activate sections as they are done. It also surfaces documentation problems early, while the same crew is still working nearby. Each phase package should use the same index and naming rules so the segments combine into one record at the end.

## Related services

- [As-Built DocumentationAccurate as-built records captured in the field during construction, not reconstructed afterward. Coordinates, depths, photos and reconciled footage.](https://strillacommunications.com/services/supporting-services/as-built-documentation)
- [Daily Production ReportingEnd of day reports covering production, next day plan, field conditions and blockers, so progress is visible without anyone having to chase it.](https://strillacommunications.com/services/supporting-services/daily-production-reporting)
- [Conduit VerificationConduit verification in Central Florida: mandrel proofing, rodding, camera inspection, obstruction location, and a pass record before fiber goes in.](https://strillacommunications.com/services/conduit-installation/conduit-verification)
- [Fiber Splicing & InstallationFusion splicing, fiber placement, termination, and enclosure installation with bidirectional OTDR support and a recorded loss value for every fiber.](https://strillacommunications.com/services/fiber-splicing-installation)
- [Outside Plant ConstructionTurnkey OSP construction that carries a fiber build from permitting and boring through aerial, splicing, restoration, and a documented closeout.](https://strillacommunications.com/services/outside-plant-construction)

---
Source: https://strillacommunications.com/blog/what-project-managers-should-expect-from-a-closeout-package