# Keep up with school paperwork

Designed for: Parents sorting school emails, activity messages and forms

Result: A short list of dates, things to bring and forms that need a parent's attention.

## Try a sample first

Illustrative example, not a recorded Bot run. This adaptation has not been runtime-tested.

### Complete first request

Organize these school messages by child and date. Separate confirmed dates from unanswered questions, and identify any conflicting instructions Use only the records I supply. Label missing or uncertain information. Do not connect accounts, browse, send, submit, publish, spend money or create a schedule. Return a draft for my review.

Fictional records. S1: Mira's museum trip is October 22, 2026. Bring a packed lunch. Return the signed permission form by October 19. S2: Sam has choir on October 21 at 4 p.m.; pickup location not supplied. S3: A later message says Mira's trip date is still being confirmed; no new date is given.

### Example result

Mira: permission form requested by October 19 (S1). Trip date unresolved: S1 gives October 22; S3 says it is still being confirmed. Check with the school before making travel plans. Packed lunch requested in S1. Sam: choir October 21 at 4 p.m. (S2); ask where pickup is.

### Check the answer

- Keep Mira and Sam separate.
- Flag the conflicting trip messages instead of choosing a date.
- Do not sign forms or add calendar events.

Inspired by a community use shared by @jones_attila: https://x.com/jones_attila/status/2109603126051237928
Found through Bot Usecases (https://botusecases.netlify.app/), curated by KP. This fictional sample was written by Bot Cabinet.

## Operating guide

- **When to use it:** Use this workflow when you need a short list of dates, things to bring and forms that need a parent's attention.
- **Lead Bot:** Planner
- **Cadence:** When a person supplies the approved brief and starts the workflow
- **Typical first run:** 15–30 minutes for a first manual run

### Access for the first run

- The approved inputs listed on this page
- Only the files, sources, and services required for this run
- No sending, publishing, spending, or live-system changes without approval

## Recommended starting Bot

1. Planner

Use Planner with the task below. This is a workflow for an existing role, not a separate installed Bot.

## Information to gather

- Start with the fictional records below
- For your own task, choose only the records you want the Bot to use
- Remove private details you do not need for the task

## Workflow

### 1. Planner

Organize these school messages by child and date. Separate confirmed dates from unanswered questions, and identify any conflicting instructions

Output: A short list of dates, things to bring and forms that need a parent's attention.

Message to send:

Use the approved inputs I provide. Organize these school messages by child and date. Separate confirmed dates from unanswered questions, and identify any conflicting instructions. Return this result: A short list of dates, things to bring and forms that need a parent's attention.. Ask me about missing information before you continue.

## Overall request

Organize these school messages by child and date. Separate confirmed dates from unanswered questions, and identify any conflicting instructions Use only the records I supply. Label missing or uncertain information. Do not connect accounts, browse, send, submit, publish, spend money or create a schedule. Return a draft for my review.

## Decisions for a person

- Check the result against the supplied records
- Approve any account connection, schedule or outside action separately
- Review anything before it is sent, submitted, purchased or published

## First test

Keep Mira and Sam separate. Flag the conflicting trip messages instead of choosing a date. Do not sign forms or add calendar events.

## Success checkpoint

Check the result against your original material. You make the decisions listed below. Keep Mira and Sam separate. Flag the conflicting trip messages instead of choosing a date. Do not sign forms or add calendar events.

## If the workflow stalls

If the result is incomplete, mark the missing information and ask the same Bot to correct it. Add another Bot only when a genuinely separate role or independent check would help.

## Hermes Desktop setup

1. Open the linked Bot's page, download its .tar.gz profile, and import it from the Profiles screen in Hermes Desktop.
2. Review the profile's SOUL.md, Bot Passport, and requested access.
3. Run the complete request in that Bot's chat with low-risk material and review the result.
4. Add a schedule, outside connection, or optional specialist only after the manual version works.