A field-service application connecting scheduling, technician rounds, signed reports, and billing through dedicated manager, technician, and customer journeys.
Case study
01
A service visit starts in the office and ends in the field, but tracking it spans several tools: scheduling, customer details, work reports, and commercial documents. Axion brings these steps together around a single intervention, giving each role the relevant information and actions.
02
Keep scheduling, assignments, status changes, and signed completion consistent while isolating each organization’s data. On mobile, technicians need to find their rounds and write reports through an interface suited to field work.
03
Next.js and TypeScript power the screens and APIs, while Drizzle structures a libSQL database, using local SQLite or remote Turso. Better Auth provides sessions and roles; every API checks the organization and access to the intervention again. Reports combine a work summary, materials, photos, and a vector signature, with PDF export. Finalization is transactional, and attachment fingerprints are recorded in an audit log.
04
Keeping photos in libSQL simplifies deployment but requires file-size limits and a quota per organization. The PWA prioritizes confidentiality: APIs and authenticated pages are never cached. Already loaded data remains visible when connectivity drops, but business operations require a connection.
05
The project covers the journey from scheduling to a signed report, with a manager dashboard, mobile technician rounds, and customer tracking. It persists interventions, customers and their sites, reports, quotes, and invoices with sequential numbering. The repository includes validation, persistence, and authorization tests; no real-world productivity gain is claimed.
Key points
Managers schedule, technicians follow their rounds and write reports, and customers view their interventions. Access is checked on the server.
Validated photos, vector signatures, PDF export, and an audit log document intervention completion in one journey.
Better Auth sessions, business rules, and filtered queries govern data access by organization, assignment, and role.
Critical perspective
Current limitation
Demo mode combines clearly labeled local examples with persisted data. Offline mutations, email invitations, and email password recovery are unavailable. Photo storage remains deliberately capped.
Next step
Add invitations and account recovery, then prepare offline change synchronization with explicit conflict handling. Validate the complete journey with a pilot team before real business use.