1. IT Procurement System
  2. Features
  3. Asset requests
Feature · Asset requests

Asset requests

Keep device needs attached to their purchase request.

OverviewAsset requests awaiting review
IT Procurement System · Asset requests

Asset requests awaiting review

Approval conditions

New
ParentDevice classRequested unitsSecurity reviewRequested atStatus
PR-64546DC-817140SR-84708 OctSubmitted
PR-63607DC-767450SR-13919 OctSubmitted
PR-85746DC-499690SR-14610 OctSubmitted
PR-12713DC-439140SR-43926 OctSubmitted
PR-43044DC-793450SR-48608 OctSubmitted
6 of 6 records
DC-817Asset requests · AR-46760
Submitted
ParentPR-64546
Requested units140
Security reviewSR-847
Requested at08 Oct
Example screen with sample data

What you can do

Asset requests in daily work

A laptop refresh can have an asset request for the device class and requested units while the parent purchase request carries the supplier, owner and requested USD amount. The asset record also holds a security review note and its own revision. This lets a reviewer read the device need beside the commercial request.

The asset request has its own status and revision. Its parent connects the device need to the purchasing amount and supplier, but the asset decision date belongs to the asset record. Check both records when a device need changes after a purchasing decision.

How the work is organized

  • Ownership. Buyer records the device need. Purchasing Approver reviews the linked purchasing decision.
  • Record context. Use the parent request and its organization when checking a related record, then confirm the selected supplier and owner where relevant.
  • Evidence. Keep the decision, accepted quantities, attachments and operation outcomes with the same purchase context so later review has the facts in order.

What to agree during setup

Agree when the device request is required and how its security review should be written. Confirm the owning organization and parent request before the asset request is submitted. A change in the device units should be checked against the parent request and its lines.

Rehearse a request for replacement laptops and one where requested units change. Let the Purchasing Approver compare the device need with the parent amount and line quantities. Agree whether a changed asset need requires a new purchasing decision.

Check the handoff on an actual case

Take a submitted asset request and open its parent purchase request. Compare requested units with the relevant purchase lines. Read the security review note before the purchasing decision. After delivery, inspect the asset request decision date and completed status together with the parent receipt evidence.

The Purchasing Approver should check the asset request status and revision alongside the parent purchase decision. The Auditor can then trace the asset need from the parent without confusing an asset decision with a purchase approval.

What your team sees

  • Asset requests awaiting review — Show submitted device needs beside their parent requests.
  • Asset request board — Compare device needs by status and revision.
  • My purchase requests — Open the parent request assigned to the current owner.

Follow the work through

Read request preparation, review and order and receipt reconciliation. The data model shows how the records connect.

What it keeps track of

Data model
Asset requests
IT asset extension requests supporting approval of an IT purchase request.
Purchase requests
IT purchase requests with lifecycle status, owner, counterparty and requested USD amount.
Organizations
Legal entities that own procurement records, with time zone and reporting currency.

Who uses it

Permissions
Buyer
Records the device need.
Purchasing Approver
Reviews the linked purchasing decision.
App Administrator
Maintains organization membership and supplier configuration.

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