What Daily Reporting Should Look Like on Fiber Projects

What is a daily report actually for?

A daily report has three jobs. It tells the owner what changed on the ground since yesterday. It creates the contemporaneous record that settles disputes about schedule, quantities, and conditions. And it feeds the as-built, so that closeout is assembled from data instead of from memory.

Reports that only do the first job read like a status update and get skimmed. Reports that do all three are short, structured, and specific, and they are the reason a project manager can answer a question from their own director without calling the field.

The audience is not one person. A superintendent reads it for progress, a scheduler reads it for durations, an accountant reads it for quantities, and a claims analyst may read it two years later for conditions. Structure the report so each of them can find their part quickly.

What fields belong on every fiber daily report?

The field list should be stable from day one so the reports can be summed, sorted, and searched. A report where the fields change from week to week is a series of essays, not a data set.

Why does production have to be recorded by station?

Footage without location is a number that cannot be checked. Nine hundred feet of conduit is a claim. Nine hundred feet of conduit from station 42 plus 00 to station 51 plus 00 is a fact someone can walk to and verify.

Station based reporting also makes the schedule honest. When production is tied to location, the remaining work is a subtraction rather than an estimate, and the point where the route stalled is visible in the record instead of buried in a narrative.

It is what makes the report useful to the as-built as well. Depth notes, structure placements, and utility crossings recorded against a station flow directly into the drawing set. Recorded against a street name, they have to be re-located later by someone with less information than the crew had.

How should delays and non-productive time be described?

Specifically, and on the day they happen. A delay entered a week later, after the argument has started, carries a fraction of the weight of one entered the afternoon it occurred.

The useful format is cause, clock times, impact, and notification. Waiting on make-ready at three poles from 7:30 to 11:15, two crews standing by, notified the owner's project manager at 8:00, is a record. Delayed by make-ready is an opinion.

The same discipline applies to the contractor's own problems. A report that only documents delays caused by others is not credible, and reviewers notice. Equipment failures and crew shortages belong in the record too, because a report that includes them is believed when it matters.

• Waiting on locates, including ticket number and requested response date.
• Waiting on make-ready or pole owner action, with the poles identified.
• Standing by for an inspector or agency approval, with times.
• Weather and ground conditions that made work unsafe or unproductive.
• Differing site conditions, described physically and photographed immediately.
• Equipment failure or crew shortage, stated plainly.

What should the report say about locates and permits?

Every day of excavation should reference a valid Sunshine 811 ticket, and the report should carry the ticket number and its validity window. Tickets expire, and the report is where an expiring ticket becomes visible before a crew arrives to find its marks are stale.

Where the design calls for potholing at crossings, the report should record which crossings were exposed, what was found, and the measured depth. That data is worth more than the same crossing described as verified, and it flows straight into the as-built.

Permit conditions belong in the report as active constraints, not as an attachment. Work hours, lane closure windows, tree protection, and restoration requirements affect the day being reported, so the report should state which conditions were in force and whether they were met.

How do photos make a report defensible?

Photos are the part of the record that nobody argues with, provided they carry location and time. A photo with no station is evidence that something happened somewhere.

Take pairs. An existing conditions photo before any work at a disturbed location, and a matching photo from the same position afterward, resolves nearly every restoration dispute before it becomes one. This is cheapest at driveways, irrigation heads, mailboxes, decorative surfaces, and anything already damaged when the crew arrived.

Photograph what will be buried. Open trench with conduit and tracer wire in place, a structure before backfill, a crossing with measured separation visible against a tape, and a splice enclosure before it is closed are all images that answer questions later that no drawing can.

Photograph the locate marks before digging starts. A photo of the paint and flags in place, in the APWA colors such as orange for communications, red for electric and yellow for gas, shows the area was marked when the crew dug. It also records which facilities were marked and where, which matters if a ticket or a strike is disputed later.

How does a daily report change on drilling, aerial and splicing days?

The core fields stay the same, but each type of work adds a few of its own. A template that ignores the activity produces reports that look complete and still leave the as-built short of data.

On drilling days the key additions are the bore identity, rod by rod depth and pitch, and what each pothole exposed. On aerial days they are the pole tags worked, the permit status of each pole, and sag readings where strand was tensioned. On splicing days they are the splice points completed, the fiber counts spliced and which test files were captured. Restoration days need the surface type, the material used and the location of each paired photo.

How should a field change be written up?

As its own entry, on the day it happens, with enough detail that someone else could draw it. A field change is any departure from the issued design: a bore shifted to clear a conflict, a handhole moved off a driveway apron, or a pole skipped because make-ready was not finished.

The entry should record what changed, why, who approved it and the new location in stations or coordinates, with a photo or a dimensioned sketch attached. If the change needed owner approval and did not get it before the work, the report should say so plainly instead of leaving it for closeout to discover.

Field changes are where daily reports and as-builts meet most directly. A change captured cleanly in the report becomes a dimensioned revision on the drawing. One that never reached the report becomes a mystery at the next locate.

How does daily reporting feed closeout?

Closeout is an assembly problem, and daily reports are the parts. When each day already carries stationing, quantities, depths, structures, photos, and changes, the as-built is compiled from records rather than reconstructed from recollection.

That relationship should be designed on purpose. If the as-built needs depth of cover at each crossing, the daily report should have a field for it. If the closeout needs structure load ratings, the day the structure was set is the day to record it.

The practical test is whether closeout requires anyone to return to the field. If it does, the daily reporting was incomplete, and the gap gets paid for twice: once in remobilization and once in schedule.

Who should own the report and when is it due?

One named person, and the same day. A single point of contact who sends the report every working day builds a record with no gaps, which is the property that makes the whole set credible.

Set the distribution list before mobilization and do not change it informally. When reports go to different people on different days, the owner's file develops holes that look like missed days even when the work was reported.

Same day delivery is what separates a report from a summary. The details that matter, exact times, exact stations, what a crossing looked like before it was backfilled, are still accurate at five o'clock and are approximations by Friday.