Requirements vary by owner, carrier, prime contractor, and project. This guide describes a practical closeout structure without presenting one customer's requirements as a universal acceptance standard.
1. Requirements matrix and transmittal
Start with the customer's closeout requirements: which files are expected, the required format, naming rules, reviewer, revision process, and open items. A closeout matrix can track required, received, reviewed, exception, and delivered so the package status is visible.
2. As-built redlines
Redlines should reflect construction changes supported by authorized source records: new or relocated assets, sleeves, repairs, assist pits, route changes, splice locations, and other required revisions. Unclear items should be flagged for follow-up instead of being completed by assumption.
3. Final or reference KMZ/KML
When a project requires KMZ/KML, the final structure should use consistent names, folders, attributes, and descriptions. Temporary, duplicate, superseded, or internal working layers can be removed when the closeout specification calls for it. GDRS uses Final Closeout KMZ/KML or Client-Defined Closeout KMZ/KML publicly because the term “blackout KMZ” can mean different things to different customers.
4. Asset index
An asset index can connect handholes, splices, reels, repairs, sleeves, markers, or other scoped features with the fields the project actually needs. The value comes from consistency and source traceability, not from adding fields the available record cannot support.
5. STA, sheet, and source references
Where an authorized stationing or chainage framework exists, features can be related to STA, the applicable as-built sheet, and the source record. That connection helps field, closeout, GIS, and operations teams move between the map and the project documentation. A record-derived STA reference is not a substitute for survey control.
6. Photos and field evidence
Photos can be indexed by asset, location, station, date, work item, or closeout requirement. Image metadata can support documentation, but it does not by itself prove survey-grade location or owner acceptance.
7. Splicer and test documentation
Fiber projects may require test results, reports, screenshots, SOR/OLTS files, templates, splice matrices, or related evidence. Under GDRS's standard documentation service, qualified testing personnel perform the testing and GDRS organizes customer-supplied results into the required documentation structure. Learn about Fiber Splicer Closeout Documentation.
8. QA/QC and exception log
A good closeout should make unresolved information visible. Track missing sources, identifier mismatches, unreadable files, duplicates, conflicts, unsupported records, and items that require direction from the customer or responsible technical party.
9. Revision history and final handoff
The package should show which revision was transmitted, when it was sent, what changed, and which records belong to that release. Controlled revisions reduce the risk that field, project management, closeout, and the customer are working from different versions.
What should the package not promise?
Document organization does not turn a source record into survey control, a utility locate, SUE, engineering certification, or owner acceptance. Technical and contractual authority remains with the parties assigned those responsibilities.
A practical way to start
Before transferring hundreds of files, share the closeout checklist, required output formats, and a representative non-confidential sample. That makes it easier to define scope, assumptions, quantities, exclusions, revision terms, schedule, and price.