Diagnostic Fields
Structured prompts for presenting problem, baseline data, prior supports, and contextual factors to ensure consistent intake across students and staff.
A documented problem-solving technique standardizes diagnosis, minimizes bias, and creates repeatable workflows for interventions, progress monitoring, and stakeholder communication while producing auditable records for FERPA and federal reporting.
These procedures are used by district teams, school leaders, teachers, and student support professionals who must assess needs and document interventions.
Use cases range from classroom-based corrective plans to district-level program evaluation; records often feed into student information systems and compliance audits.
| Field | Configuration |
|---|---|
| Role Assignment | Map signatures to job titles (teacher, coordinator, principal). |
| Authentication | Use email + district SSO for staff; guest links for parents. |
| Notifications | Set automatic reminders at 3, 7, and 14 days after assignment. |
| Retention Tag | Attach FERPA/HIPAA tags for records requiring restricted access. |
The platform should support role-based access, audit trails, exportable records, and applicable compliance controls.
Ensure the chosen platform can produce an audit trail and supports HIPAA or FERPA controls where student or health data require extra protections.
Structured prompts for presenting problem, baseline data, prior supports, and contextual factors to ensure consistent intake across students and staff.
Placeholders to attach samples, assessment scores, behavioral logs, or parent input so decisions are supported by documented artifacts.
Explicit description of the intervention, responsible staff, frequency, duration, and material resources required for implementation fidelity.
Measurable objectives with success criteria and decision rules for continuing, modifying, or escalating supports based on progress monitoring.
Calendar fields for probe frequency, review dates, and automated reminders to preserve the integrity of data collection.
Designated signers, signature dates, and an audit trail capturing timestamps and user attribution for compliance purposes.
Complete baseline and referral within 5–10 school days after concern submission.
Begin planned intervention within two weeks of the team's decision.
Conduct scheduled review after the agreed monitoring period (commonly 4–8 weeks).
Signed plan and monitoring data filed to the SIS within 7 days of team approval.
If criteria not met, escalate to special education referral per district timeline.
Document arrival and assign responsible reviewer within 48–72 hours.
Gather objective measures before intervention begins to establish a point of comparison.
Deliver the agreed strategy with fidelity and record delivery dates and times.
Review progress against criteria and decide on continuation, modification, or escalation.
| Criteria | Electronic Signature | Digital Signature |
|---|---|---|
| Definition | any electronic mark | pki-based cryptographic signature |
| Non-repudiation | depends on audit trail | strong via certificate |
| Typical Use | forms, approvals | high-assurance compliance, regulated records |
| Tech Required | minimal | certificate authority and pki |
| 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 by plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes | Yes | Yes | Yes | Varies |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | Varies | Varies |
The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers.
Tech Data uses the platform to improve internal and external customer service while increasing our speed to revenue.