Describe your program and reporting process. Makeform builds a special incident report form for event facts, immediate responses, notifications, evidence, and assigned follow-up.
Route reports to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose an editable example or send it to the Makeform builder.
Audience
Direct support staff reporting an unusual client event
Format
Incident form with immediate response and manager review
Prompt size
292 chars
Example form structure
Incident form with immediate response and manager review
Reporter, shift, and client identifier
Incident date, time, and location
What happened in chronological order?
Immediate response and notifications
Attachments and follow-up owner
Suggested routing tags
Needs review
Follow-up assigned
Closed
Separate observed facts from staff interpretation, and ask for exact times for the incident, response, and notifications.
Step 1
Observe
record facts, people, place, and exact time
Step 2
Respond
capture immediate actions and notifications
Step 3
Review
route the report to the right administrator
Step 4
Follow up
assign actions, due dates, status, and closure
Clear reporting from the start
Guide staff through fresh details and give administrators a consistent record to review.
Required time, place, people, and chronological narrative fields reduce vague reports without prompting conclusions.
Show witness, transport, impact, property, or notification questions only when relevant.
Track each action, owner, due date, status, and closure note.
Adapted to your setting
Replace example categories, roles, routes, and review fields with your process.
Record shift, unit, client identifier, witnesses, response, handoff, and review.
Capture site, activity, transport, staff response, and program follow-up.
Capture preceding conditions, observed events, staff actions, notifications, and follow-up.
Route by facility and track review, assigned actions, and closure.
Build the reporting workflow
Describe the fields and routing, review the structure, and publish one reporting path.
List settings, roles, categories, required facts, and reviewers.
Use your terminology and reveal extra questions only when relevant.
Send reports to the selected manager or administrator.
Submit scenarios and verify required fields, routes, owners, dates, status, and closure.
Form vs document vs email
An online form makes core facts consistent and keeps next actions with the report.
Field guide
Start with these six sections, then align wording, access, retention, and review with your policies.
Reporter and people involved
Capture the reporter, client identifier, staff, witnesses, and other involved people. Prefer internal identifiers when names are unnecessary.
Incident basics
Structured time, facility, activity, and category fields support sorting. Record discovery time separately when needed.
Factual narrative
Ask for observable events in order. Keep interpretations and review conclusions separate from the original account.
Immediate response
Capture immediate actions, requested assistance, and the client's observed status, with times for reconstructing the response.
Notifications and evidence
Record who was contacted, by whom, when, and how. Allow relevant files under your information-handling rules.
Review and follow-up
A restricted section can capture review, clarification, ownership, due date, status, and closure without rewriting staff's account.
Related tools
Connect incident intake with witness statements, safety observations, complaints, staff events, and closure reviews using related Makeform tools.
Create a general incident record for events outside a care-program-specific workflow.
Open toolCollect a separate first-person statement from a witness or involved person.
Open toolDocument workplace events that primarily involve an employee rather than a client.
Open toolRun structured environment checks and record issues that need correction.
Open toolOffer a separate channel for concerns when the reporter should not be identified.
Open toolCapture review outcomes, completed actions, and closure details for security events.
Open toolFAQ
Practical answers for administrators building a consistent staff reporting and follow-up process.
Staff use it to document an unusual client or program event: people, place, time, observations, response, notifications, files, and follow-up. Your organization defines which events use the workflow.
Include reporter and client identifiers, event and discovery times, location, category, people, witnesses, factual chronology, immediate actions, impact, timed notifications, and files. Add restricted review, owner, due date, status, and closure fields.
Ask for observable facts in order: what happened before, during, and after; actions or statements; who was present; and staff's response. Keep guesses separate from the original account.
Yes. Show transport fields for vehicle events, witness details when witnesses are selected, or property questions when damage is reported.
Yes. Route by the selected facility or program. Test every route before rollout and provide a fallback for unmatched cases.
Add action, owner, priority, due date, status, completion, and closure fields separate from the staff narrative. Send assignments to your existing tracker through Google Sheets or Zapier.
Yes. Makeform offers unlimited free forms and responses, so you can generate, edit, publish, and use the form without a response cap. The paid tier removes the Makeform badge.
Collect only needed information, prefer internal identifiers, limit access, and set retention practices. Have your privacy and reporting owner review fields, routes, integrations, and access settings.
Make every incident report easier to review and act on.
