Manadeeb
Manadeeb (مناديب — "delegates") is a delivery-rider ERP built for operations running hundreds of riders. It replaces spreadsheet-and-WhatsApp workflows with a real system of record: a rider registry, shift attendance measured planned-against-actual, per-rider performance scorecards, and an audited approval trail for assignments and dismissals. Arabic-first with RTL throughout, and access scoped down a three-tier geography — governorate, area, zone. Rider management ships first; finance, inventory, and HR modules follow.
- Rider registry, shifts, and per-rider scorecards in one system of record
- Daily spreadsheet ingest with deduplication and one-click rollback of a bad upload
- Nine roles, each scoped down a governorate → area → zone hierarchy
- Audited approval trail for assignment and dismissal requests
- Arabic-first interface, RTL throughout
- Django
- DRF
- PostgreSQL
- Next.js
The problem
A delivery operation running hundreds of riders runs on spreadsheets and WhatsApp. One file holds the riders, another holds the shifts, a supervisor keeps a third, and the numbers reconcile roughly once a month if someone has time. Attendance is what a supervisor remembers. Performance is a feeling. An assignment or a dismissal happens in a message thread and leaves no record anyone can point at later.
None of that is laziness — it is what happens when headcount outgrows the tools and nobody can stop to replace them. The cost shows up as disputes nobody can settle, payouts nobody can audit, and decisions that cannot be defended when they are questioned.
A system of record
Manadeeb (مناديب — "delegates") replaces that with one place the answer lives. A rider registry instead of several files. Shift attendance measured planned-against-actual, so the gap between the roster and the day is a number rather than an argument. Per-rider performance scorecards built from what the system already holds, not from a supervisor's recollection.
Assignments and dismissals run through an audited approval trail. That is the feature operations teams ask for second and value first: not preventing the decision, but making it reviewable afterwards by someone who was not in the room.
Access is scoped down a three-tier geography — governorate, then area, then zone — across nine roles. An area supervisor sees their area. The hierarchy is in the permission model rather than in a convention people are trusted to follow.
Meeting the operation where it is
The spreadsheets do not disappear on day one, so the system ingests them daily, deduplicates, and lets a bad upload be rolled back in one click. A migration that demands the old process stop before the new one works is a migration that gets abandoned in week two.
Arabic-first with RTL throughout, because the people entering the data work in Arabic. Built on Django, DRF and PostgreSQL with a Next.js front end. Rider management ships first — it is the part that replaces the spreadsheet everyone is actually fighting with — and finance, inventory and HR are sequenced behind it rather than built in parallel and launched late. Manadeeb is the studio's own product and is in build.