1. IT Procurement System
  2. Process
  3. Asset context
Process · Asset context

Asset context

A useful rehearsal starts with one purchase request and follows its linked records. The Buyer, Purchasing Approver and Auditor should identify the request revision, decision and any operation result before continuing. Keep the request number in view throughout the handoff.

Step by step

  1. Add asset context Buyer

    The Buyer links the device need to its parent purchase request, with device class, units and a security review note.

    • Links device class, requested units and security review to the purchasing case
    • Updates Asset requests, Purchase requests, Organizations
  2. Review request Purchasing Approver

    The Purchasing Approver reads the asset context beside the submitted parent request before deciding.

    • Compares asset need with the submitted revision and records the purchasing decision
    • Updates Asset requests, Purchase requests, Review decisions
    ApprovalA person approves before the work moves on.

Where it usually breaks

And how to keep it from happening.

  • A changed request is reviewed against an earlier revision. Compare the decision source revision before relying on approval.
  • The selected supplier belongs to a different organization. Check the supplier and request organization before the Buyer records an order reference.
  • A receipt says Failed or needs review but the parent appears complete. Read the failure reason and effect references before acting again.
  • An accepted quantity differs from the requested quantity. Read the line acceptance date and attached evidence before closing the delivery discussion.
Buyer
.
Auditor
Reads authorized evidence; App Administrator maintains organization access.

Set up IT Procurement System your way.

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

How to get started