Product
One record per person. Everything else hangs off it.
Most HR tools are five products sharing a login. Luwawa is one employee record that every other part reads and writes.
The record
What one employee holds.
Created before the person joins, linked to a login on acceptance, never duplicated downstream.
- Employment
- Position, department, manager, employment type, start date, work email.
- Compensation
- Base salary, pay frequency, currency, effective from. Restricted to owners and HR.
- Banking
- Bank, account name, masked account number. Encrypted, audited on every reveal.
- Leave
- Balances per leave type, accrual, history and the current request queue.
- Equipment
- Items issued, asset tags, condition and the full custody history.
- Documents
- Contracts, payslips and anything HR attaches to the person.
- Account
- Whether a login is linked, the platform role, and when they joined.
Structure
Nobody draws the org chart.
Set a manager and the tree follows. It is the same field the approval chain reads, so the chart and the routing cannot disagree.
Nkhata Group, derived from the manager field
- Yamikani Nyirenda Managing Director, Executive
- Lusungu Mwale Finance Director, Finance
- Thoko Banda Senior Accountant, Finance
- Mphatso Kaunda Accounts Assistant. Invitation pending, starts 01 Aug 2026
- Thoko Banda Senior Accountant, Finance
- Chikondi Phiri Operations Lead, Operations
- Tamandani Gondwe Field Technician, Operations. On leave
- Lusungu Mwale Finance Director, Finance
Someone with no manager set routes to HR. That is a deliberate default rather than an error state, because a managing director still needs their leave approved.
Equipment
Who has the laptop, and who had it before.
Each item keeps its history instead of a current-holder column that overwrites itself. When something goes missing, the record says when it changed hands and in what state.
Asset NKG-LT-0142, MacBook Air 13 inch
Hiring
A pipeline your hiring managers will actually open.
Stages you configure, structured reviews, applicants assigned to named people, and an event trail on every application.
Accounts Assistant, Finance
- Alinafe ZimbaApplied 12 Jun
- Grace TemboApplied 12 Jun
- Isaac MvulaApplied 13 Jun
- Chisomo NkhomaWith Thoko Banda
- Patience JereWith Thoko Banda
- Blessings KumwendaSecond round, 24 Jun
- Yamikani BandaFirst round, 25 Jun
- Limbani ChirwaSent 04 Jul, awaiting reply
- Mphatso KaundaRecord created 10 Jul
Hired is not the end of the row. Moving an applicant to hired is what creates the employee record, which is why the same name appears on the org chart above.
Modules
Five ways in.
People
Records, departments and a derived org tree
Positions, reporting lines and an org chart that comes out of the manager field rather than being drawn by hand.
Requests
Leave and expenses, one approval chain
Leave types and balances, expense categories and receipts, a manager queue and an HR payout step.
Payroll
Deduction rules, pay runs and payslips
Rules as dated data, runs that freeze on approval, payslips branded from your company settings.
Equipment
An asset register with custody history
Issue, return, condition and fault reports, tied to the person rather than to a shared spreadsheet.
Hiring
Job board, pipeline and a candidate portal
Per-job application forms with no candidate login, a configurable pipeline, structured reviews, and applicants who track their own submissions.
Not yet
What Luwawa does not do.
No performance review cycle, no time and attendance clocking, no shift rostering. If your operation runs on those, Luwawa is not the whole answer today.