Change requests

A change request (CR) is the formal record of any change to project scope, cost or schedule. Sageon Business gives you a lightweight workflow that scales from informal team change to board-level approval.

When to raise a CR

Raise one whenever the project moves outside the approved baseline:

Scope changes (added/removed feature)
Cost overrun > 5%
Schedule slip > 2 weeks on a milestone
Supplier / contract change

Creating a CR

From a project → Change control → + New change request:

Title — short
Type — Scope / Cost / Schedule / Resource / Other
Description — what's changing and why
Impact — cost £, schedule (days), scope (text)
Justification — why this is necessary
Status — Draft / Submitted / Approved / Rejected / Withdrawn
Approver — who needs to sign off

Approval workflow

Draft — author working on it
Submitted — sent to approver(s)
Approved / Rejected — decision recorded with timestamp + comments

Once approved, the CR's impact rolls into the project baseline (e.g. budget changes).

Visibility

CRs appear in:

The project's Change control tab
The project Overview's "Recent change requests" section (last 5)
The portfolio rollup as a count

Tips

One CR per change. Don't bundle multiple unrelated changes — approvers can't approve "everything except point 3".
Include the financial impact even when it's zero. "+£0, +0 days" makes it clear this is a scope-only change.
Don't backdate. A CR raised after the work is done isn't change control — it's accounting.