Describe your workplace and reporting workflow. Makeform creates a near miss incident report form for documenting what almost happened, the hazard involved, and who should follow up.
Route reports to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it to your process, or send it to the Makeform builder. The fields are an example structure.
Audience
Warehouse associates and shift leads
Format
Mobile report with location and photo evidence
Prompt size
283 chars
Example form structure
Mobile report with location and photo evidence
When and where did the near miss occur?
What almost happened?
Which hazard types were involved?
Photos of the area or equipment
Immediate action taken
Suggested routing tags
New report
Review required
Action closed
Ask what prevented harm as well as what created the hazard. Both details help reviewers choose corrective action.
Step 1
Report
capture the close call while details are fresh
Step 2
Triage
review exposure and apply immediate controls
Step 3
Investigate
identify contributing factors and actions
Step 4
Close
verify completion and share the learning
Why near misses matter
A structured report preserves the event, exposure, existing barriers, evidence, and next action in one submission.
Mobile prompts gather the time, location, task, sequence, and evidence while details are fresh.
Reporter fields document observations; reviewer fields hold severity, contributing factors, ownership, and closure.
Category, location, status, and action fields create a clear review queue.
Adaptable reporting
Keep a consistent core record, then reveal questions based on location, hazard, and equipment.
Aisle, dock, shift, vehicle, load, exposure, and photo fields.
Project, crew, task, conditions, plant, energy, and control questions.
Line, machine state, guarding, energy, process, and contributing factors.
Paths for facility, ergonomic, fleet, and contractor observations.
Reporting workflow
Start with observable facts, then add triage, assignment, and action-tracking fields.
Specify reporters, locations, hazards, identity options, and reviewers.
Add your sites, equipment IDs, hazard taxonomy, severity scale, and teams.
Notify the right reviewer and reveal conditional controls, equipment, or witness fields.
Record the owner, date, evidence, verification, and closure status.
Reporting methods compared
The best channel is easy to use and structured for sorting, investigation, and closure.
Field guide
These six sections collect observable facts and give reviewers a place to manage the response.
Reporter and timing
Separate event time from submission time. Decide whether reporter identity is required, optional, or withheld, and explain why contact details may help.
Location and activity
Use choices for site, building, floor, line, aisle, project, or zone, then ask what task was underway.
Event narrative
Ask what happened before, during, and after the close call without pushing the reporter to assign fault or diagnose causes.
Hazards and barriers
Hazard categories support filtering. A separate barrier question records whether distance, guarding, a warning, equipment, or chance prevented harm.
Evidence and immediate response
Uploads preserve equipment position, damage, surface conditions, diagrams, or documents. Ask whether work stopped and what temporary control was applied.
Investigation and closure
Reviewer fields can document contributing factors, actions, owners, dates, completion evidence, verification, and closure separately from the employee report.
Related tools
Build adjacent forms for hazard intake, observations, inspections, equipment checks, and repairs.
Document work practices, controls, and coaching observations in the field.
Open toolSchedule repeatable checks for workplace conditions, controls, and assigned findings.
Open toolRecord equipment condition, defects, service status, and inspection evidence.
Open toolFAQ
Practical answers for safety managers designing reporting and follow-up.
It records an unplanned event that caused no harm but had the potential to do so. The form captures the scene, sequence, hazard, exposure, barriers, evidence, and immediate response for review.
Include time, location, task, event description, hazard, exposure, potential consequence, barrier, immediate action, witnesses, and attachments. Add reviewer fields for triage, contributing factors, action, owner, date, verification, and closure.
A near miss had harmful potential without the outcome. Incident may be a broader label covering near misses, injuries, damage, and disruptions. Define each label and branch reporters to appropriate questions.
That depends on your policy. Optional names may reduce hesitation; contact details support clarification. Explain what is collected, who reviews it, and how reporters can offer follow-up contact.
Yes. Add uploads for photos, sketches, videos, or documents. Remind reporters not to disturb a scene or take risks to collect evidence. Pair attachments with location and equipment details.
Yes. Use site, department, and hazard choices to route each report. Include a fallback reviewer for unmatched categories so unusual events still receive an owner.
Track each action with a description, owner, target date, status, completion evidence, and verification. Preserve the original report ID when one event creates several actions.
Yes. Makeform provides unlimited free forms and responses for generating, editing, publishing, and collecting reports. The paid tier removes the Makeform badge.
Make close calls easier to act on.
