Material Submittals and Approvals: What Slows Them Down

On most GCC projects, material cannot be ordered until the consultant approves the submittal. That review sits directly on the critical path, so the quality of the package matters as much as the product. A rejection rarely costs one review cycle; it costs a cycle, a re-issue, a re-quotation and whatever the supply chain does in the meantime.

Why submittals come back

Rejections usually trace to a handful of causes:

• The datasheet does not state the specific model being offered
• A specified standard or approval is claimed but not evidenced
• The submitted item differs from the specification without a written justification
• Technical data is supplied in a different unit or rating basis than the specification uses
• Pages are illegible, partial, or reference a discontinued range
• The package answers the product but not the specification clause that asked for it
• Performance is shown at the manufacturer's nominal condition rather than the project's

None of these are product problems. They are packaging problems, and they are the ones fully within your control.

What a complete package contains

A reviewer should be able to reach a decision without opening anything else. Most sections need:

• A cover sheet naming the specification section, the system and the submittal number
• A clause-by-clause compliance statement, answering each requirement with a page reference
• The manufacturer datasheet with the offered model, size and rating clearly marked
• Dimensional or general-arrangement information where the item has to fit somewhere specific
• Selection or performance data calculated at the project's own design conditions
• Certificates and test reports, current and covering the exact model
• A physical sample where the specification calls for one

Build the package around the specification

Work section by section through the specification clause and answer each requirement explicitly. Where a datasheet covers a whole product family, highlight the exact model and rating being offered rather than leaving the reviewer to deduce it.

Resist the instinct to submit more. A sixty-page catalogue covering a range you are not offering makes the reviewer do your work, and reviewers who are made to do that work tend to return the package. Submit the pages that answer the clause, marked up.

Show performance at the project's conditions

This is where technical submittals are won or lost in the Gulf, and it is worth its own effort on every equipment package.

• HVAC equipment should be shown at the ambient the project actually designs for, not at a moderate nominal rating condition. Air-cooled plant loses capacity as outdoor temperature rises, so a nominal figure flatters the machine.
• Pumps should be shown on the curve at the specified duty point, with the operating point marked, not simply named by model.
• Electrical submittals should show cable selection with the derating actually applied — ambient, grouping, installation method — and the volt drop over the real route length.
• Water treatment equipment should be shown against the feed water analysis for the project, because the same unit performs differently on a different source.

A reviewer who can see your assumptions can approve them. A reviewer who cannot see them has to ask.

Handle substitutions openly

If you are offering an alternative, submit a comparison that sets the specified requirement against the offered product parameter by parameter, and state plainly where it differs. Reviewers approve honest comparisons far more readily than ones that quietly omit a gap.

Where a difference exists, say what it means. A deviation with a stated engineering justification is a discussion; the same deviation discovered by the reviewer is a rejection and a credibility problem on every later package.

Keep the evidence current

Certificates expire. Check validity dates on approval documents before submission, and confirm the certificate covers the exact model, not a related one. Check the scope as well as the date: a document can be valid, genuine and still cover a different size range, a different factory or a different variant of the same family.

Some systems face a second approval route beyond the consultant. Fire fighting work is subject to a civil defence approval regime, and electrical goods entering GCC markets fall under conformity schemes. Do not assume you know today's requirement — confirm with the authority approving your project, and ask the supplier early what documentation exists for the offered item, because that answer sometimes decides the selection.

Read the comment codes properly

Most reviews return one of four positions: approved, approved as noted, revise and resubmit, or rejected. "Approved as noted" is the one that causes trouble — it permits the order but binds you to comments that are easy to skim past and expensive to discover at inspection. Read the notes, transfer them into the purchase order, and confirm the supplier has accepted them before releasing.

Run a register

Keep a live register: submittal number, specification section, date issued, date returned, status, revision and the linked purchase order. It shows at a glance what is holding the programme, and it makes the resubmission cycle a short one because you know exactly what changed.

Submit early, in batches that make sense

Group items by system and submit long-lead equipment first. The programme value of an early approval is usually far greater than the effort of preparing it sooner — and an approved submittal in hand is what turns a quotation into an order without another round of questions.