Projects / MyVigi

Real-time operations · 2025

MyVigi

A guard workforce and patrol monitoring platform that replaces paper registers and manual supervision with one real-time workflow.

RoleProduct thinking + full-stack developmentDurationIndependent projectStackReact, Node.js, Express, MongoDB

01 · The problem

Why this was
worth building.

Traditional guard operations often depend on attendance registers and trust-based patrol reports. Supervisors have limited visibility into whether a route was completed on time, whether checkpoints were visited in sequence, or where a guard is during an emergency.

02 · What I wanted to achieve

01

Digitise attendance, shifts, patrols, leave, and incident workflows

02

Verify patrol activity through QR checkpoints and live location

03

Give administrators a real-time view without making field work complicated

03 · System architecture

How the pieces
work together.

01Guard web application↓
02React administration dashboard↓
03Node.js and Express APIs↓
04JWT role authorization↓
05MongoDB and Socket.IO

04 · Technical decisions

01

Verify before a patrol begins

A guard confirms the assigned location and scans a QR code before starting. This ties a shift to the right place instead of relying only on a manual check-in.

02

Validate checkpoints in sequence

Checkpoint scans follow the assigned route order. The workflow makes patrol completion verifiable while remaining straightforward for guards in the field.

03

Keep updates immediate and access controlled

Socket.IO updates the administration dashboard without a refresh, while JWT authentication and route-level authorization separate guard and administrator actions.

05 · Project targets

2role-based workflowsQR + GPSshift verificationLivepatrol and SOS updates

These are design targets and project measures, not claims about production usage.

Challenge

The hardest part

The difficult part was connecting many related workflows without making the guard experience heavy. Authentication, location checks, ordered QR scans, attendance, SOS alerts, and approvals all needed to share consistent shift data.

Tradeoff

The choice I made

Accountability mattered, but adding too many steps would make the system harder to use in the field. I kept common guard actions focused while placing monitoring and approval controls in the administrator workflow.

Lesson

What I learned

This was the first project where I independently designed the complete system. It taught me to think about how different users move through a product, how data travels between features, and how small workflow decisions affect real-world usability.

06 · What I would build next

The next
iteration.

01

Offline-first patrol capture

02

Escalation policies by site

03

Attendance and patrol analytics