Can an FBA be signed electronically?

Yes. Electronic signatures are valid under ESIGN (15 U.S.C. ch. 96) and UETA when intent, consent, attribution, and retention are met. Provide required consumer disclosures if applicable, keep the full audit trail, and attach signed consent documents.

Is parental consent required?

Parental consent is typically required for assessments and changes to special education services. Follow district procedures for notice and consent. Document any refusal and the district's response to ensure compliance with IDEA procedural safeguards.

When is HIPAA relevant?

HIPAA applies when the FBA contains protected health information from external health providers. If PHI is involved, ensure a BAA with the eSignature vendor where required and limit disclosures consistent with privacy rules.

How long should records be retained?

Retain FBA revisions for the active IEP term plus at least three years; when PHI is present retain six years per HIPAA. State agencies may require longer retention—check district policy and state guidance.

What if signatures conflict?

If parties dispute signatures, preserve all versions, print audit trails, and document communications. Escalate to district legal counsel. Time-stamped logs and third-party authentication methods strengthen evidentiary value in disputes or due process hearings.

Can external providers sign?

Yes, contractors and outside service providers can sign if authorized; verify role-based access and consent. For PHI, ensure BAAs and HIPAA-compliant workflows. Record the provider's credentials and contact for audit and follow-up.

FBA Revision Document

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

FBA Revision Document

This FBA Revision Document (the "Revision") amends and supplements the existing agreement titled Functional Business Agreement (the "Original Agreement") entered into between the parties identified below. The Original Agreement is incorporated herein by reference to the extent not expressly modified by this Revision.

WHEREAS

WHEREAS, Client Name: and Contractor Name: are parties to the Original Agreement dated ;

WHEREAS, the parties desire to revise certain terms of the Original Agreement as set forth in this Revision effective on Effective Date: ; and

WHEREAS, the parties intend that this Revision supersede only those provisions of the Original Agreement specifically amended herein and that all other provisions remain in full force and effect unless expressly modified.

AMENDMENTS

The Original Agreement is amended as follows. All capitalized terms used but not defined in this Revision have the meanings ascribed to them in the Original Agreement.

Scope of Work

Revised Scope of Work Attachment(s) included

Attachment A: Revised Statement of Work
Attachment B: Updated Project Schedule

Payment Terms

The parties agree the compensation for the revised Scope of Work shall be:

Total Revised Amount (USD) Payment Schedule and Milestones

Late payments shall be subject to a late fee of per month on outstanding amounts, or a flat fee of , whichever is greater. Interest accrual will begin on the date payment is due. All payments are exclusive of taxes; each party shall bear its own taxes unless otherwise stated.

Term and Termination

The term of this Revision shall commence on Revision Start Date: and shall continue until Revision End Date: unless earlier terminated as provided below.

Either party may terminate this Revision for convenience upon written notice of days to the other party. Termination for material breach shall be permitted where the breaching party fails to cure within days after receipt of written notice describing the breach.

Confidentiality

Each party shall maintain in confidence and shall not disclose to third parties any Confidential Information received from the other party pursuant to the Original Agreement or this Revision. "Confidential Information" means non-public information disclosed in any form that is either marked confidential or that a reasonable person would understand to be confidential given the nature of the information and the circumstances of disclosure.

Confidentiality obligations shall not apply to information that: (a) is or becomes publicly available through no fault of the receiving party; (b) is lawfully received from a third party without restriction; (c) is independently developed without use of the disclosing party's Confidential Information; or (d) is required to be disclosed by law, provided the receiving party gives prompt written notice and cooperates with reasonable measures to limit disclosure.

The confidentiality obligations set forth herein shall survive termination or expiration of this Revision for a period of years.

Representations and Warranties

Each party represents and warrants that it has full right, power and authority to enter into this Revision and to perform its obligations hereunder and that execution and delivery of this Revision has been duly authorized by all necessary corporate or other action.

Governing Law

