My apology for question not being clear, as any perfectly formulated question by itself shows an answer.
Im designing database in SQL Server. Not taking into consideration all other Entities, I have two. One entity is "Document" another "Operator".
I have three relationships from Document table to Operator Table. Each stage on document can be filled by different Operators/People.
1) Is it ever done and considered "Good Practice", elegant?
2) what are better alternatives?
3) would design matter if I had two relationships, or ten relationships?