Settings guide

Configure how jobs behave

Turn reusable settings into bookable services, eligible drivers, meaningful statuses, and the right proof of work at every stop.

Updated October 23, 2026
Start with the job model: this guide configures the behavior around jobs and stops. Read How jobs, stops, and routes work together first if those pieces are new.

How the settings connect

  1. OptionsReusable requirements such as refrigerated, wheelchair, fragile, or liftgate.
  2. Service typeThe bookable offering selected for the job, with planning and presentation defaults.
  3. WorkflowThe site's ordered states for jobs, stops, and routes.
  4. Stop actionsPhotos, signatures, scans, or forms created for matching stop types.
SettingQuestion it answersWhere it appears
OptionWhat capability or handling requirement matters?Jobs, workers, vehicles, and reusable service requirements
Service typeWhat kind of work did the customer choose?Booking, job creation, estimates, dispatch
WorkflowWhat does progress mean for this site?Jobs, stops, routes, filters, notifications
Stop action configWhat must the driver collect or confirm?Matching pickup, dropoff, or waypoint stops

For a worked example, follow Match jobs to the right people and equipment. For bookable offerings, see Service types.

1. Create reusable options

Open Settings → Options and create labels for requirements such as refrigeration, wheelchair access, fragile handling, or a liftgate. Choose whether each option can be added to workers, vehicles, service types, jobs, or a combination of them.

During automatic dispatch, the driver and assigned vehicle together must cover all the options required by the job and its service type. For example, the vehicle can meet an equipment requirement while the driver meets a certification requirement.

One label, many uses.

An option such as refrigerated can be allowed on jobs, workers, and vehicles. Select it on the job, then tag the drivers or vehicles that can actually perform it.

Pricing rules can also add a flat or percentage charge when a job carries a particular option.

2. Define the services customers can choose

Open Settings → Service Types. A service type is a bookable offering such as Standard, Express, Wheelchair Ride, or Appliance Installation.

  • Name and description explain the offer to staff and customers.
  • Short code is a stable identifier for CSV imports and external systems, even if the display name changes.
  • Capacity describes the work's capacity requirement.
  • Default service time is copied to stops that do not set their own duration and feeds ETAs and route planning.
  • Image and price details help present the service in customer-facing selection.

Service types describe the work. Pricing rules decide what that work costs.

3. Choose meaningful job statuses

Open Settings → Workflows to organize the job workflow. Each state belongs to one stable phase: pending, assigned, started, completed, or cancelled. Custom labels can describe your team's work while those groups preserve its lifecycle meaning. The screen does not provide equivalent editors for stop or route workflows.

Follow Choose job statuses your team understands for the default state, lifecycle groups, and changes that are allowed.

RouteIQ Dispatch Software workflow board grouping custom job states into pending, assigned, started, completed, and cancelled phases
Use the words your team knows. Put each custom status into one of five groups so the rest of the product knows what it means.
  • The default state must remain in the pending phase.
  • Completed and cancelled are final groups.
  • A custom job state referenced by jobs cannot be deleted. Internal states have additional protection.
  • Keep a pending default and at least one state in each required lifecycle group.

4. Require proof of work with stop actions

Start by choosing the right proof of work for each stop: the question you need to answer determines whether to use a photo, signature, scan, or form.

Open Settings → Stop Action Configs. Create one reusable task for each proof or confirmation the driver should complete. Supported actions include photos, signatures, barcode scans, and custom forms.

For each stop action, choose the stop type, when it appears, whether it is required, and where it appears in the list. New pickup, dropoff, or waypoint stops receive the active actions that match them.

Changes to a stop action apply to new stops only. They do not change the requirements already attached to existing or completed work.

Example: refrigerated delivery with proof

  1. Create a Refrigerated option and allow it on jobs, workers, and vehicles.
  2. Create a Cold Chain service type with a 15-minute default service time.
  3. Put Received and Ready in Pending, Assigned in Assigned, In transit in Started, and Delivered in Completed. Keep a separate Cancelled state in the Cancelled group for jobs that end without completion.
  4. Create a required barcode scan for pickup and a required photo for dropoff.
  5. Select Refrigerated on the job and tag the capable drivers or vehicles. Automatic dispatch can now exclude candidates that cannot cover the requirement.

Change configuration safely

  1. Create or update the setting in a low-volume period.
  2. Create a non-production test job using the target service type and options.
  3. Confirm eligible drivers, copied stop actions, workflow labels, ETA, and price.
  4. Deactivate obsolete catalog entries when history still references them; delete only when RouteIQ Dispatch Software allows it.

Troubleshooting

No driver is eligible

Check that the driver and their assigned vehicle together cover every option required by the job and its service type.

A stop action is missing

Confirm the config is active, its stop type matches, and the stop was created after the config was available.

A workflow state cannot be deleted

It may be an internal state, the current default, the last state in a required group, or referenced by existing jobs. See the workflow guide before changing it.