Describe your site and incident workflow. Makeform builds a construction accident report form for events, injuries, witnesses, evidence, notifications, and follow-up actions.
Route accident reports to email, Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a starting point, adapt the details, and send the prompt to Makeform. Each example shows a practical form structure.
Audience
Site supervisors documenting an injury
Format
Incident form with care and notification fields
Prompt size
257 chars
Example form structure
Incident form with care and notification fields
Project, location, date, and time
Who was injured and what task were they doing?
Immediate care or response provided
Witnesses and supporting photos
Corrective action owner and due date
Suggested routing tags
Immediate review
Witness follow-up
Corrective action open
Separate observed facts from conclusions, and let each witness provide an account in their own words.
Step 1
Respond
care for people and control the area
Step 2
Record
capture facts, witnesses, and evidence
Step 3
Review
identify conditions needing attention
Step 4
Correct
assign actions and document closure
Clearer site records
A guided form takes supervisors from immediate response through follow-up without relying on an unstructured email.
Date, location, activity, and narrative fields clarify the sequence without mixing observations with assumptions.
Keep every witness's contact details and account separate for follow-up.
Assign controls, due dates, status, and closure notes instead of burying recommendations.
Useful across the project
Adapt questions to the event while keeping project, people, evidence, and action fields consistent.
Document the affected person, reported injury, immediate response, care destination, and supervisor notification.
Capture asset IDs, operators, site conditions, damage photos, isolation status, and the next inspection or repair step.
Identify the general contractor, subcontractor, crew supervisors, and action owner for every company involved.
Record potential consequences and immediate controls even when an event causes no injury or damage.
Build the workflow
Generate the starting form, adjust it to the project, then connect each submission to the people responsible for review and correction.
Name the projects, trades, event types, and contacts the form should cover.
Show injury, equipment, witness, or action questions only when needed.
Notify the right contact and organize reports by site, company, type, and status.
Use owners, dates, evidence, and review notes for visible follow-up.
Choose a reporting method
Structured inputs make people, location, evidence, notification, and follow-up details easier to collect and route.
Field guide
Use these six sections, then adjust terminology, routing, and retention to your procedures.
Project and event
Identify the project, work zone, date, time, shift, conditions, and event type so reviewers can locate the scene.
People involved
Collect each person's employer, trade, supervisor, contact, work assignment, and relevant training or authorization status.
Factual account
Ask what happened before, during, and after the accident, including work methods, tools, materials, movement, and conditions.
Injury and response
Document the reported injury, first aid, emergency response, transportation, area control, and work stoppage without requesting a diagnosis.
Witnesses and evidence
Use separate witness entries and allow photos, sketches, permits, inspection records, and relevant files alongside the written account.
Review and correction
Track each contributing condition or corrective action with an owner, target date, status, evidence, and closure review.
Related tools
Build supporting forms for witness accounts, site observations, inspections, equipment checks, maintenance, and project reporting.
Create a general incident intake for events beyond construction sites.
Open toolCollect a separate, structured account and contact details from each witness.
Open toolRecord conditions and behaviors noticed during routine site work.
Open toolBuild repeatable checks for work areas, controls, and follow-up items.
Open toolCapture asset condition, defects, photos, and inspection decisions.
Open toolDocument daily progress, staffing, site conditions, and project updates.
Open toolFAQ
Practical answers for supervisors, safety leads, and project teams designing an accident reporting workflow.
It is a structured record of an accident or related site event. It captures the project and location, people involved, work activity, factual sequence, injury or damage, immediate response, witnesses, evidence, notifications, and corrective actions for internal review.
Include project, location, time, companies, people, task, narrative, conditions, injury or damage, response, witnesses, uploads, notifications, and actions. Use conditional logic for event-specific questions.
Use a separate entry for each witness: name, employer, contact, location, direct observations, and an account in their own words. Do not combine every account into one response.
Yes. Add file-upload fields for scene and equipment photos, sketches, relevant permits, checklists, and other records. Label each upload request clearly, and keep a written narrative so the report remains understandable without opening every attachment.
Yes. Conditional paths can show injury and response fields after an injury selection, asset and isolation fields for equipment damage, or potential-consequence questions for a near miss. The common site and timeline fields can stay consistent across every path.
Add one repeatable action record for each change: description, responsible person and company, priority, target date, status, completion evidence, and reviewer notes. This separates immediate controls from longer-term changes and makes open work visible.
Yes. Makeform offers unlimited free forms and responses, so you can generate, edit, publish, and use the form freely. The paid tier only removes the Makeform badge.
No. It gives you an editable collection workflow, not a determination that every internal or external reporting duty has been met. Match the fields, routing, timing, access, and retention process to your organization's procedures and the requirements that apply to the project.
Turn scattered accident details into a clear workflow.
