It’s 10am, you’re in a math tutorial, the tutor has handed out three exercises to work on. You’re on the second one, you’re stuck on an equation, and when you look up you realize they’re already correcting the third one on the board. You have two options: drop the exercise you were working on to copy the correction, or finish your calculation and skip the correction. Either way, you lose something.

This is the classic tutorial trap. Unlike a lecture where you can stay in listen-mode the whole time, a tutorial asks you to do two things at once: solve a problem on your own and follow what’s happening at the board. The result is that tutorial notes almost always end up half-written, and you spend Sunday afternoon in the library piecing the worked solutions back together.

Why tutorial notes always end up half-written

In a tutorial, the tutor doesn’t wait for you. As soon as a student has found a method that works, they go to the board to walk through it. While they’re writing, you’re still setting up your equation, checking your sign, starting over because you made a mistake on step two. By the time you finally look up, three lines are left on the board and a spoken comment you didn’t hear.

The other thing about tutorials is that the spoken correction often matters more than what gets written on the board. The tutor says “careful, you can’t apply the formula directly here” while writing one line. That comment never shows up in the printed solution you get at the end, and yet that’s exactly what shows up on the exam. If you didn’t catch the comment in the moment, it disappears when the session ends.

Even strong students lose some of the worked problems. It’s not a question of motivation, it’s a question of mental bandwidth. A brain solving a problem live can’t track a board correction at the same time. And since you can’t tell the tutor to pause and redo the correction, you end up choosing: your exercises or their corrections. Not both.

Record the session, the move that changes everything

The real shift in a tutorial is to stop trying to write everything down in real time. You start a recording with your phone on the table at the beginning of the session, and you focus on what actually needs your head: solving the problems. The tutor’s comments, the board work, the side remarks about what’s going to be on the exam, all of that is captured. You pick it up cleanly once you’re home.

Audio alone isn’t enough, obviously. A ninety-minute recording is something you’ll never relisten to. What makes this work is a tool like Cosmonote that turns that ninety minutes into readable text and a structured summary. You import the file, you get a full transcript and a summary covering the main corrections, the methods, the pitfalls flagged by the tutor. In a few minutes, you go from a raw recording to full tutorial notes.

Ten minutes from recording to clean worked solutions

Here’s the routine that actually works after a tutorial. When you get home, you import the recording into Cosmonote. You start the processing and go take a break. When you come back, you have the summary and the transcript.

You start with the summary. It gives you the three or four exercises covered, with the method for each and the key comments from the tutor. You compare with your tutorial drafts: for each exercise you had finished on the spot, you check that your method matches the worked solution. For each exercise you missed, you reconstruct the correction from the summary.

If any point in the summary feels unclear, you jump into the full transcript to find the exact passage. You retrieve the exact phrasing the tutor used, often word for word, and you add it to your sheet. The total time spent on the tutorial afterward stays very reasonable, roughly a half-hour at the library, and you end up with complete worked solutions where you had three pencil lines before.

Query the tutorial like a source

A big upside of a tutorial transcript is that you can query it. The night before the exam, you’re wondering what the tutor said about a specific edge case? You ask the app, it pulls up the passage. That’s much faster than flipping through three notebooks.

This becomes valuable when exam prep rolls around. A full year of tutorials often adds up to dozens of hours of content. Reading all of it is impossible. With transcripts properly stored, you can target what’s missing and check unclear points in a few seconds.

When this becomes essential

There are tracks where missing a tutorial correction costs a lot. In a competitive engineering prep course, a dense tutorial can cover five or six exercises in two hours, with methods you won’t find in any textbook. In medicine, problem sessions deal with clinical cases whose subtleties play out orally. In law school, worked solutions to case studies include case law references the tutor drops without always writing them down.

In all these tracks, losing half of the year’s tutorial corrections eventually shows up at the finals. Recording every session changes how you experience it: you’re not in survival mode, you actually follow what’s going on.

For your next tutorial

Next session, try the method. You get there ten minutes early, you start the recording with Cosmonote sitting on your desk. You focus on the problems. You just jot three words when the tutor emphasizes a point, so you can find it faster afterward.

When you get home, you import the file, you get your transcript and summary, you compare them to your drafts, and you put together your tutorial sheet in under half an hour. By the end of the semester, you have a complete folder per subject, searchable word for word, that you can dig into when exams approach. Your tutorial notes stop being a patchwork and actually become usable.