Typical legacy scheduling
- Static grid per driver or post
- Compliance in after-the-fact reports
- No trip, handover, or multimodal view
- Manual reaction to absences and delays
SKLA Passenger
Peak, absences, and fleet reinforcement in minutes — not spreadsheets.
While traditional systems manage people, SKLA governs people, assets, and rules in the same operational decision.
Spreadsheets and legacy systems focus on who works which shift. SKLA connects scheduling, duty, operational exceptions, and compliance — with a tower to decide before impact.
Typical legacy scheduling
SKLA enterprise
Control tower
Exceptions grouped by impact — crew deficit, handover, journey, and slots.
Integrated compliance
Labor law, driver law, CBAs, and segment profiles at publish time.
Multimodal
Road, rail, air, and maritime under one governance when contracted.
Crew positioning
Reposition crew between bases to take a trip, flight, or shift.
Real day-to-day complexity — on two axes that must be governed together.
Lines, depots, and crews in one flow — with driver gaps visible before boarding.
Manual weekly grid — publishing locks assignment edits (v1).
| Schedule | Unit | Period | Validation | Status |
|---|---|---|---|---|
| Gate 2.7 1781009471746 | DEMO | 06/01/2026 — 06/30/2026 | 1 blocking | Draft |
| June demo schedule | DEMO | 06/01/2026 — 06/30/2026 | OK | Draft |
| ICU shift — week 24 | HC-01 | 06/16/2026 — 06/22/2026 | OK | Published |
| Line 402 — north depot | TR-02 | 06/01/2026 — 06/07/2026 | OK | Draft |
06/01/2026 — 06/30/2026 · Demo unit
Validation before publish
1 blocking issue — fix before publishing.
Operations manager: 1 shift without required coverage.
Coverage
Operations manager · 08:00 — 16:00
0 of 1 on this shift (1 missing)
Shifts
Day shift
06/01/2026 · 08:00 — 16:00
Coverage: Operations manager — min. 1
Schedule by line and depot with integrated coverage.
Operational cockpit: coverage, exceptions, and same-day actions.
Scheduled staff
0
People with confirmed shifts on this date.
Allocated assets
0
Vehicles linked to trips in the period.
Blocking issues
0
Problems that block publishing or completing the operation.
Pending swaps
0
Requests awaiting acceptance or approval.
The lower the index, the more blocking or attention items exist on this date.
Reference: 06/18/2026
Interval between legs shorter than regulated rest
Bento Gonçalves → Manaus (integration)
Dual crew above 72h — schedule 6h rest
Bento Gonçalves → Manaus (integration)
Handover, duty, and gaps prioritized by operational impact.
Illustrative representation of the interface — not a client environment screenshot.
Rules by contract, sector, shift, and unit with traceable publishing.
Gap, absence, and reassignment alerts before operational impact.
Unified panel to prioritize incidents and mobilize teams.
Labor and regulatory risk indicators in daily workflows.
SKLA Passengers covers urban lines through charter and interstate service. Each scenario uses the same scheduling, compliance, and tower engine — with different narratives and capabilities.
Many routes, daily swaps, and peak demand in fixed time windows.
Seasonality, last-minute replacements, and traceability requirements.
Long-term contracts with predictable rotation and strict SLAs.
Unpredictable peaks and need to rebuild crews quickly.
Multi-base operations, city handovers, and journey accumulation across trips.
Passengers, light freight, and logistics support in the same fleet or holding.
Your plan reflects your operation's complexity — not the scenario described here. Use this section to align expectations with our sales team.
Risk indicators and blocks integrated into scheduling — not just after-the-fact reports.
A regional operator reorganizes peak teams in minutes, keeping line regularity and fewer cancellations.