Who may sign this agreement?

Typically the student's parent or legal guardian signs; students of sufficient age may sign alongside a guardian if district policy permits. Authorized school officials (teacher, principal, or records officer) should sign to confirm the district's implementation decision.

Is an electronic signature valid?

Yes. Electronic signatures that meet ESIGN (15 U.S.C. ch. 96) and applicable state UETA standards are legally valid for most school agreements. Check district policy when a wet-ink signature is explicitly required.

Does FERPA limit disclosure of the agreement?

FERPA governs education records; signed agreements are part of the education record and must be disclosed only according to FERPA procedures. Route requests through the district records office and redact nonessential information when necessary.

When is notarization necessary?

Notarization is uncommon for reading agreements but may be required by local policy or special circumstances. Verify state and district rules; if required, use in-person or RON notarization that complies with state notary law.

How long should the district retain this agreement?

Retention varies by state and content; a prudent approach is to retain signed agreements for at least three years after the student leaves. Apply HIPAA or financial retention rules where PHI or fiscal records are implicated.

Can the agreement be amended later?

Yes. Amendments should be documented in writing, signed by the same parties, and dated. Retain the amendment with the original agreement and update implementation plans to prevent gaps in accommodations.

Electronic Signature
Templates
Education
Student Right to Read Agreement

Student Right to Read Agreement

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

STUDENT RIGHT TO READ AGREEMENT

Parties and Identification

School Name District Name School Address Student Full Name

Student ID

Date of Birth

Grade / Program

Agreement Effective Date

Purpose and Definitions

Purpose: This Agreement documents the rights of the student to timely, evidence-based reading instruction and to targeted supports where reading proficiency is below expected benchmarks. The Agreement sets forth obligations of the school and the parent or adult student, informed consent for screening and intervention, confidentiality protections, timelines for response, and dispute procedures.

Definitions: "Evidence-Based Reading Instruction" means structured instruction aligned to scientific research on reading that includes phonemic awareness, phonics, fluency, vocabulary, and comprehension. "Reading Intervention" refers to targeted instruction outside of core classroom instruction intended to accelerate reading skill acquisition. "Individual Reading Support Plan (IRSP)" means a written plan developed by the school that documents present levels, goals, supports, frequency of progress monitoring, and duration of interventions.

Student and Parent / Guardian Information

Parent / Guardian or Adult Student Name

Phone

Email

Emergency Contact

Requested Supports and Consents

Please indicate the interventions, assessments, and services you authorize or request. If you do not consent, check the appropriate boxes and consult with the school representative named below to discuss alternatives.

Authorizations I authorize screening and diagnostic reading assessments to identify areas of need. I consent to evidence-based reading intervention as recommended and documented in an IRSP. I consent to regular progress monitoring and receipt of written progress reports at least every 4 weeks during intervention. I consent to provision of instructional materials and accessible formats (text-to-speech, large print, audiobooks) where appropriate. I request consideration for special education eligibility or Section 504 evaluation based on reading difficulties. I consent to the limited sharing of assessment results and IRSP details with outside providers who support the student's instruction, subject to confidentiality protections below.

Describe specific academic concerns, medical conditions, or other considerations relevant to reading instruction Desired start date for supports

School Commitments and Procedures

The school commits to: develop an Individual Reading Support Plan (IRSP) within 15 school days of documented need; implement evidence-based interventions delivered by qualified personnel; provide progress reports at least every four weeks while interventions are active; maintain written records of interventions, materials, and student response to instruction; and convene parent meetings to review progress and next steps.

Confidentiality: All assessment data, IRSPs, and documentation will be maintained in the student's educational record and disclosed only as permitted by applicable privacy requirements. The school will obtain additional written consent before releasing personally identifiable information to non-school entities not referenced in this Agreement.

Implementation obligations: If the student does not make documented progress within the IRSP timeline, the school will notify the parent or adult student and consider additional interventions, referral for evaluation for special education or 504 services, or other remedies as appropriate.

Dispute Resolution and Appeals

If the parent or adult student disagrees with assessment results, IRSP content, or implementation, the parties will first seek to resolve the dispute through an administrative meeting within 10 school days of notice. If the matter is unresolved, the parent or adult student may request an independent educational evaluation at their expense or pursue formal administrative remedies provided by applicable law. Timelines and procedures for formal appeals will be scheduled in writing by the school upon request.

Acknowledgements and Certifications

By signing below, the parent or adult student acknowledges receipt of this Agreement, understands the rights and services described herein, and certifies that the information provided on this form is accurate to the best of their knowledge. Signing indicates informed consent for the selected authorizations above unless indicated otherwise.

