One structured path for submission, review, status management, and tracking.
Turning a fragmented manual process into a structured business system.
An internal PHP and MySQL application developed to digitize equipment requests, reservation visibility, approvals, status tracking, asset administration, and operational reporting.
Users can check existing equipment reservations before creating a request.
Administrative actions are separated from the employee-facing request experience.
User and administrator manuals support non-technical daily operation.
The Situation
The request process needed to become easier to use and easier to manage.
Users needed a clearer way to submit equipment requests and understand availability, while administrators needed stronger control over application status, records, and assets.
I handled the project from requirements planning and workflow definition through interface design, PHP and MySQL development, validation, testing, administrative functions, documentation, and operational preparation.
The Challenge
Three operational problems shaped the system.
The goal was not simply to digitize a form. The application needed to support both the employee experience and the administrative workflow behind it.
Limited reservation visibility
Users needed to understand when equipment was already reserved before submitting a new request, reducing conflicting or duplicate applications.
Manual approval handling
Administrators required a centralized way to review applications, update statuses, record notes, and manage approvals and rejections.
Operational handover
The system needed clear user and administrator manuals so non-technical staff could operate it without depending on the developer.
System Anatomy
One workflow, viewed from four operational angles.
Select a module to see how the employee experience, application logic, administration, and reporting fit together.
Selected Module
01 / Request
Give employees a clear path from availability to submission.
Users select equipment, enter the requested period and purpose, review the information, and submit through a structured multi-step request flow.
- Equipment selection
- Requested period and purpose
- Reservation visibility
- Confirmation before submission
02 / Application
Keep validation, status, and request history inside one application layer.
The system manages submission handling, validation, request status, date behavior, reservation logic, and the information required for later review.
- Validation and error handling
- Status transitions
- Date and reservation logic
- Request history visibility
03 / Admin
Give administrators the controls required for daily operation.
Administrative interfaces support request review, approval, rejection, cancellation, notes, user management, and equipment record maintenance.
- Request review
- Approval and rejection
- Notes and status management
- User and asset administration
04 / Reporting
Make records usable beyond the application screen.
CSV export, filtering, and print-ready request details support practical administration and recordkeeping.
- CSV export
- Filtering
- Print-ready request details
- Operational recordkeeping
My Ownership
Full-cycle responsibility from requirements to operational readiness.
I designed both the employee-facing request experience and the administrative workflow required to review, manage, and report on applications.
-
01
Requirements
Define the workflow before building it.
Defined the request flow, user roles, administrator actions, status transitions, reservation logic, and required data.
-
02
Architecture
Design the data and application structure.
Planned the structure for users, equipment records, requests, statuses, dates, notes, and administrative management.
-
03
User Experience
Build a predictable request journey.
Developed request forms, confirmation screens, submission handling, validation, status history, and reservation visibility.
-
04
Administration
Give administrators the right controls.
Built interfaces for reviewing requests, approving, rejecting, cancelling, adding notes, managing users, and maintaining equipment records.
-
05
Output
Support practical recordkeeping.
Added CSV export, print-ready request details, filtering, and status visibility.
-
06
Validation & Handover
Test the system and prepare people to use it.
Tested validation, permissions, request status behavior, date handling, and error conditions, then prepared separate user and administrator manuals.
Key Decisions
The system was shaped around operation, not around technical novelty.
Each decision was tied to a practical requirement: reduce ambiguity for employees, centralize control for administrators, and make the system maintainable after handover.
Visibility Before Submission
Show existing reservations before a new request.
Availability information appears early so users can avoid conflicting request periods before completing the rest of the form.
Role Separation
Keep the employee experience separate from administration.
Employee actions and administrator controls are organized around different responsibilities rather than forcing both audiences into the same interface.
Operational Independence
Documentation is part of the product.
User and administrator manuals were created so the system could be operated by non-technical staff without relying on the developer for routine tasks.
Validation & Delivery
The build was tested against the workflow, not just the interface.
Testing covered the conditions most likely to affect real operation: duplicate periods, date validation, permissions, status changes, exports, and administrative management.
- Request and date validation
- Reservation conflicts and duplicate periods
- Role and permission behavior
- Approval, rejection, cancellation, and status updates
- Export and print-ready outputs
- User and asset administration
- User and administrator documentation
Outcome
A single digital workflow for submitting, reviewing, managing, and tracking requests.
The result combines employee-facing request submission with the administrative controls required to operate the process consistently.
Centralized request submission
Reservation visibility by equipment
Approval, rejection, cancellation, and status tracking
User and administrator role separation
Equipment and user administration
CSV export and print-ready request details
User and administrator documentation
Skills Demonstrated
System thinking across design, development, and delivery.
- Requirements Planning
- Workflow Design
- PHP
- MySQL
- JavaScript
- Form Validation
- Administrative UI
- Testing
- Operational Documentation
Internal URLs, user records, equipment identifiers, database credentials, production data, security settings, and source code are not displayed. Certain workflow and implementation details have been generalized.