Frequently asked questions

No. Once your application is approved, your institution's address and administrator account are opened; you use it in your browser. If you want to use your institution's own domain, your IT department adds a DNS record; the SSL certificate is obtained automatically.

Yes. The import screen reads Excel files and pages from your old system and shows a preview; the courses you confirm are imported. Old learning outcome sentences can be restructured in the Bloom builder.

The course grade is a weighted average of exams and tells you whether a student passed the course. In attainment measurement, each exam item is linked to one or more learning outcomes; each student's performance on each outcome is calculated; the proportion of students above the threshold becomes that outcome's attainment rate. This reveals results the grade hides, such as “95% of the class passed, but only 13% attained the article evaluation outcome”.

It is not mandatory; it starts switched off. If you enable it, it runs with the provider your institution chooses and your own key. Only course description texts are sent; scores, student numbers and personal names are not. Suggestions do not enter the package until you accept them.

The Dashboard opens. For your role and scope it shows average attainment of institutional outcomes, educational objectives, programme outcomes, learning outcomes and courses, your tasks, the cognitive level distribution of learning outcomes and improvement records on one screen. An instructor sees only the indicators of their own courses.

Yes. Quality coordination can click any calculated value to see step by step which formulas and inputs produced it; the window also explains what the value means and where it goes in the chain. The windows never show student numbers, student names or individual student scores.

No. Programmes are linked to a faculty or vocational school; deans and vocational school directors see only the information of their assigned unit, heads of department only that of their assigned programme. Instructors see only their own courses. Role permissions come from the permission matrix maintained by the institution administrator.

Yes. For example, an instructor can also be head of department or a member of the quality committee. The administrator gives the person an additional role; the person picks the active role from the top bar. Only one role is active at a time, screens and data scope follow that role and every role switch is written to the audit log.

Yes. Each student is assigned an academic and a career advisor. The student list is imported from the student information system as Excel or CSV; when the advisor changes, the old assignment stays in the history. Advisors see only their own advisees and managers monitor the numbers. Advisee information is never combined with assessment data.

Yes. The advisor records each meeting with date, topics, summary and action items; the record locks after 48 hours and is never deleted. The student's new advisor sees the history. The quality office, rector, dean and head of department monitor the numbers; they open the note text with a justification and every access is logged. No one can see the advisor's private note.

The advisor opens available times and invites students by email. Without signing in, the student picks a time from a personal link, adds it to their calendar or cancels it; if the times do not suit, they write when they are available. A reminder is sent the day before the meeting.

Yes. Each programme's duration is entered separately; the default is 4 years for bachelor's and 2 for associate degrees. Year and semester options follow the programme's duration.

Yes. The Advising · Students screen starts from the role's scope: a dean from their faculty, a programme head from their programme, administrators and the quality coordination office from the institution level. From there you drill down to programme, year, advisor and student list; units and programmes outside the scope are not shown.

In the “Advisors in my scope” section of Advising · Cockpit. Administrators and the quality office see the whole institution, a dean sees the faculty, a department head sees the programme; drill down with faculty and programme boxes and click an advisor to see advisee counts, meeting frequency and overdue actions. Meeting content and confidential notes are not shown. An advisor is an instructor attached to a department and is not normally assigned to another department's students; if needed, the assignment is made with a written justification.

They were merged into one step: “Bloom / Learning outcomes”. The page has three tabs: “Write an outcome” is the builder; “List and review” lets you edit all outcomes inline, reorder, delete and review them with AI; “Distribution and bulk drafting” holds the cognitive distribution table, the two-dimensional table and bulk drafting. A course package now has 10 steps; old links redirect to the new page.

Yes. In the Badges and credentials module, three layers come together in one portfolio. A badge is a single evidenced competence; it is awarded with evidence, by attaining the learning outcomes of the course or through an approved co-curricular activity. As badges accumulate, a micro-credential is earned; its workload, ECTS, TQF level and quality assurance are defined. The co-curricular transcript documents activities outside courses with categories and points. Every certificate has a verification page opened by link and QR code.

No. Every certificate is approved by an authorised person. If the institution turns it on, the system shows as candidates the students who attained all of the selected learning outcomes in a course with a locked run; the list contains only student numbers and scores are not shown. AI only suggests badge definitions; it does not decide who receives them.

