A submittal workflow is the loop by which a contractor gets the consultant's approval on record before any work depends on it: shop drawings, material submittals, samples, method statements. Best practice has four parts. One register, append-only, with one number per submittal family and a new revision per resubmission. A status on every row that means one thing everywhere — submitted, returned with comments, approved, superseded. A response age on every open row, counted from the day it went out, so delay is a number rather than an argument. And a gate: nothing downstream, from take-off to fabrication, starts on a submittal that is not approved. The register is the referee. It protects the contractor from "you never sent it" and the consultant from "you said it was approved", because the dates live in the same place.
The submittal fight is two-sided. The contractor says the consultant sat on the drawing for six weeks; the consultant says the resubmission never addressed the comments. Both are usually partly right, and the argument is unwinnable without a shared record. A register that both sides can read — number, revision, date out, date back, verdict, comments — turns the fight into a reading. It only works if it is never edited after the fact: a resubmission is a new revision row, the old row is kept and flagged superseded, and nobody can move a date.
Family number (minted once, kept across revisions) · revision · type (drawing, material, sample, method statement) · date submitted · date returned · verdict · comments · the file · who submitted and who recorded the return. Anything less and the referee has gaps in his memory.
The single most useful column in the register is the age of every open row: days since it went out with no verdict. Sorted by age, the register becomes a worklist — the drawing unanswered for 40 days floats to the top and gets chased with a date, not a feeling. Response ages also make the weekly consultant meeting short: the list is the agenda.
A register nobody is forced to consult is a filing cabinet. The discipline comes from what the register controls: quantities cannot be taken off from an unapproved material submittal, and a zone cannot enter fabrication on an unapproved drawing. When the site genuinely cannot wait, the exception is recorded as a fact — who gave the verbal go-ahead, when — so the audit shows it rather than hides it.
On consultant-led projects in Saudi Arabia and the wider GCC, the submittal register has a mirror on site. A material inspection request (MIR) asks the consultant to inspect delivered material before it is used; a work inspection request (WIR) asks for inspection of installed work before it is covered, claimed or handed over. Verdicts are usually coded — approved, approved with comments, resubmit, rejected — and the sequence is enforced by the consultant: no WIR on material that never had an MIR, no handover without approved WIRs. The contractor's job is to raise them in order, in time, with photos, and keep every verdict on the record.