Skip to main content

​
Prerequisites

Before submitting for review, ensure:
  • All hazards have complete S/E/C ratings (no blank cells)
  • ASIL values calculated for all hazards
  • At least one safety goal derived for each ASIL B/C/D hazard
  • HARA rationale fields documented for audit trail

​
Steps

​
1. Verify HARA Completeness

Open your HARA document and switch to the Full View to see all columns. Check for completion indicators:
  • Red cells or empty ASIL values indicate missing S/E/C ratings
  • Missing Safety Goal links for ASIL B/C/D hazards violate ISO 26262-3
  • Empty Rationale fields will fail audit review
Hazards without all three ratings (S/E/C) will show null in the ASIL column. The automatic ASIL calculation formula requires S×E×C values before it can compute the classification per ISO 26262 Table 4.

​
2. Generate HARA Report Preview

Navigate to Documentation > ISO 26262 HARA Report to preview the compliance output. The report displays: diagram Review the following sections:
  • ASIL Distribution: Verify counts match your risksheet totals
  • Incomplete Assessment Warning: Resolve any flagged hazards before submission
  • High Integrity Requirements Alert: Confirm ASIL C/D hazards have linked safety goals
  • Hazard Register Table: Check all hazards appear with correct S/E/C/ASIL values
  • Safety Goals Table: Verify ASIL inheritance (Safety Goal ASIL must match parent Hazard ASIL)
Projects with >30% ASIL D hazards may indicate overly conservative severity ratings. Review S/E/C assumptions before formal submission. Common mistake: rating all potential injuries as S3 instead of differentiating S1 (minor) vs S2 (severe) vs S3 (life-threatening).

​
3. Submit Document for Review

In the HARA document header, locate the workflow status badge (currently shows Draft). Click Actions → Send for Review. The system executes:
  1. Transitions document status from draft to inReview
  2. Adds all users with project_approver role as required signers
  3. Sets signature policy to at least one approver (per atLeastOne signature policy)
  4. Sends notification emails to approvers
You will see the status badge change:

​
4. Monitor Review Progress

Navigate to the document’s Signatures tab to track approval status. You’ll see a table showing:
ReviewerRoleStatusDate
John SmithApproverPending—
Sarah JohnsonApproverPending—
Reviewers with project_approver role can approve directly from the document using Actions → Approve (auto-signature enabled).
Ticket #RS-247 resolution: Add a comment in the document pointing reviewers to specific hazards needing attention (e.g., “Please verify ASIL D hazard H-05 severity justification in rationale field”). This prevents generic “needs more detail” feedback loops.

​
5. Handle Rework Requests

If reviewers identify issues, they will use Actions → Request Rework. This transition:
  • Returns document to draft status
  • Marks all existing signatures as obsolete (via MarkWorkflowSignaturesAsObsolete function)
  • Resets signature verdict (via ResetSignaturesVerdict function)
You’ll receive a notification with reviewer comments. Address feedback in the risksheet, then repeat Step 3 to resubmit.
Even if one approver already signed, requesting rework invalidates all signatures. After making corrections, you must collect fresh approvals from all required reviewers.

​
6. Track Approval Completion

Once at least one approver signs, the workflow allows transition to approved status. The document automatically advances when signature requirements are met: Approved status indicates:
  • Formal sign-off complete
  • HARA analysis reviewed and accepted
  • Document ready for publication

​
7. Publish Final HARA

When ready to release the HARA for downstream use (safety concept, functional safety requirements), use Actions → Publish. This transitions the document to published status: Published HARA documents:
  • Serve as baseline for ISO 26262-3 compliance evidence
  • Feed safety goals into functional safety concept (ISO 26262-4)
  • Establish ASIL allocation for downstream requirements
  • Enable traceability reporting and audit preparation
Create a Polarion baseline immediately after publishing. This captures the approved HARA state for compliance records and enables comparison with future revisions. Navigate to Baselines → Create Baseline and tag with the project milestone (e.g., “V1.0 Safety Concept Release”).

​
Verification

You should now see:
  • Document workflow badge shows Published
  • At least one approver signature recorded in Signatures tab
  • ISO 26262 HARA Report displays complete hazard register with no warnings
  • Safety Readiness Scorecard (Home dashboard) shows 100% HARA completion for ISO 26262 Part 3

​
Common Issues

“Send for Review button disabled”
→ Document must be in draft status. If in inReview, approved, or published, use Request Rework first to return to draft. “No approvers available”
→ Project must have at least one user with project_approver role. Contact your Configuration Manager to assign approver permissions. “Safety Goals missing ASIL inheritance”
→ Check the Safety Goal work item form. The ASIL field should auto-populate from the parent hazard via the inheritASIL formula. If blank, verify the derivedFrom link exists between Safety Goal and Hazard.

​
See Also