The certificate's name, criteria, date and validity status, and the name of the certificate holder. The student number, grade, score, evidence text and reason for revoking are not shown. The institution can also mask the name if it wishes. A revoked certificate is not deleted; it is shown as revoked on the page.

The top menu is grouped into six clusters: Dashboard, Courses, Assessment and quality, Advising, Badges and credentials, Administration. Clicking a cluster opens the screens under it with short descriptions; screens your role cannot see are not listed. For something faster, press Ctrl+K (⌘+K on Mac) or / and type the screen name, course code or programme code.

Yes. On the Administration · Dashboard layout screen you set the place, width and order of sections by dragging, for the institution default, each role and, if needed, a single user. The layout only changes display; a person does not see data they have no permission for even if it is on in the layout.

Yes. The Advising · Advisor monitoring screen and the dashboard card show, for each advisor in scope, the number of advisees, the number of meetings in the period, the share of advisees met, the last meeting date, the monthly distribution and overdue actions. Clicking an advisor opens their advisees and each one's last meeting. Meeting content, private notes and students' measurement data are not shown; every opening is written to the audit log. The institution can turn this view off with a parameter.

Yes. The Advisor Cockpit shows today's and this week's appointments, meetings awaiting a record, students for whom the times do not work and overdue actions. The advisor books appointments directly from the calendar; during the meeting they take notes while the student's information stays on screen, and set the next appointment. The student receives an e-mail with the time, a calendar file and a cancellation link.

Yes, if the institution runs a local model on its own server. From the student's outcome statuses and previous meeting summaries, the model suggests a meeting agenda, strengths, areas for support, electives from the programme's pool and career questions. The student's name, number, scores and private notes are not sent to the model; the suggestion is stored separately and is written nowhere unless the advisor selects it.

Yes. Programmes, programme outcomes, educational objectives, institutional outcomes, TQF-HE qualifications, matrices, the course catalogue, learning outcomes, the weekly plan, workload, the assessment plan, enrolments and scores are received by API, by pulling from the address of the institution's system or by file. If field names differ, the mapping is done on screen; no code is written. For students only the number is taken.

No. Design data is written only to draft courses; existing learning outcomes do not change, and the level comes from the approved verb list and is never guessed. Matrices and contribution shares arrive flagged as “not reviewed”; they are not considered final until the person responsible or the committee reviews them on screen. The cognitive level of an exam item is not imported; the course coordinator declares it.

The import does not stop. Fields the software needs that did not arrive filled are listed for the administrator with source and data type; the relevant user sees a short summary row on the entry screen and enters the value, confirms it or states that it will stay empty.

If the institution wishes, yes. Course history (term, course, ECTS, letter grade, status), current-term enrolments, GPA, term GPA and academic standing are received from the student information system through integration, with a separate permission scope. Only the student's current advisor sees them, in meeting preparation; they appear in no report. They are deleted when the retention period ends.

If the institution enables it, before sending an invitation the student's current advisor sees in one section the courses taken, the student's status in learning and programme outcomes (achieved, developing, support recommended, not yet measured), previous meetings and open actions, and chooses the invitation agenda accordingly. Raw scores are not shown and no instructor name appears; no one else can see the section and every opening is logged.

Yes. An advising report for YÖKAK B.3.2 academic support services can be downloaded as Word, PDF or Excel: the advising system, coverage and meeting indicators by programme, action tracking and evidence mapping. The report contains numbers only; no personal names or meeting content.

Yes. A course accreditation report is produced from each course's locked measurement run, and a programme accreditation report covering all courses from the programme dashboard. The reports include charts and commentary, are mapped to MÜDEK, MİAK, FEDEK, STAR and YÖKAK criteria and are saved as PDF.

No. An instructor's name and learning outcome results never appear together in any report; courses appear by code and title. Measurement results show how far the course and programme reach their learning outcomes, not the performance of individuals.

Your data is not deleted and remains readable; new records and changes are enabled once a subscription starts. The institution administrator sends a request in one click from Administration → Subscription.

The system is designed primarily for higher education course information packages. A version suited to the school outcomes structure is in preparation; select school as the institution type on the application form to find out more.

Within 30 days of termination you can export all your packages as Word, Excel and JSON; a database dump is provided on request. After that period the data is deleted. Details are in the Service and Subscription Agreement.