← Back to library

Track homework submissions across three inboxes

u/Valuable_Simple3860 describes a neighbor, a teacher, who wired no-code tools so she no longer checks three places for homework: an automation scans the classroom platform, email and paper submissions and produces one turn-in report. We keep the single-report pattern and add a missing list for teacher review before any parent contact.

  • OutcomeCheck the classroom platform, email and scanned paper submissions together and produce one report of who turned in what.
  • SetupUnder an hour
  • LevelIntermediate
  • Creditu/Valuable_Simple3860 on r/ChatGPT
View original
Works with
ZapierMakeMicrosoft Copilot

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • Submissions arrive in several places
  • Tracking turn-ins takes time after school
  • You need a missing list

Not for: Grading student work; Contacting parents automatically

What do you need, and what do you get?

You need

  • Class roster
  • Classroom platform access
  • Submission inbox
  • Scanned paper list

You get

  • Turn-in report per assignment
  • Missing list

How does it work, step by step?

  1. Load the rosterOne list of students and assignment IDs.
  2. Pull each sourceClassroom submissions, emails with attachments and a scan log.
  3. Match to studentsMatch by student ID or email, not name alone.
  4. Build the reportOne table: student, assignment, source, time.
  5. Review missingThe teacher checks the missing list before any follow-up.

The prompt

Our own prompt, inspired by u/Valuable_Simple3860 on r/ChatGPT and written to work in Zapier, Make and Microsoft Copilot. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt3 variables
Using the roster {roster} and these submission records {records}, build a table of student, assignment, source and time.
Match by student ID or email. List unmatched records separately. List students with no submission for {assignment}. Do not guess matches.

Inspired by u/Valuable_Simple3860 on r/ChatGPT: Teacher Using AI Agents for School Work. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Name matching fails on nicknames; use IDs.
  • Student data must stay in school-approved tools.

Our take

The account is secondhand and light on detail, but the task is concrete and common. Keep it narrow: track turn-ins, do not grade, do not contact parents automatically. School-approved tools only, because student data rules vary by district. Load the roster from the official source. Match submissions carefully when names differ across systems. Build a missing list the teacher reviews before anyone reaches out home. Prefer read-only access to classroom platforms. Do not store student work longer than policy allows. Test the report against a manual check for one class period before trusting it. Keep paper submissions in the loop rather than pretending everything is digital. Document who can see the report. When in doubt, ask the school's IT or privacy officer before connecting new tools. Share the report only through school-approved channels, never personal email threads with parents. Reconcile one random student by hand each week so silent mismatches surface early.

Where the time goes back: Checking three places becomes reading one report.

FAQ

Does it grade?
No. It only tracks submissions.
Which tools?
Whatever your school approves.

Source and credit

Inspired by u/Valuable_Simple3860 on r/ChatGPT. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Teacher Using AI Agents for School Work
Creator
u/Valuable_Simple3860 on r/ChatGPT
Published on
Reddit
Original date
Sep 23, 2025
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Zapier
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminWorkflow✓ AI dry run

Build a funding database from grants found online

Have an automation agent search the web for grants by country and add each one to a structured table you can review and publish.

Credit: u/Ste_XD on r/zapier

Under an hour
Operations & AdminWorkflow✓ AI dry run

Send training clients a schedule PDF and timed reminders

When a client books, send a welcome email with their session schedule as a PDF, then reminders 30 and 7 days before their first session, each sent once.

Credit: u/Accurate-Tank-2564 on r/n8n

An afternoon+
Operations & AdminRoutine✓ AI dry run

Morning brief from calendar, tasks and inbox in Make

Every weekday morning: one brief in Slack and email with your meetings, open tasks, emails that need you, weather, headlines and priorities.

Credit: Codex Solutions International (@CodexSolutions)

Under an hour
Operations & AdminWorkflow✓ AI dry run

Port a huge TypeScript runtime to Rust in small merges

Rewrite a core runtime into a faster language with agents doing most of the coding, shipping piece by piece rather than in one risky cutover.

Credit: Stephen Toub

An afternoon+