When to Use Rework
Use the Rework action when:- A reviewer identifies issues during the In Review phase
- Post-approval analysis reveals missing risk controls or incorrect scoring
- A published document needs updates due to design changes, new hazard identification, or corrective actions from post-market surveillance
Prerequisites
- The risk document is in In Review, Approved, or Published status
- You have permission to trigger workflow actions on the document
Step 1: Open the Risk Document
- Navigate to the Risks space in Polarion.
- Open the risk document that requires rework (for example,
HARA-ANALYSISorDFMEA-SUB-001). - Note the current status in the document header.
Step 2: Trigger the Rework Action
- Click the workflow action dropdown on the document toolbar.
- Select Rework.
- The system automatically:
- Transitions the document back to Draft status
- Marks all existing workflow signatures as obsolete (via
MarkWorkflowSignaturesAsObsolete) - Resets all signature verdicts (via
ResetSignaturesVerdict)
Step 3: Make Your Changes
With the document back in Draft:- Open the document in risksheet by clicking Edit Risks with Nextedy RISKSHEET in the document header.
- Make the required changes:
- Add or modify risk records / failure modes
- Update Severity, Occurrence, or Detection scores
- Add new risk controls or mitigation tasks
- Correct hazardous situation descriptions or benefit-risk justifications
- Save all changes in risksheet.
Step 4: Re-Submit for Review
After completing your changes:- Follow the standard approval process in Review and Approve a Risk Document.
- Select Send for Review to re-initiate the approval cycle.
- New default signers are assigned automatically.
- Reviewers must provide fresh electronic signatures.
Key Behaviors
| Behavior | Detail |
|---|---|
| No intermediate state | Rework always returns directly to Draft — there is no “revision” or “rework in progress” state |
| All signatures invalidated | Both MarkWorkflowSignaturesAsObsolete and ResetSignaturesVerdict execute, ensuring complete re-review |
| Available from three states | Rework can be triggered from In Review, Approved, or Published |
| Audit trail preserved | The original signatures and their obsolete status remain in the document history for traceability |
The approval policy requires at least one signature (
atLeastOne policy). After rework, a single project_approver signature is sufficient to re-approve the document. There is no requirement for multiple independent reviewers.Related Pages
- Review and Approve a Risk Document — The forward approval workflow
- Risk Document Lifecycle — Conceptual overview of the four-state lifecycle
- Risk Specification Document Workflow — Complete workflow configuration reference