Keep purchase requests clear before an order is placed.

How to build your purchase requisition tracker

1. 1

   Describe the job

   Give purchase requests a clear business reason, budget reviewer and next purchasing step.

2. 2

   Review the first version

   Choose how the buyer records the requester and how the budget reviewer 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 purchase requisition tracker

• Keep the requester in context

  Keep requester, budget owner, item, quantity, reason and approval decision together so the next person can understand the request or record.

• When the next step needs a decision

  Two departments request the same shared device. Link the demand for a budget review before creating duplicate purchasing instructions.

• Keep approval decision visible

  Keep an approved requisition separate from the purchase order it may lead to.

• Choose what each person needs

  Give the buyer a working view and the budget reviewer a review view. Keep requester and budget owner attached to the decision as the work moves between them.