Skip to main content

​
When to Use Rework

Use the rework action when:
  • Reviewers identify substantial errors requiring content changes
  • Risk analysis completeness fails internal quality checks
  • New hazards or failure modes must be added after approval
  • Regulatory feedback requires methodology changes
  • Document structure needs reorganization
The rework action permanently invalidates all approval signatures and clears the signature verdict. Previous approvers must re-sign after you complete corrections. This is not reversible—plan rework cycles carefully.

​
Steps to Request Rework

​
1. Access the Document

Navigate to the risk specification document that needs rework:
  • From Home Dashboard: Click the document link in the “Risk Specifications” section
  • From Risks Space Dashboard: Select the document from the inventory tree
  • From Role Dashboard: Follow the “Pending My Approval” or “In Review” widget links

​
2. Initiate Rework Action

  1. Open the document in the Polarion document editor
  2. Locate the Document Properties panel (right sidebar)
  3. Find the Status field showing current workflow state (In Review, Approved, or Published)
  4. Click the status dropdown to reveal available workflow actions
  5. Select ** Rework** from the action list

​
3. Confirm Rework Transition

The workflow engine will:
  • Transition document status from any state → Draft
  • Execute MarkWorkflowSignaturesAsObsolete function (invalidates all existing signatures)
  • Execute ResetSignaturesVerdict function (clears approval state)
  • Remove signature widget requirements
  • Clear the resolution field if previously set
Before requesting rework, add a comment to the document or signature widget explaining what needs correction. This helps approvers understand why their signatures were invalidated when you resubmit for review.

​
Workflow State Transitions

diagram The rework action provides a “reset path” from any approval state back to the initial draft state, enabling full correction cycles without creating duplicate documents.

​
Risksheet Content Remains Editable

  • All Risksheet rows (hazards, failure modes, risk records) remain in place
  • Data in HARA/FMEA analysis tables persists unchanged
  • No work items are deleted or modified by workflow transition
  • You can immediately edit Risksheet content after rework

​
Linked Work Items Are Not Affected

The document rework action does not cascade to linked work items:
  • Risk controls created from mitigation columns remain active
  • Tasks generated via context menu stay in their current status
  • System requirements linked to safety goals are unchanged
Unlike work item-level reopen actions that can cascade to dependent items via link traversal, document-level rework is isolated to the document’s approval state. Related work items continue their own lifecycle.

​
Common Rework Scenarios

​
Scenario 1: Incomplete FMEA Coverage

A Safety Engineer submits a DFMEA document for review but coverage validation reveals missing failure modes for two safety-critical characteristics. Resolution: Request rework → add missing failure modes in Risksheet → recalculate Action Priority → submit for fresh review cycle.

​
Scenario 2: ASIL Classification Correction

After HARA approval, stakeholders identify incorrect Severity rating for a hazard affecting a critical safety function. Resolution: Request rework → correct Severity field → recalculate ASIL per ISO 26262-3 → regenerate HARA Report → resubmit for approval.

​
Scenario 3: Methodology Change

Regulatory audit feedback requires switching from simplified FMEA to full AIAG-VDA 7-step methodology with Failure Network linkage. Resolution: Request rework → add Cause work item type to Risksheet configuration → establish Failure-Cause-Effect linkage → populate new columns → resubmit for approval.

​
After Requesting Rework

​
1. Make Required Corrections

  • Edit Risksheet content directly in Draft status
  • Add/remove rows as needed
  • Update risk ratings, classifications, or linkages
  • Regenerate embedded reports if risk matrices changed

​
2. Validate Completeness

Use coverage validation before resubmitting:

​
3. Resubmit for Review

When corrections are complete:
  1. Follow Submit Document for Review workflow
  2. The sendForReview action will re-populate approvers from project_approver role
  3. Signature widget reappears with fresh signature requirements
  4. Previous approvers receive new notification
When resubmitting after rework, add a document comment summarizing what changed. This helps approvers focus their review on modified sections rather than re-reviewing the entire document.

​
Verification

After requesting rework, you should see:
  • ✅ Document status field shows Draft
  • ✅ Signature widget is no longer visible in document sidebar
  • ✅ Document Properties panel shows resolution field cleared
  • ✅ Workflow actions dropdown now shows Send for Review option
  • ✅ Risksheet remains editable with all content intact

​
See Also