Skip to content
AI REVIEW FOR CONSTRUCTION SUBMISSIONS

Submittal review for construction

Every clause read. Every finding traced.

Mutabaqa reads the specification and the submittal, then shows what is evidenced, what does not match and what is missing. Each finding points to the document and page it rests on, or names the rule it comes from.

150 free pages every month · English documents, typed or scanned

Private preview: sign-up is open to invited addresses for now.

Submittals / C-014Example

C-014Material and product dataDone

Tower B, level 3 reinforcement

Reinforcement · Submitted 2026-03-02 · One file, 9 documents found

4To resolve
1For engineer review
19Evidenced

Top issues42 pages read · 9 documents found · 24 clauses checked

  1. The conformity certificate expired on 2026-02-28, before the submission date

    REG-002Conformity certificate, page 14

    Expiry date: 28 February 2026
    Expired or invalid
  2. Elongation of 12 % on the test report, below the minimum of 14 % the report itself states

    CON-004Test report, page 9

    Elongation (%) 12 min. 14
    MismatchMajor
  3. No bend test report for each bar diameter

    REQ-004Specification, clause 5.3.4

    Evidence not found in the package
    Not evidencedMajor
Fictitious demo data, laid out as Mutabaqa reports it.
  • 17 kinds of submittal
  • One-file packages split into their documents
  • Scanned pages read, even sideways
  • Reports in Excel and PDF

Who it is for

One check, for both sides of the submittal

The contractor preparing the package and the consultant reviewing it look for the same thing: evidence for each requirement, in the documents themselves.

Contractors and suppliers

Send a package that holds up to review.

  • Documents the specification asks for, checked as present or missing
  • Expired certificates and test results outside their own limits, caught before the consultant sees them
  • Values that fall short of a clause, quoted from your own certificates
  • Manufacturer, grade, standard and heat numbers compared across documents
  • A fix list for the technical office, the costliest issues first

Consultants

Review with the evidence in front of you.

  • The top issues first: what is out of date, what disagrees, what is missing
  • Each requirement matched to the lines that evidence it, with document and page
  • Mismatches and gaps set out with the values quoted
  • Anything that needs judgement marked for engineer review
  • A cited record of each review, in Excel and PDF

How it works

From upload to a cited report in three steps

  1. 01

    Upload the specification

    The sections that govern the submittal, or the contract drawings for steel shop drawings, as PDFs. Mutabaqa lists their requirements, each tied to its clause.

  2. 02

    Upload the submittal

    Datasheets and certificates, shop drawings, a method statement, test reports or an O&M manual, as separate files or bound into one with numbered tabs. Scanned pages are read too.

  3. 03

    Read the readiness report

    The top issues first, then what is evidenced, mismatched, missing or left for engineer review, with a compliance matrix and a fix list, in the browser, Excel and PDF.

Before any text is sent to the AI, Mutabaqa removes the email addresses, phone numbers, signature blocks and names after labels such as “Inspected by” or “HSE Officer” that it recognises. The Excel and PDF reports show how many were removed, never what.

Traced to the page

See the line a finding rests on

Open a finding to see the pages it cites, drawn from your own documents, with the quoted lines marked where the page's text is read. A quote that is not on the cited page is discarded.

  • A finding drawn from the documents names the document and page, with the quoted text
  • A finding that rests on a rule names that rule instead
  • Mark each finding as agreed or disagreed, and say why

What it checks

Rules where a rule can decide. A cited reading where a clause must be read.

Requirements against evidence

Each technical requirement is judged against the package, the clauses this submittal answers first: documents asked for, then sizes, grades and properties. The report quotes the lines relied on; a quote not on the cited page is discarded.

Package completeness

Where the specification asks for a document, such as a mill test certificate or a compliance statement, Mutabaqa checks that the package holds one.

Expired documents

The expiry date a certificate or licence states is read from the document and checked against the submission date, each one inside a combined file too: one that has lapsed, or lapses within months of it, is raised. A date left as a blank to fill in marks a template no one completed. Certification schemes are not checked.

Results against their own limits

