Study programme and qualification management system
The team handles the requirements of the study programs and their changes. The applicable program is saved to the student so that the graduation papers are prepared according to the proper requirements.
Program modules, results and credits are updated in documents, but applying the change to a specific release is not always clear. Different requirements may remain in student plans. It is difficult for a student to understand what is still missing for graduation. Administration must re-check the program's history before approving the plan or issuing the document.
How the solution works
- Describe the version of the program and its application
- Linking modules to learning outcomes
- Get official credited achievements
- Make an issuing decision and prepare a document
- Review the program based on appropriate results data
Key challenges
- The program's version of requirements does not include a specific release
- Issue of qualifications and microqualifications fragmented
- Graduate results do not return to program management
Solution capabilities
Versions of the program
Dedicates a valid, prepared and finalized program left to run; specifies which release and individual case is subject to change.
Results relationships
Modules are associated with proven learning outcomes, scope and evaluation. Units of different educational models are not brought together without an appropriate method.
Recognition decision
Previous learning or short achievement has an authorized crediting solution. Several certificates do not add up to the qualification simply because of similar titles.
Issue of a document
The official history of the results is checked according to the applicable rules and the law of issue. The wrong document is corrected or changed while maintaining its state and the previous version.
Program Preview
Employers and graduate data shall include the time period, sample and included groups.Authorized change of program shall be designated as an executor and shall be determined from when it is applied.
Business context
- The program's version of requirements does not include a specific release
- Program modules, results and credits are updated in documents, but applying the change to a specific release is not always clear. Different requirements may remain in student plans. It is difficult for a student to understand what is still missing for graduation. Administration must re-check the program's history before approving the plan or issuing the document.
- Issue of qualifications and microqualifications fragmented
- The diploma, certificate or microqualification issued is not always directly linked to the verified learning outcomes and the version of the program applied. The basis of the document has to be restored by the employees from several sources. The graduate waits longer for the submission or explanation required for the employer and further education.
- Graduate results do not return to program management
- Graduate career and employer feedback data are collected episodically. It is not always clear which program, broadcast or competence they describe. The program review is based on insufficient data about the need. The institution has a harder time justifying the update and clearly presenting what results are actually supported by the available data.
- It is clear to the student what requirements he or she is learning
- As the program changes, it is important to maintain the requirements and recognized results for the specific release. Linked versions help explain the remaining steps to qualification. Graduate data can complement the program's review by clearly separating the established results from the overall program delivery promises.
Core features
- Versions of the program
- Results relationships
- Recognition decision
- Issue of a document
- Program Preview
Key integrations
- Student and Results Sources
- Official set-offs, individual exceptions and the document taker.
- Program Papers and Graduate Data
- Program requirements, review documents and evaluated program parts have been approved.
Potential impact (%)
The ranges indicate an illustrative relative change in the metric under the stated assumptions. Results depend on the starting position and actual use of the solution. Percentages for different metrics must not be added together.
Time of completion requirements check
12–36%Decreasing
This illustrative scenario assumes that 30-60% of manual data entry and handover work can be addressed. That share is assumed to fall by 40-60%. Company data is needed to verify both the addressable workload and the resulting change.
Measure working minutes for graduation verification, while registering later-corrected solutions.
Misissue of document
2–12%Decreasing
This illustrative scenario assumes that the controls described can address 10-30% of discrepancies. That share is assumed to fall by 20-40%. Company data is needed to verify both the addressable share and the resulting change.
Counting documents corrected for an incorrect version of the program or incorrectly transferred achievement.
Conditional calculation scenarios. The assumptions have not been validated against client measurements.
When this solution is relevant
- Different versions of the programs and graduation conditions apply to different groups of students.
- Employees check the requirements and their fulfillment in several documents or registers.
Project scope and implementation
Versions of the programs are linked to student groups, results achieved and conditions of qualification. For one short course, a description of the program and the available means of issuing documents may suffice. The program and graduation criteria are approved by the academic staff responsible.
Further development options
- Additional programs and checkable digital documents after checking their issuing and long-term inspection requirements.