The asset has a record — so does the operator

The functional category is a choice from six fixed values: machine operator, services driver, delegate, site supervisor, maintenance technician, and other — and the whole system matches on exactly these, so the operator list on a machine's edit screen shows only the machine-operator category. The free descriptive job title is a separate display-only field, so a spelling slip in it can never break a match. Unknown legacy categories settle automatically into the other category with their wording preserved, so no employee disappears over an old label.

Delegate lists in movements, operator lists in daily inspection and in linking a machine to its operator, technician lists in maintenance reports — all read from this register alone, with no side tables managed separately. Even the legacy lists that predate the module migrated in automatically without duplication, matched on names beyond spacing differences in writing. Correct a name once, and it is correct everywhere it appears afterwards.

A ready spreadsheet template imports the entire team at once: whoever has a job number keeps it, whoever lacks one gets a number generated in a sequence that never collides with earlier ones, and re-uploading the same file updates existing records instead of duplicating them, returning a summary of what was inserted, updated and skipped. A non-matching category does not reject the row — it settles into the other category carrying its title, so nobody falls through on the way.

Each employee is assigned to his project and appears within its scope on project-bounded screens; the list offers search by name, filtering by category and project, and bulk re-categorization of a selection at once. The limits are declared without ambiguity: an operating register of who works, in what capacity, on which project — not payroll and not financial time-attendance — and vehicle custody with its signed forms is managed in the vehicles module, not here.