Fiber drop closeout photos: what to shoot at every install so the package is accepted

Updated November 9, 2026

Short answer: shoot the same fixed set at every drop, in the same order, with the work order number, date, time and address readable on each image, and make sure the one detail the spec names (asset ID, conduit depth, restoration, meter reading, serial label) is sharp and fills the frame. There is no single national list. Requirements come from the ISP, the prime contractor, the grant program funding the build, or the city permit, and the public documents we read range from no photos to "GIS-stamped and dated" photos of the network's support infrastructure.

Packages rarely come back for a bad photo. They come back for a photo the reviewer cannot place: no address, no job number, no asset ID in frame, or a trench shot after backfill.

What do closeout photo requirements actually say?

We read public drop RFPs, utility standards, a city right-of-way policy and two state grant programs. Requirements differ by ISP and prime; get their list in writing.

Grant programs are the strictest. A draft scope of work posted by the Utah Broadband Center for BEAD-funded fiber says milestones are documented with photos that are "GIS-stamped and dated" (or by on-site inspection), carry a "visible, unalterable date and time stamp," and "clearly display or reference the unique ID" of the asset (pole ID, handhole or pedestal number) so each photo can be matched to the as-built map. It also wants high-resolution photos with context, open trenches with conduit visible before backfilling, and erosion control or traffic safety measures.

South Carolina's ARPA CPF broadband guidelines tell grantees to "take geotagged photographs of work being conducted" and completed work, name "pedestals, splicing, fiber, fiber cabinets (with doors open)" as examples, mark camera location services "MANDATORY," and say to "avoid having people in the photographs."

Cities care about the dirt, not the fiber. Rio Rancho's fiber installation policy (effective September 2025) wants a photo after pothole excavation or any damage to sidewalks and driveways, and photos of completed restoration that "must clearly show work area and restoration quality." The close-out package must include "the permit #, map, and pictures/documentation of all completed restoration."

Municipal utilities vary. Shutesbury MLP's FTTX bid says to "take photos of any trenching work, both open and completed," to shoot "a complete set of pictures ... showing conduit placement and depth" per trench segment before backfill, and that test results "must be documented and submitted with the work order." Lewis County PUD's drop standards require no photos, but want light-level results printed on a label inside the NID door, range "-7 to -20db." Fort Dodge (2022) and Traverse City Light & Power (2024) drop RFPs mention photos only on the tech's ID badge.

Which shots cover most specs, and why does each one get rejected?

Where a row says "if your spec asks," no public document we read requires that shot; confirm with your ISP.

ShotWhat must be visibleWhy it comes back (per the specs)
Address / house numberNumber on the house or mailbox, with the drop route or NID in the same frameSet cannot be tied to the work order; Utah and SC want each photo matched to a location
Pedestal or handhole, beforeLid open, pedestal/handhole number legible, fiber slack and tracer wireUtah: no "unique ID" in frame, no match to the as-built map; LCPUD wants 10 ft of slack and stripped tracer wire
Open trench / bore pitConduit in the trench with depth shown, shot before backfillShutesbury: "conduit placement and depth" pictures before backfill; Utah: conduit visible before backfilling
Drop routeFull path from pedestal or pole to the house, aerial or buriedSC: route photos must show buried or aerial
Ground / bondGround wire from the NID or ONT closure to the clamp or rodLCPUD: #12 ground wire to the service ground, rod or mast; TCLP: ground rod at the NID base
NID / entry pointNID height and distance from the electric meter, fiber dressed insideLCPUD: NID 3–6 ft up, 12 in or more from the meter, 3 ft of fiber inside
Light levelMeter display with the dBm value, and the label inside the NIDLCPUD: printed results inside the NID door; Shutesbury: 1490/1550 nm levels submitted with the work order
ONT serial label (if your spec asks)Serial and MAC barcode in focus, nothing covering itNot in any public fiber spec we read; the Utah draft checks serial numbers only on wireless antennas and radios
Restoration, afterBackfilled trench, sod or pavement, same angle as the "before"Rio Rancho: photos "must clearly show work area and restoration quality"
PeopleNobody in frameSC asks grantees to "avoid having people in the photographs"

How do you name and order photos so the reviewer can match them?

Two things make a package quick to accept: a fixed shot order and a job reference on each image. Put the work order number in the stamp's job/reference field so it is on the pixels, not only in a filename. Keep the same order at every drop, so shot 3 is always the open trench and shot 9 is always restoration. If the portal renames files on upload, the stamp still carries the job number.

