Site Operations
Site Mobilisation, Demobilisation & Client Handover — UAE Authority Readiness
Jurisdiction-first readiness control for UAE projects: resolve the controlling authority before issuing any checklist, then run the M-01 to M-20 mobilisation gate, the D-01 to D-24 demobilisation, closeout and client-handover register, the timeframe model and the management dashboard. A planning and evidence-management tool — verify requirements, portals, fees and inspection availability with the appointed consultant and responsible authority before formal submission.
v2.1Updated 9 Aug 2026ADOSH-SF v4.1 (February 2026)Learning Objectives
- Resolve emirate, plot, mainland versus free zone or master developer, and work scope before any checklist is issued.
- Build authority cards that state why the item appears, the gate it controls, required evidence, owner, dates, reference and expiry.
- Run the M-01 to M-20 mobilisation checklist to a documented Day-One go/no-go decision.
- Run the D-01 to D-24 demobilisation, closeout and handover register with separate authority-ready and client-ready status.
- Distinguish a published authority service target from a project planning allowance.
- Report Day-One readiness, handover readiness, submission health, evidence completeness, open snags and expiry exposure.
Training Video
ProPreview
30-minute video
Unlock this training video
The first 3 modules are free. Upgrade to Pro to watch every module, save progress, and issue certificates.
Upgrade to ProNarrated Voice-Over
30-minute narrated walkthrough, levelled to -16 LUFS across 16 sections. Use the chapter list to jump to a stage.
Download chapter markers (WebVTT)Module Content
1. Jurisdiction First, Checklist Second
A UAE project must not be treated as one uniform approval path. The workflow starts with an Authority & Jurisdiction Resolver capturing emirate, exact development or plot, mainland versus free zone or master developer, client/developer, project type, height and occupancy category, enabling-works scope, road and utility impacts, temporary works and the required completion date. Every generated item is labelled required, conditional, client-controlled, consultant-controlled, contractor-controlled or not applicable. Users tick an item complete, record a reason for removal, attach evidence, assign an owner and retain an approval number and expiry date. The product message is explicit: this planner helps you prepare for likely authority, developer and client requirements; it does not replace the appointed consultant, permit conditions or formal authority confirmation.
2. Four Stages, One Control Centre
The area is a Project Readiness and Handover Control Centre, not only a start-of-site checklist. It answers four questions at any point in the job: which authority controls this plot, what must be approved before this work starts, what evidence must be retained while work proceeds, and what has to be closed, cleared and handed over before the client accepts the asset. Stages run as Mobilisation, Live Compliance, Demobilisation/Closeout and Handover, each with its own gate. Page blocks: project profile, jurisdiction resolver, Day-One readiness, authority submissions tracker, live construction evidence, demobilisation and closeout, client handover, and a management dashboard exporting a weekly readiness pack.
3. Authority Card Design
Each card names the authority (Dubai Municipality, DDA/Trakhees, DMT/municipality, SEWA, Civil Defence, RAK Municipality, client/master developer or a free-zone engineering department) and states why it appears. The gate is one of: before mobilisation, before a defined work activity, before permanent connection, before completion/handover, or ongoing. Required evidence is a permit, NOC, certificate, stamped drawing, appointment letter, work plan, inspection report, test report, as-built, clearance or client acceptance record. Owner, target submission, authority response target, latest acceptable date and dependency date are tracked. Status runs Not started, In preparation, Submitted, Comments received, Resubmission due, Approved, Expired, Not applicable, or Waived by client — with authority reference, issue and expiry date, attachment, version, approver and a reason where marked not applicable.
4. UAE Authority and Jurisdiction Matrix
Dubai: Dubai Municipality building control, Dubai Civil Defence and DEWA on the mainland path, with RTA, drainage, telecoms and master-developer NOCs as conditional interfaces. Do not default a free-zone development to the municipal path — identify the zone (DDA, PCFC/Trakhees or other) and use its planning, engineering and EHS process. Abu Dhabi: DMT through the relevant municipal pathway plus Abu Dhabi Civil Defence Authority; confirm whether the plot is mainland Abu Dhabi, Al Ain, Al Dhafra, KEZAD, ADGM, Masdar or another master-developer area. Sharjah: Sharjah Municipality, Sharjah Civil Defence and SEWA; confirm SAIF Zone, Hamriyah, SPC Free Zone or other control before showing municipal forms. Ajman: Ajman Municipality and Planning Department, Civil Defence, EtihadWE, telecoms and Ajman Sewerage. Ras Al Khaimah: RAK Municipality via RAK Digital/Sanad with RAKWA, telecoms and green-building interfaces. Fujairah and Umm Al Quwain: municipality plus Civil Defence and utility interfaces, with free-zone and port/master-developer procedures confirmed first. Trakhees does not control all of Dubai — pathways are zone-dependent.
5. Mobilisation Checklist M-01 to M-20
M-01 confirm plot, emirate and jurisdiction before programme baseline. M-02 appoint consultant and confirm contractor and subcontractor registrations. M-03 create the authority register and submission schedule. M-04 validate building or enabling-work permit status before physical works. M-05 confirm site possession, access rights and developer conditions. M-06 obtain mobilisation, hoarding, signboard, temporary works and excavation approvals where required. M-07 complete authority, fire, utility, road and telecom NOC review. M-08 issue approved drawings and a controlled document register. M-09 submit the HSE plan, emergency plan, risk register and site rules before workforce arrival. M-10 approve the site layout. M-11 install hoarding, signage, lighting and security. M-12 establish welfare, drinking water, sanitation, rest and first aid sized for workforce and climate. M-13 verify temporary power, water, boards, earthing and inspection records. M-14 establish fire points, emergency routes, muster area and contacts. M-15 mobilise only approved plant, lifting equipment and operators. M-16 approve RAMS, lifting plans, traffic plans and the PTW workflow. M-17 complete workforce and subcontractor onboarding before access. M-18 establish environmental controls. M-19 set the client reporting cadence. M-20 hold a documented Day-One readiness go/no-go review. Every row supports Complete, Not Applicable, Remove with Reason, Owner, Target Date, Evidence Link, Authority/Client Reference, Expiry Date and Escalate.
6. Demobilisation, Closeout and Handover D-01 to D-24
This is a separate register started long before physical completion, with two status types — authority-ready and client-ready. D-01 to D-04 freeze the closeout register, agree the authority, utility and client completion sequence, run progressive as-built capture and build the testing, commissioning and witness schedule 8–16 weeks out. D-05 to D-08 close quality non-conformances, complete fire and life-safety clearance, secure utility and infrastructure clearances and control the municipal or free-zone completion-certificate path. D-09 to D-16 run the joint pre-handover inspection, close the snag register, compile O&M manuals and asset register, warranties, test certificates and statutory records, deliver client training, transfer keys, access cards, BMS credentials and data, and record residual risks. D-17 to D-24 approve the demobilisation plan, isolate and certify temporary services, remove temporary works and plant safely, dispose of waste through approved channels, reinstate roads and adjacent property, close permits, accounts and access, archive the final record and hold the lessons-learned review. Emirate prompts apply: Ajman completion requires the sewerage-certified form, inspection reports, roof-insulation warranty, Civil Defence letter where applicable, roads clearance, Makani number, communications certificate, police security compliance and a valid building permit; RAK requires preliminary handover, Barjeel green-building evidence and the Civil Defence achievement certificate for defined building types.
7. Timeframe Model and Dashboard
Show two distinct time fields: the published authority service target and the project planning allowance — never label a planning allowance as an authority commitment. DDA states a two-working-day delivery target and six-month validity for its Mobilization Permit; RAK Municipality states three working days for its completion certificate; both remain conditional on a complete, compliant application and applicable inspection. Planning windows run T-16 to T-12 weeks (project setup), T-12 to T-8 (design and interface planning), T-8 to T-4 (authority and client submissions), T-4 to T-2 (site-readiness confirmation), T-2 to Day One (controlled mobilisation), then 12–16 weeks, 8–4 weeks and 2 weeks before handover for closeout mobilisation, testing and acceptance. Dashboard measures: Day-One readiness, handover readiness, jurisdiction confirmed, authority submission health (amber for response due within five working days, red for overdue response or resubmission), evidence completeness (amber under 95%, red under 85% at a critical milestone), open snags and expiry exposure (red within 14 days, amber within 30). Add a one-page 'Decisions Needed This Week' table stating the blocker, controlling authority or client, owner, required decision, last safe decision date and programme consequence.
8. What the Client Should Expect
Set expectations up front: approvals and inspections take authority time that the project does not control; temporary disruption, witness testing, snags, residual risks, warranties and record handover are part of a controlled process, not an end-of-job document chase. A submission is not an approval. Physical progress is not handover readiness. Client acceptance, completion certification and demobilisation are tracked separately, and controls or evidence are not removed or archived until client and authority obligations are complete.
Knowledge Assessment
1. The first step in the mobilisation workflow is to:
2. Which statement about Dubai is correct?
3. The DDA Mobilization Permit page states:
4. M-20 requires:
5. The demobilisation and closeout register should be started:
6. Which two status types apply on the closeout register?
7. Authority submission health turns red when:
8. Expiry exposure alerting is:
9. For Ajman mainland completion, the checklist must capture:
10. A published authority service target should be presented as:
Certificate
Pass the quiz (8 / 10) to unlock your certificate.
Acknowledgement
By signing below, you confirm you have watched the training video, understood the material, and will apply these controls on site.