Approvals
The Approval feature allows reviewers to record a pass or fail decision against individual Events directly in the editor. This provides a structured and visible QA status without requiring any external tool or separate spreadsheet, and is particularly useful when handing off a caption file between an author and a quality control reviewer.
The Approval State​
Each Event carries an approved property that cycles through three states each time the approval button is clicked. The button is displayed as a circle icon on the Event row.
When an Event has not yet been reviewed, the approval button appears as a neutral dark check-circle, indicating that no decision has been recorded. Clicking it advances the state to Approved, which displays a blue check-circle. Clicking again advances to Rejected, which displays a red X-circle. Clicking a third time clears the approval state and returns the Event to unreviewed.
Because the three states cycle in sequence, a reviewer can work through an Event list quickly by clicking once to approve or twice to reject, without needing to open any additional dialog.
Using Approvals in a Team Workflow​
Approval states are stored within the project file and travel with it when the project is shared with a team member. A reviewer can open a shared project, step through the Events, and set an approval status on each one. The author can then reload the project and see at a glance which Events require attention — rejected Events are immediately identifiable by the red X-circle.
This workflow is most effective when combined with Notes, since a reviewer can reject an Event and leave a note explaining the reason without leaving the editor. The combination gives the author everything they need to make corrections and mark the Event as resolved.
For a full description of how approvals and notes integrate into the QA review process, including Error Navigator integration, see Event Approval & Notes.