Keep the class together
A class-level review begins with a clear collection of submissions. Keep assignment names, document versions, and student identifiers consistent so each report can be matched to its source.
Review the report in context
A queue should make it easy to move from a report to the underlying writing. Review individual passages alongside assignment requirements and the writer’s process.
Keep the status of reviewed and unreviewed work visible rather than relying on a single class-wide average.
Leave a clear next step
A review should end with a useful action: a note for the teacher, a conversation with the writer, or a request for supporting drafts. This preview illustrates the workflow; it is not an integration setup guide.
Editorial preview for the Proof5 design prototype.