Skip to main content

​
When to Use This Guide

Use the Rework action when a risk document in In Review, Approved, or Published state needs substantive changes — such as adding a missing failure mode, correcting a severity classification, or updating risk controls after a design change.
Triggering Rework marks every electronic signature on the document as obsolete. All approvers must re-sign before the document can be approved again. This is a certification requirement — it ensures no unreviewed changes reach a published baseline.

​
Steps

​
1. Open the Risk Document

Navigate to the Risks space and open the risk document you need to revise (FHA, SFMEA, DFMEA, PSSA, SSA, FTA, CCA, Security Threat Assessment, Compliance Matrix, or similar). Confirm the document is in In Review, Approved, or Published state. The Rework action is not available on documents already in Draft.

​
2. Trigger the Rework Action

In the document toolbar, open the workflow action menu and select Rework. The document immediately returns to Draft state. All previously recorded electronic signatures are marked obsolete.
Reworking a Published document discards the certified baseline. If the document is referenced in a certification evidence package, notify your Configuration Manager before triggering Rework.

​
3. Edit the Risk Analysis

With the document back in Draft, open the risksheet to make your changes:
  • Add or remove failure modes
  • Adjust severity, occurrence, or detection scores
  • Update mitigation actions and risk controls
  • Revise DAL assignments or failure condition links
Rework changes the document status only. Individual failure modes and risk controls within the risksheet retain their field values (RPN scores, implementation status, links). You only need to update the rows that have changed.

​
4. Re-Submit for Review

When your edits are complete, use Send for Review to transition the document back to In Review state. This action automatically adds users with the project_approver role as signers.
The exact approver role name and auto-sign behavior depends on your project’s role configuration. Check with your project administrator if the expected approvers are not added automatically.

​
5. Obtain Re-Approval

Approvers must review the revised content and provide fresh electronic signatures. The document requires at least one valid approver signature before the Approve action becomes available. Once approved, you can Publish the document to establish a new certified baseline.

​
Workflow Summary

diagram

​
Common Pitfalls

After Rework, resist the urge to immediately re-send for approval without making changes. If a document cycles through Rework with no substantive edits, auditors may question the validity of the approval record. Document what changed and why in the document’s comment or history field.
An FHA revision that changes a failure condition’s DAL may require corresponding updates to linked PSSA, SSA, or SFMEA documents. Check for dependent documents in the traceability matrix before re-publishing.

​
Verification

After triggering Rework, confirm:
  • The document status badge shows Draft
  • The Signatures panel shows all previous signatures marked as obsolete or removed
  • The risksheet rows are editable (cells are no longer read-only)
You should now see the document open for editing with no active approval signatures.

​
See Also

Code: .polarion/documents/workflow/riskSpecification-workflow.xml (0.65) · .polarion/tracker/fields/severity-enum.xml, status-enum.xml, priority-enum.xml, implementationStatus-enum.xml, riskSpecification-document-status-enum.xml (0.64) · modules/Risks/COMPLIANCE-001/module.xml, modules/Risks/MIL-STD-882E-HTS-001/module.xml, modules/Risks/SEC-THREAT-001/module.xml, modules/Risks/SFMEA-SUB-001/module.xml, modules/Risks/SFMEA-SUB-002/module.xml, modules/Risks/SFMEA-SUB-003/module.xml (0.49) · modules/RiskTemplates/DFMEATemplate/attachments/risksheetTopPanel.vm, SubSystem-FMEATemplate/attachments/risksheetTopPanel.vm, System-FMEATemplate/attachments/risksheetTopPanel.vm, PFMEATemplate/attachments/risksheetTopPanel.vm, HazardTrackingTemplate/attachments/risksheetTopPanel.vm, DFMEATemplate/attachments/risksheetPdfExport.vm, SubSystem-FMEATemplate/attachments/risksheetPdfExport.vm, System-FMEATemplate/attachments/risksheetPdfExport.vm, PFMEATemplate/attachments/risksheetPdfExport.vm (0.48) · modules/RiskTemplates/DFMEATemplate/attachments/risksheet.json (0.47) · modules/RiskTemplates/PFMEATemplate/attachments/risksheet.json (0.47) · .polarion/tracker/workflow/workflow.xml (0.46) · modules/RiskTemplates/RiskControlPlanTemplate/attachments/risksheet.json (0.46) · .polarion/polarion-project.xml, .polarion/context.properties, .polarion/security/user-roles.xml, .claude/PROJECT.md, TODO.md (0.45) · .polarion/tracker/fields/riskRecord-custom-fields.xml (0.43)