Damage claims
The audit trail is the product.
A claim can land eighteen months after the dig. What is in the file that day is what you have.
Damage claims
The audit trail is the product.
Every action writes a timestamped entry to the ticket's log: created, renewed, response recorded, call placed, note added, closed. In hosted mode the log table has an insert policy and deliberately no update or delete policy, so a ticket's history cannot be rewritten after the fact. That's the entire point of having one.
When a claim lands eighteen months later, it prints as one file: everyone notified, every response with timestamps, every chase call with its reference number, and the full history. That's what an adjuster asks for on day one, and it's the difference between a defended claim and a paid one.
Where the dig was is part of that file. A crew standing on the spot drops a pin from the phone in their hand, and it's stored with the time it was taken and how good the fix was. Not an address geocoded to the middle of a street number, and not sent to any mapping company to work out. Somebody was there, and the file can say so, with a map on the ticket for anyone who needs to see where.
What people said about the job is in there too. The back and forth on a ticket goes into that same append-only log, so Frontier says Thursday, told Danny to hold sits beside the renewal it explains. It cannot be edited later either. That matters most on the one day it ever will: after a line gets hit, when the story starts moving.
Talk about your exposure- 10/02 08:14 Ticket created: Harbor St tie-in, Tampa FL
- 10/02 08:14 5 facility owners notified
- 10/02 08:31 Site pin dropped: 27.94812, -82.45934 (±4 m)
- 10/04 11:47 Response: Electric, clear, marked
- 10/04 15:02 Response: Water, clear, marked
- 10/07 09:30 Call placed: Comms, no answer
- 10/08 10:12 Call placed: Comms, ref #48812, escalated
- 10/09 07:55 Response: Comms, marked, conflict noted
- 10/14 06:30 Renewed: responses reset to pending