Skip to main content
FIRSTPASS ADAbu Dhabi Back to home

Coverage

What FirstPass checks — and what it does not

Run the review on a package and this is what happens. Every figure is read from the same registers that run the product.

45

in-scope Abu Dhabi code sources

38,356

requirements tracked, each one accounted for

839

drawing-checkable — the ones a drawing can actually show

11

built-in checks on every package, no model involved

How a package is reviewed

Your package

Uploaded as you would submit it

Read sheet by sheet

Text layer first; every value keeps its sheet and place

AI review

Comments a reviewer is likely to raise, on the sheet they came from

Clause checklist

The drawing-checkable clauses for your disciplines, cited

Built-in checks

11 document-integrity checks, no model involved

Your engineer decides

Confirm, dismiss with a reason, or resolve — every item

Report + Register

Pre-Review Report and Cross-Check Register, with the decisions in them

What you receive

Review comments that cite the clause

About nine in ten code comments cite the clause they rest on and point at the sheet. Each is a screening prompt for your engineer to confirm or dismiss — never a compliance verdict.

A clause checklist your engineer works through

839 drawing-checkable requirements in the library; a single-discipline package typically receives a few hundred, each clause-cited. Decisions are recorded under your engineer's name and travel into the report.

Built-in checks, run automatically

11 document-integrity checks on every package with no model involved: drawing-number naming conformity, title-block machine-readability, drawing register versus sheets present, revision consistency across the set and more. They cite no code clause and never claim to.

What is not automatic

No automatic pass/fail code rule today

A rule is switched on one at a time, only after a named engineer has verified it against the printed clause. No deterministic clause-cited rule returns automatic results today, and no page of this site will imply otherwise.The AI code check reads each applicable clause against the drawings and states a result for your engineer to confirm; it is measured and is issued in the Pre-Review Report. As at 20 September 2026, 84% of the clause check's verdicts were correct on inspection, and 79% of the potential non-compliances it flagged were confirmed.

Most of a design manual is not on a drawing

Requirements about reports, approvals, construction, process, permissions or professional judgement live outside the drawing set. Every one is tracked and routed to your engineer — never counted as screened.

Screening is never a statement of compliance

FirstPass predicts what a reviewer is likely to raise and shows the evidence; your engineer decides. Zero findings does not mean full verification, and the report says so on its face.

Your own codes. Project-specific standards or client design criteria can be added to your workspace and enter the same flow — clause-cited prompts to your engineer, same traceability, visible to your organisation only.

Run it on a package

The clause-by-clause register behind these figures is maintained continuously; clients can request a walkthrough for their discipline as part of onboarding.

What FirstPass gives your team

A stronger review before submission

Six engines, one traceable workflow. Open a card for what each one does.

Document checks

Available

Checks drawing registers, title blocks, revisions, numbering and document completeness across the whole package.

What it does
  • Register versus submitted sheets
  • Revision consistency across the set
  • Title-block field coverage
  • Duplicate drawing numbers
  • Legend completeness — designators used on a sheet but absent from its legend
  • Submission stage recorded in screening and reports

AI review

Available

Reads your drawings and surfaces the comments a senior reviewer is likely to raise — IDAS-style, code, design and cross-discipline — each grounded to a sheet for you to accept or dismiss. Likely comments, not every one, and never a compliance verdict.

What it does
  • Code comments cite the held Abu Dhabi standards — a clause we cannot vouch for is removed, never shown
  • Every code comment has its clause retrieved from the standard we hold and vouched before you see it. Where the comment also attributes a value to the code, that value is checked against the clause's own text (102 of 111, 92%); where it quotes a reading off the drawing, that reading is checked as printed there (61 of 68, 90%). A comment that attributes no value has nothing to check that way, and is not counted as though it had passed.
  • Grounded to a specific sheet
  • Tagged by type (IDAS · Code comment · Design · Cross-discipline)
  • A prediction to verify — never a compliance verdict
  • Sent to the engineer, never auto-applied
  • In testing against the authority's own review comments on real submissions, the review raised a comment touching 40% of them and matching 30% outright. About six in ten authority comments concern something a drawing can show; against those, it touched 49% and matched 40% outright. Of the review's own comments checked back against the drawing, 62% held, 9% did not, and 29% could not be judged either way. Upload the whole volume the authority will review: on a partial upload the rate falls to 9%.

Code check

Available

The Abu Dhabi code requirements that apply to your sheets, each cited to its clause and printed page.

