This sprint focuses on improving scheduling flexibility while kicking off our Local Empowerment initiative—giving local teams better visibility on their deviations—alongside key stability fixes.
Enhancements
Timeslots after midnight
Users can now configure checklist timeslots that extend beyond midnight, aligned with the location’s business day. The system correctly evaluates task completion status across overnight periods.
Why this matters
Previously, tasks completed after midnight could be incorrectly marked as late, impacting reporting accuracy and compliance tracking.
Key benefits
- Accurate on-time/late evaluation for overnight tasks
- Better alignment with real operational hours (e.g. restaurants, night shifts)
- Improved audit reliability and reporting consistency
- Reduced manual workarounds for late-night operations
Deviations tab on Local level
Why this matters
This is the first step toward local empowerment—giving site teams the same visibility as HQ, directly at location level. Previously, teams lacked a centralized view of their deviations, making it harder to identify issues early and act quickly. The Deviations view is now available directly within the Local Overview, providing access to all past deviations for a specific location with filtering capabilities.
Key benefits
- Stronger local empowerment with direct access to deviation data
- Faster identification of recurring issues
- Improved audit preparation and corrective actions
- More proactive and efficient compliance management
Bugs & Fixes
- Task completed on time not updating | Inaccurate reporting of task performance
- Tasks from the future marked as late | Incorrect task status causing confusion
- In-time answers marked as early/late (midnight edge cases) | Wrong compliance evaluation for overnight tasks
- “Tasks about to be late” message missing | Loss of proactive alerts for teams
- Duplicate Unit Group creation | Data inconsistency when updating group names
- White page with Mapal logo | Intermittent access issues requiring multiple refreshes
- Wrong communication title in exports | Confusing or incorrect export data
- Procedure updates not syncing to locations | Outdated procedures at local level
- Filter and UI issues (forms, permissions, menus) | Reduced usability in key workflows
