Adobe Acrobat DC 2015 (classic): lock on file server set by read-only users access prevents write access

I'm adding comments to our customer's requirements documents and publish these PDF on our internal file server. Only I have write access. Others may apply for read access.

At actual documents many colleagues are reading at the same time. At the same time I try to add the latest comments to the document to provide best practice information and similar.

Unfortunately the read access of the read-only users blocks the write access.

At very new documents or if the document is used for an actual project I've to save the PDF at a different name like this (with an underscore added):

documentsname_.pdf

Often the day ends with 2 or 3 underscore characters added to some PDF. This messes our server and confuses the readers.

I've discussed this issue with the responsible for the file server. He says that locking depends on how the application opens the file.

Office documents can be opened in read only mode or write protected until a password input for example.

Proposal:

Would it be possible that at file opening Acrobat firstly checks for write protection at the location?

If the file location is write protected the Acrobat releases the file immediately when it's displayed on users screen.

But if the user has write access the file will become locked as at present.

Would this be possible? Is there a work around without changing to Office document's format or distribution by web server?