Need capture
Item, quantity, purpose, branch, department, need date.
AWRA OpsHub
Loading workspace...
Give requesters a clean way to raise needs, give approvers the evidence to decide, and give procurement a governed path from request intake to sourcing action.
This page covers request creation, approval queues, value thresholds, comments, attachments, review evidence, escalation behavior, and the controls that keep buying decisions explainable.
Approval queue
Laptop replacement request
IT equipment · KES 148,000
Printer toner replenishment
Office supplies · Low stock signal
Emergency warehouse repair
Facilities · High urgency
Purchase requests should not be vague messages that procurement has to decode. AWRA helps teams capture the operational context before buying begins: item details, quantity, branch, warehouse, department, project, need date, budget line, preferred supplier notes, attachments, and justification.
The request becomes a controlled starting record. Procurement can decide whether to source externally, check existing stock, route approval, ask for clarification, attach evidence, or convert the request into RFQ work.
Item, quantity, purpose, branch, department, need date.
Specification, photos, supplier notes, or internal justification.
Budget line, approval rule, category, and risk signal.
Ready for review
AWRA approval queues are designed to show what matters before a decision is made. Reviewers can see requester details, value, category, branch, linked stock signals, budget notes, attachments, comments, prior decisions, and escalation status.
Separate pending, escalated, returned, high-value, and urgent procurement requests so reviewers act on the right work first.
Ask for clarification, capture approval notes, explain rejections, and keep the conversation attached to the request.
Make attachments, quotes, specifications, budget support, and policy proof visible before approval.
Move sensitive, overdue, over-budget, or high-value requests to the right owner without losing the audit history.
Show due windows, overdue decisions, follow-up reminders, and bottlenecks before procurement stalls.
Only users with the right responsibility can approve, reject, return, or escalate procurement decisions.
Routine replenishment should move quickly. Strategic purchases, emergency buying, restricted categories, and high-value awards should carry stronger review. AWRA helps buyers express that difference with practical approval thresholds.
| Trigger | Approval behavior |
|---|---|
| Low-risk request | Route to procurement officer or department owner for fast review. |
| Budget threshold crossed | Escalate to finance or budget owner before sourcing or award. |
| Restricted category | Require policy owner review and supporting evidence. |
| Emergency purchase | Allow expedited path while preserving reason, actor, and follow-up review. |
| Overdue decision | Notify owner, escalate manager, and surface in action queue. |
Procurement approvals often become important long after the request is closed. A finance reviewer may ask why a vendor was chosen. A manager may ask why a purchase bypassed a normal path. An auditor may ask who approved a high-value request. AWRA keeps the request, comments, attachments, status changes, and approval timestamps together.
Escalation is treated as part of the work, not a side conversation. When a request is overdue, incomplete, high-risk, or outside policy, the system can surface the right owner and keep the action traceable.
Questions, clarifications, rejection reasons, and approval notes remain close to the request.
Specifications, photos, supplier files, quote evidence, and policy documents support the decision.
Once approved, a request can move into RFQ creation, quotation comparison, purchase order preparation, budget review, receiving, reports, and exception monitoring. The approval record stays attached so downstream teams understand why the work exists.
See how requests feed RFQs, POs, budgets, receiving, and integrations.
Open pageUnderstand how approvals and overdue tasks can surface in one role-aware queue.
Open pageSee how evidence, attachments, quote packs, and audit files stay connected.
Open pageHelp Center
Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.