The real cost of a slow submittal review

Submittals are the most common source of programme slippage that nobody planned for, and the reason is arithmetic rather than negligence.

Take a facade package with two hundred technical submissions. Assume a contractual review period of fourteen days, and assume — realistically — that a third come back for resubmission. That is not a fortnight of review time. Depending on how the queue is sequenced, it is somewhere between four and nine months of elapsed calendar during which work cannot start.

Why it stays invisible

A programme shows the facade installation activity. It does not show the approval queue feeding it. So the slippage accumulates in a place nobody is looking, and surfaces as a delayed start that gets attributed to the subcontractor’s mobilisation.

Meanwhile each party has a partial view. The contractor knows what has been submitted. The consultant knows what is on their desk this week. Nobody holds the ageing profile of the whole queue, which is the only number that would have prompted action.

Three bottlenecks that account for most of it

• Incomplete first submissions. A submittal missing a required attachment is returned without review, costing a full cycle. Guided submission removes most of these.
• Unrouted items. Submissions that reach the wrong reviewer, or sit unassigned, are the single largest source of dead time and the easiest to eliminate.
• Resubmissions treated as new. When a Code C comes back as a fresh submission with no history, the reviewer starts from scratch and the cycle takes as long as the first one.

What visibility changes

The intervention that works is not chasing harder. It is making the queue and its ageing visible to both parties at once.

When a consultant can see that eleven items have been with them for more than twenty-one days, and the contractor can see the same list, the conversation stops being about blame and becomes a question of sequencing. In our experience that alone typically removes between a third and a half of the accumulated delay, without anyone working longer hours.

A number worth tracking

If you track one metric on submittals, make it median turnaround by reviewer, measured against the contractual period rather than against the date somebody picked it up.

It is uncomfortable, because it makes performance visible. That is precisely why it works.