ShiftDesk: Workforce Ticketing and Shift Tracking
Workforce platform combining GPS-verified clock-ins, threaded support tickets and role-specific dashboards for employees and managers.
- HR and internal operations
- Full-stack developer, schema through role dashboards
- SaaS
- Deployed
What problem does ShiftDesk solve?
Distributed teams often track attendance in one tool, raise IT problems in another and escalate through a group chat where requests disappear. Managers cannot see who is on shift and what is blocking them from the same place.
How does ShiftDesk work?
ShiftDesk puts attendance and support inside one operating picture. Clock-ins carry location evidence, tickets move through named states with their history attached, and each role sees the decisions it is responsible for.
Which architecture decisions shaped the build?
- Clock-in stores the captured coordinates with the shift record
- Attendance disputes are settled against the record that created them rather than a separate location log that may not line up.
- The conversation belongs to the ticket
- Context and resolution live together, so reassigning a ticket carries its history.
- Dashboards derived per role from shared tables
- One source of attendance and ticket data, three read models, no synchronisation between them.
Field notes from the build
A manager needs two answers at the start of a shift: who is working, and what is keeping them from working. ShiftDesk keeps both answers in the same operating picture.
Attendance keeps the evidence beside the claim
A clock-in stores its captured location on the shift record. If attendance is questioned weeks later, the evidence is already attached to the event instead of waiting in another log to be matched by timestamp.
A ticket never loses its history
The support thread belongs to the ticket. Reassignment carries the history with it, so the next person continues the diagnosis. Named states make progress visible without guessing from the age of the latest reply.
Evidence in the build
Two related workflows sharing one source of truth, role-separated employee and manager surfaces, and evidence stored beside the event it may need to defend.