Versions and Comments
SOPHIE tracks every change to your SOPs and gives your team built-in tools to discuss and refine procedures together. Version history and comments work hand in hand -- one keeps a record of what changed, the other captures why.
Version history
Every time a SOP is saved, SOPHIE creates a new version. You never lose previous work, and you always have a clear record of how a procedure evolved over time.
Viewing version history
Open a SOP and click the Versions tab in the sidebar. You will see a list of every version with:
- Version number -- A sequential counter (v1, v2, v3, and so on)
- Timestamp -- When the save happened
- Author -- Who made the change
- Diff view -- A side-by-side comparison highlighting exactly what was added, removed, or modified
Change categories
SOPHIE labels each version with a category so reviewers can quickly understand the nature of the change:
| Category | What it covers |
|---|---|
| Safety | Changes to safety-critical steps or warnings |
| Instructions | Updates to procedural steps or guidance |
| Clarification | Wording improvements that do not change the actual procedure |
| Media | Added or updated images, videos, or attachments |
| Administrative | Metadata changes like assigned roles, frequency, or department |
Restoring a previous version
If a change was made in error or you want to go back to an earlier version, click Restore next to that version in the history panel. Restoring does not overwrite anything -- it creates a new version with the restored content, so the full audit trail is preserved.
This is useful when someone accidentally overwrites a section, or when a revised SOP turns out to be less effective than the original.
Comments
The comments panel on each SOP lets your team have focused discussions about the procedure without editing the document itself.
Adding a comment
- Open the SOP detail view.
- Click the Comments tab in the sidebar.
- Type your comment and click Submit.
Threaded discussions
Comments support threaded replies, so you can respond to a specific comment and keep related discussion grouped together. This prevents conversations from getting tangled when multiple topics are being discussed on the same SOP.
Mentions
Tag a team member by typing @ followed by their name. They will receive a notification in their Inbox so they can jump into the conversation. Mentions are treated as actionable — the notification stays open until the person replies. If they have not responded after a while, SOPHIE sends a nudge email as a reminder.
You can also use voice input to mention someone. Say "at Mauricio" while dictating and SOPHIE will match the name to the right team member.
Comment priority
You can set a priority on your comment to signal urgency:
- Normal — Standard discussion (default).
- Low — Minor note, no rush.
- High — Needs attention soon.
- Urgent — Requires immediate response.
Priority is visible on the comment and affects how the notification appears in the recipient's inbox. You can set priority from the comment input or by saying "urgent" or "high priority" during voice input — SOPHIE detects the priority and sets it automatically.
Comment notifications
When someone comments on a SOP you own or are assigned to, you receive a notification in your Inbox. If your workspace has Slack configured, you can also receive comment notifications there.
When to use comments vs. editing
- Use comments when you have a question, want to suggest a change for discussion, or need to flag something for the SOP owner to address. Comments are ideal during the review process.
- Edit the SOP directly when you are the author making revisions, or when a change has already been agreed upon and just needs to be applied.
Activity log
The activity log at the bottom of the SOP detail view provides a complete timeline of everything that has happened -- creation, edits, status changes, comments, acknowledgements, and version restores. This log cannot be modified and serves as a reliable audit trail for compliance purposes.