Record a CCB decision
After the CCB has met and reached a decision, the coordinator records it in Redline. This triggers the appropriate next steps automatically.
Recording a decision
Section titled “Recording a decision”1
Open the ECR in CCB Review status
Navigate to Change Requests and open the ECR. The decision panel appears in the right sidebar.
2
Select the decision
Choose Approved, Rejected, or On hold.
3
Provide rationale (if rejecting or holding)
Enter the reason for the decision. This is mandatory for rejections and holds, optional for approvals.
4
Assign coordinator (if approving)
Select the coordinator who will own the resulting Engineering Change. This is mandatory for CCB approvals.
5
Confirm
Click Submit decision. The ECR status updates immediately and the appropriate follow-up actions are triggered.
What happens after each decision
Section titled “What happens after each decision”Approved
Section titled “Approved”- An Engineering Change (EC) is created in Draft status
- EC number is derived from the ECR number
- Title, description, trigger source, severity, classification, and change type are carried over
- Affected items are copied to the EC
- Preliminary actions are carried over
- The assigned coordinator receives ownership
The coordinator can now proceed to upload a BOM and continue the ECO process.
Rejected
Section titled “Rejected”- The ECR creator receives an email with the rejection rationale
- The ECR becomes editable again
- The creator can:
- Accept the rejection — archives the ECR permanently
- Edit and resubmit — updates fields and sends the ECR back to Submitted status for another review cycle
On hold
Section titled “On hold”- Same behaviour as rejected — the ECR becomes editable and can be resubmitted when the blocking condition is resolved
- The rationale should specify what condition needs to be met before re-evaluation
Decision from screening
Section titled “Decision from screening”Coordinators can also record decisions during the screening step without escalating to the CCB. The process is identical — the only difference is that decision_source is recorded as “coordinator” instead of “ccb”.