Our general practice is to label our fields for each tenant. So if you were department A, the field would be called "A - Report Type". This, of course, is less than ideal, especially for outward facing forms. We also have a problem where we have generic field names (ex. "Type" "Report Type" "Category") that one tenant has already claimed, so we have to get creative and come up with a variation because we have different field values that are needed. There's a great idea on the Idea Exchange to redesign the custom fields so they have different names in the backend vs frontend. That way, you could have multiple fields with the same "literal" name (Type, Report Type), but different backend names. Currently, the literal is the same as the backend name.
https://support.workfront.com/hc/en-us/community/posts/115006012627-Have-separate-Field-API-Names-vs... Vincent Goodwin The Capital Group Companies