DispatchCheck
Founder review · synthetic schedules onlyCustomer launch pending

For teams who dispatch from a spreadsheet

Catch schedule conflicts before the crews leave.

Find double bookings, tight handoffs and arrival-window mismatches in one row-numbered review. Keep your sheet. Fix the exceptions.

Schedule review

Explore a synthetic dispatch day. Customer files are disabled in this public review.

Interactive sample
01 / INPUT
Synthetic identifiers · October 5, 2026 · UTC
job_id,crew_id,start,end,window_start,window_end,buffer_minutes
DEMO-101,North,2026-10-05T08:00:00-06:00,2026-10-05T10:00:00-06:00,2026-10-05T08:00:00-06:00,2026-10-05T09:00:00-06:00,30
DEMO-102,North,2026-10-05T09:30:00-06:00,2026-10-05T11:00:00-06:00,2026-10-05T09:00:00-06:00,2026-10-05T10:00:00-06:00,15
DEMO-103,South,2026-10-05T08:00:00-06:00,2026-10-05T09:00:00-06:00,,,

Capacity counts booked crew time per UTC day. Buffers and travel are excluded. Blank windows or buffers stay explicitly unchecked.

02 / REVIEWRow provenance included
3Valid jobs
1Errors
3Warnings
warningRows 4

window unchecked

Arrival window not fully provided; arrival-window check omitted.

warningRows 4

buffer unchecked

Buffer not provided; post-job buffer check omitted.

errorRows 2 & 3

crew overlap

Crew booked for overlapping jobs.

warningFile

scope unchecked

Travel feasibility, breaks, skills, crew members and access restrictions are not checked. Capacity uses booked union per UTC day only.

Reports neutralize spreadsheet formulas. Reviewed rows are not silently corrected. Crew-hours per UTC day: union of booked intervals; overlapping time counted once. Buffers, travel, breaks and crew headcount are excluded; they require separate review.

ONE BOUNDED TASK

Review the schedule.
Keep the judgment.

Booked times are not route feasibility. The checker cannot know individual crew members, traffic, breaks or whether a job will finish early. A quiet report means the supported rules passed, not that dispatch is guaranteed.

01PrepareUse explicit timestamps and stable crew IDs.
02ReviewFind both rows behind each conflict.
03CorrectChange your source and run the review again.
Read the worked review guide →