Plan the workflow
Defined request stages, roles, status changes and the data structure before development.
Case study / 01 · Systems
Turning a manual process into a workable system.
An internal PHP and MySQL application for equipment requests, reservation visibility, approvals and operational records.
01 / THE CHALLENGE
What needed to change.
Employees needed to see when equipment was available before submitting requests. Administrators needed a consistent way to review, track and export records.
02 / MY CONTRIBUTION
From requirements to delivery.
Build both experiences
Developed employee forms, availability checks, confirmations, and a separate administrative interface.
Prepare for operation
Tested date conflicts, status handling and exports; prepared user and administrator guides.
03 / DESIGN DECISIONS
Choices made for actual use.
Availability before submission
Make conflicting bookings visible before users invest time in a form.
Separate admin workflow
Keep employee tasks simple without removing control from administrators.
Documentation is part of delivery
Operational teams should be able to use the system without relying on the developer.
04 / OUTCOME
What this work delivered.
A single process for requests, reviews, cancellations, tracking, asset administration and reporting. The public KITAXIS demo uses fictional data and is not the production system.
The linked public demo is an independently prepared example using fictional data.