Route an absence notice to the responsible teacher

Why use this

1. A parent arranging an absence notice may have several school contacts and an outdated timetable close at hand. Selecting the first listed teacher is not enough if the school expects a central attendance address or the student's schedule has changed.

2. A notice preview could bring the verified recipient, absence date and minimum necessary wording together. The guardian could approve the exact disclosure and any contact addition without sharing a medical explanation or assuming that a sent message records attendance successfully.

Why an agent / simpler alternative

Useful judgment

Reconcile supplied timetable and contact information while detecting ambiguity about the school's notification route.

Simpler alternative

Use the school's established attendance form when its destination and required fields are clear.

Unsuitable when

Guardian authorization or the specific recipient is unresolved, or the task asks for a diagnosis.

Proposed inputs

1. Name

   Absence instruction

   Owner

   Verified guardian

   Minimum scope

   Approved student identifier, date and intended notice wording

   Quality check

   Exclude unnecessary health or family details.

2. Name

   School routing information

   Owner

   Guardian

   Minimum scope

   Current timetable and verified attendance instructions

   Quality check

   Confirm that the selected contact is appropriate for this notice.

Access and setup — proposed or unknown

Proposed minimum

1. Fictional timetable and contact records with a local notice preview.

Compatibility unknowns

1. Unknown: current runtime, school communication route and phone-contact integration.

External actions requiring approval

1. Guardian approval of the student, date, exact recipient and notice; separately approve adding the verified contact.

Expected deliverable and review checks

Proposed artifact

Recipient-resolution note, minimal absence-message draft and optional contact-addition preview.

Critical checks

1. The recipient is verified beyond a matching display name.

2. The draft includes only the child's information approved for that specific school recipient.

Missing output evidence

No new workflow run or output inspection is performed for this editorial layer. The linked implementation evidence retains the original source-specific outcome and artifact limits.

Failure signals and proposed responses

1. Signal

   The timetable names one teacher but attendance instructions name another route.

   Why it matters

   The notice may not reach the responsible person.

   Proposed response

   Hold the draft and ask the guardian to resolve the current school process.

2. Signal

   The draft includes an unrequested medical reason.

   Why it matters

   It discloses sensitive information unnecessarily.

   Proposed response

   Remove the explanation and return the exact remaining wording for guardian review.

Effort and cost — unknown

Setup work

1. Verify school instructions and minimum required fields.

Ongoing review

1. Reconfirm recipient and date for each authorized notice.

Unknowns

1. Unknown: school acknowledgment behavior, contact freshness and message costs.

First check — proposed, unexecuted

Status

proposed_unexecuted

Synthetic fixture

A fictional school packet has conflicting teacher and attendance-office instructions plus an unnecessary health detail.

Acceptance checks

1. Keep routing unresolved.

2. Remove the health detail and require exact guardian approval.

Stop conditions

1. Real child information, external messaging or contact writes are needed.

Limits

1. The proposed checks and safeguards are editorial recommendations, not evidence of successful execution or permission to act. The linked implementation retains its own observed outcome and approval limits.