Build a visit brief that keeps purpose, itinerary, confirmations, and actual participation distinct. Each unknown needs a role to check it. Planned times and illustrative records should remain visibly separate from an approved trip and the counts recorded on the day.
The University of Texas at Austin Meadows Center's 2011 guide includes a field-trip appendix with learning purpose, logistics, and separate permission and attendance fields. It supports these planning distinctions, but it is historical program material rather than current school policy. The brief and example below are original; they do not reproduce its form or behavioral instructions. Meadows Center guide, Appendix M
Begin with a purpose the visit can answer
The fictional destination is the Learning Gallery. The proposed learning task is to record one visible feature of an exhibit and one question for the host. Students distinguish an observation from an explanation that still needs confirmation.
Before the visit, rehearse that distinction with an original fictional exhibit description: a display card contains a blue circle and a red square. “The card contains a red square” is supported by the description. Why the exhibit uses those colors remains a question for the host. This rehearsal card is not an actual gallery exhibit; actual displays and host answers have not been supplied.
After the visit, use the actual observation note and any recorded host answer to discuss what became supported and what remains unknown. Leave those fields blank in the advance plan. Do not manufacture a host explanation to make the learning task look complete.
Make the proposed itinerary add up
The visit date, local time zone, host booking, and transport authorization are all TO CONFIRM. The following local-clock schedule is a planning example, not a booking or a checked journey time:
| Proposed local time | Activity | Planned minutes |
|---|---|---|
| 09:00–09:30 | Outbound travel | 30 |
| 09:30–09:40 | Host orientation | 10 |
| 09:40–10:20 | Exhibit observation task | 40 |
| 10:20–10:40 | Questions and reflection | 20 |
| 10:40–11:00 | On-site buffer | 20 |
| 11:00–11:30 | Return travel | 30 |
The two travel legs total 60 minutes. On-site activities and buffer total 90 minutes. The whole proposed period is 150 minutes, from 09:00 to 11:30. Keep the buffer visible rather than treating it as a completed learning activity. Actual route durations and host availability need confirmation before the plan is used.
Assign confirmation work without inventing policy
Use a proposed teacher-lead role to check the school's purpose, approval process, permission requirements, supervision arrangements, and approved record workflow. Use a proposed host-liaison role to confirm the destination, booking, available exhibits, activity timing, and access arrangements. Coordinate transport details with the actual authorized school role.
Record the actual owner and answer for each question when confirmed. Emergency procedures, transport rules, individual access arrangements, and supervision requirements must come from the school and host. Do not fill them with an invented ratio or treat this planning packet as a safety certification. A proposed role label is not an assignment to a real person.
Keep permission records separate from attendance
For an anonymous fictional illustration, S01 and S02 have permission records marked received; S03 is pending. That is two received records out of three illustrative entries. It is not two actual attendees, three approved participants, or approval to depart.
Keep actual departure, arrival, and return counts blank until recorded in the school's approved workflow. At each checkpoint, reconcile who is present against the actual roster; a numerical total alone can hide an identity discrepancy. An unknown count should stay unknown rather than turn into the planned three or zero.
The review copy can show a checkpoint label, planned timing, missing actual count, and responsible confirmation role without displaying children's names, contact details, or medical information. Handle the actual roster and any needed sensitive records privately in the school's approved system. S03's pending example should stay visible, with a question for the teacher lead about the required next step, rather than become a “ready to go” badge.
Copy this prompt for the visit preparation packet
Create one complete, self-contained US-English HTML companion for “Field trip • Learning Gallery planning brief”. Return the full HTML document, with inline CSS and any JavaScript needed for the local interactions. Use the original scenario, named records, numbers and expected cases below.
Design the page for this task: use clearly labeled input or source records, a readable result or worked example, and an adjacent explanation of the evidence. Use a restrained visual hierarchy, left-aligned text, readable tables or stacked records, and a responsive layout at 720px and 360px. Provide meaningful labeled controls for Restore proposed itinerary; The card contains a red square; Red means danger here; Select text. Use keyboard-accessible native controls and visible focus. Keep the complete content readable without an external dependency.
The following brief supplies the substantive content and constraints. Native-format requests describe the material to represent or copy manually; this HTML must not pretend to create DOCX, XLSX, PDF, PPTX, H5P or another native file, run Python/Flask/Django/Snowflake/Power BI, connect a live service, send messages, or perform an authorized real-world action. Where the task requires a native source, actual observation or separate approval, retain that requirement and leave unsupplied evidence blank.
Create a complete US English field-trip preparation packet: purpose-linked visit brief, proposed itinerary, school/host confirmation questions with roles, anonymous illustrative permission-state example, separate blank actual checkpoints, and before/after learning notes. Original wording/layout only; no copied institutional forms or current-policy claim. Fictional destination Learning Gallery. Actual date,localtimezone,hostbooking,transportauthorization TO CONFIRM. Learning task: record one visible exhibit feature and one question for host,distinguishing observation from unconfirmed explanation. Original rehearsal card:bluecircle/redsquare;colors'purpose unknown. Actualexhibits/hostanswers/studentwork blank. Proposed local itinerary:09:00-09:30outbound30;09:30-09:40orientation10;09:40-10:20observation40;10:20-10:40questions/reflection20;10:40-11:00buffer20;11:00-11:30return30. Total150minutes=60travel+90onsite. Actualroutes/timing mustbe confirmed,notbooked/performed. Teacher-lead andhost-liaison roles are proposed,actualownersblank. Ask school/host to supply approvals,permissionprocess,transport,supervision,access andemergencyprocedures. Do not inventratios,individualarrangements or safety certification. Anonymous illustration S01/S02 permissionrecordsreceived,S03pending:2of3records only,notattendance/tripapproval. Actualdeparture/arrival/return counts andidentityreconciliation remainblank/unknown inapprovedschoolworkflow. No publicchildnames/contact/medicaldetails,collection orpermissionexecution. Missingcount notassumed3or0;pendingnotreadybadge. If proposing HTML preparation/itinerary/checkpoint views,preserve plannedversusactual distinctions andunresolvedroles/questions;implementation/testingpending. No booking,attendanceapproval,studentcollection orsafety-compliance controls. Actual schoolrecords remainauthoritative.
COMPLETE AUTHORED SCENARIO AND EXPECTED CASES
The following is the supplied reading/teaching/calculation record to represent in the companion. Preserve its particular content, examples, source references and unknowns. Wording about a future native implementation refers to that native task, not permission to omit this HTML companion.
# A Field Trip Planning Template That Separates the Plan from the Permission to Go
Two permission records have been received and one is still pending. That tells you something about paperwork. It does not tell you who will board the transport, whether the visit is authorized, or what the group will learn when it arrives.
Build a visit brief that keeps purpose, itinerary, confirmations, and actual participation distinct. Each unknown needs a role to check it. Planned times and illustrative records should remain visibly separate from an approved trip and the counts recorded on the day.
The University of Texas at Austin Meadows Center's 2011 guide includes a field-trip appendix with learning purpose, logistics, and separate permission and attendance fields. It supports these planning distinctions, but it is historical program material rather than current school policy. The brief and example below are original; they do not reproduce its form or behavioral instructions. [Meadows Center guide, Appendix M](https://meadowscenter.org/wp-content/uploads/2022/04/DOPIIG_Final1.pdf)
## Begin with a purpose the visit can answer
The fictional destination is the Learning Gallery. The proposed learning task is to record one visible feature of an exhibit and one question for the host. Students distinguish an observation from an explanation that still needs confirmation.
Before the visit, rehearse that distinction with an original fictional exhibit description: a display card contains a blue circle and a red square. “The card contains a red square” is supported by the description. Why the exhibit uses those colors remains a question for the host. This rehearsal card is not an actual gallery exhibit; actual displays and host answers have not been supplied.
After the visit, use the actual observation note and any recorded host answer to discuss what became supported and what remains unknown. Leave those fields blank in the advance plan. Do not manufacture a host explanation to make the learning task look complete.
## Make the proposed itinerary add up
The visit date, local time zone, host booking, and transport authorization are all `TO CONFIRM`. The following local-clock schedule is a planning example, not a booking or a checked journey time:
| Proposed local time | Activity | Planned minutes |
| --- | --- | --- |
| 09:00–09:30 | Outbound travel | 30 |
| 09:30–09:40 | Host orientation | 10 |
| 09:40–10:20 | Exhibit observation task | 40 |
| 10:20–10:40 | Questions and reflection | 20 |
| 10:40–11:00 | On-site buffer | 20 |
| 11:00–11:30 | Return travel | 30 |
The two travel legs total 60 minutes. On-site activities and buffer total 90 minutes. The whole proposed period is 150 minutes, from 09:00 to 11:30. Keep the buffer visible rather than treating it as a completed learning activity. Actual route durations and host availability need confirmation before the plan is used.
## Assign confirmation work without inventing policy
Use a proposed teacher-lead role to check the school's purpose, approval process, permission requirements, supervision arrangements, and approved record workflow. Use a proposed host-liaison role to confirm the destination, booking, available exhibits, activity timing, and access arrangements. Coordinate transport details with the actual authorized school role.
Record the actual owner and answer for each question when confirmed. Emergency procedures, transport rules, individual access arrangements, and supervision requirements must come from the school and host. Do not fill them with an invented ratio or treat this planning packet as a safety certification. A proposed role label is not an assignment to a real person.
## Keep permission records separate from attendance
For an anonymous fictional illustration, S01 and S02 have permission records marked received; S03 is pending. That is two received records out of three illustrative entries. It is not two actual attendees, three approved participants, or approval to depart.
Keep actual departure, arrival, and return counts blank until recorded in the school's approved workflow. At each checkpoint, reconcile who is present against the actual roster; a numerical total alone can hide an identity discrepancy. An unknown count should stay unknown rather than turn into the planned three or zero.
The review copy can show a checkpoint label, planned timing, missing actual count, and responsible confirmation role without displaying children's names, contact details, or medical information. Handle the actual roster and any needed sensitive records privately in the school's approved system. S03's pending example should stay visible, with a question for the teacher lead about the required next step, rather than become a “ready to go” badge.
Implement the local companion rather than returning a text-only plan. Preserve every numerical fixture and the distinction between illustrative expectations and actual evidence. Any native-runtime or classroom tests mentioned above remain tests to perform in the proper environment; do not mark them passed. Keep edits and practice responses in this open page only, without claiming persistent storage. Provide invalid/missing-input feedback and reset behavior that agree with this specific brief. Do not claim accessibility certification, learning gains, real approvals or test results that were not observed.
Review the preparation
Use the HTML companion to inspect unresolved confirmations beside the learning task in the companion. Keep actual permissions, approvals, rosters, and day-of-visit records in the school's approved workflow.
Finish the planning review with a clear learning purpose and a named next confirmation for each unresolved item, while leaving actual participation to the records made on the day.