You shouldn't have that many processes that work in the same area, without knowing what is being done with each. Even in large development teams, 20 people, I haven't seen naming collisions get beyond test. We know that the same name is being used and someone changes.

This is team communication. Either you have a failing here, or an architectural failing that allows the same table to be used for two things.

If you have the need for a permanent table that you use for temporary storage, then you create a name. The name doesn't matter, but if you create it and only truncate or clear it, you easily know if it is there . If you are dropping tables, then there's no reason not to use a tempdb temp table.