1. Change Request Management
  2. Process
  3. Impact assessment review
Process · Impact assessment review

Impact assessment review

An assessment records why the proposed change affects effort or cost. It belongs to a package, has its own status and revision, and can name the preparer and owner. A reviewer needs to see the explanation alongside the change scope.

Step by step

  1. Prepare the assessment Business Analyst

    Business Analyst adds a title, note and link to the parent package and organization. The assessment begins in Draft.

    • Tie the estimate to one change
    • Updates Impact assessments, Work packages
  2. Quantify the effect Business Analyst

    Business Analyst records added hours and dollar cost delta, then checks the figures against the package budget and task plan.

    • Show effort and dollar cost effect
    • Updates Impact assessments, Tasks
  3. Submit for examination Business Analyst

    The assessment moves from Draft to Submitted. The reviewer opens Assessments submitted with the package and preparer visible.

    • Make the estimate ready to read
    • Updates Impact assessments
  4. Examine the source Independent Reviewer

    Independent Reviewer reads the assessment note, package revision, project context and attached evidence. A changed scope calls for an updated assessment.

    • Check scope and supporting material
    • Updates Work packages, Record attachments
  5. Record the decision Independent Reviewer

    Independent Reviewer records Approve, Reject or Return on the related package revision, with a reason.

    • Preserve choice, reason and revision
    • Updates Review decisions
    ApprovalA person approves before the work moves on.
Business Analyst
Prepares the estimate, Project Manager reconciles it with work, and Independent Reviewer decides on the package revision.

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