JOB & DISPATCH SETTINGS
Structured Job & Dispatch Settings
Define the global rules that shape how jobs are planned and dispatched. Set default timing, shift boundaries, and service assumptions used in planning calculations. Configure alert playbooks to guide dispatcher responses to field issues. Control automation behavior for job generation and archiving. Establish clear permission boundaries for live dispatch actions. DispatchFleet keeps this workflow connected across the platform.
CAPABILITIES
Inside Job & Dispatch Settings
Define the global rules that shape how jobs are planned and dispatched. These capabilities show how DispatchFleet supports day-to-day execution in this area. They capture the decisions dispatchers and field teams make every shift. They also define the guardrails that keep data consistent when plans change. Scan the list below to understand the major functions at a glance. Next, the Features section breaks each capability into concrete actions, screens, and reusable building blocks.
Default job rules
Sets the defaults applied when jobs are created. Keeps planning consistent when a job does not specify every parameter. Drives planner layout and feasibility assumptions through duration and yard defaults. Adds standard guidance to timesheet outputs for compliance discipline. Reduces configuration drift across the organization.
- Default shift selection
- Default job duration (hours)
- Default home yard
- Timesheet reminder text block
Shift hours
Establishes the time model the platform relies on. Ensures jobs appear in the correct shift context. Keeps payroll grouping aligned to operational reality. Prevents midnight edge cases from changing states unexpectedly. Provides a stable foundation for automation and reporting.
- Day start and end boundaries
- Night start and end boundaries
- Shift resolution used across planning and time tracking
Service times
Sets the assumptions used to estimate throughput before execution begins. Keeps route feasibility and cycle math consistent. Adds buffer to reflect real-world delays. Includes inspection time so shift capacity is not overstated. Supports predictable planning without hardcoding job-specific guesses.
- Load service time
- Unload service time
- Buffer time
- Pre-trip inspection time
- Post-trip inspection time
Alerts playbooks
Standardizes how common issues are handled under pressure. Reduces decision time by surfacing recommended actions. Keeps customer communication consistent through templates. Supports rerouting options with predefined alternates. Improves repeatability across shifts and dispatchers.
- Predefined dispatcher responses
- Customer update template support
- Alternate site/dump suggestions
- Driver escalation suggestions
Automation
Defines when jobs are created automatically and how far ahead planning is seeded. Keeps generation aligned to operating days. Cleans up completed work through auto-archiving without deleting history. Ensures automation follows explicit rules rather than hidden logic. Reduces manual overhead while preserving auditability.
- Auto-generate jobs
- Generation horizon
- Generation days
- Auto-archive completed jobs after N days
Dispatcher permissions
Controls how much authority exists in live planning surfaces. Prevents accidental changes to targets when restrictions are needed. Governs whether drivers can self-assign into open slots. Keeps responsibility boundaries clear across roles. Reduces operational risk while keeping workflows flexible.
- Planner edits enable/disable
- Driver self-assignment enable/disable
- Authority boundaries for live changes
WORKFLOW
Job & Dispatch Settings workflow
Define the global rules that shape how jobs are planned and dispatched.
01
Support Default job rules with clear rules, visibility, and consistent execution.
02
Support Shift hours with clear rules, visibility, and consistent execution.
03
Manage maintenance and service state so non-ready assets stay out of dispatch.
04
Use alert playbooks so teams respond consistently when issues occur during the shift.
05
Set permission boundaries so live changes stay controlled and accountable.
01
Support Default job rules with clear rules, visibility, and consistent execution.
02
Support Shift hours with clear rules, visibility, and consistent execution.
03
Manage maintenance and service state so non-ready assets stay out of dispatch.
04
Use alert playbooks so teams respond consistently when issues occur during the shift.
05
Set permission boundaries so live changes stay controlled and accountable.