Title VI Complaint Procedure and Investigation Log
Track Title VI discrimination complaints from intake through investigation, timeliness review, findings, and closure in one log. Use it to document the 180-day filing window, assigned investigator, corrective action, and notice to the complainant.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Public Sector · Education · Transportation · Housing · Healthcare
Overview
This Title VI Complaint Procedure and Investigation Log template is built for organizations that need to intake, review, investigate, and close discrimination complaints tied to a federally funded program or service. It combines the submission notice, complaint intake, 180-day filing window review, investigation tracking, and findings and resolution into one case record so staff can document what was reported, who handled it, what evidence was reviewed, and how the matter was resolved.
Use it when you need a repeatable process for civil rights complaints, especially when multiple staff members may touch the case over time. The structure supports accessibility and data minimization by separating identity and contact fields from the core complaint details, and it gives you space to record anonymous submission requests, preferred language, and follow-up notes. It is also useful when you need an audit trail for internal review, legal review, or program oversight.
Do not use this as a generic incident form for unrelated workplace issues, and do not overload it with unnecessary PII. If the complaint does not involve a Title VI-covered program or service, route it to the correct policy or intake form instead. If your organization cannot assess timeliness, assign investigators, and document corrective action, this template should be paired with a clearer workflow before rollout.
Standards & compliance context
- The intake fields should follow GDPR-style data minimization by collecting only the PII needed to evaluate and route the complaint.
- The form should support WCAG 2.1 AA accessibility with clear labels, logical field order, and accessible error validation for public-facing submission.
- If the complaint process is used in an employment or accommodation context, keep ADA reasonable-accommodation prompts separate from the Title VI intake unless they are truly needed.
- For any health-related program complaint, apply the minimum-necessary principle and avoid collecting diagnosis details unless they are required to investigate the issue.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Submission Notice
This section captures how the complaint arrived, whether the submitter wants anonymity, and whether you have consent to process PII.
- Submission type
- Submitter identity
-
Consent to process personal information
By submitting this form, you consent to the organization using the personal information provided only for complaint intake, review, investigation, resolution, recordkeeping, and required reporting. Do not include SSNs, full financial account numbers, or other unnecessary PII.
-
Request anonymous submission where permitted
Select this if you want to limit identifying information. Anonymous submissions may reduce the organization’s ability to investigate or follow up.
Complaint Intake
This section records the core facts needed to understand the allegation and route it to the right program owner or investigator.
-
Complainant name
Optional if anonymous submission is requested or not permitted to collect. Provide only if needed for follow-up.
-
Preferred contact email
Use only if you want updates by email.
-
Preferred contact phone
Use only if you want updates by phone.
-
Preferred language
Optional. Helps support accessible communication and language assistance.
-
Date of alleged discriminatory incident
Enter the date the alleged discrimination occurred.
-
Date complaint was received
This is the date the organization received the complaint.
-
Basis of complaint
Select all that apply.
-
Program, service, or activity involved
Identify the federally funded program, service, or activity involved.
-
Location of incident
Provide the location if known.
-
Complaint summary
Describe what happened, who was involved, and what outcome is being requested. Avoid unnecessary personal details.
-
Supporting documents
Upload any relevant documents, screenshots, or correspondence.
180-Day Filing Window Review
This section documents whether the complaint was filed on time and why the intake decision was accepted or declined.
-
Days since alleged incident
Calculated from the alleged incident date and the date received.
-
Filed within 180 days
Title VI complaints are generally expected to be filed within 180 days of the alleged discriminatory act.
-
Timeliness rationale
Document the reason for acceptance, dismissal, or exception review when the complaint is outside the 180-day window.
- Intake decision
Investigation Tracking
This section keeps the case moving by logging assignment, status updates, interviews, and evidence review.
-
Case number
Automatically assigned complaint identifier.
-
Assigned investigator
Name or role of the assigned investigator.
- Assignment date
- Investigation status
-
Status update notes
Record progress updates, outreach attempts, and any barriers to completion.
-
Interviews conducted
Enter the number of interviews completed.
- Evidence reviewed
Findings and Resolution
This section closes the loop by recording the finding, corrective action, notification, and final closure notes.
- Finding
- Corrective action required
- Corrective action description
- Resolution date
- Complainant notified
-
Closure notes
Summarize final disposition, notifications, and any follow-up actions.
How to use this template
- 1. Configure the submission notice fields so complainants can identify themselves, request anonymity, and consent to processing any PII before the case is opened.
- 2. Complete the complaint intake section with the incident date, date received, complaint basis, program or service involved, and any preferred language or contact details needed for follow-up.
- 3. Review the 180-day filing window by calculating days since incident, recording whether the complaint was filed within 180 days, and writing the timeliness rationale and intake decision.
- 4. Assign a case number and investigator, then update investigation status, interviews conducted, evidence reviewed, and status notes as the case progresses.
- 5. Record the finding, any corrective action required, the resolution date, complainant notification, and closure notes so the file shows what happened after the investigation ended.
Best practices
- Mark required fields clearly and keep optional fields optional so staff do not collect more PII than the case needs.
- Use conditional logic to hide investigator-only fields until the complaint is accepted for review.
- Capture the incident date with a date picker and the days-since-incident field as a calculated value to avoid manual errors.
- Include a plain-language note that explains what happens after submission, including who reviews the complaint and when follow-up may occur.
- Offer an anonymous submission path when your process allows it, and explain how anonymity may affect the ability to investigate.
- Record preferred language early so outreach, notices, and interviews can be handled with appropriate accessibility support.
- Document every status change in the investigation log so the case file has a usable audit trail.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What is this template used for?
This template records a Title VI discrimination complaint from submission notice through final resolution. It captures the complainant’s intake details, the 180-day filing window review, investigation status, evidence reviewed, and closure notes. Use it to keep a clear audit trail for each case.
Who should use and maintain this log?
It is typically maintained by a civil rights coordinator, compliance officer, HR or intake staff, or another designated investigator. The person running it should be able to assess timeliness, assign a case number, and document status updates consistently. If your organization has a formal grievance process, this log should sit inside that workflow.
Does every complaint have to be filed within 180 days?
The template includes a dedicated 180-day filing window review because timeliness is a key intake decision point for Title VI complaints. The log helps you document the number of days since the incident and the rationale for accepting or declining the complaint. If your policy allows exceptions or alternate review paths, capture that in the timeliness rationale.
Can someone submit anonymously?
Yes, the submission notice includes an anonymous submission requested field so you can record that choice up front. If anonymity limits follow-up, document that in the intake and investigation notes so the case file reflects any constraints on contacting the complainant. Be clear about what information is still needed to evaluate the complaint.
What fields should be required versus optional?
Keep required fields limited to what you need to open and route the case, such as incident date, date received, complaint basis, and program or service involved. Contact details, preferred language, and identity fields should be optional when possible to support data minimization and accessibility. Use conditional logic so you only ask for follow-up details when they are relevant.
How does this differ from an informal complaint form?
An informal form usually captures only the initial report, while this template tracks the full case lifecycle. It adds timeliness review, investigator assignment, interviews, evidence review, findings, corrective action, and closure. That makes it better for organizations that need a documented process rather than a one-time intake record.
What should be integrated with this log?
Common integrations include case management, email notifications, document storage, and an audit trail for status changes. If your team uses a shared inbox or ticketing system, map the case number and assignment date so updates stay synchronized. Keep PII access limited to staff who need it for the investigation.
What are the most common rollout mistakes?
A common mistake is collecting too much PII at intake instead of using progressive disclosure and only asking for what is needed. Another is leaving the 180-day review undocumented, which makes intake decisions hard to defend later. Teams also forget to include a clear note about what happens after submission, which can confuse complainants and staff.
Related templates
Go deeper on the topic
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Job hazard analysis (JHA) — also called job safety analysis (JSA) — is the structured exercise of breaking a work task into sequential steps, identifying the...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
AI governance is the framework a company uses to decide what AI tools are allowed to do, who's accountable for their outputs, what data they're allowed to...
-
See how MangoApps Forms helps teams collect, track, and analyze employee data in real time — with mobile access, file uploads, and enterprise-grade security.
-
MangoApps Shifts & Schedules unifies frontline scheduling, time, and leave management in one native platform for faster, simpler operations.
-
Measure employee engagement with eNPS to track loyalty, uncover morale issues, and turn employee feedback into action.
-
Align remote and distributed teams with practical tools to improve communication, boost alignment, and reduce costly productivity gaps.
Ready to use this template?
Get started with MangoApps and use Title VI Complaint Procedure and Investigation Log with your team — pricing built for small business.
