A wildlife reserve's HR system fails when it treats rangers the same way a corporate office treats desk workers. The logistics are different. The posting is remote. The staff covers both NPR and ZimParks units. Uniform sizing matters operationally — a ranger who can't get replacement boots in the right size isn't a minor administrative inconvenience, it's a readiness problem. The Sables system exists because cash bonuses don't always reach the field in time, and motivating rangers who are six weeks from the nearest town requires something they can redeem locally.
The Catalogue That Makes Incentives Work
The catalogue items database is the consumer end of the Sables incentive system. Each entry holds a Catalogue Items name and a Value of Catalogue Item — the Sables cost to redeem it. The linked Ranger Directory field connects each redemption to a specific ranger record, which is how Sables spent this month and Total Sables spent stay accurate without any manual reconciliation.
The clean design is that the catalogue and the staff directory are bidirectionally linked. When a ranger redeems an item from the catalogue, the Sables balance in their staff record updates through ft_lookup fields. Sables remaining calculates as Total Sables earned + Total adjustments - Total Sables spent. No manual totaling, no end-of-month reconciliation worksheet.
The $USD Value of total Sables spent field converts point activity into actual monetary equivalency — which matters for budgeting the incentive program, and for demonstrating the real-world value of the reward to rangers who are earning points.
The Staff Record That Covers the Whole Person
The Ranger Staff Directory carries more data per person than most corporate HR systems. It captures the standard identity fields — Name, ID Number, Works Number, Rank (nineteen options from Private through Senior Ranger, Ecologist, and Trainer), Division, Birthday with an auto-calculated age, and Next of Kin. It also stores employment contracts and service files directly in the record.
The anthropometric profile is operational, not administrative. Neck Size, Chest Size in both inches and centimeters, Arm Length, Waist Size, Inside Leg, Shoe Size, and Hat Size exist because a ranger who needs to be fitted for replacement field kit in a remote posting can't wait for the supply chain to guess their measurements. When a procurement order goes out for uniform replacements, the admin pulls sizes directly from the database rather than waiting for rangers to respond to a measurement survey.
Relatives at the station is a self-referential entries field that links to other records in the same Ranger Staff Directory. It exists because having two family members in the same unit affects posting decisions, emergency notifications, and sometimes disciplinary handling. That relationship is operational context, not just biographical trivia.
When the Wage Line and the Fine Line Collide
The remuneration section is direct: Current monthly wage minus Fines this month equals Total to pay this month. The Fines this month field is a lookup from a separate transactions table — fines are recorded as events, not manually edited into the wage record, which means the history is preserved rather than overwritten.
The Service notes (include reporter's name) richtext field is where the career narrative lives — disciplinary actions, commendations, cross-postings, incident involvement. The instruction to include the reporter's name is a governance measure: any note added to a ranger's record is attributed. When a dispute arises about a service record entry, the record shows who wrote it and when.
Dismissed/Transferred is a boolean that lets the directory distinguish active from inactive staff without deleting records. A ranger who transfers to ZimParks is still in the database, still has their historical Sables data, and still has their service record intact — they just filter out of active headcount views.