See where your class got stuck
alcoia works on top of the readings you already assign. It shows you which paragraphs slowed the class down, so you can spend class time on the parts that need it and leave the parts that landed.
What the class view shows you
When you assign a reading, alcoia watches how the class moves through it and reports back for the group. You see where people re-read, where they slowed, and where they gave up. Not who. The class, together.
A reading you could only guess about becomes something you can act on. If a lot of the class stalled on the same passage, that is where the next session goes, or that is the part of the material worth rewriting. You can also ask the class directly, now that you know which paragraph to ask about. Teach the difficult section differently: spend more time on it, break it into smaller pieces, or bring in different examples. The data tells you exactly where to redirect.
A genuine signal that the reading was done
You can see, for the group, that a reading was worked through rather than opened and skimmed to the end. The signal comes from how people read: pace, re-reading, where they stopped. It is harder to fake than a completion tick, though it is a signal of engagement, not a claim about any one student.
It fits how you already teach
alcoia does not replace Canvas, Moodle, or your slides. You assign readings the way you do now. alcoia adds a layer that tells you how the reading landed, which nothing in your current stack reports.
What you can and cannot see
At launch, everything you see is anonymous and grouped. You never see an individual student's results. When too few students have done a reading, alcoia reports that there is not enough data yet, rather than a figure that could point to one person.
alcoia never sees your students' browsing. Material you assign is uploaded by you, on purpose, and your students' reading of it is aggregated anonymously. What a student reads on their own is never shared, with you or with us.