Skip to main content

Version control

Every change in the Answer Workspace is saved and snapshotted automatically. Learn how snapshots are created, how to review them, and how to revert.

h
Written by henry brogan

Every change made in the Answer Workspace is captured automatically, traceable, and recoverable. There is nothing to save manually and no files to manage.

In practice this means you can experiment freely - regenerate a section, restructure an answer, let a colleague rework a passage - knowing the previous version is still there.

Automatic saving

Content saves continuously and in real time. You never need to save a draft, and you cannot lose work by closing the tab.

This covers:

  • Manual typing and edits

  • AI-generated drafts and regenerations

  • Accepted inline edits

  • Structural changes to content

How snapshots are created

Alongside continuous saving, BidScript creates editorial snapshots — the points you can return to.

  • A snapshot is created when you have been inactive in the editor for more than 30 seconds.

  • Further snapshots may be created during long editing sessions when significant changes occur.

Snapshots capture meaningful states of a response rather than every keystroke, which keeps the history readable.

Open version history

  1. Open the question's Answer Workspace.

  2. Click the Version History icon in the top toolbar.

The Version History panel opens, listing the available snapshots in chronological order with the time of each.

Review a previous version

Click any snapshot in the list to see a read-only preview of the answer as it stood at that point.

Use this to see how content has evolved, compare an earlier approach with the current one, or check exactly what a regeneration or a colleague's edit changed.

Snapshots are view-only until you explicitly restore one.

Revert to a previous version

  1. Open the Version History panel.

  2. Select the snapshot you want to restore.

  3. Click Revert.

That snapshot becomes the active version in the workspace. The revert itself is recorded in version history, so the audit trail stays continuous and nothing is lost by reverting.

Best practice

  • Use version history to experiment with AI regeneration or structural changes without hesitation.

  • Preview a snapshot before reverting, to be certain it is the version you want.

  • Treat the Answer Workspace as the authoritative copy of the answer.

  • Rely on version control rather than keeping duplicate copies in external documents — a copy outside the platform has no audit trail.

Related articles

Did this answer your question?