AI for teachers: record, then check.

You can use the lab's record-then-check pattern to turn your notes into a parent email with every factual claim traced back to those notes.

Give the agent a record, the source material it must work from: your lesson objective for prep, or your rubric and observations for feedback. Apply Natthan.AI Lab's split between drafting and approval: you check the first pass against that record and decide what reaches a student or parent.

1. Give the agent the record for this job.

   Put your lesson objective beside the material you will teach from. For feedback, supply your rubric and your own observations of the student's work. For a parent email, use your own notes on the student. Ask the agent to list the source notes it received and count them. Mark missing information and tell the agent to leave it out of the draft.

   You know it worked when you can reproduce every count the check reports from the records you supplied, the test behind the lab's 250-reachable audience. Check that the agent used all the relevant notes, just as that audience check needed both consent sources.

2. State what stays with the teacher.

   Write your version of what stays with the owner, the decisions you keep: grades and anything about a named child stay with you. Keep approval of anything sent to a parent with you too. Put that rule in the instruction before you ask for a draft.

   You know it worked when your instruction reserves those decisions for you, just as client-facing changes wait for the owner on Agencies & client delivery. Keep the tool out of the send step so it cannot approve its own draft.

3. Ask for a first pass tied to the record.

   Ask for a lesson outline tied to your objective, or feedback tied to a rubric passage and your observation. For a parent email, ask for a draft using only your notes, with missing facts left out. Require the source note beside each factual claim so you can check it before using the draft.

   You know it worked when each claim about completed work points to a note you supplied. Reject a draft that reports work that did not happen, the failure behind the lab's rule about checkable claims of done.

4. Put your check between the draft and the world.

   Match every factual claim to the record yourself. Remove anything the notes do not support, including a date the agent added to make the email sound complete. Test any AI check against the notes too; make it show the passage behind each verdict.

   You know it worked when you can show why a claim passed or failed, and anything you have not checked stays marked unchecked. Use the lab's checker that needed teeth as the warning: it produced false failures until the checker itself was fixed.

5. Decide what the recipient will actually see.

   Open the final worksheet or message in the form you will use. Read it after your corrections, then decide whether it can leave the draft. Hold it if an unresolved fact changes what you would tell the parent.

   You know it worked when you have read the actual output and approved that version. Apply the check missing from 463 passing tests beside a blank page: look at what the person will receive.

6. Keep the version you checked.

   Keep a receipt, evidence of what you checked and approved, with the exact version you used. Store it beside the source notes in school-approved records, including any unsupported claim you removed.

   You know it worked when you can reopen that version with its source notes and see why you approved it. Copy the link between work and evidence from the receipts in Under the hood; keep your approval attached to the text you checked.

Fictional practice. Rowan is an invented student. Every classroom detail below is invented for this exercise.

Copy the sequence from the 250-reachable audience: I required current consent before anyone could be emailed. The tool returned four reachable. The check found a missing consent source, so I decided that consent had to be read across both systems. Use that same split here: you supply the notes and own the decision after the check.

• Avoid checking only part of the record: the tool read one consent source and reported four reachable in the 250-reachable audience.
• Reject unsupported “done” claims: the lab's false status reports said work had happened when it had not.
• Open the result before trusting green: 463 passing tests missed a blank page because none looked at the rendered result.
• Put the check in the path to sending: the lab's lie-detector was built but not plugged in.

Pick one recurring parent email and apply the check from the fictional Rowan example. Write the rule that stays with you in one line: you approve every claim about the child and anything sent to the parent. Use invented notes unless your school has approved the tool and this use of the records.

Draft from your notes, then check every fact against them. Remove anything you cannot point to in those notes, as you removed “last Monday” above. Send only what you verified; keep practice on invented material unsent. Save the checked email beside the notes with your receipt of the correction.