Internal Affairs Complaint Intake Form

Use it when your agency needs a consistent way to receive complaints about officer conduct from the public or from inside the organization. It is designed for intake staff, supervisors, professional standards units, and investigators who need the same fields every time. If your process starts with a phone call, email, or in-person report, this template helps convert that information into a structured record. It also supports anonymous submission when your policy allows it.

It can support both, because the submission notice and complainant information sections let you capture either a named reporter or an anonymous submission. That makes it useful for public complaints, employee reports, and supervisor-initiated intake. If your agency separates those workflows, you can use conditional logic to show or hide contact fields based on submission type. The key is to keep the classification and routing fields consistent across both paths.

It is typically used every time a complaint is received, so the intake process stays standardized from the first report through assignment. Some agencies use it at the front desk, some in a web portal, and some as an internal case-opening form. If you receive complaints by multiple channels, this template becomes the single intake record that feeds the investigation workflow. That reduces missing details and makes later review easier.

Only require fields that are necessary to identify the incident, classify the allegation, and route the case. Complaint summary, incident date or approximate date, allegation category, and submission type are usually core fields, while phone number, witnesses, and attachments can be optional unless your policy says otherwise. Avoid over-collecting PII, especially if the complainant wants anonymity or only wants to provide a brief report. Progressive disclosure works well here because it keeps the form shorter for low-detail submissions.

The template includes an anonymous_submission field so the complainant can submit without providing identity or contact details when permitted. If anonymous reporting is allowed, the form should clearly explain what happens after submission and whether follow-up is possible. You should also make sure the contact fields are hidden or marked optional when anonymous submission is selected. That avoids confusing the user and helps protect privacy.

A common mistake is asking for too many details up front, which can discourage reporting and create unnecessary PII collection. Another is using free-text fields where structured fields would improve routing, such as a multi-select for allegation categories or a date picker for incident date. Agencies also sometimes skip the assignment fields, which makes it harder to prove who received the case and when. Finally, leaving out a submission notice can create confusion about confidentiality, follow-up, and next steps.

Yes. The investigation routing section is designed to map cleanly into case management, ticketing, or records workflows through field mapping or automation. You can route intake_classification to a queue, assign an investigator based on allegation type, and store assignment_date for audit trail purposes. If your system supports attachments, supporting_documents and video_audio_evidence can be passed along as linked files. That makes the intake form a practical front end for a larger investigation process.

Start by aligning the fields with your complaint policy, then test the form with intake staff and investigators before publishing it. Make sure the submission notice explains anonymity, consent, and what happens after submission in plain language. If the form is public-facing, check accessibility and keyboard navigation so it works under WCAG 2.1 AA expectations. For internal rollout, train staff on when to use the form, how to classify allegations, and how to avoid adding extra narrative in case_notes that is not needed.