Course reports

For educators

Two different reports live under activity, and they answer different questions.

	Covers	Produced
Weekly report	One week	Generated by Alexandria, stored, exportable
Course report	The whole course to date	Assembled on demand, printable

Weekly reports

A week’s conversations are summarised into an written report with recommendations.

Each week appears in a list with its status:

Status	Meaning
Week in progress	The week has not ended
n/10 Needed for a report	The week ended with too little activity
A Generate button	Eligible; the status is replaced by the button
Generating…	In progress
Pending	A report record exists but has not started
Completed	Ready to read
Failed	Generation did not finish; try again

A week needs at least ten conversations before a report can be produced. Below that there is not enough material for a summary to be worth reading.

The Reports tab of a course's activity area. The Available Weeks sidebar lists one week per row with its question count: the current week Jul 27 to Aug 2 shows Week in progress, the completed Jul 20 to Jul 26 week is highlighted and marked Completed, and every earlier eligible week offers a Generate button. The generated weekly report opens beside it. — Each week carries its own status. Eligible weeks show a Generate button in place of a status label.

What a report contains

Executive summary
Key topics discussed
Common challenges and confusion points
Frequently asked questions
Student engagement insights
Recommendations for educators
Statistics

The recommendations section is the one to read first if you read only one.

A completed weekly report for Thermodynamics, scrolled to the Recommendations for Educators section. Bulleted recommendations cover bridging theory and practice, clarifying wall physics, a crystallization deep-dive, stability workshops, validation logic, and reviewing Navier-Stokes. Student Engagement Insights sits above it and a Statistics section listing the report period, 188 conversations and 712 questions answered sits below. — Recommendations for educators, with the engagement insights it was drawn from above and the week's statistics below.

Getting it out

Export as PDF produces a file. Markdown copies the text to the clipboard, which is more useful when pasting into a course-team document or an email.

Weekly emails

Where enabled in course settings, the report is emailed to educators and administrators when it is generated, so the report arrives rather than needing to be fetched.

Generation happens either way. The setting controls only the email.

The course report

The course report control produces an all-time summary of the course: usage over time, which answering modes students used, the topics behind their questions, and how their questions classify.

It is assembled when you open it and is not stored. Save as PDF prints it through the browser.

The course usage report for Thermodynamics, opened over the activity area. A Save as PDF button sits at the top beside a note that it opens the browser print dialog. Below the title is a Summary paragraph followed by eight figure tiles: 300 enrolled students, 300 active students, 6,619 total questions, 6,018 total assessments, 29 generated questions, and 100 percent for returning students, returned next day, and active of enrolled. A Usage over time section follows with a Questions over time area chart running from Jun 2 to Aug 2 and peaking at 1,333 questions on the busiest day. — The all-time course report, assembled on open and printed with Save as PDF.

This is the one to produce for a course evaluation or a conversation with a programme director, where the whole run matters rather than one week.

Availability

Reports require the Educator role. An institution can disable course analytics entirely, in which case this area shows a maintenance message.