Last updated Jul 03, 2017

Setting: Separate the Steps of Application from Reworking for the sake of Easy Monitoring

Cases of connecting the arrow-path for Reworking in the upstream process are not uncommon. However, there is a possibility that visibility might be reduced in the [My Tasks] or on [the Heat Map], if "Issues to be reworked" and "Issues not yet handled" were mixed together. Therefore, you should consider isolation of "Steps for Re-inputting" in a flow where many Issues goes by and also occurrence of Rework is high.


a. Unplanned Rework
For example: When insufficiencies are found in the work Application, or when a Task for which the operator has no validation authority is assigned, etc.
b. Planned Rework
For example: To gradually increase the completeness by receiving feedback in Planning operations, etc.

a. Steps where Input Items are many
For example: Reimbursement claim of Expense paid on behalf, Request for leave, request for Decision-making, etc.
b. Steps which are Focused on Reviewing purposes
For example: Creating an estimate, Registering of draft agreement which was accepted by a Business partner, etc.

1. Place a dedicated Step on the Same Swimlane
Add a Step which is dedicated for Reworking
2. Connect using Arrow-path
Add a path for Reworking, and name it. For example, “Rework request”
  • You can also make this using an XOR Gateway
  • In many cases, its data reading level (read-write permission) will have the same settings as the “Input Step” of the first time
  • Also, consider placing a [Throwing Message Intermediate Event (Email), in order to quickly recognize the occurrence of Rework

1. Measurement of the Number of Occurrence
Aggregate the number of Issues which have reached the Re-input Step, or the total number of re-inputting, etc.
2. Investigate the Cause
Classify the cause of Rework that often occurrs at a Step.
3. Improve it
Improve the Description on the Input screen or “Work Manual”