About Uploading Tickets
Completing a ticket records the outcome — but it doesn't send anything out. Uploading is the step that actually transmits: it pushes the official status back to the call centre, and it emails completion packages to customers. This guide explains the Upload buttons and, critically, why forgetting to press them is a compliance risk.
LocateOps deliberately separates completing from sending. You complete tickets as you finish them in the field, then upload a batch when you're ready. That batching is convenient — but it means the send only happens when a human clicks Upload.
Why Uploading Is Separate from Completing
When you complete a ticket, LocateOps queues the outbound work but holds it. Nothing leaves until you upload. This lets you review your day's completions before they go to the call centre and customers — but it puts the responsibility on you to actually send them.
A completed ticket that is never uploaded is never reported. For call-centre tickets, reporting the status back is a legal obligation with a deadline. A forgotten Upload click means the update simply never happens. Treat uploading as the final, required step of every completion.
The Upload Buttons
There are two upload actions on the tickets board, plus an admin escape hatch.
| Button | Who sees it | What it sends |
|---|---|---|
| Upload Tickets | Everyone | Your own completed tickets — the ones you completed. |
| Upload all completed tickets | Supervisors / managers / admins (with the right permission) | Every ticket completed today across the company. |
| Run Push Queue Now | Administrators (Logs → OneCall tab) | A full flush of everything still waiting, including earlier retries — the escape hatch. |
Upload Tickets (everyone)
This is the button you use daily. It finds the tickets you completed that are waiting to be sent, and sends them. Use it at the end of a job or the end of your shift.
Upload all completed tickets (managers)
A supervisor or manager can sweep up everything completed today in one click — useful for making sure nothing a locator forgot is left unsent. It covers tickets completed today in the company's local day.
Run Push Queue Now (admins)
If something got stranded — a send that failed earlier and is waiting to retry, or a ticket completed on a previous day — an administrator can run a full flush from Logs → OneCall tab. This is the catch-all for anything the two board buttons didn't cover.
What Upload Does, Per Ticket Source
Upload does different things depending on where the ticket came from. The button is the same; the behaviour follows the source badge.
| Source | What Upload does |
|---|---|
| On1Call | Pushes the official status (Completed, Cleared, etc.) back to Ontario One Call's 360 Feedback service, with the closed date and your field markings. |
| Irth | Sends a positive response code back to Before You Dig Partners / IRTHNet (paint vs sketch completion, cleared, etc.). |
| Private | Emails the completion package to the customer. There's no call centre to push to. |
A private ticket's customer email is sent once — LocateOps remembers it has been sent and won't re-send it on a later upload. Call-centre pushes are likewise de-duplicated, so uploading again is safe.
Reading the Result
After you upload, LocateOps tells you what it did — typically a summary like “Uploaded 6, emailed 2.” Here's how to read that:
- Uploaded — the number of call-centre status pushes that were sent (On1Call + Irth tickets).
- Emailed — the number of private-ticket completion emails sent to customers.
- If a ticket was skipped (for example, a private ticket whose customer has no email), it isn't counted in either number — check the ticket if a count looks low.
If something fails
A send that hits a temporary problem (a call centre being briefly unreachable, say) is automatically retried in the background. A send that fails for a real reason shows up in the Maintenance tab, where an administrator can investigate and retry it. See the Maintenance Tab guide.
The Compliance Reminder
This is the single most important habit in LocateOps.
Upload is not automatic, and a forgotten Upload is invisible until someone checks. For call-centre work, the law requires you to report a completed locate within a few business days. LocateOps queues the report the moment you complete — but it only sends when you click Upload. If you complete tickets all day and never upload, none of those reports go out.
Build the habit:
- Upload at the end of every job or shift — make it part of finishing, like packing up your truck.
- Managers: use “Upload all completed tickets” at end of day to catch anything missed.
- Watch the dashboard reconciliation banner — it warns when the call centre says it sent you locates you don't have, and (combined with the Maintenance tab) helps catch gaps.
If you're ever unsure whether your completions went out, open the Maintenance tab — it shows exactly what's still waiting to send.
Common Scenarios
“I finished my tickets — am I done?”
Not until you press Upload Tickets. Completing records the work; uploading sends it. Always finish with an upload.
“The excavator/customer says they never got the completion.”
Check that the ticket was uploaded. Completing alone doesn't email anyone. If it was uploaded and still didn't arrive, see the Troubleshooting guide (check spam and the excavator email address).
“It said ‘Uploaded 5, emailed 0’ but I had a private ticket.”
The private ticket was probably skipped because its customer has no email address. Open the ticket, add the email, and upload again.
“A bunch of old completed tickets never got sent.”
An administrator can run Run Push Queue Now from Logs → OneCall to flush everything still waiting.
Gotchas & Tips
Completing does not send. Uploading sends. This is the #1 thing to remember.
A forgotten upload is a missed legal report for call-centre tickets. Upload every job/shift.
Uploading twice is safe — pushes and customer emails are de-duplicated.
“Emailed” counts private-ticket customer emails; “Uploaded” counts call-centre pushes.
Managers: sweep with “Upload all completed tickets” at end of day.
The Maintenance tab is your proof of what has and hasn't been sent.
Can't find what you need? We respond personally to every message.