Scope of Duties
Define specific SRO responsibilities (safety presence, mentoring, law enforcement actions), list activities excluded from SRO duties, and clarify when school administrators must retain disciplinary control.
A well-drafted SRO MOU reduces ambiguity about responsibilities, protects student privacy, allocates liability, and documents training and de-escalation expectations. It helps school leaders and law enforcement coordinate while preserving constitutional and statutory safeguards.
Several local stakeholders are usually involved in creating and approving an SRO MOU.
Final signatories generally include an authorized official from the school district and an authorized representative of the law enforcement agency.
The superintendent or their authorized delegate typically negotiates terms with law enforcement, ensures board review, and signs on behalf of the district. They coordinate policy alignment with district counsel and ensure the MOU conforms with FERPA and district policies.
The agency head or authorized command staff negotiates operational details, assigns the SRO, certifies training, and signs for the agency. They are accountable for officer conduct and ensuring the MOU aligns with departmental protocols.
Define specific SRO responsibilities (safety presence, mentoring, law enforcement actions), list activities excluded from SRO duties, and clarify when school administrators must retain disciplinary control.
Specify chain of command, supervisory responsibility, incident reporting procedures to the district, and regular status reports or meetings between agency and district leadership.
Address student records access, data sharing limits, FERPA compliance, and handling of sensitive information including law-enforcement records and juvenile information.
Require SRO-specific training (student interaction, de-escalation, bias awareness), periodic refresher training, and procedures for addressing misconduct or performance concerns.
Allocate responsibility for claims, specify required insurance coverages, indemnification terms, and procedures for handling potential litigation arising from SRO actions.
State the effective date, term length, automatic renewal conditions if any, notice periods for termination, and transition steps for reassignment or program suspension.
| Field | Configuration |
|---|---|
| Signer Order | Role-based, district then agency |
| Authentication | Email plus optional SMS code |
| Notarization | Enable RON where permitted |
| Retention | Auto-archive signed copy |
Choose a platform that supports audit trails, secure storage, and required authentications.
Ensure the selected system meets ESIGN/UETA requirements and any applicable agency or district IT policies.
2–6 weeks depending on negotiation complexity
Allow 1–3 weeks for counsel review
Submit 2–4 weeks before meeting
Signing usually within 1–7 days after approval
Standard 30–90 days before term end
Negotiation and initial drafting between parties
District and agency counsel review and redline
School board and agency authorization
Authorized signatures recorded and copies stored
Export signed agreements as PDF/A for long-term archival and legal reproducibility while preserving the embedded audit trail metadata.
Keep an editable DOCX master copy for internal revision history, but do not treat it as the signed legal record.
Use signed, tamper-evident PDF with embedded timestamp and certificate for evidentiary support if disputes arise.
Export a machine-readable audit log (CSV) capturing signer emails, IPs, timestamps, and action events for compliance review.
A rural district and county sheriff negotiated duty hours and incident reporting
An urban district required de-escalation and youth-interaction certifications
| 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 | Varies | Varies | Varies | Varies |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| Envelope Cap | No cap | 100 envelopes/user/year | Varies | Varies | Varies |