A relationship connects records through identity. In a one-to-many design, the child can hold a lookup to its parent. A copied display label may help reading, but it cannot guarantee that two records refer to the same entity. Names can change or repeat.
Decide when the relationship is required and how retirement affects historical records. An unknown owner at intake might be allowed while an unowned review request is not. Deletion and cascade policies need separate review in a real environment. The local model uses simple field values and executable views, not complete Dataverse relationship metadata. These tasks pair conceptual decisions with checked unassigned and department populations.