Changelog

5 updates

Organisation hierarchy and admin foundations

OperationSavvy added the first web-app administration foundations for managing the structure behind a workforce operation: roles, permissions, organisations, departments, instruments, levels, regions, services, and teams. This release matters because workforce operations software has to model how a business is actually organised — a flat roster is not enough when teams work across different sites, regions, departments, service lines, and permission boundaries.

What changed

  • Added role management and API/web support for roles.
  • Added permission management and the ability to manage role permissions.
  • Added organisation model, API resources, policies, seeders, and organisation UI.
  • Added department model/API/settings pages.
  • Added the first instrument, level, region, service, and team model stacks.
  • Added supporting TypeScript types, Inertia pages, settings navigation, and model-generation improvements used by later admin areas.

Why it matters

Labour-intensive businesses are rarely simple. They need software that can separate responsibility, location, service type, seniority, permissions, and team structure without forcing everything into one generic list. These early web-app commits established the administrative model that later scheduling, site management, compliance, payroll, and field workflows could build on.

View release

Mobile shifts and verified clock-in

OperationSavvy added connected mobile shift workflows: employees can view their shifts, open shift details, acknowledge shifts, and begin a clock-in flow from the app. The release connected scheduling to attendance capture in the mobile experience, moving OperationSavvy closer to a complete shift-to-attendance workflow for labour-intensive teams.

What changed

  • Added API-backed shift loading and cached shift queries.
  • Added today’s shift UI on the mobile home screen.
  • Added a shift detail sheet and shift acknowledgement flow.
  • Added a clock-in flow that captures location and posts attendance to the API.
  • Added face-verification camera UI and a verification sequence before clock-in completion.
  • Added conditional visibility support in mobile forms.

Why it matters

For shift-based businesses, a roster is only useful if it connects cleanly to attendance. This release gave workers a practical mobile path from “what am I working?” to “I am here and signed in,” while giving operations teams better evidence around attendance events.

View release

NFC checkpoint tours for mobile field work

OperationSavvy added mobile tour and checkpoint workflows using NFC tags. Workers can open tours for a site, see the checkpoints that need to be completed, and verify checkpoint visits by scanning the correct NFC tag on a supported mobile device.

What changed

  • Added a mobile tours strip for site-related tours.
  • Added a checkpoint sheet showing tour checkpoints and completion state.
  • Added NFC availability checks for iOS and Android.
  • Added NFC tag reading and writing helpers for NDEF text/URI records.
  • Added checkpoint verification logic that matches the scanned NFC tag to the expected checkpoint.
  • Added UI for setting up and programming checkpoint NFC tags.

Why it matters

Many operational roles need proof that work happened at the right location, in the right order, and at the right time. NFC checkpoint tours give teams a simple mobile verification mechanism for patrols, inspections, site walks, and other recurring field routines.

View release

Mobile onboarding forms

OperationSavvy added mobile onboarding forms so workers can complete required information directly from the app. Instead of pushing onboarding and profile requirements into separate paperwork, this release brought structured forms into the same mobile workflow employees use for their shifts and daily work.

What changed

  • Loaded onboarding form definitions from the user details API.
  • Rendered form fields inside a mobile bottom sheet.
  • Added field support for common onboarding inputs including text, email, digit, and radio-style choices.
  • Added multi-step form rendering with section navigation.
  • Submitted completed form responses to OperationSavvy through the API.

Why it matters

New-starter and compliance information is easiest to collect when it is part of the worker experience. Mobile onboarding forms reduce admin handoffs, keep data attached to the right worker profile, and give operations teams a path to collect structured information without relying on disconnected documents.

View release

Secure mobile access for every workforce account

OperationSavvy’s mobile app gained the foundations for secure workforce access: employees can sign in with their OperationSavvy account, connect to the right employer workspace, and keep their session available on device.

What changed

  • Added mobile sign-in through an OperationSavvy authentication session.
  • Stored authenticated sessions on device so workers do not need to start from scratch every time.
  • Added employer URL entry so the app can connect the worker to the right organisation environment.
  • Added a guided permission flow for notifications, camera/gallery access, and location access.

Why it matters

Workforce operations software only works if people can actually get into it quickly and reliably. This release established the mobile entry point for field workers and shift-based teams, while preparing the app for location-aware clock-ins, photo/document capture, and operational notifications.

View release