1. Change Request Management
  2. Process
  3. Revision and decision
Process · Revision and decision

Revision and decision

A decision is useful only when it identifies the scope the reviewer saw. The work package has a revision, and the review decision stores a source revision. The reason and reviewer complete the history of that decision.

Step by step

  1. Prepare the revision Project Manager

    Project Manager checks the current package summary, assessment, task work and attachments, then places the package in Review.

    • Present one coherent scope
    • Updates Work packages, Impact assessments, Tasks
  2. Check reviewer independence Delivery Lead

    Delivery Lead routes the package to an Independent Reviewer who is not the package owner or preparer.

    • Separate owner from reviewer
    • Updates Team members, Work packages
  3. Examine evidence Independent Reviewer

    The reviewer compares the package revision with the impact and supporting files. Any material change should be presented as a new revision.

    • Give the reviewer supporting material
    • Updates Record attachments, Work packages
  4. Decide Independent Reviewer

    The reviewer records Approve, Reject or Return, a reason, decision date and source revision.

    • Record choice, reason and source revision
    • Updates Review decisions
    ApprovalA person approves before the work moves on.
  5. Resolve the result Delivery Lead

    Delivery Lead records acceptance for an approved current revision. For Return or Reject, the owner corrects or reconsiders the package before another decision.

    • Accept or return the correct revision
    • Updates Work packages, Review decisions
Project Manager
Submits the revision, Independent Reviewer decides, and Delivery Lead confirms the resulting package status.

Set up Change Request Management your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started