Participant Info
Student full legal name, preferred name, date of birth, student ID and school district to match enrollment records and verify identity against roster systems.
A well-prepared Student Bridge PP reduces administrative friction, documents parental consent and emergency instructions, and centralizes required disclosures such as FERPA permissions and medical authorizations. It helps schools manage liability, coordinate services, and maintain a consistent, auditable record for each enrolled student.
Several roles interact with this packet depending on program size and governance.
Clear role definition reduces rework and ensures the packet is complete when the program begins.
Student full legal name, preferred name, date of birth, student ID and school district to match enrollment records and verify identity against roster systems.
Primary and secondary contacts with relationship, daytime and alternate phone numbers, and authorized pick-up designees for release of the student.
Allergies, chronic conditions, medications, physician contact, and specific permission for administration of medications or emergency medical transport.
Program dates, daily schedule, participation expectations, behavioral rules, and any fees or materials required for the bridge program.
FERPA release language for education records access and any HIPAA-consent language for clinical information shared during program activities.
Parent/guardian signature, printed name, relationship, date, and optional witness or notary fields if the jurisdiction or district policy requires them.
| Field | Configuration |
|---|---|
| Routing Order | Parent signs first | program coordinator reviews last |
| Authentication | Email link or SMS code for parent verification |
| Conditional Fields | Show medication fields only when 'Yes' is selected for medical needs |
| Storage | Secure cloud storage with access controls and audit trail |
Use file formats and integrations that align with school systems and privacy controls.
Confirm integration and encryption requirements with your IT or data‑privacy officer before accepting electronic submissions.
Forms typically due at least one week before program start
Update medical information immediately on any change prior to attendance
Districts may require annual reauthorization under FERPA policy
Provide signed transportation permissions before first transported trip
Late packets may be accepted at program discretion or denied for safety reasons