Header information
School name, program, and intake office details so submissions are correctly routed and officially logged for tracking and accountability.
A formal request creates a written record for case review, supports consistent decision-making, improves traceability for appeals, and helps institutions meet legal obligations such as FERPA recordkeeping and, where applicable, HIPAA protections for health-related documentation.
Stakeholders at schools and institutions each play a role in submitting and reviewing support requests.
Roles and responsibilities vary by district and institution; verify which office accepts the form and the routing process before submitting.
| Field | Configuration |
|---|---|
| Required Fields | Mark identity and support fields as required to prevent incomplete submissions. |
| Conditional Logic | Show document upload fields only when specific supports are selected. |
| Signer Authentication | Use email verification, SMS code, or higher assurance for sensitive records. |
| Retention Location | Route signed records to secure archive or LMS per policy. |
Choose systems that support secure uploads, access controls, and a verifiable audit trail for each submission.
Ensure the chosen platform meets institutional privacy requirements and integrates with student information systems to keep records synchronized and searchable.
School name, program, and intake office details so submissions are correctly routed and officially logged for tracking and accountability.
Full legal name, date of birth, student ID, contact details, and guardian information to match records and avoid duplicate cases.
Clear, specific request fields that let reviewers understand what accommodation or aid is sought and its intended scope.
A checklist for required attachments (medical letters, IEPs, income proof) to reduce back-and-forth and speed eligibility determinations.
Signature blocks and releases for records sharing, FERPA consent where applicable, and third-party communications authorization.
Fields indicating priority, desired start date, and preferred contact method to help staff schedule implementation.
Save signed requests as PDF/A for archival stability and compatibility with records management systems.
Provide a print-ready version that includes the audit trail and signature timestamps for offline retention.
Include signer identity, IP address, timestamp, and any authentication method used to support future verification.
Export to secure cloud storage or student information systems with restricted access for authorized personnel only.
Submit before registration or term start to enable accommodations.
Expect confirmation of receipt within 1–5 business days.
Processing commonly requires 10–30 business days depending on evidence.
Institutions typically issue written decisions and implementation steps.
Allow time for internal appeals; check institutional policy for deadlines.
Applicant submits form and supporting documents to intake office.
Institution confirms receipt and assigns a case number.
Staff review evidence, consult providers, and determine eligibility.
Approved supports are scheduled and communicated to involved parties.
| 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 | Varies | Varies | Varies | Varies |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies | Varies | Varies |