Updating App - Suggestions on table/form design best practice?

I am updating an app I previously created and trying to implement some better "best practices".
One of the areas I am focusing on is better use of intermediate tables, aka Many-to-Many.

My previous app had a part of it set up as follows:

• Tables
  • Work Orders
  • Clients
  • Contacts
• Relationships
  • Clients < Contacts
  • Clients < Work Orders
  • Contacts < Work Orders (x8)

In my contacts table, there are several different types of contacts, e.g. VP, AVP, Supervisor, Manager, Specialist, etc.
In the main Work Orders form, I have 8 drop downs, each stemming from one of the 8 Contacts<Work Orders relationships, and each representing one of the different contact types. Each dropdown is conditionally reliant upon the client selected in the Work Orders form.

I was curious if there was a better way to do this, perhaps using a M:M relationship, maybe a table between Contacts and Work Orders, .... however thinking through this, I would still need to have 8 dropdowns, one for each contact type .... would it really add any benefit using a M:M table in that scenario, or should I leave it as I previously had it ????

Thanks for your input and suggestions ... I appreciate them ...

------------------------------
Andrew
------------------------------