Project teams sometimes treat MIR and SUB as two labels for the same document because both concern materials and both reach the consultant. They answer different questions. A SUB establishes what may be procured or installed; an MIR verifies that the material delivered to site matches that prior approval.

The dividing line: technical approval or site inspection?

A technical Submittal (SUB) is raised before procurement or installation to present the proposed technical choice. It may include manufacturer data, catalogues, conformity certificates, drawings, and required samples. The consultant reviews that package against the specification and design, with owner review where the authority matrix requires it.

A Material Inspection Request (MIR) is raised after material reaches the site and before it is used. The contractor references the approved SUB and records the delivery, quantity, storage location, and inspection evidence. This review checks the physical delivery and its condition against the approval; it does not reopen the original technical selection.

The practical sequence from proposal to delivery

The contractor creates a SUB for the proposed material or system and attaches the required technical data.
The consultant reviews the SUB, records an A/B/C/D response under the project matrix, and routes it to the owner where authority requires.
Once the response permits procurement or installation, the contractor delivers the approved material to site.
The contractor creates a separate MIR linked to the SUB number and the accepted revision.
The consultant inspects the actual delivery and records a response before the material enters the work.

Who reviews each document?

Both documents originate with the contractor and move to the consultant, but the review group differs. A SUB normally needs discipline-level technical review and may pass through several coordinators because it governs what will be built. An MIR sits closer to the site and quality teams, with discipline input when the delivery differs from the approval. Owner involvement remains a matter for the contractual authority matrix.

How A/B/C/D outcomes affect the next action

In operational terms, the response establishes whether the team may proceed, proceed with comments, revise and resubmit, or stop. On a SUB, that result governs procurement or the proposed technical solution. On an MIR, it governs acceptance and use of the delivered batch. The code, reviewer comment, and response date therefore belong in one traceable record.

Common filing mistakes

Typical errors include filing a new product catalogue as an MIR, using a SUB to prove that a shipment arrived, or raising an MIR without the approved SUB revision. Another is issuing a fresh document number for a resubmission instead of a linked revision. Comments then split across registers, and the team loses sight of which version governs the work.

The cost is not merely administrative. Material can sit unused because its technical approval is missing; a site team can mistake catalogue acceptance for delivery acceptance; or the consultant can spend review time moving a document into the correct workflow. A descriptive filename cannot repair a record created under the wrong type.

Why MIR and SUB need separate numbering sequences

A project should keep separate SUB and MIR registers, each with its own sequence, revision history, and current status. Separation exposes the number of open technical decisions and prevents repeated delivery inspections from obscuring the SUB register. It also lets teams retrieve a record by controlled number rather than a changing attachment name.

Separate does not mean disconnected. Each MIR should reference the relevant SUB and accepted revision, while each SUB should expose the inspection requests created from it where applicable. Those links make the record useful during daily control and handover within the contractor–consultant–owner approval chain.

A quick test before choosing the form

If the question is “is this technical choice acceptable?”, start with a SUB. If it is “does this delivery match the accepted choice?”, start with an MIR. Link them by controlled number and revision, not a free-text email reference. Read the construction submittals guide, or book a working demo to see the flow in Mutamad.