RSE Compliance in Dispatch
How Sixième Étoile surfaces and enforces RSE compliance rules during dispatch — indicators, warnings, blocking policies, and crew mode alternatives.
Overview
RSE (Responsabilité Sociale des Entreprises) compliance checks run automatically every time a driver is about to be assigned to a mission, regardless of the dispatch method — direct assignment, broadcast, or Gantt drag-and-drop. They protect both operators (legal liability) and drivers (health and welfare).
Compliance rules are configured per organization in OrganizationLicenseRule and can be tuned to match your collective agreement or contractual obligations beyond the legal minimum.
What is checked
The compliance engine evaluates three categories of rules:
1. Minimum rest time
The driver's rest time since completing their last mission is compared against the configured minimum.
- Default legal minimum: 11 hours for TRANSFER trips
- Calculated from
previousMission.estimatedEndAt(or actual end time if recorded) to the newpickupAt - Missions of type DISPO or OFF_GRID may have different thresholds configured in
OrganizationLicenseRule
2. Maximum continuous working hours
The driver's cumulative work time in the rolling 24-hour window ending at the new mission's estimatedEndAt is computed. If it would exceed the configured maximum (default: 10 hours), a compliance flag is raised.
3. Staffing selection policy
staffingSelectionPolicy is a configurable policy that influences driver ordering and eligibility. It can require that drivers with fewer total hours this week are prioritized, or that specific categories of drivers are preferred for specific mission types. Violations of the policy produce amber (advisory) indicators rather than red (blocking) ones.
Compliance indicators
Results appear as color-coded indicators on the assignment panel and on driver cards in the assignment wizard:
| Color | Meaning | Default effect |
|---|---|---|
| Green | Fully compliant | No action needed |
| Amber | Borderline — below recommended threshold but above legal minimum | Warning displayed; operator must acknowledge before confirming |
| Red | Non-compliant — at or below legal minimum | Blocks confirmation in strict mode; requires explicit override in flexible mode |
The indicator shown is the worst across all three rule categories for that driver.
Strict mode vs flexible mode
Your organization's dispatch policy (configured in Settings → Dispatch) sets one of two modes:
| Mode | Red indicator behavior |
|---|---|
| Strict | Confirmation button disabled; the operator cannot assign a non-compliant driver without an admin override |
| Flexible | A warning modal appears; the operator must explicitly acknowledge the violation (with a mandatory reason field) before the confirmation button activates |
Amber indicators behave the same in both modes: they show a warning but do not block the confirmation button.
Compliance-driven staffing alternatives
When RSE compliance blocks the default single-driver assignment, the system suggests alternative crew configurations. These suggestions appear in the assignment wizard below the blocked driver, or in a dedicated Staffing alternatives panel.
| Situation | Suggested alternative |
|---|---|
| Rest time too short for single driver | DOUBLE_CREW — two drivers share the mission, one resting while the other drives |
| Trip duration exceeds continuous driving limit | RELAY_DRIVER — two drivers cover sequential legs |
| Multi-day assignment exceeds weekly limits | MULTI_DAY — mission is split into daily segments, each with its own driver |
Clicking a suggestion opens the relevant crew mode configuration in the assignment wizard. See Crew Modes for details on each configuration.
RSE in broadcast mode
When you use broadcast mode, the compliance engine runs at offer generation time to exclude non-compliant drivers from receiving the offer (based on strict-mode rules). Amber-indicator drivers still receive offers; the accepting driver's compliance is re-checked at the moment of acceptance.
RSE in Gantt drag-and-drop
When you drag a mission block to a different driver row, compliance is checked before the drop is confirmed. A red overlay on the target driver row indicates a blocking violation; the drop is rejected. An amber overlay allows the drop but shows a warning tooltip.
Viewing compliance history
Each assignment confirmation records whether any compliance warnings were acknowledged, by whom, and with what reason. To view this audit trail:
- Open the mission from any dispatch view.
- Go to the Dispatch history tab in the Mission Detail panel.
- Each assignment event shows the compliance status at the time of assignment and any operator acknowledgements.
Configuring RSE rules
RSE thresholds are managed by organization administrators in Settings → Compliance rules. You can configure:
- Minimum rest time per trip type (TRANSFER, EXCURSION, DISPO, OFF_GRID)
- Maximum continuous working hours (rolling 24-hour window)
- Maximum weekly working hours
staffingSelectionPolicypreferences
Changes to RSE rules take effect immediately for new assignments. In-flight missions are not affected.
Related pages
- Direct Assignment — compliance indicators in the assignment wizard (FR394)
- Crew Modes — alternative staffing configurations suggested by compliance
- Broadcast Pipeline — how compliance filters the broadcast driver pool
- Gantt View — compliance warnings on drag-and-drop