Yes, I have seen that type of strange behavior before when having multiple editors reconciling & posting to the same parent version.
The way out is for you to create a separate public "Posting Version" for each editor.
Example:
1) DEFAULT (Protected) > Post_WalterQ (Public) (created and owned by an account you control) > WalterQ (Private, the user creates off of their assigned "Posting Version".
2) DEFAULT (Protected) > Post_TommyV (Public) (created and owned by an account you control) > TommyV (Private, the user creates off of their assigned "Posting Version".
3) DEFAULT (Protected) > Post_FrankQ (Public) (created and owned by an account you control) > FrankQ (Private, the user creates off of their assigned "Posting Version".
This isolates each editor from hitting a single parent posting version and making it dizzy.
Then you have a Windows scheduled task that runs the reconcile and post tool from all the "Posting" versions to DEFAULT.
(A note about the "Typical" weekly routine)
We have that scheduled task set to run each 30 minutes throughout the day.
The editors are responsible for their edits, quality control, etc.
So, as soon as they are comfortable reconciling & posting to their assigned posting version the next run of that task puts the changes into DEFAULT for all to see and use.
We have a weekly maintenance window on Thursdays at 16:00 - 18:00 when we can do a state zero and other chores.
The editors know they are free to work in their private editing versions during the week but must reconcile and post before Thursday at 16:00 or loose their work when all the versions are deleted and recreated during maintenance (a few other simple python scripts).
Friday mornings the editors create their private editing version off their posting version and around we go again for the next week.