CCB process explained

The Change Control Board (CCB) is the governance body that approves, rejects, or defers major engineering changes. Redline does not replace your CCB meeting — it gives the board a structured place to record decisions and automatically triggers the next steps.

What the CCB sees

CCB members (users with the CCB member flag) see ECRs in CCB Review status in their dashboard. Each ECR shows:

• Title, description, and trigger source
• Classification and severity
• Affected items with part numbers
• Attachments (supplier letters, drawings, test reports)
• Preliminary actions already defined
• The full timeline of status changes and edits

The three decisions

Decision	What happens next
Approved	An Engineering Change (EC) is auto-created. ECR data, affected items, and preliminary actions carry over. The assigned coordinator owns the EC.
Rejected	The ECR creator receives an email with the rejection rationale. They can accept the rejection (archives the ECR) or edit and resubmit.
On hold	The ECR is deferred pending resolution of a condition. The creator can resubmit when the condition is met.

Rationale is mandatory

For rejected and on-hold decisions, a rationale is required. This is stored in the audit trail and included in the notification email to the ECR creator.

Coordinator vs CCB decisions

Not all decisions require a CCB meeting:

• Coordinator decisions — the coordinator can approve minor changes and emergencies directly during screening, without escalating to the CCB
• CCB decisions — major changes are escalated to the board. When the CCB approves, they must also assign a coordinator for the resulting EC

The decision_source field tracks whether the decision came from a coordinator or the CCB.

CCB configuration

In Settings, you can control:

• CCB member flag — assign the CCB role to specific users so they see CCB-pending ECRs
• CCB required for minor — when enabled, even minor changes need CCB approval instead of coordinator-only screening

Audit trail

Every CCB decision is recorded with:

• Who made the decision
• The decision type (approved / rejected / on hold)
• The rationale text
• The assigned coordinator (for approvals)
• Timestamp

This creates a complete, auditable governance record.

Next steps

• Record a CCB decision →
• What is an ECR →