Build your change request tracker.

How to build your change request tracker

1. 1

   Describe the job

   Keep proposed scope changes and their impacts attached to the accepted project baseline.

2. 2

   Review the first version

   Choose how the project coordinator records the request and how the workstream owner reviews the next step.

3. 3

   Refine the views

   Ask First to adjust the fields and views for the people who will use the app.

4. 4

   Test before sharing

   Walk through the process with a sample record and check who owns the next action.

What to include in your change request tracker

• Keep the request in context

  Keep request, baseline, scope change, impact estimate, decision and accepted version together so the next person can understand the request or record.

• When the next step needs a decision

  A client asks for two extra reports after accepting the scope. Keep the request proposed while the owner reviews effort and price; only the accepted revised scope becomes the delivery baseline.

• Keep accepted version visible

  Record the new decision before replacing the accepted scope version.

• Choose what each person needs

  Give the project coordinator a working view and the workstream owner a review view. Keep request and baseline attached to the decision as the work moves between them.