Most GRN problems on UAE construction sites are not missing quantities — they are accepted deliveries that should have been rejected at the gate.
Start here
- GRN software overview — how Gestio handles goods receipt workflows
- Procurement software — full procurement chain from MR to GRN
- Audit logs — every inspection decision is timestamped and attributed
Why inspections fail on site
Site teams receive materials under time pressure. The delivery truck is blocking traffic, the foreman needs rebar today, and nobody wants to send it back. So materials get accepted without checking specs, quantities, or damage.
The result: disputes with vendors weeks later, wasted materials, and zero paper trail for who approved what.
What a GRN inspection should capture
Every goods receipt should record these fields before acceptance:
- PO reference — which purchase order does this delivery satisfy?
- Quantity received vs. ordered — partial deliveries must be flagged, not silently accepted
- Visual condition — damaged, wet, rusted, or non-conforming items documented with photos
- Spec compliance — grade, size, brand match the PO line item
- Inspector name and timestamp — the person who physically checked the delivery
If any item fails, the GRN should allow partial acceptance: accept conforming lines, reject others, and generate a return or credit note request.
Controls that prevent silent acceptance
- Require at least one inspection field completed before GRN status moves to
accepted - Attach photo evidence for any rejected or flagged line item
- Lock the GRN from editing after approval — use audit logs to track every state change
- Route rejected items to the procurement team via approval workflows
Operationalize it weekly
Run a weekly report of all GRNs with rejected or partially accepted lines. Group by vendor and project. Vendors with repeated quality issues should be flagged in your vendor management records before the next RFQ cycle.
This is not a one-time checklist. It is a standing control that compounds over months.