Modify requisitions
How modify requisitions are reshaped as AGI capability advances.
The bottom line
Roughly 85% of the work in Modify requisitions is information-shaped — already within reach of AI delivery. The question here is not whether it shifts, but which tasks go first and who staffs the residual.
Why: With no child occupations seeded, the evaluation relies on the process name 'Modify requisitions' within the Retail Trade context. Modifying a requisition is an administrative task that involves updating procurement records, quantities, or approval routing within a digital ERP or procurement system. Because this work consists entirely of software-based information transformation rather than the physical handling of goods, it sits firmly in the digital band.
grounded in the economy graph · digital scalar 0.85 · digital
Business-as-Code
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Modify requisitions sits inside a larger value-flow — 1 parent structure it composes into. The hierarchy is grounding, not the story: it tells you which aggregate exposure Modify requisitions inherits.
Where Modify requisitions sits
Related articles
No articles yet for this entity.
Recent capability events
No capability events for this entity yet.
How the work flows
Trigger: A stakeholder or approver requests a change to an existing purchase requisition due to shifted requirements, budget constraints, or data entry errors.
- Receive modification request for existing requisition
- Retrieve active requisition from the procurement system
- Validate requested changes against budget and purchasing policies
- Update quantities, specifications, delivery dates, or accounting codes
- Route for re-approval if the modification exceeds defined thresholds
- Commit the updated requisition to the purchasing queue
Outcome: The requisition reflects the requested changes, clears necessary re-approvals, and is queued for purchase order creation.