I acknowledge that I will receive written progress reports as indicated above. I acknowledge that the school will attempt to develop an IRSP within 15 school days of documented need. I understand the dispute resolution process described above. Signature Authority (if student is 18 or older, student may sign as parent/guardian) Student is 18 years of age or older and will sign as the student.

Parent/Guardian or Adult Student:

By:

Date:

School Representative:

By:

Date:

What the Student Right to Read Agreement Is and Why It Exists

The Student Right to Read Agreement is a written school-level record that documents a student's or guardian's choices about access to assigned reading, requests for alternative materials, and related accommodations. It sets expectations for review procedures, opt-out options, and the school's obligations to provide substitutes or supervised review. Used primarily in K–12 settings, the agreement creates a clear, reproducible record that supports consistent classroom responses and administrative review while aligning with student privacy and access protections such as FERPA.

Why Schools and Families Use This Agreement

The agreement reduces ambiguity by documenting consent, objections, and accommodation plans; this lowers disputes and creates a durable record for compliance, audits, and appeals while supporting consistent instructional implementation.

Who Completes and Maintains These Agreements

Intended users include school administrators, classroom teachers, parents or guardians, special education coordinators, and district compliance staff responsible for reading assignments.

K–12 parents: request opt-outs, track reviewed materials, and record consent or objections in writing.
Teachers: document accommodations, assign approved alternatives, and maintain consistent classroom records for audits.
District staff: ensure policy alignment, process appeals, and preserve record for FERPA access requests.

Each role has distinct responsibilities: parents provide preference and signatures, teachers implement alternatives, and administrators document decisions and retention paths.

Step-by-Step: Completing the Agreement

Follow these steps to complete and record a Student Right to Read Agreement accurately and consistently at the school level.

01

Prepare Form: Confirm student identity and gather IDs.
02

Detail Request: Describe materials, dates, and accommodation specifics.
03

Obtain Signatures: Collect guardian and administrator signatures with dates.
04

File Record: Store signed copy in student record and school compliance folder.

How to Configure the Digital Agreement Workflow

When customizing the digital agreement, set field rules, signer order, authentication, and retention settings before sending.

Field	Configuration
Signer Order	Guardian -> Teacher -> Administrator (sequential routing)
Authentication Method	Email link with optional SMS code; stronger KBA if required
Conditional Fields	Show alternative-assignment details only if opt-out selected
Retention Settings	Auto-save signed PDF to SIS and compliance folder for 6 years

Where Completed Agreements Are Sent and Stored

Common submission pathways and recipients for completed Student Right to Read Agreements in a school district workflow.

Local School: File signed copy in student cumulative folder and notify teacher.
District Office: Submit a copy to district records and compliance team.
Special Ed: Share with special education coordinator for accommodation implementation.
FERPA Requests: Provide redacted copies on written request per FERPA rules.

Platform and Security Considerations for Electronic Completion

Digital signatures and distribution require compatible platforms that support audit trails, access controls, and FERPA-safe storage.

Authentication Options: Email, SMS code, or SSO.
Audit Trail: IP, timestamp, action history preserved.
Storage Encryption: AES-256 at rest, TLS 1.2/1.3 transit.

Timing and Deadlines to Expect

Key timing expectations for processing Student Right to Read Agreements, from receipt through record retention.

Receipt Acknowledgment:

Acknowledge receipt within 3 business days.

Administrator Review:

Complete review within 10 school days of receipt.

Accommodation Start Date:

Begin agreed alternative within one grading period.

FERPA Request Response:

Provide copies within 45 days per district policy.

Record Retention Start:

Retention begins on signed effective date.

Milestone Sequence from Request to Archival

Milestone timeline from initial request to archived retention for Student Right to Read Agreement records.

01

Submission

Guardian submits request and completes required sections online or on paper.

02

School Review

Teacher and administrator review request and recommend action.

03

Decision

Administrator documents approval, denial, or alternative and signs.

04

Archival

Signed agreement saved to student record and district archive.

Common Preparation and Processing Mistakes

Failing to match the student name or ID with school records causes processing delays and may trigger requests for corrected documentation.
Using ambiguous language for requested accommodations (e.g., 'reasonable alternative') leads to inconsistent implementation and frequent follow-up from staff.
Not obtaining all required signatures, including district reviewers, can invalidate the agreement under local policy and complicate FERPA recordkeeping.
Storing signed documents in personal email or unsecured drives risks FERPA violations and loss of audit trail integrity.

Penalties and Risks from Incorrect or Incomplete Agreements

