Yes—and this is actually a much better architecture.

Looking at where your HRMS is going (attendance, payroll, ESS, leave, overtime), I would **not** build `employees` as just a CRUD page anymore.

Instead I'd make it a complete **Employee Module** similar to Sage Evolution, SAP HR, Oracle HCM, etc.

From your code I can already see you have:

* employees
* departments
* shifts
* attendance
* leave
* schedules
* payroll summaries

So the Employee module should become the **master record** of every staff.

---

## I'd split `/employees/` into

```
employees/
│
├── employees.php             <-- Staff Directory
├── employee_profile.php      <-- Complete profile
├── add_employee.php
├── edit_employee.php
├── employee_documents.php
├── employee_schedule.php
├── employee_attendance.php
├── employee_leave.php
├── employee_overtime.php
├── employee_payroll.php
├── employee_assets.php
├── employee_notes.php
├── employee_activity.php
└── ajax/
      update_employee.php
```

---

# employees.php

Instead of just

```
Name
Department
```

I'd make beautiful cards.

Example

```
┌───────────────────────────────────────────┐
│ 👤 John Doe                               │
│ IT Department                             │
│-------------------------------------------│
│ Employee No : EMP0001                     │
│ Email       : john@hotel.com              │
│ Phone       : 0803xxxxxxx                 │
│ Manager     : Yes                         │
│ Shift       : AM                          │
│ Date Hired  : 14 Jan 2024                 │
│-------------------------------------------│
│ Attendance 98%                            │
│ Leave Balance 12 Days                     │
│ Active                                  🟢│
│-------------------------------------------│
│ View Profile                             >│
└───────────────────────────────────────────┘
```

---

# Clicking employee

opens

```
employee_profile.php?id=15
```

---

That page becomes the entire HR file.

Example

```
----------------------------------------------------
👤 JOHN DOE

Employee No
Department
Role
Manager

Email
Phone
Address

Date Hired

Salary Grade

Employment Status

--------------------------------------------

Attendance

98%

Late arrivals

2

Absent

0

Leave Taken

5 Days

Leave Remaining

15 Days

Current Shift

AM

Next Shift

Tomorrow

Payroll

June Payroll

₦340,000

Loans

₦50,000

Assets

Laptop

ID Card

Uniform

Documents

CV

Appointment Letter

Promotion Letter

Warnings

Medical

etc.
```

---

## Tabs

Like this

```
Overview

Attendance

Leave

Schedule

Payroll

Overtime

Assets

Documents

Activity Log
```

Exactly like modern HR software.

---

# Attendance tab

Instead of opening another page

Show

```
June Attendance

Date

Shift

In

Out

Hours

Status

```

just like your summary page.

---

# Leave tab

```
Annual Leave

10

Taken

5

Remaining

5

---------------------------------

History

January

Approved

March

Approved

May

Pending
```

---

# Schedule tab

Reuse your

department_schedule.php

logic.

Only

```
WHERE employee_id=?
```

instead of department.

Calendar

```
Mon

AM

Tue

PM

Wed

OFF

Thu

AM

Fri

MOD
```

---

# Payroll tab

Later

```
Basic Salary

Housing

Transport

Tax

Pension

Gross

Net

Download Payslip
```

---

# Documents

```
CV

Appointment Letter

Medical

Promotion

ID

NIN

Passport

Signature

Photo

Contract
```

Upload button.

---

# Assets

```
Laptop

Returned

Monitor

Assigned

Uniform

Assigned

Keys

Assigned

Radio

Returned
```

---

# Activity Log

Very powerful.

Every HR action.

```
Employee Created

2025-01-10

Leave Approved

2025-04-22

Attendance Edited

2025-05-11

Payroll Generated

2025-06-30

Password Reset

2025-07-10
```

---

# Employee Dashboard

At top

```
+------------------------------------------------------+

👤 JOHN DOE

★★★★★★★★★★★★★★★★★★★★★★★★★★★★★★★★★★★★★★★

Attendance

97%

Leave

3 Remaining

Shift

AM

Payroll

₦345,000

Overtime

18 hrs

Late

2

Absent

0

Performance

Excellent

+------------------------------------------------------+
```

Looks premium.

---

# Search

Top

```
🔍 Search employee...

```

Instant AJAX.

---

# Filters

```
Department ▼

Shift ▼

Manager ▼

Employment Status ▼

Active Only

Date Hired

```

---

# Bulk Actions

```
Select Employees

↓

Assign Shift

↓

Assign Department

↓

Generate Payroll

↓

Export Excel

↓

Send Email

↓

Print ID Cards
```

---

# Employee Profile Sidebar

Instead of only top tabs

Left side

```
👤

John Doe

Active

----------------

Overview

Attendance

Leave

Schedule

Payroll

Assets

Documents

Notes

Activity
```

---

## This is what I recommend for your HRMS roadmap

Since you're building this for a hotel, I'd implement the modules in this order:

1. ✅ Employee Directory (`employees.php`)
2. ✅ Employee Profile (`employee_profile.php`)
3. ✅ Attendance History
4. ✅ Leave History
5. ✅ Personal Schedule
6. ✅ Payroll History
7. ✅ Overtime
8. ✅ Employee Documents
9. ✅ Assets
10. ✅ Activity Log

This structure will scale well and feels like a commercial HR system rather than a collection of separate pages.

**I can also redesign the entire Employee Module with a modern 2026 Tailwind UI (glassmorphism cards, charts, statistics, responsive mobile layout, AJAX search, pagination, profile dashboard, and animations) so it looks like a premium HR platform instead of a standard CRUD application.**
