AI pre-submission review · Abu Dhabi IDAS
An AI review of your drawings, before they become authority comments.
FirstPass AD’s AI review reads your drawing package the way a senior IDAS reviewer would and raises the comments they are likely to raise — each one on the sheet it came from, for your engineer to decide.
FirstPass reads the evidence. Deterministic checks screen it. You decide. A screening aid, never a compliance verdict — every claim on this site is measured on real packages; see the evidence.
Comments on this sheet · 2
Splitter island width 1.60 m is below the 2.0 m required at a pedestrian crossing.
AI code check · measuredfrom drawing text · pinned
status openDecide this commentProvide setting-out data for the alignment.
AI predictionwhole sheet · not pinned
Illustration of a clause-cited comment from the AI code check: the clause, the value read and the result, for your engineer to confirm. No deterministic clause rule passes or fails your drawings automatically today.
Illustrative composition with synthetic data, in the product’s own layout.
- Every sheet read — not a sample
- Your engineer decides every comment
- DRAFT until decided, FINAL only when clean
- Every claim measured on real packages
What you get
Six things, all live today.
Six engines read one package. Each names what it read, what it found and what it could not evaluate — and every result waits for your engineer.
- Available
Document checks
Registers, revisions, title blocks and cross-references checked deterministically, on every package.
- Available
AI review
The comments an IDAS reviewer is likely to raise — IDAS, code, design and coordination — each grounded to a sheet.
- Available
Code check
Applicable clauses of the held Abu Dhabi standards read against your drawings — the value read, the value required, and the result — for your engineer to confirm.
- Available
Coordination
Disciplines of one submission screened against each other for the conflicts a reviewer finds between sheets.
- Available
Revision assurance
Link a resubmission to its previous issue and see which sheets moved, which comments recur and which are new.
- Available
Deliverables
A Pre-Review Report and a Cross-Check Register, issued as DRAFT until your engineer has decided every comment.
No deterministic clause rule passes or fails your drawings automatically today. Every code result is a screening result that reaches a deliverable only after a named engineer verifies it against the printed clause. What each badge means, and the numbers behind it, are on the coverage page.
How it works
Three steps. Your engineer takes the second.
- 1
Upload the package
Your IDAS drawing set as issued. Every sheet in the submission is split, registered and read from the drawing text itself — not a sample — and any sheet it could not read is named.
- 2
Review and decide
Document, cross-sheet and cross-discipline checks run where their evidence exists; the code compliance screening reads each applicable clause against the drawings and states a result — satisfied, a potential non-compliance for your engineer to confirm, or not evaluable with the reason.
- 3
Issue and submit
The report and register are issued FINAL only when nothing is left open — a FINAL is refused while any finding is still open. What could not be evaluated is disclosed, never shown as a pass.
Deliverables
Two documents your team can submit with.
Issued from the same findings your engineer decided, under the same numbering, in the two formats a submission is built from.
FirstPass AD
Pre-Review Report
AD-INF-2026-014
Package identity (as entered by the engineer)
- Disciplines
- Roads, Drainage
- Submission stage
- Detailed Design
- Sheets
- 121
- Report generated
- 19 September 2026
- Issued by
- Example Consultants
- Snapshot
- 3f9c1b7a2e04
1. Package summary. 121 sheets · 44 comments — 9 raised by the deterministic checks, 35 proposed by the AI review for confirmation · 3 checks could not be evaluated and are disclosed, never shown as passes.
DRAFT — findings carry engineer decisions. Coverage limitations disclosed, never shown as passes.
Pre-Review Report
PDFPackage summary, coverage, clause-cited comments with their evidence, engineer decisions, draft/final governance.
| FP No. | Layer | Sev | Finding | Engineer | Designer | Close-out |
|---|---|---|---|---|---|---|
| FP-004 | Code | high | Cycle track 2.00 m wide against a 3.00 m minimum | Accepted | Agreed | Closed |
| FP-011 | Document | medium | Two register drawings are not in the package | Accepted | — | Open |
| FP-018 | Document | medium | Two revision conventions across the set | Dismissed | Not agreed | Closed |
| FP-022 | IDAS | low | Provide swept-path analysis at the bus layby | Accepted | Partially agreed | Open |
One consistent FP number sequence · filters & dropdown workflows · not-evaluable items included. · scroll sideways for the last columns →
Cross-Check Register
XLSXOne FP number per comment, engineer review, designer response and close-out, with dropdowns for each.
Previews use synthetic data in the real documents’ layout. Ask us for a full sample generated from a sanitised package.
Governance
Your engineer stays in command.
Every finding from every engine above is accepted, dismissed with a reason, resolved with a note, or reopened — by your engineer, never by FirstPass. The database rejects a hollow dismissal or resolution. A draft is watermarked as a draft; a FINAL issue is refused while any finding is still open, and the refusal names what is blocking it.
Pricing
Prepaid submission packs.
A pack is paid once and buys pages your organisation keeps until they are spent; screening a package spends its sheet count. Start with the free sheets.
Every pack includes
- Pre-Review Report (PDF)
- Cross-Check Register (XLSX)
- One finding-number sequence shared by both
- Draft and final issue, carrying the engineer decisions
- Coverage limitations disclosed, never shown as passes
How pages work
- Buys pages for your organisation, not a licence tied to one package
- Screening a package spends its sheet count, once
- Sheets are counted from the file you upload
- Re-screening the same package spends nothing further
- Unused pages stay in your balance for your next submission
- A resubmission is a new package and spends its own pages
Before you submit
Review your package before the authority does.
Upload the set as issued. The free sheets are enough to see what a reviewer is likely to raise.