Parties
Identify student, parent/guardian, and the school entity by legal name and address; include student ID when applicable.
A concise Student School Agreement reduces disputes, clarifies financial and behavioral expectations, and creates an auditable record for compliance with FERPA, state education codes, and privacy laws. Properly executed agreements also support enforcement of attendance and fee policies and demonstrate parental consent where required.
Typical participants include the student (or parent/guardian), school administrators, program coordinators, and occasionally third‑party service providers such as health vendors or transportation contractors.
Signatures establish consent, attribution, and an execution date used for enforcement and record retention; verify signer authority before finalizing.
Identify student, parent/guardian, and the school entity by legal name and address; include student ID when applicable.
Specify effective date and term, plus renewal or re‑enrollment rules and any probationary periods.
State behavioral standards, attendance expectations, reporting requirements, and tiered disciplinary responses.
List tuition, deposits, refunds, payment schedule, and consequences for late or missing payments.
Address FERPA authorizations, directory information choices, and any HIPAA disclosures for health services.
Provide signature blocks, notice addresses, governing law clause, and amendment procedure.
| Field | Configuration |
|---|---|
| Signer Order | Parent → Student (if required) → School Admin |
| Authentication | Email link; optional SMS code or knowledge‑based check |
| Notifications | Auto reminders 3 and 7 days after first request |
| Storage | Export signed PDF to student record and retain audit log |
Ensure the signing platform supports legal requirements, preserves an audit trail, and exports standard PDF/A or PDF with embedded metadata.
Confirm platform encryption, retention, and access controls meet FERPA and any applicable state student‑privacy or health privacy rules before routing signed agreements.
Enter immediately before signatures; determines when obligations begin.
Match school calendar cutoffs and add grace periods if applicable.
List specific payment dates and late fee assessment timelines.
Retention counts from creation or last effective date per regulation.
Provide required notices at or before record disclosure.
Legal or admin reviews the draft and clears required consent language.
Obtain signed consent and capture the timestamp and signer details.
Enter fee schedule into finance system and set up autopay if applicable.
Store signed copy in SIS with searchable metadata for retrieval.
A district adopted a standard Student School Agreement for summer camps to centralize consents and payments, cutting processing time by half.
A charter network used online agreements to capture health consents for on‑site clinics, avoiding paper delays during enrollment.
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | No | No | Yes, limited | Yes, limited |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |