REQ-FUN-126

Change Request entity with submission / approval workflow

ID: REQ-FUN-126
Category: Functional Requirements
Status: approved
Priority: P0
Created: 2026-05-11T19:30:00.000Z
Approved: 2026-05-11T21:07:00.000Z
Updated: 2026-05-11T21:07:00.000Z

What

First-class change_request entity: id, project_id, originator, category, title, description, justification, impact_assessment, status (submitted / under_review / approved / rejected / deferred / withdrawn), submitted_at, decided_at, decided_by, linked_signoff_id.

Why

established project management guidelines names Change Requests as outputs of every Control-* process and Perform Integrated Change Control. The audit flagged Partial across all Control-* processes.

How

New table change_request with FK to project; CCB approval is a sign-off entity. Baseline-mutation operations require an approved CR.

Done when

REST + MCP CRUD; sign-off integration; baseline-mutation APIs reject without approved CR; Web UI: CRs tab per project.

Out of scope

Cross-project CRs. Automated impact analysis.

established project management guidelines Mapping

Primary Knowledge Area: Integration Management
Secondary KAs: Scope Management, Schedule Management, Cost Management, Quality Management, Risk Management, Resource Management, Stakeholder Management
Primary Process Group: Monitoring & Controlling
established project management guidelines Deliverable: Change Request

Change Request entity is the data backbone of Perform Integrated Change Control and every Control-* process output.