What Tanzania HRMS actually does.

Every authenticated screen lives under /admin, behind one shared login. There is no public area and no mobile app — this is purely an internal system of record.

What it manages

The full employee lifecycle and the money that flows from it: employee master records, branch/department/designation structure, leave entitlement and approval, payroll from payscale through payslip, KRA-based performance appraisal, statutory and management reporting, a per-employee document library, and database backup.

Why it exists

Five rules are specific enough to this organisation that generic HR software couldn't have met them:

5. A formal, bank-style appraisal instrument — fixed self-assessment questions, KRA attributes scored out of 10, and separate reporting/review-authority scoring.

Who uses it

Every feature below was traced from a route through its controller to its models and views. Class labels: Core, Supporting, Admin, User, Automation, Integration, Reporting, System.

Authentication & accountRestrict the system to active employees and force a password change off any seeded credential

Errors are verbatim from the code, typos included: “You Account is deactived”, “The provided credentials do not match our records.”

Roles & permissionsA custom implementation — Spatie's package is not used

Employee managementOne record drives leave, payroll, payslip template, tax treatment and appraisal routing

Onboarding is a multi-step wizard: each step saves its slice and hands back the next URL. The employee id (emp-<year>-<count+1>) is generated on step 1 and used to address every later step.

LeaveBalances feed directly into net pay via loss-of-pay days

PayrollTurns a standing salary structure plus a month's events into net pay and GL postings

Performance appraisalA three-stage KRA-based cycle: self-assessment → reporting authority → final authority

Documents

Files move to public/assets/document/ under their original filename — a later upload with the same name silently overwrites the earlier one.

Self-service profile16 screens under Personal Information & Personal Profile — visible to everyone except the Managing Director role

Master data

Reporting

Three different financial-year conventions are in use across these reports — see Business Rules § Financial year.

System & operations

Access is decided by three independent mechanisms that must be read together: permission gates (what the menu shows), hard-coded role-slug checks (what data scopes actually return), and the isemplooye() helper (self-service vs. everyone's-records views).

The six permission audiences

The permission catalogue targets six audiences. Only three of them (admin, hr_head, employee) are actually carried by a seeded role — see the risk register.

Row-level visibility

*Conditional on the HR head's role slug matching what the scope actually tests — flagged in the risk register.

Default administrator

Six representative journeys, each traced route → controller → model → database/UI. The full documentation set covers 18; these carry the most operational weight.

Seeded leave entitlement

Status vocabularies

Appraisal category bands

Financial-year conventions

The system uses three different financial-year windows depending on the report — there is no single canonical year.

Twenty-five items in the underlying documentation could not be settled from the repository alone, or show the code contradicting its apparent intent. The ten highest-priority items, ranked by the coverage report:

Generated from a full pass over routes/, app/, database/ and resources/views/ — 68 controllers, 74 models, 71 migrations, 23 seeders, 7 traits and 264 Blade views.

Confidence distribution

What this document does not cover

Before publishing to end users

Query the live roles, permissions and employees tables to resolve the role-slug mismatch and the employment-type inconsistency — these determine whether the role matrix and payroll behaviour described here match production. Confirm whether the DomPDF removal and disabled TTUM generation are intentional before documenting either as working.