Has anyone else come across the inefficiency created when a collection has publishing workflows enabled, and a non-publishing verifier submits a ‘request to publish’, the card is not automatically verified upon publishing? Like it normally would for collections without publishing workflows enabled.

Understanding that the reason is likely because the publishing user opens in draft mode so they have the opportunity to change the content without the verifier knowing. Is there a way while publishing for the system to run a check for updates in content and if no updates were made, auto-verify? 

Interim workaround - encourage publishers to immediately request verification after publishing because there would also be no automatic notification when a card is published (by a non-verifier publisher).