This Revision shall be governed by and construed in accordance with the laws of the State of , without regard to principles of conflicts of law.

Entire Agreement

Except as expressly amended herein, the Original Agreement remains in full force and effect. This Revision, together with the Original Agreement and any referenced attachments, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, understandings and negotiations, whether written or oral.

Miscellaneous Provisions

Any amendment to this Revision must be made in writing and signed by authorized representatives of both parties. If any provision of this Revision is held invalid or unenforceable, the remaining provisions will remain in full force and effect.

Additional Notes

Client Name:

By:

Date:

Contractor Name:

By:

Date:

What the FBA Revision Document Is

The FBA Revision Document records updates to a student's Functional Behavioral Assessment (FBA), documenting observed behavior, analysis, and adjustments to interventions and supports. Used within special education processes, it captures data the multidisciplinary team relies on when modifying a Behavior Intervention Plan (BIP) or Individualized Education Program (IEP). The document summarizes antecedents, consequences, frequency and severity measures, proposed revisions, and implementation responsibilities. While educational privacy laws like FERPA commonly apply, health-related data may invoke HIPAA; electronic execution is generally acceptable under ESIGN (15 U.S.C. ch. 96) and UETA where adopted.

Why a Formal Revision Document Matters

Use an FBA Revision Document to formalize behavior data, ensure procedural compliance, clarify responsibilities, and document evidence-based changes to interventions. It creates a clear audit trail for teams, supports informed IEP decision-making, and helps meet education and privacy obligations.

Who Typically Prepares and Reviews This Document

School teams, special educators, school psychologists, behavior specialists, and parents typically prepare or review an FBA Revision Document during IEP meetings.

School psychologists and behavior analysts with direct observation and data interpretation responsibilities.
Special education teachers who implement BIPs and document classroom-level effects of revisions.
Parents or guardians providing consent, historical context, and home-based behavior reports.

District administrators, IEP coordinators, and contracted providers use the document for compliance records and cross-agency communication.

Primary Signatories and Their Roles

School Lead

Typically the school district's designated representative—often a school psychologist or special education coordinator—reviews assessment data, documents the behavior support changes, and signs on behalf of the educational team. Their role includes tracking implementation, assigning responsible staff, and updating the IEP record.

Parent/Guardian

A parent or guardian provides informed input, consents to revisions when required, and contributes home-based observations. Their signature documents agreement or recorded dissent, and their participation supports legally defensible educational decisions and continuity between school and home interventions.

Security, Compliance, and Technical Protections

Encryption: TLS 1.2/1.3 transit; AES-256 at rest

Certifications: SOC 2 Type II; ISO 27001; PCI DSS

Privacy Frameworks: HIPAA (BAA available); GDPR; CCPA

eSignature Law: ESIGN (15 U.S.C. ch. 96); UETA

Accessibility: WCAG 2.0 Level AA support

Audit Trail: Comprehensive timestamped logs and history

Risks and Consequences of Incomplete or Incorrect Revisions

IEP Compliance Risk: IEP deadlines missed; due process exposure

FERPA Exposure: Unauthorized disclosure risks loss of trust

Service Delays: Implementation gaps harming student progress

Documentation Gaps: Evidence lacking for meetings or appeals

State Sanctions: Regulatory penalties or corrective action plans

Provider Liability: Contractor disputes and billing denials

Common Preparation Mistakes to Avoid

Failing to update measurable behavior goals makes it difficult to evaluate intervention efficacy and can invalidate progress tracking for IEP reviews.
Incomplete data logs or truncated observation periods reduce credibility of recommendations and hinder selection of appropriate evidence-based strategies.
Using vague descriptors like 'often' or 'frequently' instead of exact counts or rates complicates measurement and compliance reporting.
Not securing parental consent or failing to document team decisions can create procedural violations and delay implementation of revised supports.

Step-by-Step: Completing an FBA Revision Document

Follow these steps to complete and finalize the FBA Revision Document accurately and in compliance with school procedures.

01

