Field report · Jackson, Michigan
We lost half our production in two weeks, and documented our way back
We moved crews into Jackson and almost immediately lost about 50 percent of the productivity we had in the market we came from. Rigs were on site and idle roughly one day a week. Commitments were made about when areas would be marked, expectations were set, and they were not going to be met.
We answered with retransmits. That works until it does not. Some tickets reached revision five or six, and once a ticket has that many revisions the history becomes its own problem: which revision cleared which station, what was still open, what was a system error. All of it was already in Quick811, so we could actually read it instead of reconstructing it.
We compiled what we had into a detailed report and sent it to the one-call area managers and directors. Two days later there were eight locators on the project, and they cleared two weeks of backlog in two days.
That job is the reason the ticket history PDF export exists. A ticket can carry multiple revisions, and inside a single revision a station can respond more than once, so a ticket can go from 003 to 002 and back to 003. Having an auditable time trail is not a nice-to-have when you are the one asking somebody to send more people.