# Learning Outcomes (مخرجات التعلم), mapped to what Tondro Consulting configures Pillar 2 of MoHESR's Outcome-Based Evaluation Framework, 25% of the score. For each KPI, this page lists the points the guidebook asks for and, against each point, how Tondro Consulting configures its offerings to meet it. HTML version: https://www.tondroconsulting.com/uae/learning. The whole framework: https://www.tondroconsulting.com/uae.md ## KPI 2.1 Assessment Quality Review (جودة تقييم الطلبة) - Weight: 7.5% of the institutional score - Period: Last assessment - High: 90% - Collected: External experts during CAA review visits, using a standard rubric. - Guidebook pages: 22–24 The average score external reviewers give a sample of the institution’s assessments. ### KPI 2.1: Every assessment tied to its course, program, learning outcomes and QFEmirates level (Guidebook p. 23, alignment criterion (45%)) - Salesforce as SIS: Courses and programs carry their learning outcomes and QFEmirates level on the record, and each assessment is recorded against the course section and the outcomes it measures. ### KPI 2.1: Number of assessments, score distribution and student population, for any program the reviewers choose (Guidebook p. 22, data submitted during the CAA visit) - Salesforce as SIS: Grades live on the record per assessment and section, so the count, the distribution and the population are one report, filtered by program and term. - Integrations: Where assessments are graded in the LMS, grades and assessment metadata are brought onto the record rather than exported for the visit. ### KPI 2.1: A representative, randomized sample of graded work, possibly across several years (Guidebook p. 22, 3R sampling) - Salesforce as SIS: Graded work is attached to the assessment record and kept across terms, so earlier years are still there when the reviewers ask. - Agentforce: An agent draws the sample to the reviewers’ specification, checks each item is present and graded, and lists anything missing before the visit. ### KPI 2.1: No reuse of items in major assessments within three years, and grade distributions that are not inflated (Guidebook p. 23, design and grading criteria) - Agentforce: Before a visit, an agent compares assessment items across the last three years and compares each course’s grade distribution with its own history, and flags both for a person to review. - Managed Services: The pre-visit checks run on a schedule each term, so a problem is found in a normal term rather than the week before review. ## KPI 2.2 Retention Rate (FYR) (نسبة الاحتفاظ بالطلبة) - Weight: 5% of the institutional score - Period: 3-yr rolling - High: 90% - Collected: Master API, collected today through the interim HEDB portal (formerly CHEDs). - Guidebook pages: 25 The share of first-year students who continue into their second year. ### KPI 2.2: The denominator: every first-year student enrolled in the fall of the previous academic year (Guidebook p. 25) - Salesforce as SIS: The first-year cohort is set on the student record at enrollment, so the denominator is a fixed list rather than a query rebuilt each year. - Recruitment & Admissions: An admitted applicant becomes the enrolled student on the same record, with entry route, equivalency and Foundation Program placement carried across rather than re-keyed. ### KPI 2.2: The numerator: first-year students who registered and continued into year two (Guidebook p. 25) - Salesforce as SIS: Registration for the second year is read directly from the registration records the guidebook names as the source. ### KPI 2.2: The status rules: internal transfers, deferrals, undeclared students and one-year programs each counted the way the guidebook says (Guidebook p. 25) - Salesforce as SIS: Each case is a status or reason code on the program enrollment, and the retention report applies the guidebook’s rule to the code, so the count does not depend on who ran it. ### KPI 2.2: Moving the number: finding a first-year student at risk while there is time to act - Student Advising: Each adviser sees their first-year students and where each stands, with the conversation history kept on the student record. - Slack for Education: Alerts reach the adviser in the channel they already work in, and the action they take in Slack is written back to the record. - Agentforce: An agent watches attendance and registration signals and flags a first-year student who has stopped engaging, for an adviser to act on. ### KPI 2.2: Filing through the Master API as a three-year rolling average, with definitions held steady across the three years (Guidebook pp. 9, 16) - Integrations: The return is produced from the record in the format the HEDB portal takes today, and moves to the Master API as a change of transport. - Managed Services: Tondro runs the return each cycle and keep a dated record of any change to a status definition, so three years of cohorts stay comparable. - Agentforce: Before submission, an agent compares the figure with prior years and flags a step change for a person to explain. ## KPI 2.3 Employer Feedback in Work Placements (ملاحظات أصحاب العمل خلال التدريب العملي) - Weight: 2.5% of the institutional score - Period: 3-yr rolling - High: 4.5 out of 5 - Collected: Employer Work Placement Survey, designed by MoHESR. The institution sends it to site supervisors and shares the results with MoHESR. - Guidebook pages: 26 The average rating employers give interns and apprentices at the end of a placement. ### KPI 2.3: A named site supervisor for every formally recognized placement in the study plan (Guidebook p. 26) - Salesforce as SIS: The placement is recorded on the student’s study plan with the host, dates and site supervisor, and completion shows on the transcript. - Alumni and Corporate Relations: The host organization and its supervisors sit on the partner record, so the same employer is not re-entered for every student it hosts. ### KPI 2.3: Sending the Employer Work Placement Survey to each supervisor and following up until the response floor is met (Guidebook p. 26, Appendix C) - Marketing Communications: The survey is sent automatically when a placement is marked complete, with reminders timed to the survey window. - Agentforce: An agent follows up with supervisors who have not responded and reports the response rate by program each day. ### KPI 2.3: Results recorded per student and shared with MoHESR, with raw data and metadata kept for the CAA (Guidebook p. 26, Appendix B) - Salesforce as SIS: Each response is stored against the placement it rates, with the date it was sent and returned. - Integrations: Results are delivered to MoHESR from the record in the required format. - Managed Services: Tondro keeps the raw respondent-level file for each cycle ready for an evidence request. ## KPI 2.4 Employer Feedback in Employment (ملاحظات أصحاب العمل خلال التوظيف) - Weight: 2.5% of the institutional score - Period: 3-yr rolling - High: 4.5 out of 5 - Collected: Employer Satisfaction Survey, collected by MoHESR. The institution supplies the employer list. - Guidebook pages: 27 The average rating employers give the graduates they hired. ### KPI 2.4: The employer of each graduate, for the list the institution supplies to MoHESR (Guidebook p. 27) - Alumni and Corporate Relations: The graduate record continues the student record and holds the employer, role and start date, kept current after graduation. ### KPI 2.4: Adequate responses to the Employer Satisfaction Survey, which MoHESR collects (Guidebook p. 27, Appendix C) - Marketing Communications: Employers on the list are told the survey is coming and reminded during the window, from the same partner record their other contact comes from. - Agentforce: An agent tracks which employers have not yet responded and prompts the relationship owner to follow up. ### KPI 2.4: The institution’s own employer survey, where it is more complete than the ESS (Guidebook p. 27) - Marketing Communications: Your own survey runs against the same employer list, with each response stored against the employer and the graduate it concerns. - Managed Services: Tondro prepares the alternative submission with its raw data and metadata, which MoHESR requires before it will consider it. ## KPI 2.5 Rate of graduates obtaining microcredentials & licenses (معدل النجاح في الحصول على التراخيص والشهادات) - Weight: 5% of the institutional score - Period: 3-yr rolling - High: 90% licenses, 40% microcredentials - Collected: Master API, collected today through the interim HEDB portal. - Guidebook pages: 28–30 How often graduates earn the professional licenses their field requires, and microcredentials during their studies. ### KPI 2.5: Which programs lead to a mandatory license, and which license, such as DHA, DOH, MOHAP, MOJ, CDA, MoE or GCAA (Guidebook p. 29) - Salesforce as SIS: Each program record names the license it leads to, so the license-bound cohort is defined by the program rather than listed by hand. ### KPI 2.5: Graduates of license-bound programs who hold the license three years later, with the issuing body and date (Guidebook p. 28) - Alumni and Corporate Relations: The license is recorded on the graduate record as a credential, with issuing body and date, and asked for at the three-year point. - TondroAI Extract: When a graduate uploads a license certificate, Extract reads the issuing body, license number and date and writes them to the credential record. - Marketing Communications: Graduates approaching the three-year point are asked to confirm their license status. ### KPI 2.5: Graduates who earned at least one approved microcredential during their studies, counting awards and not attempts (Guidebook p. 28) - Continuing Education on Commerce Cloud: Microcredentials are sold and delivered through the Commerce Cloud storefront, and each completion writes the award to the same learner record. - Salesforce as SIS: The award appears on the transcript with its approval status, which is the record the CAA can ask to see. ### KPI 2.5: Filing through the Master API (Guidebook p. 16) - Integrations: Both ratios are produced from the record and submitted in the HEDB format. - Managed Services: Tondro runs the calculation each cycle, including the 50/50 weighting and the normalization. ## KPI 2.6 Student Satisfaction with Learning Experience (مستوى رضا الطلبة عن تجربة التعلم) - Weight: 2.5% of the institutional score - Period: 3-yr rolling - High: 4.5 out of 5 - Collected: Student Experience Survey, run by MoHESR, at institutional level. Course evaluations, run by the institution, at program level. - Guidebook pages: 31 Average student satisfaction with the learning experience and the skills gained. ### KPI 2.6: The contact list for the Student Experience Survey, limited to students with at least two completed semesters (Guidebook p. 31) - Salesforce as SIS: Eligibility is a rule on the record, so the list is produced from enrollment history rather than filtered by hand. ### KPI 2.6: Response rates that meet Appendix C, for the SES and for course evaluations (Guidebook p. 31, Appendix C) - Marketing Communications: Students are reminded during the survey window through the channels they respond to. - Slack for Education: Announcements reach students and staff in the channels they already use, with response rates by program visible to the people who can move them. - Agentforce: An agent reports response rates by program each day and prompts program leads where a program is below the floor. ### KPI 2.6: Course evaluations after every course, every semester, reported at program level with raw data kept (Guidebook p. 31, Appendix B) - Salesforce as SIS: An evaluation is triggered when each course section closes, and responses are stored against that section and term. - Marketing Communications: The evaluation is delivered and reminded from the record. - Managed Services: Tondro keeps the per-respondent file with release and collection dates ready for an evidence request. ### KPI 2.6: Moving satisfaction, which the guidebook measures through the learning experience and the skills gained - Student Advising: Advisers see each student’s progress and history before a conversation, rather than asking the student to repeat it. - Slack for Education: Handoffs between offices carry the student’s context and leave a trail, so a question does not restart at every desk. - Agentforce: A student-facing agent answers routine questions in Arabic and English from the student’s own record, at any hour. Every agent on this page can run on Claude through Claudeforce, or on a self-hosted model where student data has to stay in the country. Source: MoHESR, University Guidebook for Outcome-Based Evaluation Framework (OBEF), Version 11.5, 23 March 2026. English: https://www.mohesr.gov.ae/Documents/OBF%20University%20Guide%20-%20EN.pdf . Arabic: https://www.mohesr.gov.ae/Documents/OBF%20University%20Guide%20-%20AR.pdf . Page reviewed 22 September 2026.