FAQ

Questions about ROAR.

What does ROAR stand for?

Record, Organize, Access and Recall.

Does ROAR analyze students?

No. ROAR’s job ends at Recall: generating the student’s collected list of notes. Analysis, summarization or other interpretation can happen in a separate tool chosen by the teacher.

Does ROAR change my original note?

The design preserves the original teacher note. Organization and routing should not replace the teacher’s observation with generated language.

What happens if ROAR is unsure about a student name?

The intended workflow is to surface uncertainty for review rather than silently route a questionable name to a student.

Can one note apply to several students?

Yes. Group and all-student notes are part of the design. Attendance-aware routing can constrain an all-student note to the students who are present.

Can I export my notes?

Recall is designed to create a student notes report that can be printed, saved or exported for use outside ROAR.

Who can use the beta?

The current beta is invitation-only. Each tester receives an invited email and an invite code for first-time account activation.

What permissions will ROAR ask for?

The beta login page will list the exact permissions and warnings that the deployed version requires. Those details should match the real authorization flow rather than making broader promises in advance.