Solutions
Assessment delivery
Assessment types
Integrations
Let students demonstrate engineering thinking and doing in MATLAB, Excel and Python. You decide which software and files they can use, and whether AI is allowed. Everything else is blocked, so the work they hand in is their own.
.webp)

"With Schoolyear, students can use bookkeeping software, visit the exam site, open and fill in an Excel file, and then write a report about it in Word. All in a secured session, without access to AI or outside resources."


"The teachers are satisfied with the BYOD setup for their Moodle exams. Schoolyear saves us money in the sense that we do not have to have so many computer rooms anymore."
"With Schoolyear, students can use a desktop application during an exam and we can make it AI-proof. This way, we can assess if students have the necessary knowledge themselves."



"We had cases with our previous proctoring setup where we needed to look into whether we were dealing with a cheating case or not. The moment that you're conducting exams in Schoolyear, that is reduced heavily. This is saving us a lot of time."



"We can secure exams proactively instead of after the fact. This creates calm for students, clarity for teachers, and less hassle with the e-invigilators you no longer need."



"Schoolyear makes it possible to do skills assessments with the use of extra applications, like Rstudio, Excel and Matlab. Before, this was only possible with managed computers."

"We wanted to introduce safe and robust digital testing on campus. However, no combination of exam rooms had 800+ computers available at the same time. Schoolyear was the perfect and robust solution that we were looking for, as this allowed us to use the laptops of the students in regular exam rooms."
"We sought a flexible solution for fraud prevention during exams on students' own laptops. Schoolyear allows us to use our educational spaces more flexibly and reduce the need for fixed PC rooms."
"Before the introduction of the Schoolyear, lots of eyes were needed to make sure students didn’t use search engines, chat apps, notes, or email."


A working model or a finished report doesn’t show who did the thinking: the student or the AI.
Easy to trust, but students can’t model, simulate or code on paper. The best exam takers aren’t always the best engineers.
A conversation shows real understanding, until you need one with every student in a cohort of hundreds.
Students model in MATLAB, calculate in Excel and code in a real IDE, just like they do during the course.
Other apps, personal files, chat and unapproved AI stay blocked. What students hand in, they made themselves.
Run assessments in a lab or lecture hall, on managed computers or students’ own laptops, for a whole cohort at once.
Excel has Copilot built in, so opening the app opens the AI too. With Schoolyear, students build cost estimates, mass balances and design checks in a real spreadsheet, and you decide whether Copilot belongs in the assessment.

Students write, run and test Python in VS Code with the libraries the assessment needs. GitHub Copilot, extensions and the rest of the internet stay out of reach, so the code is theirs.

Project work shows how students think, but not always who did the work. Add a short supervised checkpoint where each student applies the project to a new problem, in the same software. You set it up in your LMS like any other quiz.

Give students access to the simulation software, models, input data and documentation your assessment requires. Keep everything else out of reach.
.webp)
That depends on your learning outcomes. Block AI when students must work on their own, or allow supervised AI when working with AI is part of the skill.
To assess what students can do on their own
To assess how students work with AI
Allow support tools such as spellcheck, text-to-speech and screen magnification, so students can demonstrate their skills within a controlled assessment environment.
To assess what students can do on their own
To assess what students can do on their own
To assess what students can do on their own
Compare design alternatives under different loads in MATLAB and explain the simulation results.
Build a plant cost estimate in Excel, compare process options and justify the design choice.
Calculate beam deflections in Python, check them against the design limits and explain the margin.
Simulate a circuit in Simulink, compare component values and explain whether it meets the requirements.
Compare capacity scenarios, measure waiting times and throughput, and recommend a process improvement.
Implement an algorithm in a real IDE, run the tests and debug what fails.
We secure the assessment by locking down the device, not by filming the student or their screen. Nothing is recorded, so there is no footage to store, review or leak.
Anything outside the whitelist is blocked at system level. Cheating is stopped the moment it's tried, not spotted on a recording afterwards.
Students are not filmed or analyzed while they work. Less stress during the assessment, and no arguments afterwards about what a recording showed.