What it does
  • Scoped to your drawings — 839 requirements from 20 codes, spread unevenly over the 13 disciplines your sheets evidence
  • Nothing you never drew — a bridge-deck clause is withheld before anything is checked
  • Cited, never recalled — code, clause, edition, printed page. A citation we do not hold verbatim is stripped before you see it
  • Code compliance screening — every applicable clause of the held Abu Dhabi standards is checked against your drawings and reported as satisfied, a potential non-compliance for your engineer to confirm, or not evaluable with the reason. As at 20 September 2026, 84% of the clause check's verdicts were correct on inspection, and 79% of the potential non-compliances it flagged were confirmed. 958 clause checks so far over 12 packages.
  • Excluded and counted — 36,922 no drawing can evidence, 555 blocked on a source, 40 unmatched to a sheet

Coordination

Available

Reconciles references and interfaces across sheets, across disciplines within a package, and across the separate discipline packages of one submission.

What it does
  • Cross-sheet — a reference to a sheet not in the set, and two sheets sharing a number, found deterministically on every package. Datum agreement is live and returns a determination on screened packages. Level agreement is withdrawn: no sheet carries both a chainage and a level at usable confidence
  • Cross-discipline — Roads ↔ Drainage ↔ Structures ↔ Utilities, AI-assisted over selected sheets. Live: 24 findings issued on screened packages
  • Coordination sets — separate discipline packages screened against each other for a shared base drawing, datum and alignment. Live: 47 findings issued
  • In testing on a multi-discipline submission, the cross-package review touched 1 of the 3 coordination comments the authority raised (4 of 8 on a broader reading) — a small set; the rate is stated, not claimed. It reads up to 16 detail sheets from each member of a four-package set; where a package holds more, the run is a sample and the report says which sheets it read.

Revision assurance

Available

Links a resubmission to the previous revision of the same submission and compares them — which comments recur, which are resolved, which are new, and which sheet revisions moved. Run and checked on a real revision cycle.

What it does
  • Link a resubmission to its previous revision, matched on submission reference, shared discipline and upload order
  • Recurring comments are named, not just counted — each is re-decided on the new revision, never carried silently
  • What it cannot place, it says so: a sheet with no recorded revision is never reported as unchanged, and a sheet with no drawing number is disclosed rather than dropped
  • Compared on 4 real revision cycles — most recently a 21-sheet resubmission compared with the 21-sheet issue before it: 19 revised, 0 withdrawn, 0 added, each checked against the drawings

Deliverables

Available

A Pre-Review Report and a Cross-Check Register, issued as DRAFT until your engineer has decided every comment.

What it does
  • 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
  • FINAL is refused, not degraded, while a comment is open, a not-evaluable check is unacknowledged, a sheet is unread or the drawings changed after the review — the refusal names what is blocking
  • Every issued FINAL stays downloadable by version, including one a later version has superseded

The engineer is 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.

Which disciplines the code check covers

Disciplines covered today

  • Traffic284
  • Roads193
  • Stormwater & Drainage106
  • Irrigation & Landscaping96
  • Structures52
  • Road Safety37
  • Survey28
  • Access Design16
  • Rail & Transit11
  • Street Lighting9
  • Pavement Design3
  • Utilities / NDRC3
  • Geotechnical1

Clause counts are per code discipline. A package receives the union of the disciplines its own sheets carry, so a roads submission draws on more than the roads row alone. A row in single figures is a toehold in that discipline, not coverage of it.

FirstPass holds 45 in-scope Abu Dhabi code sources and 38,356 requirements, each one tracked and accounted for. The card above states how they divide. No deterministic clause rule passes or fails your drawings automatically today. The AI code check states a result for your engineer to confirm. A rule is enabled only after a named engineer verifies it against the printed clause, and it may not raise a finding against your drawings until its precision and recall have been measured. What the checklist gives your engineer is a scoped, cited list to work: a screening aid, never a compliance verdict. How the code check works

Coverage

Clear about what was checked—and what was not

Every check ends in one of five outcomes. A gap is disclosed, never dressed up as a pass.

Passed

The check ran and the evidence satisfied it.

Potential issue

A comment to review, with its evidence.

Not evaluable

Required evidence was missing — reported, never counted as a pass.

Not applicable

The rule does not apply — at this submission stage, or in the road context your engineer recorded.

Error

The check could not complete — surfaced honestly.

Zero findings does not necessarily mean full verification when the required evidence was unavailable. FirstPass does not certify compliance and does not catch every possible authority comment — it is a screening aid that puts evidence in front of the engineer who decides.

Discipline & stage awareness

One package, multiple disciplines

Roads Traffic Stormwater & Drainage Sewerage Potable Water Irrigation & Landscaping Street Lighting Electrical Power Telecommunications Utilities / NDRC Structures Survey Geotechnical Pedestrian & Cycle Rail & Transit Planning & Masterplan

