From one person's private Excel file to a shared, version-controlled tracking system for the whole Traffic Department.
Vehicle positions across warehouse, shed, and yard were recorded in one person's personal Excel file — invisible to everyone else. When that person was unavailable, the whole team lost visibility, creating bottlenecks and a single point of failure.
Mongla Port Authority's Traffic Department — everyone who needs current vehicle positions, not just the one person who used to own the spreadsheet.
Terminal locations don't guarantee reliable connectivity, so it had to work offline-first. No budget or infrastructure for a hosted database. Needed a real history of position changes, not just a current snapshot.
Offline-first PWA tracking 8 port locations, a Bangladesh Government Holiday Calendar loader, a Chart.js analytics dashboard (7 charts + KPIs), 13 report sections, and Excel export.
Used a private GitHub repo as the data store instead of standing up a database — every write becomes a version-controlled commit, which gives a full audit history for free with no database to host or maintain. PWA + offline-first because terminal connectivity isn't guaranteed.
Replacing a single Excel file with a shared system without introducing a point of failure worse than the one it replaced — the Worker-proxied sync had to be reliable enough that staff would actually trust it over the spreadsheet they already knew.
Now the Traffic Department's shared, version-controlled tracking system — the single-person Excel dependency it replaced is gone.
Version control can be the actual data layer, not just for code — the "no budget for a database" constraint led to a genuinely different, defensible architecture rather than a compromise.