Pause a Job: Check Out, Stop Prep, and "on hold"

Jobs get interrupted. You break for lunch, get pulled to an emergency, or leave a site because the part you need is back at the shop. None of that is a reason to close the request.

In the Work view you pause by checking out. There is no On hold button, and in a standard Bricks organization there is no On hold status — the lifecycle is Open → In progress → Closed.

Steps — pause a job you've started:

1. On the working screen, click Check Out in the bottom bar.
2. Your check-in timer stops and the green Checked in banner disappears from the top of the screen.
3. You return to the Work screen. The request stays open and assigned to you.
4. To pick it back up, open it from your Work List and click Start Work again. The time you already logged is kept.

Steps — stop a prep clock:

1. While prep is running, click Stop Prep in the bottom bar.
2. The prep timer stops. Nothing else about the request changes.

Use this when you started getting ready for a job and then got redirected to something else.

Check Out vs. Complete Job

• Check Out — stops your clock, leaves the request open and assigned to you. The work isn't finished.
• Complete Job — stops your clock and closes the request. The work is finished.

Don't close a job you haven't finished just to clear it off your screen. Closing is what feeds cycle-time and completion reporting, so a request closed early makes your team's numbers look better than the work actually was — and the next person to look at that asset will think the problem was solved.

What about "on hold"?

You'll see On Hold referred to in a couple of places even though there's no hold button in Work. Here's where it comes from:

• Custom workflow statuses. Organizations that define their own statuses under Admin → Workflows can include an On Hold stage. If yours does, it appears in the Update Service Status dialog on the working screen alongside the standard options.
• Command Center reporting. The Status Mix chart and the Aging Backlog metric both count On Hold as a bucket, so that organizations using custom statuses are represented in the dashboard.

If your team needs a formal on-hold stage — for waiting on parts, waiting on approval, or waiting on access — that's a workflow to configure, not something to improvise by closing requests.

Parking a request for someone else? Check out and leave it open. Leave a note first explaining where you got to and what's blocking it, so whoever picks it up doesn't start from zero. If it should go to a specific person, use Assign Internally on the request record.

Related articles:

• Work a job: notes, photos, parts, and status
• Close a job with the Complete Job wizard
• Preview a job, start prep, and start work
• Update status, close, or cancel a request
• Create a custom workflow (service-request statuses)
• Assign or dispatch a service request