Article Summary
Response Version History provides a complete timeline of all changes made to a response, including who made changes, when they occurred, and what was modified. Review previous versions and restore earlier content if needed to maintain quality control and track response evolution.
Estimated Time
1-3 minutes per response review
Prerequisites
Active project with existing responses
Editor or Reviewer role assigned
Step-by-Step Instructions
Step 1: Access Response Version History
Navigate to the Project Editor.
Locate the response you want to review.
Click the pencil icon (the Response Editor) on the right side of the response row.
The Response Editor opens.
Step 2: Open the History Tab
In the Response Editor, locate the navigation panel in the top right section.
Click the History tab.
The complete version timeline appears showing all changes.
Step 3: Review Version History
Scroll through the timeline of changes.
Each entry shows:
User who made the change
Timestamp of when the change occurred
Type of change (content update, regeneration, status change, assignment change, etc.)
Preview of the response content at that version
Review changes chronologically to understand response evolution.
Step 4: Compare Versions (Optional)
Click on any version entry to expand and view full content.
Compare different versions to see how the response evolved.
Identify which version best meets the requirement.
Step 5: Restore a Previous Version (Optional)
Find the version you want to restore.
Click the Restore button below that version.
The selected version replaces the current response content.
Make any additional edits if needed.
Note: You cannot restore versions when the response is already approved or when the version matches the current response.
🙋🏽 What Gets Tracked in Version History?
Response History automatically records the following events:
Content Changes:
Initial generation: When AutoRFP first generates the response
Updates to content: When editors modify the response text
Regeneration: When a user requests AI to regenerate the response
Workflow Changes:
Assignment changes: When editors or reviewers are added or removed
Status changes: When a response is submitted for review or approved
Requested changes: When reviewers request modifications
Grouping Rules:
Updates by the same user within a 30-minute window are grouped as one entry
Each new update by a different person creates a separate entry
Status changes and assignment changes always create new entries regardless of timing
💡 Tips & Best Practices
Use history to identify who made specific changes for follow-up questions
Restore previous versions instead of manually rewriting when earlier content was better
Review multiple versions before deciding which to restore
✋🏼 Common Mistakes to Avoid
Not reviewing version history before approving - missing context about response evolution
Forgetting that 30-minute grouping exists - expecting to see every single edit as separate entry
Need Help?
💬 Live Chat: Available in-app
📧 Email: [email protected] or contact your Success Manager directly for urgent support.
📚 Learning Centre: learn.autorfp.ai/en