BBM-STD-90-RECORDS_RETENTION_AND_PERSONAL_DATA-V0.1 | Office standard | 4 November 2026 | V0.1 | Private controlled WIP draft for office review
| Version | Date | Change |
|---|
| V0.1 | 2026-11-04 | First issue: closes rows,,,,, (personal-data interface), (decennial and personal-data interfaces), (transfer check),, and top-gap 13 / §1.3 "Records retention & personal-data annex" + cross-doc pointer pass (BBM-STD-87 SensitivityClass and breach record) |
1 Purpose, owner and boundary#
This standard is the one owner of the office retention schedule and of personal-data handling rules for BIM and project information. Other documents keep a pointer only: custody, backup, archive format and disposition mechanics stay in BBM-STD-76; the restricted people register stays in BBM-STD-03 Directory; security classification stays in BBM-STD-87; health and safety information stays in BBM-STD-88.
| Role | Duty |
|---|
| Legal owner (office director or appointed legal adviser) | Rules the final retention value for every record class and every personal-data purpose; signs the schedule revision. The values in §3 are office minimums, not legal advice |
| Records owner (document controller) | Keeps the schedule, applies holds, records disposition decisions per BBM-STD-76 §5 |
| Data-protection lead (named in the Directory) | Keeps the personal-data register (§4), answers data-subject requests, leads breach response (§6) |
| BIM Manager / project information manager | Tags each container with its record class and personal-data flag at creation; no untagged container is Published |
2 Legal basis (checked 2026-11-04)#
| Instrument | What it fixes for this standard |
|---|
| Federal Decree-Law No. 25 of 2025 Promulgating the Civil Transactions Law, effective 1 June 2026 | Art. 821: engineer and contractor jointly liable for 10 years for total or partial collapse and for defects that threaten structural integrity and safety; the period runs from the employer taking delivery. Art. 822: a design-only engineer is liable for design defects. Art. 823: a clause exempting or limiting this liability is void. Art. 824: claims are barred 3 years after the collapse or defect |
| Federal Law No. 5 of 1985 (Civil Transactions Law), Art. 880 | Applies only to contracts signed before 1 June 2026 and governed by the 1985 law. Same retention minimum as below until the legal owner rules otherwise |
| Dubai Law No. 3 of 2026 on the Quality and Safety of Buildings (emirate law, issued 27 February 2026, in force 60 days after Official Gazette publication) | Asset-life obligation, not a design-permit rule: a Quality and Safety Certificate is required 20 years after completion, valid 10 years (5 years once the completion certificate is 40 years old or more), based on an engineering inspection report. Record information handed to the owner must support those inspections |
| Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (PDPL), effective 2 January 2022, Active | Governs personal data in directories, CDE metadata, RFI/issue records, occupancy and CCTV/BMS data, training records and staff metrics. Executive Regulations: as listed on uaelegislation.gov.ae at project start |
| DIFC and ADGM data-protection regimes | Apply where the project, a party or the office sits in those free zones. Confirm the current law and regulator at project start and record them in the BEP; this standard cites no free-zone law number |
3 Retention schedule by record class#
Minimum periods run from handover (the employer taking delivery of the relevant works). "13 years" = 10-year decennial period (Art. 821) + 3-year claim period (Art. 824). Because the 3 years run from the collapse or defect, the legal owner may set a longer period; never a shorter one without a signed legal ruling. A legal hold (claim, dispute, authority request, client instruction) suspends every disposition in its scope until released in writing.
| Class | Record examples | Office minimum | Final value | Disposition rule |
|---|
| RC-01 Design records | Issued drawings, specifications, calculations, design reports, basis of design (BBM-STD-12), design-risk records | 13 years after handover | Ruled by legal owner | Keep the Published/Archived set complete and readable (BBM-STD-76 §2 format rules); never dispose during a hold |
| RC-02 Models | Native models and IFC/BCF/IDS exchanges at each Published revision; federated coordination sets at each gate | 13 years after handover for every Published revision; WIP-only versions until project close-out | Ruled by legal owner | Keep the authoring release and exporter build (BBM-STD-91) with the archive so the record can be opened; superseded WIP disposed only by recorded decision |
| RC-03 Approvals | Authority submissions, decisions, NOCs, conditions, gate records (A/B/C), acceptance records | 13 years after handover | Ruled by legal owner | Keep with the decision scope and conditions; status vocabulary per BBM-STD-93 |
| RC-04 Correspondence | Instructions, transmittals, RFIs, change records, meeting minutes that evidence design decisions | 13 years after handover | Ruled by legal owner | Non-project administrative mail: period set by the legal owner |
| RC-05 Health and safety information | Residual-risk records, H&S information per ISO 19650-6:2025 (BBM-STD-88) | 13 years after handover; operational H&S information passes to the owner for the asset life | Ruled by legal owner | Never disposed while the office holds the only copy of a residual-risk record |
| RC-06 Record / handover information | As-built record models, AIM contributions, O&M information (BBM-STD-75) | 13 years after handover (office copy) | Ruled by legal owner; for Dubai buildings consider the Law 3/2026 inspection cycle | Owner holds the asset copy; the office copy proves what was delivered |
| RC-07 Personal data | Directory contacts, CDE user metadata, signatures, occupancy/CCTV/BMS data, learner records | Only as long as the recorded purpose needs (§4) | Ruled by legal owner and data-protection lead | Delete or anonymise at purpose end. Personal data embedded in an RC-01..RC-06 record (a name in a title block, a signature on an approval) is kept with that record under its own basis |
| RC-08 Training and competence records | Assessments, certificates, attendance, recordings (BBM-STD-82) | Employment period plus the period the legal owner sets | Ruled by legal owner | Personal-data rules of §4 apply (lawful basis, consent where used, retention per learner record); aggregate statistics may be kept without identities |
| RC-09 Office and system records | Software and licence evidence (BBM-STD-94), AI use logs (BBM-STD-92), audit logs | Ruled by legal owner | Ruled by legal owner | Credentials are never records in this schedule; they live only in the office password manager |
Each container carries Record_Class (RC-01..RC-09), Personal_Data (Y/N) and Retention_Until (computed from the handover date; blank until handover is recorded). The schedule revision, the legal owner's signature and the date ruled are stored with the BBM-STD-76 disposition records.
4 Personal data (PDPL)#
| Rule | Requirement |
|---|
| Register | One personal-data register row per processing purpose: purpose, data categories, data subjects, lawful basis, source, systems/locations, recipients, hosting country, transfer route, retention (RC-07 value), owner |
| Lawful basis | Recorded before collection: consent, contract, legal obligation or another basis the Decree-Law allows, as ruled by the legal owner. No basis recorded = no collection |
| Minimisation | Collect only the fields the purpose needs. Directory and CDE profiles carry business contact data only. Occupancy and space-use analysis uses aggregated counts; no individual tracking without a recorded basis. Staff productivity metrics (BBM-STD-83) are reported at aggregate level; staff-level metrics need a recorded basis and restricted access |
| Hosting and transfer outside the UAE | Record the hosting region of every CDE, cloud, collaboration and AI service that holds personal data. Transfer outside the UAE only on a route the Decree-Law permits for that destination, approved by the data-protection lead and recorded; otherwise hold the upload. AI services follow BBM-STD-92 §4 |
| Data-subject requests | Access, correction, deletion, restriction and objection requests are logged with date received, identity check, decision, date answered and any retention reason that blocks deletion. Response time: as the Decree-Law and its Executive Regulations current at the request require |
| Security | Containers holding personal data carry SensitivityClass Confidential or Restricted under BBM-STD-87 §2 (never Public or Internal), whatever the project's T0/T1/T2 triage outcome; access by role, logged |
| Free zones | Where DIFC or ADGM law applies (§2), the data-protection lead records the regime and applies the stricter requirement where the two differ |
5 Holds, offboarding and disposition#
Offboarding a person removes their access the same day, keeps their authored records under the owning record class and deletes their personal data that has no remaining purpose. Disposition at the end of a period needs: record class, Retention_Until passed, no open hold, legal-owner ruling for the class, method (secure deletion per BBM-STD-76 §5) and a disposition record. Nothing is disposed by a script without that record.
6 Personal-data breach#
- Contain: revoke access, isolate the system, keep the logs.
- Record within one working day: what happened, whose data, how many subjects, which systems, cause, time found.
- The data-protection lead and legal owner decide notification to the competent UAE authority (or the free-zone regulator, §2) and to affected subjects, with the timing the Decree-Law and its Executive Regulations require at the date of the event.
- Link the incident to the BBM-STD-87 §4 security information and breach record; corrective action follows BBM-STD-68.
7 Acceptance#
| Check | Evidence |
|---|
| Schedule ruled | Legal-owner signature and date on the current schedule revision |
| Tagging | Sample of Published containers shows Record_Class, Personal_Data and, after handover, Retention_Until |
| Register | Every personal-data purpose in use has a register row with lawful basis, hosting and retention |
| Requests and breaches | Log exists; each entry has a decision and date |
References#
- UAE Federal Decree-Law No. 25 of 2025 Promulgating the Civil Transactions Law, Art. 821–824: https://uaelegislation.gov.ae/en/legislations/4011, checked 2026-11-04.
- UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data: https://uaelegislation.gov.ae/en/legislations/1972, checked 2026-11-04.
- Dubai Law No. 3 of 2026 Concerning the Quality and Safety of Buildings: https://dlp.dubai.gov.ae/Legislation%20Reference/2026/Law%20No.%20%283%29%20of%202026%20Concerning%20the%20Quality%20and%20Safety%20of%20Buildings.html, checked 2026-11-04.
- ISO 19650-6:2025 (health and safety information): https://committee.iso.org/standard/82705.html, checked 2026-11-04.
- ISO/IEC 27001:2022 + Amd 1:2024 (information security controls interface): https://committee.iso.org/standard/82875.html, checked 2026-11-04.
- Office interfaces: BBM-STD-76, BBM-STD-03, BBM-STD-87, BBM-STD-88, BBM-STD-92, Manual V0.5, BEP V0.5.