Smart scheduling
Rules by contract, sector, shift, and unit with traceable publishing.
SKLA
Plan, publish, monitor coverage, and make decisions in real time — for healthcare, services, transport, and mobility across Latin America.
While traditional systems manage people, SKLA governs people, assets, and rules in the same operational decision.
Each vertical combines two axes that must be governed together — not in parallel spreadsheets.
| Segment | People | Assets |
|---|---|---|
| Healthcare | Care teams | Beds and wards |
| Services | Field teams | Sites and contracts |
| Transport | Teams and shifts | Fleet and lines |
| Mobility | Urban teams | Vehicles and areas |
Most enterprise buyers still coordinate critical operations in Excel, chat apps, and isolated systems. SKLA replaces that fragmentation with in-flow governance.
| Spreadsheets and legacy | SKLA |
|---|---|
| Isolated scheduling | Unified operational governance |
| Manual, reactive control | Decision tower with prioritization |
| Compliance checked later | Compliance in the publish flow |
| Fragmented view | People, assets, and rules in one context |
| Reacting to problems | Anticipating gaps and exceptions |
Illustrations based on the real SKLA interface — showing how governance, schedules, and tower connect.
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)
Prioritized exceptions with people, assets, and rules in context.
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
Planning, coverage, and publish with integrated compliance.
Driver × hour grid — trips and duty.
Drag to move, drop on another row to swap resource, or use edges to resize. Validation before save.
Shifts, duty, and assets on one operational timeline.
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.
From setup to continuous improvement — five connected steps in one operational flow.
Configure rules
Contracts, work patterns, and profiles per site.
Plan schedules
Build teams and publish with compliance.
Monitor coverage
Real-time alerts for gaps and absences.
Make decisions
Prioritize exceptions in SKLA Tower.
Analyze results
Metrics to evolve your operation.
Scheduling, coverage, compliance, and tower are not isolated modules — they are one operational governance flow.
Planning
Schedules and work patterns
Coverage
Absences and gaps
Compliance
Rules and blocks
Tower
Exceptions and priority
Analytics
Metrics and continuous improvement
Choose your business vertical. Under Transport, open modules by mode (passenger, freight, rail, aviation, maritime, and multimodal).
SKLA connects to your enterprise ecosystem — without trapping operations in parallel spreadsheets.