Overview
QR Talep is a location-based operations system. QR codes are placed across physical areas. From those QR codes the system handles request creation, assignment, field update and manager approval. The product was designed to work across hospitals, hotels, facilities, schools, factories and similar physical operation areas.
Problem
In field operations, requests usually travel over WhatsApp messages, verbal notifications, scattered notes or manual processes that no one can track. Where the request came from, who is on it, when it closed, and whether it was actually finished stays unclear.
System
I built the product around QR, mobile web form, task, field update and manager approval flow. Physical location inventory, room / floor / area mapping, the form that opens after the QR scan, request creation, task routing, field staff update and manager approval became the core structure.
After completing a task, the field worker can scan the QR again to update status. States like "done", "waiting on materials" and "couldn't complete" were added to the operation flow. Rather than ship a native mobile app, I chose a PWA opened in the browser after the QR scan. That was the right starting point for adoption.
Outcome
QR Talep is positioned not as a basic form or QR page but as an operation management product that digitizes request, task, responsibility and closure control across physical operations.
My role
MVP scope, location-based product logic, the QR flow, the request and task lifecycle, field worker and manager roles, the PWA approach, notification logic, audit trail, and a growth path where parts of QR Talep can later become an AiRX module.