Limited reservation visibility
Users needed to understand when equipment was already reserved before submitting a new request, reducing conflicting or duplicate applications.
Business System
An internal PHP and MySQL application developed to digitize equipment requests, reservation visibility, approvals, status tracking, asset administration, and operational reporting.
Overview
The system was created to make equipment requests easier to submit, review, approve, and track while giving users better visibility into existing reservations and application status.
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
Users needed to understand when equipment was already reserved before submitting a new request, reducing conflicting or duplicate applications.
Administrators required a centralized way to review applications, update statuses, record notes, and manage approvals and rejections.
The application needed clear user and administrator manuals so non-technical staff could operate the system without depending on the developer.
My Responsibilities
I designed both the user-facing request experience and the administrative workflow needed to review, manage, and report on applications.
Defined the request flow, user roles, administrator actions, status transitions, reservation logic, and required data.
Planned the data structure for users, equipment records, requests, statuses, dates, notes, and administrative management.
Developed request forms, confirmation screens, submission handling, validation, status history, and reservation visibility.
Built interfaces for reviewing requests, approving, rejecting, cancelling, adding notes, managing users, and maintaining equipment records.
Added CSV export, print-ready request details, filtering, and status visibility to support practical administration and recordkeeping.
Tested validation, permissions, request status behavior, date handling, and error conditions, then prepared user and administrator manuals.
Solution
Request Workflow
Users select equipment, enter the requested period and purpose, review the information, and submit through a clear multi-step flow.
Reservation Visibility
Upcoming reservations are displayed for the selected equipment so users can avoid conflicting request periods.
Administrative Control
Administrators can review request details, update statuses, record notes, manage assets, and maintain user accounts.
Documentation
Separate user and administrator manuals explain submission, review, approval, management, and common operating procedures.
Process
Reviewed the existing request process, user needs, administrative tasks, equipment management requirements, and common sources of confusion.
Mapped user and administrator responsibilities, request states, approval paths, reservation checks, and required system actions.
Implemented the database, request forms, confirmation flow, status pages, administrator interface, and management tools.
Tested duplicate periods, date validation, permissions, error handling, status updates, exports, and management functions.
Removed test data, prepared user and administrator manuals, documented the workflow, and supported operational review before launch.
Outcome
The system provides a single digital workflow for submitting, reviewing, managing, and tracking equipment requests.
Skills Demonstrated
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.