A material request workflow that actually survives the prorab
Most paper-based material request processes die within a month. Here is the four-step workflow Uzbek sites use to keep foremen, directors, and warehouses in sync — and where it breaks.
The reason paper-based material request processes fail is not laziness. It is that a prorab on a muddy site at 7 a.m. cannot fill out three forms, find a director to sign, and fax the result to the warehouse before the concrete pour starts. A workflow that ignores that reality will be abandoned inside a month. Here is what Uzbek firms that make it work actually do.
Step 1 — The prorab files the request from the site, not the office
The request has to leave the foreman's hands within 60 seconds or it will not happen. That means a phone-based form, a Telegram bot, or at worst a WhatsApp message to a designated number — not a paper slip that must reach the main office. Three fields are enough: material, quantity, and the SMETA section it belongs to. Everything else — delivery location, urgency, notes — is optional and usually unnecessary.
Step 2 — The director approves or reroutes in under an hour
A request sitting in a director's inbox for three days is a request that gets bypassed. The director has two decisions to make: is this inside the SMETA line, and is it urgent enough to bypass the normal delivery schedule. The first check is automatic if the request carries a SMETA section number; the second is a 10-second judgment call. Anything more complex means the process is overloaded. Escalation — to a second director, to a revised SMETA — is a separate flow that must not block the main one.
Step 3 — The warehouse or supplier dispatches within the agreed window
Once approved, the warehouse manager decides storage location (their site or the central depot) and dispatches against the approved request. If stock is insufficient, a purchase order is triggered, but the original request does not re-queue — the foreman sees the PO tracking the same request number. Splitting this into "approved, pending stock, dispatched" states prevents the foreman from re-requesting the same materials.
Step 4 — The delivery is counted in front of the foreman
The single biggest leak in paper workflows is between dispatch and receipt. A delivery arrives, the truck driver hands over a slip, the prorab signs without counting. Introduce one rule: the count happens in front of the prorab, and a photo of the delivery goes with the confirmation. The warehouse sees the photo. The director sees the confirmation. The SMETA line updates. Done.
Where it breaks
Three failure modes show up. First, requests filed with the wrong SMETA section — fix this by making the section a dropdown from the project SMETA rather than free text. Second, urgent requests that bypass approval — these will happen; do not try to eliminate them, track them as "emergency" and review the pattern monthly. Third, warehouse splits that lose visibility — always retain the original request number through a dispatch chain, no matter how many sub-deliveries it generates.
The two-week trial
Run this workflow on one site for two weeks. At the end, measure: how many requests entered, how many were fulfilled the same day, how many were rejected, and how many bypassed the workflow entirely. If the bypass rate is over 10%, the workflow has friction that needs to come out. Usually the fix is removing a field, not adding one.
A good material request workflow is invisible to the foreman. He types three fields, sees a green check within an hour, and gets the material before he has time to worry about it.