Scope
Describe which state tests, grade levels, and student populations are affected; include test codes or names and specify whether changes apply to statewide or district-administered assessments.
Used to document agreed changes to state testing arrangements, an Education State Testing Amendment reduces ambiguity and preserves compliance with state rules. For e-signed amendments, ESIGN (15 U.S.C. §7001) and UETA govern enforceability; check state-specific statutes for intrastate effect.
Typical users who prepare or approve these amendments include district administrators, state testing coordinators, and contracted test vendors.
Stakeholder review, public notice where applicable, and formal sign-off by authorized officials are commonly required before amendments take legal effect.
Describe which state tests, grade levels, and student populations are affected; include test codes or names and specify whether changes apply to statewide or district-administered assessments.
Provide a clear effective date in MM/DD/YYYY format, and state whether the amendment applies retroactively or prospectively to scheduled administrations and reporting cycles for the relevant academic year.
List roles and duties for state offices, district coordinators, site test supervisors, and vendors; include timelines for task completion, contact points, and escalation procedures for issues.
Specify what test data will be shared, permitted recipients, retention limits, security controls, and compliance with FERPA and any state student privacy statutes, including applicable recordkeeping requirements.
Detail approved accommodations, eligibility criteria, documentation required, implementation steps during testing, and procedures for re-evaluation or appeals of accommodation decisions and specify responsible parties and timelines for dispute resolution.
Identify authorized signatories, signature order, any required witness or notary authentication, and whether electronic signatures or Remote Online Notarization are acceptable under state law and specify record retention for executed amendments.
| Field | Configuration |
|---|---|
| Authentication Level | Email link, SMS code, or KBA. |
| Required Fields | Signatures, dates, affected test IDs. |
| Notifications | Email confirmations and reminder schedule. |
| Retention Settings | PDF, audit trail, and storage duration. |
Digital distribution can use secure email, secure portal, or an eSignature platform integrated with SIS and records systems.
At least 60 days before test administration.
Allow 14–30 days for legal and stakeholder review.
Collect all signatures within 10 business days.
Submit to state education agency per their schedule.
Amendment becomes enforceable on the effective date.
A mid-sized school district amended its testing schedule after a natural disaster to shift statewide assessment dates and extend accommodation windows for affected students.
A state amended a vendor contract to require additional security controls and incident reporting timelines after a data exposure affecting test content confidentiality.
| 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 |