Who this is for
Right-sized support for real operational needs
Procurement officers and special education leaders preparing an RFP or service agreement.
Organizations rarely need another generic policy document. They need a clear professional scope, experienced judgment and practical steps that can be followed by the people doing the work.
Signs it may be time for outside support
- An RFP does not specify deliverables
- Vendors are difficult to compare on a consistent basis
- Schools need to verify qualifications across jurisdictions
These signals are starting points for a conversation—not a diagnosis or proof that a specific service is required. The useful question is which responsibilities and constraints need to change first.
What a well-scoped engagement can address
- Define the type of assessment and direct support requested
- State deliverables, reporting, review and safety protocols
- Confirm licensure, education requirements, privacy and contract terms
How the work should be approached
Procurement documents should make service expectations measurable without promising outcomes a contractor cannot control. Consider a written rubric for clinical fit, experience and implementation support.
Before an engagement begins, the parties should confirm deliverables, timelines, contact points, professional qualifications, confidentiality requirements and how progress will be reviewed. For direct clinical or school-based services, any required state licenses and contract approvals must be in place first.
Common questions
What should an RFP include?
At minimum: populations served, campuses, desired services, estimated hours, deliverables, qualification requirements and records-handling expectations.
Should districts request proof of state licensure?
Yes when applicable. Confirm professional authorizations and any district-specific contracting requirements before work begins.
Related services and resources
For related responsibilities and implementation decisions, explore the neighboring topics below.