A chemistry professor ran 11 students' problem sets through Claude to see if its annotations could help manual grading; the project was accidentally left public, exposing student information.
A chemistry professor ran 11 students' problem sets through Claude to see if its annotations could help manual grading; the project was accidentally left public, exposing student information.
Chemistry professor Paul Robustelli made a project called "PS3 Grading" in Dartmouth's Claude enterprise portal. He uploaded 11 students' problem sets from his CHEM 76 class and ran them through Claude. He wanted to see whether its annotations could later serve as a reference for his manual grading. He says Claude had no role in any grade.
The project was visible to everyone in the Dartmouth Claude group, with students' names and work exposed. It came down May 2 after The Dartmouth asked for comment. The source reports no results on annotation quality.
New projects default to private. Sharing happens only if you pick the organization-wide visibility option, and Robustelli says he thought the project was private, so check the setting before uploading student work.
Take the student problem sets in [folder] after I remove names and IDs from them. For each one, annotate where the work goes wrong against [solution key or rubric] and write a short comment I could use while grading by hand. Save the annotations in a local folder [output path] and stop when every file is done. Keep everything private, don't upload it anywhere, and pause and ask me before any step that shares or publishes files.
Score every demo request against your ICP, update HubSpot and ping the right rep in Slack within a minute of the form submit.
Every new Zendesk ticket gets a category, priority and sentiment tag plus a draft reply in an internal note before an agent opens it.
Copilot and Claude review each PR for bugs, missing tests and risky changes before a human looks, so reviewers can focus on design.