Collect Data: Compile observation logs, incident reports, and frequency charts.
02

Analyze: Identify functions, antecedents, and maintaining consequences from data.
03

Draft Revisions: Specify measurable goal changes, interventions, responsible staff, and timelines.
04

Review & Sign: Share with team and obtain signatures and dates.

Typical Workflow for Electronic Revision and Distribution

Routing, approvals, and record storage form the core workflow for electronic FBA revision and distribution within district systems.

Upload: Attach current FBA, behavior logs, and related reports.
Assign Reviewers: Add team members with roles and review deadlines.
Collect Signatures: Obtain electronic or printed signatures; note consent or objections.
Archive: Store final PDF with audit trail and access controls.

Core Elements of a Professional FBA Revision Document

A professional FBA Revision Document combines clear assessment summaries, measurable objectives, defined responsibilities, and compliance-ready metadata to support school decision-making.

Assessment Summary

Concise description of behavior, occurrence patterns, antecedents, consequences, and prior interventions. Include exact observation windows and metrics to support trend analysis and evidence-based revision decisions.

Measurable Goals

Define specific, observable, and time-bound behavior targets. Use exact measurement units (e.g., incidents per week) and baseline comparisons to track progress objectively during subsequent IEP reviews.

Intervention Details

Document each intervention component, delivery agent, schedule, dosage, and setting. Note training needs, materials required, and fidelity checks to ensure consistent implementation across staff and environments.

Responsibilities

Assign named staff with titles and contact information for each task. Include timelines, monitoring intervals, and escalation steps if progress criteria are not met within specified review windows and documentation.

Data Collection

Specify data sources, observation methods, frequency, and responsible observers. Attach templates or example charts and state how data will be aggregated and reported for IEP meetings and compliance audits and inter-rater reliability.

Review Schedule

Set clear review dates, interim check-ins, and criteria for returning to the full team. Indicate who triggers a revision and the notice period required and documentation.

Configure a Digital Workflow for the FBA Revision

Configure a digital workflow to route the FBA Revision Document for review, signature, and archival while preserving audit data and access controls.

Field Name and Configuration Settings	Field \| Configuration
Primary Signer Role and Assignment	Assigned role \| Approval order
Notification Timing and Reminders Settings	Immediate \| 7-day reminder cadence
Authentication Method Level Required	Email link \| SMS code or KBA
Storage Location and Access Controls	District ECM \| Read-only audit access

Technical Requirements and Integrations

Ensure the chosen platform supports secure signing, role-based access, and integrates with district record systems for consistent FBA workflows.

Integrations: Salesforce, Microsoft 365, Google Workspace support
File Formats: PDF, DOCX, and fillable forms
Authentication: Email, SMS code, or SSO options

Key Dates and Deadlines to Track

Key dates include review schedules, parental consent deadlines, IEP update windows, and retention start dates — plan accordingly.

Initial Multidisciplinary Review Meeting Scheduled:

Occurs within district-specified timeline after behavior incident review; document attendance and decisions.

Parental Response and Consent Deadline:

Parent must respond to proposed revisions per district notice period; document consent or objection.

IEP Update and Implementation Window:

Incorporate approved FBA revisions into the next IEP review or amendment within district timelines.

Interim Checkpoint and Progress Review:

Set a date for progress monitoring to assess intervention fidelity and early outcome signals.

Record Retention Start and Audit Date:

Begin retention period from final signed date; preserve audit trails for compliance reviews.

eSignature Pricing and Feature Comparison for Document Workflows

Compare common eSignature plan features and starting prices for executing FBA Revision Documents and managing workflows across vendors.

	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 credit card	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
Envelope Cap	No envelope cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Practical Best Practices for Accuracy and Efficiency

Adopt consistent templates, clear data standards, and digital workflows to reduce errors and support defensibility of FBA revisions.

Use Standardized Templates and Charts

