Change Control
Controlled Change in ComplereRaise a change request, authorise and implement its changes, and close it.
Tasks
Do a task
Lifecycle
Select a status to see who acts there and the article for that step.
-
1Initiated
InitiatedStatus 1 of 9
- Who acts
- InitiatorsCoordinators
- What happens
- The change request is saved here. Sign to send it on to Awaiting Approver sign-off.
- Signature
- Yes
-
2Awaiting Preliminary Reviewer sign-offOptional
Awaiting Preliminary Reviewer sign-offStatus 2 of 9
- What happens
- Not used on every change request.
-
3Awaiting Approver sign-off
Awaiting Approver sign-offStatus 3 of 9
- Who acts
- Approvers
- What happens
- Sign to move the change request to Authorise Changes Implementation, or send it back to Initiated with a reason.
- Signature
- Yes
-
4Authorise Changes Implementation
Status 4 of 9
- Who acts
- QAs
- What happens
- Sign to authorise the changes: the change request moves to Implement Changes. Or send it back with a reason.
- Signature
- Yes
-
5Implement Changes
Implement ChangesStatus 5 of 9
- Who acts
- CoordinatorsQAs
- What happens
- Each change is carried out and closed by its own Coordinators and QAs; a change whose Closure Dependencies are open waits in Awaiting Dependency. When the last change is Closed, the change request moves to Awaiting QA sign-off by itself.
-
6Awaiting QA sign-off
Awaiting QA sign-offStatus 6 of 9
- Who acts
- QAs
- What happens
- Sign to move the change request to Awaiting Effectiveness Review; the QAs' panel also offers Escalate status to Closed. Or send it back to an earlier status with a reason.
- Signature
- Yes
-
7Awaiting Effectiveness Review
Awaiting Effectiveness ReviewStatus 7 of 9
- Who acts
- Coordinators
- What happens
- Answer Was the action effective? on the Effectiveness Form tab and sign with Save And Escalate; Yes moves the change request to Awaiting Effectiveness Verification.
- Signature
- Yes
-
8Awaiting Effectiveness Verification
Awaiting Effectiveness VerificationStatus 8 of 9
- Who acts
- QAs
- What happens
- Sign to close the change request, or send it back to Awaiting Effectiveness Review with a reason.
- Signature
- Yes
-
9Closed
ClosedStatus 9 of 9
- What happens
- The change request is complete; its status button is greyed.
- Signature
- No
Select a status above to see who acts there.
Other moves
- Send backAwaiting Approver sign-offtoInitiatedorAwaiting Approver sign-offApprovers send back to Initiated; QAs to Initiated or Awaiting Approver sign-off. With a reason.How a change request moves from Initiated to Closed
- Send backAwaiting QA sign-offtoan earlier statusQAs, with a reason: Initiated, Awaiting Approver sign-off, Authorise Changes Implementation or Implement Changes.How a change request moves from Initiated to Closed
- Send backAwaiting Effectiveness VerificationtoAwaiting Effectiveness ReviewQAs, with a reason.How a change request moves from Initiated to Closed
- Send backAwaiting Effectiveness ReviewtoAwaiting QA sign-offCoordinators, by answering No on the Effectiveness Form, with a rejection reason and a signature.Record the effectiveness review of a change request
A dashed status is not used on every record. The QAs' panel in Awaiting QA sign-off also offers "Escalate status to Closed".
Status names and colours as Complere shows them.
The whole workflow, step by step: How a change request moves from Initiated to Closed
Who can do what
Who can take the key actions. A status name in a cell means the action is allowed in that status only.
| Your system role | Named on the change request | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Action | Administrator | Supervisor | Regular User | Read Only User | Initiators | Preliminary Reviewers | Coordinators | Approvers | QAs |
| Create a change request How to: Create a change request | Yes | Yes | Yes | No | Not a role on the change request for this action | Not a role on the change request for this action | Not a role on the change request for this action | Not a role on the change request for this action | Not a role on the change request for this action |
| Change the change request's details | Initiated, Awaiting Preliminary Reviewer sign-off, Implement Changes | No | No | No | Initiated, Awaiting Preliminary Reviewer sign-off | Initiated, Awaiting Preliminary Reviewer sign-off | Initiated, Awaiting Preliminary Reviewer sign-off | No | Initiated, Awaiting Preliminary Reviewer sign-off, Implement Changes |
| Sign to send on from Initiated Read: How a change request moves from Initiated to Closed Initiators and Coordinators of the change request. | No | No | No | No | Initiated | No | Initiated | No | No |
| Sign the preliminary review Read: How a change request moves from Initiated to Closed | No | No | No | No | No | Awaiting Preliminary Reviewer sign-off | No | No | No |
| Sign to move the change request on How to: Sign a change request as Approver or QA | No | No | No | No | No | No | No | Awaiting Approver sign-off | , Awaiting QA sign-off, Awaiting Effectiveness Verification |
| Move on from Implement Changes How to: Close a change of a change request Every change must be Closed first. When the last change closes, the change request moves on by itself; its Audit Trail records it as Auto-advanced. | No | No | No | No | No | No | Implement Changes | No | Implement Changes |
| Record the effectiveness review How to: Record the effectiveness review of a change request Signed. | No | No | No | No | No | No | Awaiting Effectiveness Review | No | No |
| Send back with a reason Read: How a change request moves from Initiated to Closed | No | No | No | No | No | No | Awaiting Effectiveness Review | Awaiting Approver sign-off | , Awaiting QA sign-off, Awaiting Effectiveness Verification |
Every action, status and role — Controlled Change: who can do what