Create a useful field dictionary
Course overview · 4 min reading + 12 min practice, estimated
Principles and method
For each field, define meaning, type, allowed values, owner, source and update rule. Distinguish unknown from no and not applicable. Dates need clear semantics: created, observed, effective and last verified are not interchangeable. Avoid overloaded fields such as status that mean different things in different teams. Required fields should be necessary at the stage they are demanded, otherwise staff invent values to proceed. Use controlled vocabularies where consistency matters and free text where nuance is essential. Record units for numerical fields such as compensation.
Worked example
A salary field stores 60 without currency or period. The revised design separates amount, currency, annual or hourly basis and whether it is expectation, advertised range or agreed offer.
Put it into practice
Define ten fields for a vacancy and application, including missing-value rules.
Use fictional information and keep your work in your own notes.
Compare your approach: self-review guidance
Every field should have one meaning and an owner. Include units and source dates where needed. Remove required fields that cannot legitimately be known at initial research.
Sources and further reading
Original Academy teaching and fictional examples. These references provide context, not endorsement. Edition 2026.09; updated 2026-09-24.
- GOV.UK: Responsible AI in recruitment
UK guidance on procuring and deploying recruitment AI.
- NIST: AI Risk Management Framework
Voluntary framework for organising AI risks and controls.