I wonder if Confluence even with non collaborative editing meets the requirements of an ISO QM standard without using additional addons, like Comala Workflows , Scroll Versions, etc. You always want to have a single person being responsible for a published version & not everyone should be allowed to publish a version. Collaborative editing & controlled ISO quality management simply don't work together. I suggest setting up a solution with collaborative editing enabled for draft / unpublished versions of a page (These are not the drafts handled by Confluence) & then having a review / publishing process of a single person responsible for ALL the changes made by the editors before. In this case there's no need for a complete audit trail of a Confluence draft page.

I completely agree with the comments above regarding the regulatory requirements and this being a roadblock.

As a technical writer, I need to be able to see who made a change so that I can follow up with the appropriate contributor for clarification when necessary. 

Tracking every change and maintaining subsequent version control is of at most importance to any organizations especially, if we have to be compliant with ISO standards.

This is a huge roadblock for us. We need to track each changes made to the page as per the compliance standards and we cannot upgrade to 6.x unless this is implemented.

We will not be able to upgrade to Confluence 6.x without the ability to have audit trail if each individual author.  This capability is needed to compliant with ISO standards. Please help us clear this road block.

All our stakeholders and customer value this feature as must have for next upgrade. We are waiting for this ISO compliance feature - please help us to implement this feature and clear the roadblock for our customers. Thanks!
 

This is an ISO compliance must have - please remove this obstacle.

At the last Atlassian Summit I met with several Atlassian customers in regulated healthcare and financial industries that have to fulfill auditing and e-signature requirements for any content changes.  Not capturing entire audit trail including editors/timestamp for collaborative editing changes essentially devalues Confluence 6.x product because it's not usable for these regulated contexts.  Controlled documentation is the primary use case for our Confluence instance which we have over 130K registered users and hate to be forced to explore alternative solutions to mitigate our risk if this is not fixed before 5.x EOL in June 2018.  I am a strong advocate and solution owner for Confluence at our company, but this issue is a huge roadblock for us.

ISO standards states that you have to be able to view what changes were made and who made them to a controlled documentation. We cannot implement Confluence 6.0 unless this is completed as we would be out of compliance if utilized and risk the possibility of losing our accreditation which would mean losing many of our clients.