# Dispatching and triaging jobs

> Every job has one status-aware action surface — the Job Command Sheet — reachable from any board view. Assign or do it yourself, dispatch, reschedule with a reason, hold, cancel, or complete on behalf. A needs-attention strip surfaces overdue, missed, and soon-unassigned work so nothing goes invisible.

URL: https://biloh.com.au/docs/how-to/dispatching-and-triage
Category: How-to guides | Audience: operator | Updated: 2026-07-07

To dispatch and triage work in Biloh you use one status-aware surface — the **Job Command Sheet** — reachable from every board view. You can do each step by chat (ask your AI assistant) or in the app; the actions are identical.

## How do I get a job to a contractor?

Open the job's card and the Job Command Sheet appears with the actions that make sense for its status. For an unassigned job you can **Assign** it to a compliant contractor, or — if you do the work yourself — **Do it myself**, which assigns to your own crew and dispatches in one tap (see [delivery models](/docs/concepts/delivery-models)). Once assigned, **Dispatch** hands it to the contractor. Assignment runs a compliance gate: a contractor who lacks the service capability, a signed agreement, or current insurance is blocked with the exact reason, not silently dropped.

## What can I do from the sheet?

The sheet is the whole triage menu, so control never lives on some other screen:

- **Reschedule** — move this one occurrence to a new day, with a reason. Editing a recurring series instead asks whether you mean this occurrence or all future ones ([scheduling by the day](/docs/concepts/scheduling-jobs-by-the-day)).
- **Reassign / Unassign** — hand the job to a different contractor, or pull it back to the unassigned pool.
- **Hold / Resume**, **Cancel** (reason required), and **Complete on behalf** — record a completion for a job done in the field, honouring the site's photo and notes requirements.
- **Un-complete** — undo a completion (until the job has been invoiced), the way Housecall Pro's "unfinish" works.

## What needs my attention this morning?

The board leads with a **needs-attention strip**: Overdue, Missed, Unassigned within the next few days, Declined, and Awaiting re-acceptance. Each chip filters the list to exactly those jobs. The design rule is that **every fetched job appears in at least one bucket** — a job whose date has passed surfaces in Overdue rather than falling into a gap. Tap a chip, work the list, and the count drops as you clear it.

## Bulk moves after a bad-weather day

When a whole day needs to shift — a public holiday, a rain-out — select the affected jobs and **bulk-reschedule** them to one new date with a shared reason. Bulk gestures are a Pro-plan capability; single-job reschedule is always available. The move records a per-job audit trail and moves only the jobs whose lifecycle allows it, returning any it couldn't move.

## Related

- [Delivery models: dispatch, self-perform, or both](/docs/concepts/delivery-models)
- [Scheduling jobs by the day, not the minute](/docs/concepts/scheduling-jobs-by-the-day)
- [Route optimization: the runs bolt-on](/docs/reference/route-optimization-bolt-on)