The Build in Dubai platform is where more Dubai building and fit-out submissions are consolidating. As Dubai Municipality expands AI-assisted permit checking, messy layers, conflicting dimensions and bloated DWGs become expensive—not just untidy. Cleaner packages clear faster whether a human or an automated rule set reviews them.
This guide gives drafters and consultants an AI-ready drawing checklist: layer hygiene, PURGE/AUDIT habits, title consistency, Bluebeam markup discipline, and links to official DM and Media Office sources. It complements—not replaces—the authority’s portal help text.
Key takeaways
- Treat every sheet as machine-readable: consistent names, layers, dims.
- PURGE and AUDIT before every upload.
- Align notes to Dubai Building Code clauses you claim compliance with.
- Keep markups in Bluebeam structured for resubmission.
Official references
Dubai Municipality is the home base. AI permit direction has been covered via Dubai Media Office, including releases such as Dubai’s AI building permit announcements. Download the Dubai Building Code only from the official DM page.
AI-ready drawing checklist
| Check | Why it matters | How |
|---|---|---|
| Layer standard | Automated filters and human review both fail on “Layer1” | Follow UAE layer standards |
| PURGE / AUDIT | Corrupt or bloated files stall uploads | See PURGE and AUDIT workflow |
| Title-block vs form | Mismatched plot/parcel data triggers rejects | One source spreadsheet for all sheets |
| Dimension consistency | AI/rulesets flag contradictions | Cross-check plans vs elevations before PDF |
| Code notes | Claims must match DBC | Quote current DBC section IDs carefully |
| Markup trail | Resubmissions need clear deltas | Bluebeam Revu markups |
Package structure that reviewers like
- Cover / index with sheet list matching PDF filenames.
- Architectural plans, elevations, sections with one north and one unit system (mm).
- Fit-out or specialty packages clearly separated—see Dubai fit-out approval drawings.
- Shop drawings only when that gate is open—process map in shop drawing approval process Dubai.
- If BIM is in scope, pair PDFs with validated models—Dubai BIM mandate 2026 and IFC OpenBIM workflow.
Pre-upload 15-minute drill
- Plot to PDF at the required sheet size; zoom 400% on a random dimension.
- Search PDF for “TBD”, “???”, and default text styles.
- Confirm every Xref is bound or packed per CDE rules.
- Run one peer review with Bluebeam status symbols only—no chat-app markups.
Naming convention that survives resubmission
Automated systems and tired reviewers both hate random filenames. A durable pattern:
PROJECT_DISCIPLINE_SHEETNO_REV_DATE.pdf— e.g.DXB123_AR_A101_R2_20261027.pdf- Keep the same sheet number when content updates; bump revision only.
- Mirror names in the drawing index and the portal upload list.
- Never upload
final_FINAL_v7.pdfbeside the official set.
What AI-oriented checks tend to punish
- Conflicting room areas between schedule and plan.
- Missing fire-exit widths that the code tables expect.
- Layers or objects that plot as solid black blobs after a bad CTB.
- Scanned PDFs with no vector text for searchable fields.
None of this replaces a licensed engineer’s code review—it simply reduces avoidable portal loops before that review starts.
Vector vs scan policy
Where the portal accepts either, prefer vector PDFs from CAD/BIM. Scans of marked-up paper should be temporary clarification only, not the record set. If a scan is unavoidable, OCR and a typed revision narrative reduce AI/search friction.
Internal QA sign-off box
Add a small stamp area on the index sheet (or CDE metadata) with:
- Drafter · Checker · Discipline lead initials.
- PURGE/AUDIT done (date).
- Code notes verified against DBC edition date.
- Filename list matches portal list (yes/no).
That stamp will not impress the algorithm—but it catches human misses before the algorithm does.
Sheet index columns that help everyone
| Column | Purpose |
|---|---|
| Sheet number | Stable ID across revisions |
| Title | Human-readable content |
| Rev | Matches title block |
| Scale | Spot-check annotative mistakes |
| Model/BIM link | IFC or RVT revision ID if applicable |
| Portal filename | Exact upload name |
Export the index to CSV for the document controller. Humans mistype portal names; spreadsheets mistype less often.
Resubmission delta sheet
When the portal or reviewer returns comments, attach a one-page delta: comment ID, response, sheet changed, revision. Bluebeam statuses should match that delta. Reviewers clear packages faster when they do not hunt through unmarked PDFs for what actually changed.
Consultant coordination tip
Before uploading, ask the lead consultant which PDF standard they want (single multi-page vs one file per sheet). Match that exactly. A perfect drawing set uploaded in the wrong file structure still burns a review cycle on the Build in Dubai platform.
FAQ
What is the Build in Dubai platform?
Build in Dubai is Dubai’s digital construction permitting and related services environment under Dubai Municipality. Exact modules evolve—always follow the current dm.gov.ae instructions for your permit type.
How do I make drawings AI-permit ready?
Keep layers consistent, purge junk, match title-block data to forms, align dimensions across sheets, and ensure notes reflect Dubai Building Code requirements before upload.
Where is the Dubai Building Code published?
Dubai Municipality publishes the Dubai Building Code on its official planning and construction pages. Download only from dm.gov.ae or authorised competent entity sites.
Need permit-ready drafting packages? D3DDD · info@d3ddd.com.
ConversionConversion EmoticonEmoticon