Version history

Every document keeps its history. You did not have to turn it on, and you cannot lose work by editing.

What is recorded

Workover snapshots a document periodically as it changes, and records who changed it. You can also name a version at a moment that matters — “sent for legal review”, “pre-rewrite” — which makes it easy to find later among the automatic ones.

Each tab has its own history.

Browsing

Open version history from the document menu. The list runs newest first, with the time and who was editing. Select one to see the document exactly as it was.

Compare two versions to see what changed between them, additions and removals marked inline. This is usually more useful than reading an old version on its own — the question is almost always “what changed”, not “what did it say”.

Restoring

Restoring makes an old version the current one. It does not delete anything: the version you were on is still in the history, so restoring is itself reversible. Restore the wrong one and restore back.

Where history saves you

• A pull overwrote your work. Pulling from WordPress replaces the document body. The version before the pull is in the history.
• A rewrite went wrong. Accepted a set of AI suggestions and preferred the original — restore.
• Someone changed something and nobody knows who. The history says who and when.

What history is not

It is not the activity log, which records events around the document — shares, pushes, comments — rather than the text itself. Two different questions: what did this say versus what happened to it.

It is also not a WordPress revision. WordPress keeps its own revisions of the published post; Workover keeps its own of the document. A push writes to WordPress and creates a revision there too, so both sides have their own trail.

Related

• Comments and suggestions
• Pulling changes from WordPress
• Document tabs