Standardize observation forms and data entry fields to ensure comparability across observers. Pre-fill contextual fields where possible, use auto-calculated summaries, and attach raw logs to support auditability and ease of data review during meetings.

Document Full Team Decision Rationale

Record why each revision was chosen, referencing specific data points, assessment methods, and alternative strategies considered. Clearly state criteria for success and the timeframe for evaluation to facilitate transparent reviews and potential appeals.

Verify Authorizations and Consent Obtained

Confirm parental consent requirements and document any informed refusals. For outside providers, ensure BAAs or data-sharing agreements are in place and that consent language meets ESIGN consumer disclosure rules when executed electronically.

Regular Fidelity Checks and Training

Schedule periodic fidelity observations and staff training to maintain consistent implementation. Use checklists, inter-rater reliability measures, and corrective action steps when fidelity falls below predetermined thresholds to protect student outcomes.

Real-World Examples of Document Use

Two practical examples show how an FBA Revision Document clarifies supports, documents consent, and improves implementation fidelity in real-school scenarios.

Elementary School

A district psychologist revised an elementary student's FBA after weekly ABC charts showed escalation during transitions; data collection spanned four weeks.

Updated interventions added transition cues and staff scripting.
The documented revision included measurable goals, assigned staff, and a two-week fidelity checkpoint. Electronic signatures from parents and staff were attached to the student file, enabling timely implementation and a clear record for later review.

High School Transition

During a high school transition, staff adjusted an FBA after behavior rates doubled in unstructured lunchtime settings over six weeks of data.

Added campus supervision and peer supports.
Signatures from team members and parent consent were captured electronically; the document included monitoring forms and a phased reduction plan. The audit trail showed timely reviews and improved compliance evidence.

Milestones: From Revision to Review

Typical processing milestones from revision to archived record include data collection, team decision, implementation, and scheduled fidelity checks.

01

Data Collection Complete

All observation windows and logs submitted.

02

Team Decision Recorded

Revision approved or notated with dissent.

03

Implementation Begins

Assigned staff start interventions per schedule.

04

Fidelity Checkpoint

Monitor outcomes and adjust if criteria unmet.

How an FBA Revision Document Differs from Related Records

Quick comparison to distinguish FBA Revision Documents from related records such as IEP amendments and consent forms.

Document Type Comparison Matrix for FBA	FBA Revision Document	IEP Amendment
Primary Purpose	update behavior analysis	modify educational goals
Requires Parent Consent	sometimes	typically yes
Integration With IEP	becomes bip exhibit	alters iep sections
Notarization Required

Frequently Asked Questions and Troubleshooting

Answers to common questions about completing, signing, and storing FBA Revision Documents, including digital signatures, consent, and privacy considerations.

Need help? Contact support

Can an FBA be signed electronically?
Yes. Electronic signatures are valid under ESIGN (15 U.S.C. ch. 96) and UETA when intent, consent, attribution, and retention are met. Provide required consumer disclosures if applicable, keep the full audit trail, and attach signed consent documents.
Is parental consent required?
Parental consent is typically required for assessments and changes to special education services. Follow district procedures for notice and consent. Document any refusal and the district's response to ensure compliance with IDEA procedural safeguards.
When is HIPAA relevant?
HIPAA applies when the FBA contains protected health information from external health providers. If PHI is involved, ensure a BAA with the eSignature vendor where required and limit disclosures consistent with privacy rules.
How long should records be retained?
Retain FBA revisions for the active IEP term plus at least three years; when PHI is present retain six years per HIPAA. State agencies may require longer retention—check district policy and state guidance.
What if signatures conflict?
If parties dispute signatures, preserve all versions, print audit trails, and document communications. Escalate to district legal counsel. Time-stamped logs and third-party authentication methods strengthen evidentiary value in disputes or due process hearings.
Can external providers sign?
Yes, contractors and outside service providers can sign if authorized; verify role-based access and consent. For PHI, ensure BAAs and HIPAA-compliant workflows. Record the provider's credentials and contact for audit and follow-up.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now