Describe how your animal control office, clinic, or shelter handles bite reports. Makeform turns your instructions into a structured intake form that records when and where the bite happened, who was involved, how the animal can be identified, what was observed, and who needs the submission next.
Route new reports to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose the reporting situation closest to yours, edit the details, or send the prompt into the Makeform builder. Each structure is an example you can adapt to local procedures.
Prompt ready4 formats
Audience
Dispatchers and officers receiving public bite reports
Format
Detailed incident intake with conditional follow-up
Prompt size
544 chars
Brief qualitySends to builder
Example form structure
Detailed incident intake with conditional follow-up
Prompt exampleEditable in builder
Reporter and victim contact details
Short answerFirst ask
2
When and where did the bite occur?
Date & time
3
Describe what happened in sequence
Long answer
4
Animal identity, owner, and current location
Conditional fields
5
Upload scene, animal, or injury photos
File upload
Suggested routing tags
Suggested
New bite report
Animal located
Follow-up needed
Ask separately where the incident happened and where the animal is now. Those locations may differ, and responders often need both.
Step 1
Receive
capture the reporter, victim, time, and place
Step 2
Identify
record the animal, owner, and current location
Step 3
Document
separate accounts, observations, files, and witnesses
Step 4
Route
assign the case, status, next action, and due date
Why structured intake matters
A bite report needs more than one open text box.
A rushed phone note can omit the animal's location, mix accounts with observations, or leave nobody responsible for follow-up. A structured animal bite report form gathers each fact in the right place.
One record of people, place, and sequence
Required contact, date, time, address, and narrative fields reduce follow-up. Separate questions for the reporter, victim, owner, and witnesses keep their roles clear.
Animal details responders can use
Species, breed or type, color, markings, name, tag, microchip, owner, and last known location turn a vague description into a workable identification record. Conditional fields prevent irrelevant dog questions from appearing for every species.
A defined handoff after submission
Add status, assigned staff, next action, and due date so the report becomes a trackable task instead of an attachment sitting in an inbox. Notifications can alert the designated team without asking the reporter to repeat the story.
Adapted to the reporting point
One core incident record, different operational views.
The useful facts overlap, but public intake should not look like an officer's field update. Match the form to its submitter and review process.
Public and dispatch reports
Use plain-language prompts, label optional details, and ask how to reach the reporter. Put the animal's current or last known location near the start.
Clinic documentation
Keep patient reports separate from staff observations. Include the encounter date, affected area, care or referral recorded, animal availability, attachments, and report destination.
Shelter and rescue incidents
Link the report to the animal ID, kennel, handler activity, and shift. Ask what happened before and after, who was notified, and who owns follow-up.
Officer field updates
Start with a case number, then branch on whether the animal was located. A mobile-friendly update can add observed identifiers, owner contact attempts, document notes, photos, disposition, and a dated next action without reopening the entire intake.
Build the reporting workflow
From form prompt to a report your team can route.
Start with the decisions staff need to make. Makeform generates the structure; you review the wording, add instructions, and connect the report to the next responsible person.
Tell Makeform whether the form is public, staff-only, or an officer update. Name the people who review it and the facts they need first, such as the animal's location, an existing case number, or whether the victim is a minor with a guardian contact.
02
Add branches for the facts that change
Show owner and vaccination-document questions only when an owner is known, guardian fields only when relevant, and search notes when the animal is not located. Conditional logic keeps the first screen manageable without losing detailed follow-up fields.
03
Review labels, instructions, and access
Replace generic wording with the terms your team uses. Clearly label reported statements, staff observations, optional uploads, and internal-only fields. Add a reminder that the form is for documentation and place urgent contact instructions outside the normal submission flow when appropriate.
04
Test submission and routing
Submit one known-animal case and one unknown-animal case. Confirm required fields, notifications, attachment access, spreadsheet columns, ownership, and due dates all land where staff expect before sharing the form link.
Choose the right intake method
Why a generated report form beats an unstructured note.
A downloadable document can be a starting reference, but a tailored online form can collect, branch, attach, and route in one submission.
Approach
What it captures
Operational result
ApproachPhone message or email
What it capturesUsually a narrative plus whichever details the receiver remembers to ask.
Operational resultFast to start, but missing locations, identifiers, witnesses, or contact permission often require another call.
ApproachDownloaded PDF or document
What it capturesA fixed set of fields that may not match your submitter, species, or internal status process.
Operational resultConsistent on paper, but files still need naming, delivery, attachment handling, and manual assignment.
Approach
Generated online form
What it capturesRole-specific fields, conditional branches, uploads, acknowledgments, and routing details.
Operational resultA structured submission arrives ready for review, export, notification, and a documented next action.
Field guide
What an animal bite report form should include.
Build the form around six connected sections. Together they establish who reported the incident, what occurred, which animal was involved, what was observed, what supporting material exists, and what your team plans to do next.
People and roles
Identify the reporter, victim, owner, and witnesses.
Do not assume the person submitting is the person bitten. Ask each role separately and allow a submitter to indicate that they also fill another role. For a minor or another person whose report needs a representative, provide an appropriate guardian or representative contact section based on your process.
Reporter name, preferred contact method, phone, email, and relationship to the incident.
Victim name and contact, plus guardian or representative details when applicable.
Animal owner or keeper and independent witness names with reliable follow-up contacts.
Time, place, and narrative
Reconstruct the incident without leading the response.
Collect the date, approximate time, address, and a precise scene description before asking for a narrative. Use neutral wording such as 'describe what happened in order.' Separate preceding activity, the bite event, and immediate actions so reviewers can understand the sequence without the form assigning blame.
Incident date, time, address, property type, and specific location within the property.
Activity immediately before the bite and a factual, chronological account.
Where the victim, animal, owner, and any handler went immediately afterward.
Animal identification
Record enough detail to distinguish the animal.
An animal name alone is not enough, and the location during the bite may not be its current location. Ask for observable identifiers and ownership separately. Let 'unknown' be a valid response so submitters do not guess, then branch to last-known-location and direction-of-travel questions when the animal is loose or unidentified.
Species, breed or type if known, size, color, markings, sex if known, and animal name.
Collar, tag, license, shelter ID, or microchip details only when available.
Owner contact, home address, current animal location, containment status, and last known direction.
Injury and care record
Separate reported symptoms from observed facts.
Use a body-area selection plus a plain-language description field rather than asking submitters to diagnose an injury. If staff complete the form, distinguish what the victim reports from what staff can directly observe. Record care already sought or referrals made as history, not as advice generated by the form.
Affected body area, side of body, clothing or equipment involved, and victim's description.
Visible observations documented in neutral terms, with optional images when appropriate.
Care already received, facility or contact provided by the respondent, and relevant dates.
Evidence and source labeling
Keep every attachment connected to its source.
Record who supplied each photo, document, or statement and what it depicts. Do not imply that an upload proves a conclusion. Provide a follow-up path for people who cannot attach a file during intake.
Animal, scene, clothing, or injury images with a short caption and uploader identity.
Available tag, license, vaccination, or clinic documents, labeled as submitted material.
Witness account, contact permission, file date, and notes about material to be supplied later.
Review and follow-up
End with ownership, status, and the next action.
A complete intake still fails operationally if nobody knows who has it. Add internal fields or a companion staff form for case number, triage status, assigned person, contact attempts, animal-location result, follow-up date, and disposition. Keep internal notes out of a public confirmation when they are not intended for the submitter.
Case number, received timestamp, review status, priority chosen by staff, and assignee.
Contact attempts, visit results, animal located status, and new supporting material.
Next action, responsible person, due date, disposition, and final reviewer.
Related tools
Build the surrounding animal and incident workflow.
Pair bite intake with broader incident, lost-animal, surrender, adoption, welfare, or clinic appointment forms. Each linked generator is already available in the Makeform tools library.
Practical answers for animal control teams, clinics, shelters, and administrators designing a clearer intake and follow-up process.
What is an animal bite report form?
An animal bite report form is a structured record of an incident involving a person and an animal. It usually captures the people involved, date and location, a factual account, animal identifiers and ownership, the animal's current or last known location, injury observations, witnesses, attachments, and follow-up routing. The form supports documentation and workflow; your organization decides how each report is reviewed and handled.
What fields should an animal bite report form include?
Start with reporter and victim contacts, incident date and time, exact location, chronological narrative, affected body area, animal species and description, owner or keeper contact, current animal location, witness details, and optional uploads. For staff use, add case number, assigned person, contact attempts, status, next action, due date, and disposition. Mark information as unknown when a respondent cannot reliably provide it instead of forcing a guess.
Can the same form work for animal control, a clinic, and a shelter?
They can share core incident fields, but each audience benefits from a tailored version. Public intake emphasizes location and identification. A clinic separates reported details from staff observations. A shelter links the incident to an animal ID, kennel, handler activity, shift, and supervisor. Duplicate the core structure, then adjust access, internal fields, and routing.
How should the form handle an unknown or loose animal?
Make 'owner unknown' and 'animal not located' valid options. When selected, show questions for last known location, time last seen, direction of travel, observable description, collar or tag, behavior observed, and safe contact details for follow-up. Do not require microchip, vaccination, or owner fields when that information is unavailable. Route these submissions according to your team's own review procedure.
Can people upload photos and documents with the report?
Yes. Add file-upload fields for animal, scene, clothing, or injury images and for available identification or vaccination documents. Pair each upload with a caption, source, and date so reviewers know what it is and who supplied it. Make uploads optional when appropriate and provide a way to note that material will be sent later. An attachment should be treated as submitted information, not an automatic conclusion about the incident.
How do I keep a public report separate from internal follow-up notes?
Use a public intake form for reporter-facing questions and an internal follow-up form keyed to the same case number. The internal version can collect assignment, priority, contact attempts, visit findings, documents viewed, animal-location status, disposition, and next action. If your workflow uses one form, control which fields are visible to respondents and review the confirmation message so it does not expose staff-only notes.
Is the animal bite report form generator free?
Yes. Makeform is unlimited free for generating, editing, publishing, and collecting responses with your form. The paid tier removes the Makeform badge. You can begin from a sample prompt, change every field and instruction, test the conditional paths, and publish a link when the form matches your process.
What should I test before publishing the form?
Submit at least two scenarios: one with a known owner and located animal, and one with an unknown or loose animal. Check required fields, guardian and species branches, uploads, confirmation text, notification recipients, spreadsheet columns, case identifiers, and internal access. Ask an actual reviewer to confirm that the submission contains enough information to assign a next action without requesting the same details again.
Turn scattered incident details into one reviewable report.
Generate an animal bite report form built around your intake and follow-up process.
Unlimited freeConditional incident fieldsUploads and routing
