Revit Outsourcing UAE: A Practical Guide for Consultancies

Most Commonly Outsourced Tasks

UAE consultancies most often outsource ELV/ICT system modelling within a larger architectural or MEP model, custom family creation for equipment that isn't in a standard manufacturer library, and general modelling overflow during tender submission or design-development crunch periods. Clash detection and coordination support is another common request, particularly on projects with a compressed BIM coordination schedule.

Keeping Your Own Standards

Outsourcing doesn't mean adopting someone else's modelling conventions. Work is done in your project's existing Revit template, family library and BIM Execution Plan — matching your naming conventions, parameter setup and LOD requirements exactly, so the output slots directly into your project model without requiring your in-house team to rework it to match standards.

ELV and ICT Modelling in Revit

ELV and ICT content is the most frequently outsourced part of a Revit package because it is dense and changes late. A typical scope covers cable containment routes, device placement for CCTV, access control, fire alarm and PAVA, rack and cabinet families, and the MDF and IDF room layouts that link them. Each device family should carry the parameters your schedules need: circuit or data point reference, cable type, mounting height and system tag. Without those parameters, the schedules built from the model will not match the drawings or the BOQ.

Family creation is where most of the effort sits. Non-standard equipment, such as a bespoke gate barrier controller or a specific rack layout, often has no usable manufacturer family, so it is built from a dimensioned reference with connectors placed at real cable entry points. Shared parameters should be loaded from your project file, not created locally, so the same family behaves identically across every project model.

BIM Coordination and Clash Detection

Clash detection works only when the model is federated correctly. Each discipline model should be linked at its agreed origin and shared coordinates, with a clear rule for which clashes are resolved by the modeller and which go back to the design team. Typical ELV clashes include containment crossing ductwork and beams, cable trays blocking access clearances, and wall-mounted devices sitting inside door swing zones. Log each clash with its level, grid reference and status so the coordination meeting works from one list rather than from screenshots.

Drawing Extraction and Revision Control

Sheets extracted from the model should use your title block, drawing numbering and revision scheme, and every sheet should carry a revision cloud and a revision schedule entry when it changes. Views for plans, riser diagrams and schedules should be controlled with view templates so the outputs stay consistent when the model is updated. Before each issue, check that sheet numbers match the drawing register and that no unplaced or orphaned views remain in the project browser.

Quantity Take-off Support

Model schedules can support BOQ preparation for devices, cable lengths, containment and cabinets, but they are only as reliable as the modelling behind them. Cable length schedules should be cross-checked against routing assumptions, and containment quantities should separate straight runs, bends and fittings. Quantities must still be validated against the project specification and the drawings. Where the specification sets wastage, termination allowance or spares, those values override any default in the schedule. We do not publish universal cable or containment allowances, because the correct figure depends on the project.

Authority and Project Requirements

The requirements for drawing submissions, BIM deliverables and ELV layouts vary by project, client and emirate, and they should be taken from the tender documents and the relevant authority or client guidance, not from general practice. Document format, model deliverable stage and the level of detail for fire alarm or surveillance layouts can all be set by the approving body for a given project. Outsourced production support follows those requirements; it does not replace the design responsibility of the consultant of record. Statutory approvals, authority submissions and site commissioning remain with the project team.

Inputs Your Team Should Provide

A smooth engagement starts with a complete information pack: the BIM Execution Plan, the Revit template and family library, the shared parameter file, the current model or a clear start point, the design drawings for the scope being modelled, the project coordinate system, and the naming and revision rules. Also confirm the CDE to be used and the access method. Missing inputs are the most common reason for delay, so a short checklist agreed at scoping saves rework later.

Deliverable Quality Checks

Each delivery should pass an internal check before it is returned: audit for unused and duplicate families, check parameter population on device families, confirm levels and grids match the host model, verify that links are not pinned to the wrong origin, and review sheets against the drawing register. Keep a short QA log with each issue, its fix and the reviewer's sign-off, so the same error does not recur across revisions.

What a Typical Engagement Looks Like

Most engagements start with a short scoping call to review the BEP and current model state, followed by an agreed modelling schedule with defined delivery milestones. Models are exchanged through your existing CDE (BIM 360, Autodesk Construction Cloud, or equivalent), reviewed by your team, and revised based on markup — the same cycle you'd run with an in-house resource, just distributed across time zones in a way that often lets revisions turn around overnight.