Skip to main content

​
Prerequisites

  • Document must be in In Review status
  • You must have project_approver role assigned in the project
  • Sender must have used the Send for Review action to populate the signature widget

​
Steps

​
1. Navigate to the Document

From the Home dashboard or relevant space (Risks, Design, Testing), click on the document name in the Document Inventory table.

​
2. Locate the Signature Widget

Scroll to the bottom of the LiveDoc page. You should see a Signatures widget showing:
  • Required Signers: Users from the project_approver role automatically added when the document entered In Review
  • Signature Role: Approver
  • Current Verdict: Pending (if no one has signed yet)

​
3. Review the Document Content

Click through the Risksheet tables or PowerSheet sections to verify:
  • All work items are complete (no empty required fields)
  • Risk ratings (ASIL, Action Priority, RPN) are calculated correctly
  • Mitigation controls are linked where required
  • No placeholder or draft content remains
For FMEA documents, open the FMEA Coverage Report from the Documentation space dashboard before approving. This validates that all SC/CC classified items have linked failure modes.

​
4. Sign the Document

In the Signatures widget:
  1. Click your name in the signers list
  2. Select Approve from the verdict dropdown
  3. (Optional) Add a comment: “Reviewed HAZID analysis - ASIL classifications verified per ISO 26262-3 Table 3”
  4. Click Sign
diagram
The document will not transition to Approved until:
  • At least one approver signs with “Approve” verdict
  • No approver signs with “Disapprove” verdict
If anyone selects Disapprove, the document cannot proceed to Approved. Use the Request Rework action instead.

​
5. Verify Automatic Transition

Once the signature policy is satisfied (minimum one approval, no disapprovals), the document automatically transitions to Approved status. Check the document header:
  • Status: Now shows ✅ Approved
  • Status Color: Green indicator
  • Workflow Actions: Now shows “Publish” and “Rework” buttons only
If you have the project_approver role, you can approve directly from the document page without waiting for others. The system supports auto-signature when you trigger the workflow action yourself.

​
6. Notify Stakeholders

After approval:
  1. Navigate to Home → Documentation Space dashboard
  2. Verify the document appears in the “Approved” status group in the Document Inventory
  3. (Optional) Use the Generate HARA Report or Generate FMEA Reports actions to create PDF deliverables for stakeholders

​
What Happens After Approval

ActionEffect
Baseline CreationApproved documents are typically baselined for audit trail and change control
Downstream TraceabilitySafety goals, failure modes, and risk controls can now be referenced by design requirements and test cases
Configuration Item StatusDocument becomes a controlled configuration item under ISO 26262-8 requirements
Publishing EligibilityDocument can now be transitioned to Published status via Publish Document action
Approved documents are read-only in practice. To make changes:
  1. Use Request Rework to return to Draft
  2. All signatures will be marked obsolete (invalidated)
  3. The document must go through the full review cycle again after edits

​
Verification

You should now see:
  • ✅ Document status badge shows Approved in green
  • ✅ Signatures widget shows your signature with “Approve” verdict and timestamp
  • ✅ Document appears in “Approved” section of Documentation space dashboard
  • ✅ Publish action is available in the workflow toolbar
  • ✅ Safety Readiness Scorecard updates to reflect approved document count for relevant standard

​
See Also