IoL Workflows
Administrative   Family L · Learner and stakeholder services  ·  IoL Administrative Affairs

AW-20 · Non-Academic Complaints Handling

Primary KPIsnone
Contributes to
TriggerAn expression of dissatisfaction received by any channel: desk (AW-18), web form, email, letter, in person, through a partner, or transferred from MBRU
EndpointComplaint closed with an outcome communicated, any remedy delivered, learning captured, and the entry complete in the complaints log
OBEF touchpointNone

BPMN 2.0 (ISO/IEC 19510), generated from the procedure section of this document. Lanes are the roles in the RACI; a cylinder marks a capture point and the KPI it feeds; a diamond is a decision point. Click a task to jump to its step. Scroll to zoom, drag to pan.

AW-20 — Non-Academic Complaints Handling

Workflow ID AW-20
Pack owner IoL Administrative Affairs (decision of 2 September 2026; see Architecture/04_Ownership_Model.md)
Family L — Learner and stakeholder services
Ownership IoL. MBRU's complaints and student affairs functions are the escalation tier and own the institutional policy; IoL owns intake, investigation, outcome and learning for complaints about IoL services [IoL to confirm]
Governing policy MBRU student complaints policy; MBRU code of conduct; Dubai Health customer happiness or complaints standard where applicable [IoL to confirm]; ISO 21001:2018 clauses 8.2, 9.1.2 and 10.2 (complaints and appeals, learner satisfaction, nonconformity)
Interfaces AW-18 desk (intake route); WF-11 academic appeals and complaints (boundary); AW-09 staff grievance and conduct (boundary); AW-16 data protection; AW-17 health and safety; AW-24 CAPA; AW-25 management review
OBEF touchpoint None
Process owner ______________
Version 0.1 draft
Effective
Next review

1. Purpose and scope

Purpose. To ensure that anyone dissatisfied with an IoL service, the conduct of its staff, its facilities or its administration can complain easily, is acknowledged, has the matter looked into by someone independent of it, receives an outcome with reasons and a remedy where one is due, and can escalate to MBRU. The consequential point is independence: a complaint investigated by the person it is about is not an investigation, and ISO 21001 assessors will ask to see the evidence that it was not.

Scope statement. This procedure manages a non-academic complaint from receipt to closure, including escalation, the capture of learning and the reporting of trends.

Applies to. Complaints from learners, CPD participants, placement partners, suppliers, visitors and members of the public about IoL service, staff conduct towards them, facilities, communications, administration, events or data handling.

Does not apply to. Academic appeals and academic complaints (assessment, progression, supervision, integrity), which are WF-11; staff grievances and staff discipline, which are AW-09; complaints about MBRU or Dubai Health services outside IoL, which are forwarded to the owning function with the complainant told; safeguarding, harassment or discrimination allegations, which are logged here and transferred the same day to the MBRU function named in policy [IoL to confirm].

2. Trigger, boundary and interfaces

Trigger An expression of dissatisfaction received by any channel: desk (AW-18), web form, email, letter, in person, through a partner, or transferred from MBRU
Endpoint Complaint closed with an outcome communicated, any remedy delivered, learning captured, and the entry complete in the complaints log
Upstream AW-18 (routing); any IoL service; WF-11 and AW-09 (transfers of misrouted matters); MBRU (transfers to IoL)
Downstream MBRU complaints function (stage 3); AW-24 (corrective action); AW-25 (trend report); AW-16 (any data-protection complaint is also an incident); AW-17 (any safety complaint is also an incident)
Handoff to the academic pack WF-11 receives any complaint whose substance is academic, within 2 working days, with the complainant told. The boundary is the substance, not the channel: a complaint about how a result was communicated is administrative; a complaint about the result is WF-11

3. Roles and accountability

Process owner. IoL Quality Lead or equivalent, acting as Complaints Officer [IoL to confirm].

Step Complainant Complaints Officer Head of the area complained about Investigating Officer Senior Director, IoL MBRU complaints function
Log, acknowledge and categorise R A/R I I I I
Confirm the boundary (WF-11, AW-09, MBRU) I A/R C I I C
Stage 1: local resolution C I A/R I I I
Stage 2: appoint an independent investigator I R I I A I
Investigate and report C I C A/R I I
Decide outcome and remedy I C C C A/R I
Communicate the outcome I A/R I I C I
Stage 3: review or escalation R R I I C A/R
Capture learning through AW-24 I A/R R I I I
Report trends to AW-25 I A/R I I I I

[CONTROL] Segregation. The investigator is not the subject of the complaint, not in the subject's reporting line, and not involved in the matter. The decision maker is not the investigator. A complaint about the Senior Director, or about the Complaints Officer, goes directly to the MBRU complaints function.

