Make the workflow visible.
Organize the system around the actions people actually take, not around a database diagram.
Desktop Operations2024Logistics & Back Office
Fleet-X Office Operations Suite
A Windows operations suite for attendance, employees, carriers, invoices, payments and reporting across an internal logistics office.
01 / CONTEXT
Behind every screen is a job someone is trying to finish.
A C# WinForms business application developed to centralize internal office workflows. The suite includes administrator and employee dashboards, attendance logging and corrections, employee timing and short-leave workflows, carrier and driver management, invoice management and printable reporting, payment calculations, RPM tools and operational reports. SQL Server and Dapper provide the data layer, while ClosedXML and reporting components support spreadsheet and document workflows.
DISCIPLINEDesktop Operations
INDUSTRYLogistics & Back Office
STACKC#, WinForms, .NET Framework, SQL Server, Dapper, ClosedXML, RDLC/ReportViewer
YEAR2024
02 WHAT THE BUILD NEEDED
Protect the boring parts.
Validation, permissions, state and recovery are what keep useful software useful.
Leave room to change.
The first release should solve today without trapping the business tomorrow.
03 SYSTEM ANATOMY
Useful software is a stack of
decisions.
Interface, rules, data and operations have to agree with each other. A clean screen cannot compensate for a broken state model.
INTERFACEWORKFLOWRULESDATAHANDOVER
04 / HANDOVERThe build should remain
The build should remain
understandable.
Deployment, operating assumptions and important technical decisions should not live only in the head of the person who wrote the code.