What Happens When You Build a Real Management System Without Any Frameworks

Esandu Hansaka Epa — Sat, 02 May 2026 15:37:00 +0000

Running a cricket academy is much more than registering players and scheduling a few events.

The real challenge is in the daily flow of operations.

Who manages player records? Who handles staff coordination? How are training sessions scheduled? How do coaches and trainers work with different responsibilities? How do players view their sessions, progress, and bookings?

That is the idea behind the project I built: a multi-role Cricket Academy Management System designed to support the real workflows of an academy through one connected platform.

This is not just a basic management website with a login screen and a few forms.

It is a role-based system where each user sees a different side of the academy.

Admin : Manages overall system
Coach : Players & training
Trainer : Fitness & structured sessions
Player : Sessions & schedules
Shop : Shop & Rentals

Why I built this

I wanted to build something that felt closer to a real-world software product.

Many projects stop at simple CRUD operations, but real systems are shaped by user responsibilities. A cricket academy is a good example of that — it has multiple people doing different kinds of work, and all of them depend on organized information.

In this project, I focused on building a system where:

each role has its own dashboard and workflow
sessions are a core operational feature
staff and players interact with the system differently
scheduling and management feel practical, not just visual
separate modules still work together as one product

The main idea behind the system

At the heart of the platform is the idea that an academy runs on coordination.

And one of the biggest parts of that coordination is sessions.

SESSIONS CONNECT EVERY PART OF THE SYSTEM

Admins manage the overall structure and scheduling
Coaches and trainers conduct and oversee sessions
Players depend on session visibility and participation
Scheduling affects both staff and academy resources

Because of that, session management becomes more than just showing a timetable. It becomes one of the main ways the system reflects real academy operations.

What this series covers

Each post will focus on one role: what that role does in the system, what features are available to them, how the interface supports their responsibilities, and how that role connects with the larger academy workflow.

What makes this project different

This project was designed with a role-first mindset.

Instead of only thinking about features page by page, I focused on questions like:

Who creates and manages sessions?
Who needs to see upcoming schedules?
Who is allowed to manage staff or players?
How should different dashboards behave for different users?
How do we keep the system useful for both management and daily operations?

That approach made the project more realistic and much more meaningful to build.

Technologies Behind the Project
This project was built completely using pure PHP, HTML, CSS, and JavaScript without relying on any frameworks. I wanted to focus on understanding the core logic behind a multi-role system by building the structure, routing, backend handling, and frontend behavior more directly.

Pure PHP for backend development
MySQL for database management
HTML, CSS, and JavaScript for the user interface
MVC architecture for clean project organization
Chart.js for analytics and dashboard charts
Email integration for notifications and account-related communication
PayHere for online payment processing
XAMPP for local development and testing

What you can expect from this series

In the next five posts, I'll break the system down role by role and show how each user interacts with it.

This series will be useful if you are interested in:

multi-role application design
role-based dashboards
session and schedule management systems
practical web application structure
building software that reflects real workflows
full scratch web dev

A management system is not only about storing data. It is about supporting people in their responsibilities and helping different parts of an organization work together smoothly. For this system, sessions became one of the strongest examples of that idea.

In the next post, I'll start with the Admin role and show how the central management side of the academy works.

If you are building something similar or have questions about multi-role system design, drop a comment below.

DEV Community: Esandu Hansaka Epa

What Happens When You Build a Real Management System Without Any Frameworks