Title IX Sex Discrimination Complaint Intake and Formal Complaint Form

Use this form when a student, parent/guardian, staff member, or other reporting party needs to report sex discrimination in a K-12 setting and request supportive measures. It is designed to capture both an intake report and a formal complaint attestation in one workflow. If your district separates intake from formal filing, you can split the template into two steps without changing the core fields. The form is especially useful when you need a consistent record for the grievance process and follow-up.

This template is built for sex discrimination concerns under Title IX, including harassment, unequal treatment, retaliation, and related conduct in a school environment. The incident section supports a narrative summary, date, location, and whether the issue appears ongoing or has been reported before. If the concern is unrelated to sex discrimination, use a different incident intake form. Keeping the scope narrow helps reduce unnecessary PII collection and improves routing.

This template includes contact and identity fields because it is intended for intake and formal complaint processing, not anonymous-only reporting. If your district also offers anonymous submission, add a separate anonymous intake path and keep this form for cases where follow-up is needed. For any optional contact fields, make the choice explicit and explain how the information will be used. That helps with consent, confidentiality, and data minimization.

Typically, a Title IX coordinator or designated administrator should review submissions, assess immediate safety concerns, and route the matter into the grievance and supportive-measures workflow. If your district uses multiple reviewers, define assignment rules so the form does not create delays or duplicate handling. The template works best when the reviewer can see the incident summary, respondent information, and requested supports in one place. An audit trail is important for documenting who received the report and when.

Use it each time a new Title IX sex discrimination concern is reported, even if the same people or school are involved. If the matter continues over time, keep the original submission as the baseline record and add follow-up notes or supplemental reports rather than overwriting the first entry. That preserves the timeline and makes it easier to identify patterns. For recurring concerns, the ongoing-pattern field helps distinguish a single event from repeated conduct.

Common mistakes include writing a vague incident summary, leaving the location or date blank, and collecting more personal data than the district actually needs. Another frequent issue is skipping the supportive-measures section, which can delay urgent accommodations or safety steps. Users also sometimes list every field as required, even when some details are unknown or not applicable. The best approach is to mark optional fields clearly and use conditional logic for follow-up questions.

Customize the terminology to match your board policy, grievance procedure, and local reporting roles, but keep the core sections intact. You can add school-specific contact details, routing rules, or a separate field for preferred language and accessibility needs. If your district serves minors, include age-appropriate wording and clear guidance for parents or guardians where appropriate. Avoid adding fields that are not needed for the investigation or supportive-measures process.

Yes. The form maps well to case management, HR-style intake, or student conduct workflows because it already separates reporting party details, incident facts, evidence, and attestation. You can route submissions to a secure inbox, create a case record, or trigger notifications to the Title IX coordinator. If you integrate it, keep access limited to authorized staff and preserve the submission timestamp and audit trail. That makes later review and documentation easier.

The submitter should receive a confirmation that the report was received and that the district will review it for next steps, including supportive measures and any required grievance actions. The reviewer should assess urgency, contact the affected party if appropriate, and document any immediate safety or medical needs. If the form is used for formal complaints, the attestation and signature should be retained with the case file. A clear post-submit message reduces confusion and sets expectations.