Structured reporting
Lost and found items can be recorded with useful identifiers such as type, colour, size, make, label and badge number.
Case study · PHP and MySQL web application
Lost Property Management System for schools.
A role-based application designed to help administrators, students and parents report, search and manage lost property through a structured, database-backed workflow.
Project overview
A structured alternative to manual lost-property administration.
Manual lost-property management can create significant workload for schools. Found items need to be recorded, stored, searched and matched with students or parents who report or claim them.
LPMS was developed as Adrian Iscru’s final Open University project. It brings reporting, database search, controlled access, administrative management and change logging into one browser-based system.
See the User JourneysThe problem and solution
Designed around the people and tasks involved.
Controlled search
Users search using relevant item details rather than browsing the entire database of reported property.
Role-based access
Administrators, students and parents receive different permissions and dashboard options according to their role.
Item matching
The application can retrieve a possible item match when the appropriate combination of identifying details is provided.
Administrative tools
Administrators can view and update records, change item status, manage users and oversee the wider item register.
Accountability
Changes can be logged so the system records who made an administrative update and supports clearer internal accountability.
User journeys
Different access for different responsibilities.
01 / NEW VISITOR
Register or log in
New visitors can choose Login / Register or Get Started, provide student details and a badge number, then access the system. Existing users can log in or recover a password.
02 / STUDENT OR PARENT
Report and search
Students and parents can update their profile, report a lost item and search for a possible match while being prevented from browsing the complete item database.
03 / ADMINISTRATOR
Manage records
Administrators can search and view all items, report new items, edit records, update statuses, manage users and review the history of changes.
Project screens
Landing page, dashboards, search and performance evidence.
The screenshots show the LPMS interface, including its landing page, role-based dashboard, item search, reported-item management and a historical PageSpeed Insights result.
Development work
A practical application built around data, permissions and workflow.
PHP and MySQL development
Built a database-backed web application using PHP scripting and MySQL to store users, item records, reports, searches and status updates.
Authentication and permissions
Created role-based access so administrators, students and parents received appropriate access to the application and its records.
Search and matching logic
Designed the search process around combinations of relevant item details, helping protect data while supporting genuine item claims.
Administrative interface
Built screens for viewing all items, editing records, updating item statuses and managing user accounts within the system.
Audit trail
Included change logging so administrative updates could be traced, supporting accountability in the management process.
Responsive web interface
Created a browser-based interface designed around clear navigation, accessible tasks and the needs of users working across different devices.
Application logic
From reported item to a controlled search process.
The system was built to support a more orderly process, rather than simply publishing a public list of lost items.
01
Register or authenticate
Users register with relevant student details or log in to access the role-appropriate dashboard.
02
Report or search
Users can report an item or enter a combination of identifying information to look for a possible match.
03
Match and manage
Relevant records can be retrieved for a legitimate search, while administrators manage item status and related data.
04
Record changes
Administrative actions are logged so record updates can be traced to the responsible user.
Historical performance evidence
A fast, lightweight landing-page result.
The supplied PageSpeed Insights screenshot records a desktop performance score of 100 for the LPMS landing page in the displayed historical test.
100Historical PageSpeed Insights desktop performance score shown in the supplied screenshot.Project notes
What LPMS was designed to demonstrate.
This project combines database-backed functionality, controlled access and a practical workflow for a defined school-administration problem.
Who could use the system?
LPMS was designed for school administrators, students and parents, with different actions and access levels assigned to each role.
Could ordinary users see every lost item?
No. Students and parents could search for a possible match using identifying details, but they were not intended to browse the full database of reported items.
What could administrators do?
Administrators could search, report and view all items; edit records; update item status; add or edit users; and review logged changes.
What technology was used?
The application was built with PHP and a MySQL database, supported by a browser-based HTML and CSS interface.
What does the PageSpeed screenshot represent?
It is a historical desktop PageSpeed Insights result for the displayed LPMS landing page. Results can vary by test conditions, device, browser, server and later code changes.
Need a practical digital tool?
Discuss a web application built around your workflow.
Start by defining the users, the problem, the data and the actions your application needs to support.