If you export files yourself, name them work order, two-digit shot number, short label: WO48213-03-trench.jpg. The Utah draft wants the asset's unique ID readable in the photo; typing the pedestal number on the stamp's note line covers a faded tag. For a per-drop PDF instead of loose files, see the photo report template guide.

Why print the date and address on the image at all?

Your phone writes the date, time and GPS into EXIF. The reviewer does not see EXIF in a portal thumbnail, and if the portal strips it or renames files, that data is gone. Utah asks for a "visible, unalterable date and time stamp" and GIS stamping; South Carolina asks for geotagged photos. A stamp burned into the image shows the date, time with UTC offset, address and coordinates in any viewer, and says where each value came from (GPS, phone clock checked against a time server, typed). An app like Asof does this on the phone without an account.

Be honest about the limit. The program's wording describes what it wants, not a property of any stamp. Pixels can be edited, and so can EXIF. A visible stamp claims less: this date, address and job number were written on the image by the camera app, and the value next to "GPS" came from the receiver, not from typing. If a program wants more, it will ask for a hash, a server-side upload time or its own capture app. For what else a crew gets from a stamping app, see what contractors need from a jobsite photo app.

The per-drop routine

  1. Type the work order number into the stamp's job field before the first shot; add the pedestal or pole ID to the note line.
  2. Address shot. House number legible, NID location or drop path in the same frame.
  3. Pedestal or handhole, open, before you touch it. ID tag, slack and tracer wire visible.
  4. Route shot. Pedestal or pole to house in one frame; buried or aerial must be obvious.
  5. Open trench or bore pit with conduit in it. Tape in frame if depth is in the spec. Before backfill; there is no retake.
  6. NID or ONT housing mounted. Show the distance to the meter and the height.
  7. Ground/bond. Follow the wire from the closure to the clamp in one frame.
  8. Light level. Meter display readable, then the printed label inside the NID door if your utility wants one. If the spec wants the ONT serial, shoot it now, square on.
  9. Pedestal closed and restoration done. Same angle as shot 3 and shot 5.
  10. Check the set before you drive away. Job number on every shot, nobody in frame, nothing blurred. Then upload or build the PDF.

Questions people ask

Is there one standard list of closeout photos for fiber drops?

No. The list comes from the ISP, the prime, the grant program or the city permit. Public documents range from no photo requirement (Fort Dodge, TCLP) to detailed lists (Utah). Ask for it in writing before the first drop.

Does the light meter reading have to be in the photo?

Only if your spec says so. LCPUD wants printed results inside the NID door; Shutesbury wants 1490 nm and 1550 nm levels recorded at the NID input and submitted with the work order. A photo of the meter next to the label covers both and takes ten seconds.

Why put the date and address on the image if the phone already saves them?

EXIF is invisible in a portal thumbnail, and if the portal strips it or renames files, the photo loses its date and location. A visible stamp stays readable. It does not stop edits.

Sources

  1. Utah Broadband Center (hosted on its site; the PDF text itself names neither the issuer nor BEAD, and "draft 1" and the 1-30-2026 date appear only in the file name), "Attachment C: Project Scope of Work and Deliverables" — the center's "BIG BEAD Subgrant Agreement Draft v.1 2025" lists this attachment by title (checked November 9, 2026) — connecting.utah.gov
  2. South Carolina Office of Regulatory Staff, "2023 ARPA CPF 1.0 Broadband Grant Program Guidelines, Attachment 1 – Data Dictionary for Submission of GIS Shapefiles" (checked November 9, 2026) — ors.sc.gov
  3. City of Rio Rancho, Development Services, "Fiber Infrastructure Installation Policy" (effective September 8, 2025; checked November 9, 2026) — rrnm.gov
  4. Shutesbury Municipal Light Plant, "Invitation for Bids, Bid #19-01, Installation Contract for FTTX Services" (2019) — shutesbury.org
  5. Lewis County PUD (named only as "LCPUD" in the file), "LCPUD FTTH Standards – Service Drop Standards" (sheets dated 10/2025), hosted by NoaNet — noanet.net
  6. Traverse City Light & Power, "TCLPfiber Smart Grid FTTP Drop Placement Construction and Service Installation RFP" (2024) — tclp.org
  7. City of Fort Dodge, "Drop & In-Premise Installation, Request for Proposal" (August 5, 2022) — fortdodgeiowa.org
  8. The Fiber Optic Association, "FOA Technical Bulletin: Guide To Fiber Optic Installation" (documentation per ANSI/TIA/EIA-606, loss testing) — thefoa.org