A test report that prints a limit beside each result is read row by row: a result outside its own limit is raised, with its page. So is a document that contradicts itself, such as a yield strength above the tensile strength it states.

Consistency across documents

Manufacturer, product, grade and standard are compared across documents, a certificate's scope against the product, and heat numbers are traced to the mill test certificate.

Packages bound into one file

A package submitted as one PDF with numbered tabs is split into its documents, each certificate and licence its own, each read and checked with its own pages. Documents of other projects in it are left aside.

Shop drawings against contract drawings

For structural steel, the contract drawings cited on each sheet, their dates and revisions, and the member sizes are compared with the contract drawings uploaded.

Scans, tables and hidden text

Scanned pages are read with OCR, tables row by row, and pages printed sideways turned to be read. A PDF can carry text no reader can see, so each page's text is compared with what the page shows.

The top issues first

The report opens with what is most likely to cost the submittal: a document out of date, values that disagree, evidence missing. Then every finding: its status, its citation or the rule it rests on, a suggested fix where one is needed.

The whole workflow

From the project's specification to the resubmission

The check sits where submittals are prepared and reviewed, for the whole team.

Projects

Upload a project's specification and contract drawings once. Each submittal of the project picks the sections it is checked against.

Required submittals

The submittals a specification asks for, listed from its own words, each with its section and clause, so none is forgotten.

Resubmissions

Upload the consultant's comment sheet with the new revision: each comment is looked for in it, and the report says what the revision shows, what is still shown and what is missing.

Method statements

Besides the specification, a practice checklist of the points reviewers commonly check: roles, sequence, hazards for each activity, lifting, emergency arrangements, permits and inspections.

Draft statements

A draft statement of compliance, or of deviations, made from the report: each clause with what was found, for your technical office to check and sign.

Your team

A company's people share its projects, submittals and monthly pages. Owners invite colleagues and choose who manages the account.

Coverage

Every kind of submittal, read against its specification

Each one is checked clause by clause, with the lines each finding rests on.

Action submittals

Reviewed before purchase, fabrication or installation.

  • Material and product data
  • Shop drawings
  • Structural steel shop drawings
  • Combined services and coordination drawings
  • Samples and mock-ups
  • Design calculations

Quality and information

Showing how the work is done, tested and qualified.

  • Method statement
  • Inspection and test plan
  • Test and inspection reports
  • Testing and commissioning procedures
  • Certificates
  • Sustainability submittals
  • Prequalification
  • Manufacturer's instructions

Closeout

Handed over at the end of the work.

  • Operation and maintenance manuals
  • Warranties and guarantees
  • As-built and record drawings

A method statement's practice checklist is shown apart from the findings: points reviewers commonly check, not requirements of your specification.

Principles

Built to stand up to scrutiny

A check is only useful if its findings can be traced and trusted.

01

Cited, or labelled

A finding drawn from the documents names the document and page, with the quoted text. A finding that rests on a rule names that rule instead.

02

Nothing guessed

A value that cannot be read is reported as Not found. Mutabaqa never fills a gap with a default.

03

No predicted outcomes

Mutabaqa reports the evidence it finds and does not find. It does not predict the outcome of a consultant's review, and it does not replace the engineer's judgement.

04

Personal details removed first

Before any text is read by the AI, email addresses, phone numbers, signature blocks and the names it recognises are removed. Reports count what was removed, never what.

05

Your documents, kept apart

Each company's documents are stored apart from every other company's, and seen only by its own people and, to support them, Mutabaqa's administrator. A company's owners can delete its submittals, and its account, at any time.

Pricing

Start free

No plan to choose. Create an account and check your next submittal.

Free

150free pages checked every month

A check uses the pages it reads: the specification, the package and any comment sheet, at least 10 a check. A 40‑page package against a 10‑page specification uses 50.

Create your free account

Included

  • Readiness report in the browser, Excel and PDF
  • Every finding cited, or labelled with its rule
  • Recognised personal details removed before any AI step
  • Your company's owners delete its data at any time

Need more pages? Ask us once you have an account.

Check your next submittal before it goes out.

Create an account, upload a specification and a package, and read the report.