SAFE RESOURCES LTD SECURITY MANAGEMENT SYSTEM V6
==================================================

BASE
----
V6 is built from the supplied working V4 package. Existing guards, posts, clients,
deployments, roster and attendance code are preserved.

INSTALLATION
------------
1. BACK UP your current security_management database in phpMyAdmin.
2. Import database/update_v6.sql into the EXISTING security_management database.
3. Replace the application folder with this V6 package.
4. Keep the project folder name security_management_system unless you change BASE_URL
   in config/config.php.
5. Open http://localhost/security_management_system/public/

DO NOT import database/security_management.sql over your existing production data.

NEW V6
-------
- Professional responsive topbar; sidebar removed.
- Operations dropdown: Guards, Posts, Clients, Deployments, Roster, Attendance, Reports.
- Finance dashboard: Invoices, Salaries/Payroll, Expenses, Revenue Estimations.
- Day/Night post coverage checker.
- Understaffed and overstaffed post detection.
- Roster page shows coverage before operational use.
- Finance tables for invoices, salaries, expenses and revenue estimates.
- Audit logs, leave requests, incidents and equipment tables ready for expansion.
- Bank-account cleanup removes common bank-name suffixes accidentally stored after
  account numbers while preserving the Bank Name field.
- Dashboard command center with operational and finance indicators.
- Existing pagination maximum remains 10.

ROSTER SAFETY
-------------
A generated roster uses active guard deployments and assigns one OFF day per active
guard. The V6 roster screen separately checks each post's active Day/Night deployment
against its configured requirements. Management should resolve red/amber coverage
alerts before treating the roster as final.

IMPORTANT
---------
Salary statutory rates, VAT/PAYE/NSSF rules, contract billing policies and official
company document details are intentionally configurable. Do not hard-code statutory
rates without confirming the current company/accounting rules.

PRODUCTION BACKUP
-----------------
Before every database migration or major deployment, export security_management from
phpMyAdmin and keep at least one dated backup.
