About Scope
Tools that make students more capable, not less.
Why we started
A course site is a filing cabinet. Instructors post files, assignments, and grades there. Students leave it to read, annotate, write, code, and ask for help, then come back to upload a result.
That gap adds up: finding the right file, moving it to the device you write on, keeping notes in order, and getting it back in on time. It also pushes students toward tools that will happily do the work for them.
Scope closes the gap from the student's side first. It works with the Canvas or Brightspace course a school already runs, and nobody has to set anything up.
What we build by
Automate everything around learning. Don't automate learning itself.
Finding the reading, filing the notes, and tracking deadlines are chores, so Scope takes them on. Understanding the material is the point of the course, so Scope leaves that to you. That's why Polya starts with a hint, why you choose how much help you get, and why Scope never submits work for you.
What you can use today
Where Scope is headed is on the direction page.
Who builds it
Scope started at UC Berkeley and is built by Noel Sason. It was called Canvascope until 2026. If something in Scope gets in your way, or you want it to do something it doesn't, email the team.