4. Procedure

  1. Receive and log. Every complaint enters the complaints log [IoL to confirm system] within 1 working day with complainant, channel, date, subject and area. An expression of dissatisfaction is a complaint whether or not the word is used. [CONTROL] A matter settled in conversation is still logged with its outcome.

  2. Acknowledge. Within 2 working days, in writing, with the reference number, the stage, the expected timescale and a link to this procedure. Anonymous complaints are logged and assessed; they cannot be given an outcome, but the learning is captured.

  3. Categorise and confirm the boundary. Category from the controlled list: service; staff conduct; facilities; communications; administration; events; data handling. Decision point. If the substance is academic, transfer to WF-11; if it is a staff grievance, to AW-09; if it concerns safeguarding, harassment or discrimination, transfer the same day to the MBRU function in policy; if it concerns a data-protection or safety matter, also raise the AW-16 or AW-17 incident. The complainant is told of any transfer within 2 working days.

  4. Stage 1: local resolution. The Head of the area complained about attempts resolution with the complainant within 10 working days: an explanation, an apology, or a practical fix. [CONTROL] Where the Head is the subject, stage 1 is skipped. The outcome and the complainant's acceptance or otherwise are recorded in the log.

  5. Stage 2: formal investigation. If the complainant is not satisfied, or the matter is serious, the Senior Director appoints an Investigating Officer who meets the segregation rule. The investigator gathers the complainant's account, the staff account and the records; the subject of a conduct complaint is told what is alleged and given the chance to respond. [CONTROL] The investigator's independence is recorded in the log before the investigation starts.

  6. Decide the outcome and remedy. The Senior Director decides on the investigation report whether the complaint is upheld, partly upheld or not upheld, and what remedy applies: an apology, a corrected record, a refund or fee adjustment through AW-12 within delegation (AW-05), a change to practice, or a referral of staff conduct to AW-09. [CONTROL] A financial remedy is approved at the AW-05 level for its value and paid through AW-11 or AW-12, never by the Complaints Officer.

  7. Communicate. The Complaints Officer writes to the complainant within 5 working days of the decision with the finding, the reasons, the remedy, and the stage 3 route with its time limit [IoL to confirm the MBRU time limit]. The staff involved are told the outcome that concerns them.

  8. Stage 3: escalation. A complainant who remains dissatisfied may ask the MBRU complaints function for a review. IoL supplies the complete file within 5 working days of the request and implements MBRU's decision. Decision point. MBRU may also direct that a complaint be handled at MBRU from the outset where the subject or seriousness warrants it.

  9. Capture the learning. Every upheld or partly upheld complaint, and any not-upheld complaint that exposes a weakness, generates a corrective action in AW-24 with an owner and a date. [CONTROL] A complaint is not closed until the AW-24 entry exists or the Complaints Officer records why none is needed.

  10. Report trends. Each quarter the Complaints Officer reports to AW-25: volumes by category and area, time to close against standard, outcomes, remedies, recurring themes and open corrective actions. Individuals are not identified in the trend report.

Exception routes. Vexatious or repeated complaints on a decided matter: the Senior Director may close without further investigation, with reasons in writing and the stage 3 route stated. A complaint that reveals an immediate risk to a person: AW-17 is invoked before this procedure continues.

5. Service standards

Service Standard
Complaint logged 1 working day
Acknowledgement in writing 2 working days
Transfer of a misrouted matter, complainant told 2 working days
Stage 1 outcome 10 working days
Stage 2 investigation complete 20 working days from appointment of the investigator
Outcome letter after decision 5 working days
File supplied to MBRU at stage 3 5 working days from request
Corrective action raised in AW-24 Before closure
Trend report to AW-25 Quarterly

Where a standard cannot be met, the complainant is told the new date and the reason before the standard expires.

6. Records, retention and controls

Record System Retention Owner
Complaints log: reference, category, area, stage, dates, outcome, remedy, AW-24 link Complaints log [IoL to confirm] 7 years after closure Complaints Officer
Acknowledgement, correspondence and outcome letters Complaints file 7 years after closure Complaints Officer
Investigation file: statements, records reviewed, independence declaration, report Complaints file, restricted 7 years after closure Investigating Officer
Financial remedy approval AW-11 or AW-12 record 7 years Budget holder
Stage 3 file and MBRU decision Complaints file and MBRU system 7 years after closure MBRU complaints function
Quarterly trend report AW-25 pack 7 years Complaints Officer

Key controls. (1) Every complaint is logged, including those resolved informally. (2) The WF-11 and AW-09 boundary is decided on substance and recorded. (3) The investigator is independent of the subject, the decision maker is not the investigator, and independence is recorded before the investigation starts. (4) The subject of a conduct complaint is given the allegation and the chance to respond. (5) Financial remedies follow AW-05 and are paid through AW-11 or AW-12. (6) No closure without an AW-24 entry or a recorded reason. (7) The complainant is always told the next stage.

OBEF touchpoint. None.

7. Performance measures

Dimension Measure Target
Timeliness Complaints acknowledged within 2 working days 100%
Timeliness Stage 1 and stage 2 closed within standard 90%
Compliance Stage 2 files with an independence declaration on record 100%
Compliance Upheld complaints with an AW-24 corrective action 100%
Accuracy Stage 3 reviews that overturn the IoL outcome Tracked; each one reviewed
Experience Complainants reporting the process was fair, regardless of outcome, closure pulse 75%
Learning Recurring themes closed by corrective action within two quarters Tracked

8. Change control

Date Version Change Reason Approved by
2026-09-02 0.1 Initial draft IoL administrative pack draft, unapproved