Dawami
An in-development attendance and HR system with check-in/out, leave workflows and balance calculations, and shift scheduling; offline operation, broader reporting, and document management remain planned work.
- Problem
- Attendance and leave become difficult when shifts cross midnight, policies vary, and approvals need a defensible history.
- Approach
- The current build centers attendance, leave approvals, balances, and schedules in one API. Audit history and offline operation are design goals, not completed capabilities.
The problem in context
Attendance and leave stop being simple timestamps when shifts cross midnight, policies vary, and managers need to review earlier decisions. A useful system has to keep calculations and approval states consistent without presenting planned controls as finished.
Who it is for
The current build supports employees checking in and out, managers reviewing leave requests, and HR teams working with balances and schedules. Document management, broader reporting, and offline operation remain planned work.
One decision being tested
Attendance, leave approvals, balances, and schedules use one API contract. The build is testing that shared model before broader history and reporting capabilities are added.
Current boundary
Audit history and offline operation are design goals, not completed capabilities. Location validation and the wider operational controls also require further production work before they can be presented as launch-ready.
Have something to build?
Email us in Arabic or English, whichever is easier, or call us directly.
Contact detailsDirect contact
- contact@jiwar.io
- +962 7 9174 8028
- Amman, Jordan