Document screening runs on any of these disciplines. The code checklist is a narrower thing: it is concentrated in roads, traffic, drainage, landscaping and structures, and several disciplines listed here carry no drawing-checkable code requirements at all today. The per-discipline code table names its rows in the code library’s own taxonomy, not this one, so Road Safety, Access Design and Pavement Design carry clause counts without being disciplines you declare a package under. Coordination coverage depends on the evidence available for the declared submission stage.

Concept StudyConcept DesignPreliminary DesignDetailed DesignOther / Authority-defined

FAQ

Questions, answered plainly

What does FirstPass check?+

Document readiness (registers, title blocks, revisions, numbering) and cross-sheet coordination (references, duplicates), and an AI review that surfaces likely IDAS, code, design and coordination comments.

Clause-cited standards screening is deliberately narrow. Its source is cleared to cite, and no clause-cited rule is active today, so it screens nothing on your package. When one is activated it will read its value only where the drawing itself labels it — from the drawing text beside that label, entered by an engineer, or taken from an AI reading only where the drawing’s own text confirms both the value and what it measures. Document, cross-sheet and coordination screening are unaffected and run on every package. Two built-in checks have been withdrawn — required sheets for the submission type and level agreement at a shared chainage — because the evidence they need cannot be extracted from drawings today; they are switched off rather than left to abstain.

FirstPass currently has no verified through-lane minimum check: the standard varies the minimum by road class, and no through-lane rule has yet been authored and reviewed against a road class your engineer records.

Where required evidence is missing a rule reports not evaluable rather than passing, and where some sheets are unclassified the result states how many readings it could not reach instead of passing over them silently.

Beyond those rules, the AI code check reads each applicable printed requirement against the drawings and states a result with both values — satisfied, not satisfied, not determinable, or not applicable. The AI code check reads each applicable clause against the drawings and states a result for your engineer to confirm; it is measured and is issued in the Pre-Review Report. As at 20 September 2026, 84% of the clause check's verdicts were correct on inspection, and 79% of the potential non-compliances it flagged were confirmed.

Does FirstPass certify that a design is compliant?+

No. FirstPass is a screening aid. It raises comments and findings with their evidence for a professional engineer to review. It never issues a compliance judgment.

Does the code check just ask me to “confirm” things?+

No — that is the failure it was built to replace. Given the printed clause and the drawing, it reads the value, compares it and states the result: “vertical clearance dimensioned 6500 (MIN) on the sheet; TR-514 cl. 3.10.2 requires 6.5 m minimum — satisfied.” If it cannot read the value it says not determinable; if the clause governs a different element than the one drawn it says not applicable; if a number on the sheet measures a different quantity than the clause governs, the drawing’s own text layer is used to reject it. Every result is a screening result for your engineer, not a determination.

How is AI used?+

Less than you might expect. Document and cross-sheet checks are deterministic code, and dimensions printed as text on the drawing are read directly from it — no model involved. AI is used to predict the comments a senior reviewer would likely raise, and to propose readings of dimensions drawn as graphics rather than printed as text. Every AI comment is a prediction for the engineer to accept or dismiss. An AI reading only reaches a standards rule where the drawing’s own text independently confirms both the value and what it measures; anything less waits for an engineer to confirm it.

Which disciplines are supported?+

Generic document screening can span many infrastructure disciplines. Detailed standards and coordination coverage depends on the active rules and the evidence available for the declared submission stage.

Does FirstPass support multiple submission stages?+

Yes — Concept Study, Concept Design, Preliminary Design, Detailed Design and Other / Authority-defined. A rule runs only at the stages it is scoped for; at any other stage it reports not applicable rather than passing.

What happens when a check cannot be completed?+

It is reported as a coverage limitation — not evaluable — never silently presented as a pass. Zero findings does not necessarily mean full verification.

What deliverables do I receive?+

A Pre-Review Report (PDF) and a Cross-Check Register (XLSX), sharing one consistent finding-number sequence and carrying your engineering decisions.

Can I review and dismiss findings?+

Yes. Engineers accept, dismiss (with a reason), resolve and note each finding. A draft report can be generated at any point and is watermarked DRAFT; a FINAL issue is refused while any finding is still open or any not-evaluable item is unacknowledged.

How does prepaid package pricing work?+

A pack is prepaid and one-time, and it buys pages for your organisation rather than a licence tied to one drawing package. Screening a package spends its sheet count once; re-screening it spends nothing further. Pages you have not spent stay in your balance for your next submission. Your first 10 sheets are free, once per organisation.

The code check — FirstPass AD