FERPA Disclosure Risk: Unauthorized access penalties; district liability.

Delayed Education: Missed accommodations harm instruction.

Policy Noncompliance: Administrative sanctions possible.

Recordkeeping Errors: Harder to respond to access requests.

Appeal Costs: Attorney or hearing expenses.

Data Breach: Fines and remediation costs.

Illustrative Examples from Typical School Scenarios

Real examples illustrate typical scenarios where a Student Right to Read Agreement clarifies rights and school responsibilities.

District Accommodation

A parent requested their child be excused from a novel for religious reasons and proposed an approved substitute course packet.

School reviewed request and proposed alternatives.
The signed agreement documented the agreed substitute, set dates for assessment, and required teacher confirmation of completion; the record resolved disputes and provided a clear audit trail for district compliance reviews.

Opt-Out Appeal

A student sought to examine assigned material before deciding on participation; school offered supervised review and alternate assignment options.

Guardian consented to on-site review.
The agreement recorded the process, timelines, and final decision; it made appeals transparent and ensured both instructional continuity and respect for parental concerns, reducing administrative hearings.

Essential Elements to Include in a Professional Agreement

Core components of a professional Student Right to Read Agreement ensure clarity, legal conformity, and operational readiness across classrooms and districts.

Identification

Student, guardian, and school identifiers including full names, student ID, grade, school site, and contact details. Accurate identifiers prevent mismatches with education records.

Request Details

Explicit description of the material in question, dates assigned, reason for objection or accommodation, and proposed substitute materials or activities.

Decision Record

Administrator's determination noting approval, denial, or modification, including rationale, appeal rights, and signatures of the decision-maker and any reviewers.

Implementation Plan

Timetable for alternate assignments, responsible staff, monitoring procedures, and measures to confirm student engagement and assessment equivalency.

Signatures

Signed and dated blocks for guardian, student (when appropriate), teacher, and an authorized school official; include printed names and titles to confirm authority.

Retention

Clear instructions on storage location, retention period, and procedures for producing copies in response to FERPA or legal requests.

Download Options and Supporting Documents

Download options and supporting documents ensure consistent records and easy sharing with authorized parties while preserving audit trails and data integrity.

Supported Formats

Provide signed PDFs and editable DOCX versions. Signed PDFs should include an audit certificate suitable for district archives and legal review.

Supporting Docs

Attach lesson plans, alternative assignments, correspondence, or IEP excerpts as exhibits to document the context and rationale for accommodations.

Exporting

Export signed files to the student information system or document storage using file names that include student ID and effective date for easy retrieval.

Backup

Keep encrypted backups in district-approved cloud storage with role-based access and periodic export for compliance verification.

Required Information: Quick Reference

Student Full Name: Exact legal name as on records.

Student ID: School-assigned numeric identifier (no spaces).

Guardian Contact: Phone, email, and mailing address.

Material Details: Title, author, publisher, and date.

Reason: Concise factual justification for request.

Signatures & Dates: Signed and dated by all required parties.

Comparison: Common eSignature Platforms for This Agreement

Comparing common eSignature options for executing and archiving Student Right to Read Agreements; signNow appears first per platform availability and pricing.

	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

FAQs and Troubleshooting for Common Questions

Answers to common questions about completing, signing, storing, and disputing Student Right to Read Agreements in U.S. school settings.

Need help? Contact support

Who may sign this agreement?
Typically the student's parent or legal guardian signs; students of sufficient age may sign alongside a guardian if district policy permits. Authorized school officials (teacher, principal, or records officer) should sign to confirm the district's implementation decision.
Is an electronic signature valid?
Yes. Electronic signatures that meet ESIGN (15 U.S.C. ch. 96) and applicable state UETA standards are legally valid for most school agreements. Check district policy when a wet-ink signature is explicitly required.
Does FERPA limit disclosure of the agreement?
FERPA governs education records; signed agreements are part of the education record and must be disclosed only according to FERPA procedures. Route requests through the district records office and redact nonessential information when necessary.
When is notarization necessary?
Notarization is uncommon for reading agreements but may be required by local policy or special circumstances. Verify state and district rules; if required, use in-person or RON notarization that complies with state notary law.
How long should the district retain this agreement?
Retention varies by state and content; a prudent approach is to retain signed agreements for at least three years after the student leaves. Apply HIPAA or financial retention rules where PHI or fiscal records are implicated.
Can the agreement be amended later?
Yes. Amendments should be documented in writing, signed by the same parties, and dated. Retain the amendment with the original agreement and update implementation plans to prevent gaps in accommodations.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now