Skip to main content

​
Steps

​
1. Verify Document Readiness

Before submitting for review, ensure your document meets baseline quality criteria:
  • All required work items are created and populated
  • Risk analysis complete (for HARA/FMEA documents)
  • Traceability links established (for requirement documents)
  • No incomplete or placeholder content remains
  • Document author/owner is assigned
Use the document space dashboard to check traceability coverage percentages before submitting. Gaps in coverage often trigger rework requests during review.

​
2. Navigate to the Document

  1. Open the appropriate Space from the sidebar (Requirements, Design, Risks, or Documentation)
  2. Locate your document in the Document Inventory table
  3. Click the document title to open it
Alternatively, navigate directly via Documents → [Your Space] → [Document Name]

​
3. Initiate the Review Workflow

  1. Click the Actions menu in the document toolbar ( icon)
  2. Select Send for Review from the workflow actions dropdown
  3. Confirm the action in the dialog prompt
Document Workflow Transition
  • Current Status: Draft
  • Target Status: In Review
  • Required Fields: [Assignee]
  • Approvers: Auto-assigned from project_approver role [Cancel] [Send for Review]
The Send for Review action requires the document’s Assignee field to be set. If you see an error, edit the document properties to assign an owner before attempting the transition.

​
4. Automatic Approver Assignment

When you send the document for review, TestAuto2 automatically:
  • Transitions the document status from Draft → In Review
  • Adds all users with project_approver role as required signers
  • Sets their signature role to Approver
  • Configures the signature policy target as Approved status
The approver list appears in the document’s Approvals widget, showing:
Approver NameRoleStatusDate
Jane SmithApproverPending—
John DoeApproverPending—

​
5. Notify Reviewers (Optional)

While approvers receive automatic notifications, you can send a custom review request:
  1. Click More Actions → Send Notification
  2. Select approvers from the recipient list
  3. Add context about what to focus on during review
  4. Click Send
In your notification, highlight specific sections needing attention (e.g., “Please review ASIL classifications in Section 3” or “Verify traceability completeness for SC/CC requirements”). This accelerates the review cycle.

​
6. Track Review Progress

Monitor review status via the Approvals widget on the document page:
  • Pending: Reviewer has not yet responded
  • Approved: Reviewer signed with approval
  • Disapproved: Reviewer rejected the document
  • Obsolete: Signature invalidated due to rework
The document cannot proceed to Approved status until the signature policy is satisfied: at least one approver must sign with Approved verdict, and no Disapproved signatures can exist.

​
7. Handle Review Outcomes

If approved: Once the signature policy is met, transition the document to Approved status via Actions → Approve. See Approve Document. If rework requested: If reviewers request changes, use Actions → Rework to return the document to Draft status. This automatically marks all existing signatures as Obsolete and resets the approval state. See Request Rework.
The Rework action calls MarkWorkflowSignaturesAsObsolete and ResetSignaturesVerdict functions, clearing all approval history. After rework, you must repeat the entire review cycle—there is no partial re-approval.

​
Verification

You should now see:
  • Document status changed to In Review (yellow badge in document header)
  • Approvers listed in the Approvals widget with Pending status
  • Workflow action menu shows Approve and Rework as available next steps (grayed out until signature policy is met)

​
Workflow State Diagram

diagram

​
See Also