> ## Documentation Index
> Fetch the complete documentation index at: https://docs.probaseapp.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Timing a visit
> Start, pause and resume the clock so you know how long the work really took
## Overview
Every visit has a clock. Tap **Start visit** when you get to the property, **Pause** when you step away, **Resume** when you're back, and **Complete visit** when you're done. ProBase adds up only the time you were actually working, and keeps the result on the visit for good.
You never have to time a visit — a visit completes perfectly well without the clock ever being started. But when you do use it, you get an honest number for how long the job took against what you estimated, which is the quickest way to find out whether your pricing matches your day.
The clock is **yours and your crew's**. Customers never see the timer, the working windows, or how long you took.
## Starting the clock
Open the visit and tap **Start visit** — the solid button on the [action row](/routes/visit-page#the-action-row).
The page changes straight away:
* The state pill in the header reads **Working**, and the line underneath it becomes *Started 12:15 PM*
* The timer panel appears under the buttons and starts counting
* The solid button becomes **Complete visit**, with **Pause** as the quiet action underneath
* **Directions** and **Text on my way** move into the **⋯ More** sheet — you're already there, so they stop taking up the top of the screen
You can start a visit whenever you like — including one scheduled for a future day. ProBase doesn't stop you working ahead.
## The timer panel
The dark panel under the buttons is the live readout.
* **ON SITE** across the top while the clock is counting
* The big number is the working time so far — `12:07` under an hour, `1:07:12` once you pass one
* The line underneath reads *Started at 12:15 PM · estimated 45 min*, so you can see at a glance whether you're ahead of or behind the time you allowed for the job
The number ticks up on its own. You don't need to refresh the page, and leaving the visit and coming back picks up exactly where the clock is.
## Pausing and resuming
Tap **Pause** — the quiet action under the main buttons — when you stop working: a supply run, lunch, a phone call, waiting on a gate to be opened.
The panel turns to **PAUSED**, the number holds where it is, and the caption tells you plainly: *Paused — this time isn't counting.*
Tap **Resume** to start counting again.
You can pause and resume as many times as the day needs. Each stretch of work is recorded separately, so a visit you came back to twice shows up as two working windows rather than one long block with the break silently included.
Pausing doesn't change the visit's status for anyone else — the job is still yours and still on the day's schedule. It only stops the clock.
## Finishing
Tap **Complete visit** and the clock stops for good. You go straight into the [completion flow](/routes/completing-jobs); the elapsed time is stamped on the visit whether you finish the completion form now or come back to it.
If you never started the clock, **Complete visit** works exactly the same way — the visit simply carries no timing, rather than a misleading `0:00`.
## What happened, after the visit
Once the visit is complete, the timer is replaced by a **What happened** block between the header and the buttons. It's three plain facts:
| Row | What it says |
| ---------------- | --------------------------------------------------------------------------------------------- |
| **Completed by** | The person who tapped Complete, and the crew — *Callie Gates · My Crew* |
| **On site** | *Arrived 12:15 PM → finished 1:07 PM*, plus *· 2 working windows* if you paused at least once |
| **Took** | *52 min · estimated 45 min* — the working time beside what you'd allowed |
A row with nothing true to say is left out rather than filled with a dash. A visit you never started shows no **On site** row, and **Took** reads *Not timed · estimated 45 min* — the estimate is still a fact about the job even when nobody timed the work.
Under the rows sits the reminder: *Yours and your crew's — never the customer's.*
## The History card
At the bottom of the **Visit** tab on a completed or cancelled visit, a **History** card lists everything that happened on the visit, newest first:
* *Started 12:15 PM by Callie*
* *Paused 12:40 PM*
* *Resumed 12:52 PM*
* *Completed 1:07 PM*
* *Checklist reopened* and *Checklist edited after completion*, if you went back in
* *Cancelled by Callie Gates · Wed, Aug 26*
Times are always shown in your business's timezone, so a line reads the same on every phone on the crew.
A visit that was finished before the clock existed has no history to show, so no card appears — you won't see an empty **History** heading.
## Timing an assessment visit
[Assessment visits](/customers/assessments) time the same way. Tap **Start visit**, and the solid button becomes **Mark assessment complete** with **Pause** underneath.
## Timing a marketplace visit
You can run your own clock on a [marketplace visit](/marketplace/marketplace-jobs) too — it's your time, so ProBase tracks it for you even though the visit itself is completed in the marketplace app.
Once the marketplace tells ProBase the visit is no longer scheduled (because it was completed, cancelled or moved), a running clock is stopped automatically so it doesn't keep counting on a job that's already finished.
## Who can use the clock
Starting, pausing and resuming needs the same permission as completing a visit, and only on a visit assigned to a crew you work. If your role can't complete visits, the buttons simply aren't shown — nothing is greyed out. See [Roles and permissions](/team/roles-and-permissions).
## Next steps
* [The visit page](/routes/visit-page) — everything else on the screen
* [Completing a visit](/routes/completing-jobs) — the flow **Complete visit** opens
* [Charges on a visit](/routes/visit-charges) — bill for the extra you did
* [Cancelling a visit](/routes/cancelling-visits) — when the visit doesn't happen