Choose the right proof of work for each stop
Give drivers a clear handoff checklist and keep the evidence your team needs to answer questions about completed work.
Choose evidence that helps your operation
A stop action is a task attached to a pickup, dropoff, or waypoint. It tells the driver what to collect or confirm at that part of the job.
| Action type | Useful when you need to know | Example |
|---|---|---|
| Photo | What was present, its visible condition, or where it was left | A package beside the agreed delivery entrance |
| Signature | Who acknowledged the handoff | The recipient's signature and name at a staffed reception desk |
| Barcode Scan | Which labeled items passed through the stop | Scanning the labels on parcels collected from a depot |
| Custom Form | The same structured answers at every stop | An item count, condition choice, or short handoff checklist |
Choose a photo when the picture answers the question. Choose a form when staff need consistent answers they can read quickly. Use a scan to record a label; it does not replace a condition photo or a recipient's acknowledgment.
Choose where and when the action belongs
Stop Type chooses the matching part of the job: Pickup, Dropoff, or Waypoint. The configuration applies to new matching stops in the site, so use instructions that make sense across those jobs.
Stop Trigger chooses the stage of the stop. For the usual driver handoff:
- Started: use for a task the driver can finish after starting that stop and before marking arrival. Required actions at this stage must be finished before arrival.
- Arrived: use for evidence collected at the address, such as a delivery photo, recipient signature, or collection scan. Required actions must be finished before completing the stop.
A delivery photo belongs after the driver reaches the destination and before the stop is marked complete. That is the setup used below.
Create a stop action
Use an account that can manage the site's settings. Have a test job and a test driver ready so you can check the instructions before using them for customer work.
- Open Settings → Stop Action Configs and select New Config.
- Give it a clear Display Name, such as “Photograph the delivery location.” Add a unique Internal Name, such as
delivery_location_photo. The internal name cannot be changed after creation. - Choose the Stop Type, Stop Trigger, and Action Type.
- Set the relevant Action Type Config. Photos can have minimum and maximum counts; signatures can request the signer's name; custom forms can contain named fields with labels, types, required answers, and choices.
- Turn on Is Required when the driver must supply this evidence. Leave it off for a task the driver may skip.
- Set Sort Order and write a short Display Description explaining what a useful result looks like. Select Save.
New configurations start active. To pause one, use Disable in the list or edit its Active setting.
| Setting | Decision it controls |
|---|---|
| Required | The driver must complete the action at its relevant stage. |
| Optional | The action is offered, but the driver may skip it. |
| Active | The configuration is used when new matching stops receive their actions. |
These decisions are separate. An optional action can be active, and disabling a required configuration does not remove actions already attached to jobs.
Example: a furniture delivery handoff
A delivery team wants to record the condition of boxed furniture at collection and show where it was handed over. Start with two actions:
- Pickup — Arrived — Photo: “Photograph the boxes before loading.” Make it required if the condition record is needed for every collection.
- Dropoff — Arrived — Photo: “Photograph the agreed delivery location.” Make it required and set a minimum of one photo. Ask for an image that clearly shows the items and location.
If the team needs a named recipient's acknowledgment, add a signature action at dropoff. If the useful detail is an item count or condition category, use a custom form. Add each action because someone will use the result.
Plan changes for new stops
New stops receive the active configurations matching their stop type. Those actions carry their own instructions, trigger, required status, and order.
Saving or disabling a configuration does not replace the actions already attached to existing jobs. When changing your process, create a new test job and check its actions. Review any work already in progress separately.
Verify the driver handoff
- Create a test job after saving the configuration, with the pickup or dropoff type you configured.
- Assign it to a test driver and open it in the Driver App.
- Start the stop and mark arrival for an Arrived action. Check that its name, instructions, and position in the list are clear.
- Try to complete the stop before supplying its required evidence. Confirm that the unfinished action is identified.
- Complete the action, then complete the stop. Reopen the job in the Dashboard and confirm the collected evidence is available.
- If you also configured an optional action, confirm that the driver can skip it without blocking the required handoff.
A useful result is evidence that another dispatcher can understand without calling the driver to ask what it means.
Troubleshooting
The action does not appear
Check the site, the configuration's active status, and the stop type. Create a new test stop after saving. An existing stop does not acquire a newly created configuration automatically.
The driver cannot complete the stop
Look for unfinished required actions from the Started or Arrived stage. For photos, check the required count and that uploads finished; for a form, check every required answer.
The evidence is requested at the wrong time
Review Stop Trigger. Use Arrived for a photo, signature, or scan that needs to happen at the address. Save the change and verify it on a newly created job.
Disabling a configuration did not remove a task
Disable stops the configuration being added to new matching stops. It does not erase the actions or evidence already attached to existing work.
For the wider setup, see Configure job behavior.