DPMS
psychologyMy Role in the Product
The goal was simple to make DPMS the command engine of project execution, digitising every project pillar from planning to execution to billing, eliminating manual processes and closing any scope for manipulation in records. Designed AI-powered agents Site Entry Validation.
warningProblem & Challenges
Field Entry Edge Cases : Countless field operation variations made it difficult to design a single, standardised site entry form that worked across scenarios
Unstructured Role Framework : No defined roles, site allocations, or record-keeping structure, leaving accountability unclear across the field workforce.
Attendance-Entry Disconnect : Attendance was marked independently through the HRMS app, creating cases where attendance was logged with no corresponding site visit recorded that day.
No Photo Evidencing : Site entries had no photographic proof, leaving field visits unverifiable.
Unverified KM Claims : Kilometers travelled weren’t captured, so expense bills and Kilometers vouchers had no way to be validated.
architectureStrategic Execution
1Dynamic Field Entry Forms
Designed flexible, condition-based entry forms that adapted to different field scenarios instead of forcing a rigid one-size-fits-all format
2Role-Based Site Structuring
Introduced defined roles, site allocations, and structured record-keeping to bring clarity and accountability to field operations
3Unified Attendance-Site Linkage
Integrated site entry directly with HRMS platform for attendance, so an engineer’s presence at a site automatically reflected in attendance records.
4Photo-Based Evidencing
Built mandatory photo capture into the site entry workflow, making every visit verifiable with visual proof
5KM Tracking for Expense Verification
Using Google Destination APIs and defined site entry points, kilometers were digitally captured, eliminating manual KM entry and enabling accurate, tamper-proof verification of travel expense claims.