Build a Workplace Incident Report Form in monday.com
Published on November 21, 2026
Someone slips on a wet floor, a visitor is turned away at the door, a laptop goes missing. The person who saw it needs somewhere to report it that day, while the details are fresh. If that place is an email thread, the facts end up scattered and nobody owns the follow-up.
An incident report form gives every report the same fields and puts each one on a board row with an owner. This post covers the form, the access settings worth turning on, and how to freeze a report once it has been reviewed. It is about workplace safety, security, and HR incidents. For software bugs, see the bug report form guide.
Quick answer
- Build an insert form with incident date, type, location, people involved, a description, and a photo upload. Each submission becomes one item on your incident board.
- Add an optional Signature field for the reporter. It saves as a PNG image, not a legally verified signature.
- Protect the link with a password or country restrictions if reports contain sensitive detail.
- Lock the form after review so closed reports stay as filed.
- Build a visitor check-in form →
- Install FormFlow to build the form on your own board.
What Goes on the Form
Collect what an investigator will ask for first. Every field maps to a column on the incident board. The field types reference lists what is available.
| Field | Type | Maps to | Why |
|---|---|---|---|
| Incident date | Date | Date column | When it happened, separate from when it was filed |
| Incident time | Hour | Text or Hour | Narrows the timeline |
| Incident type | Selection | Status column | Safety, security, HR, property, other |
| Site or area | Dropdown | Dropdown column | Lets you filter and assign by location |
| People involved | Text | Long Text column | Names as the reporter knows them |
| What happened | Textarea | Long Text column | Plain account, in the reporter’s words |
| Photos | File | Files column | Evidence of the scene |
| Reporter email | Email column | For follow-up questions | |
| Signature | Signature | Files column | Optional acknowledgment from the reporter |
Keep “People involved” as text. A People column lists monday.com users, and the people in an incident are often visitors or contractors. If you want to assign an owner, see assigning a person through a form.
For photos, FormFlow accepts up to 100 MB per file and 30 files per submission, as covered in the file uploads guide.
About the Signature Field
A signature is useful when the report is also a statement: the reporter confirms the account is accurate. FormFlow’s Signature field captures a drawn signature and saves it as a PNG to a file column. That is a drawn image with no identity verification or audit trail. If a report may be used in a legal or regulatory process, check your jurisdiction’s requirements. Our post on electronic signatures on monday.com forms covers where a drawn image stops being enough.
Control Who Can File and Where From
Incident reports can name people and describe injuries. Treat the link as sensitive. The form settings include a form password and an allowed-countries list. Use a password when reports come only from staff, and share it through your internal channels. Use country restrictions when your sites are in known regions.
If the form is open to the public, add CAPTCHA to cut down on junk. Our spam prevention guide compares the options.
Route Reports After They Arrive
Do the routing on the board, with monday.com automations:
- When Incident type changes to “Safety”, notify the safety lead.
- When Site changes, assign the report to the site manager.
- When Status changes to “Under review”, start the review checklist.
Native incident tooling exists on the IT side: monday.com’s Incident Management in monday dev creates a board with an incident form and dashboard for engineering incidents. It is aimed at service outages, not workplace safety or HR reports, so a general intake form fills a different need.
Lock the Report After Review
Once an investigator closes a report, the filed account should not change. FormFlow’s read-only mode with rules makes the form view-only under conditions you set, for example once Status equals “Closed”. The lock-after-approval guide walks through it. If you need the reporter to add details during review, use an update form with the original account set read-only and a separate “Additional details” field.
When a Simpler Setup Is Enough
If you get a handful of reports a year and one person reads them all, a single insert form with a description and photo field is enough. Add routing, signature, and locking when reports start to need owners and an audit-style record. Our operations templates include a shorter incident pattern if you want a starting point.
Frequently Asked Questions
Can people report an incident without a monday.com account?
Insert forms are built for public submissions, so reporters do not need an account. You can still add a password or country restrictions in form settings if the link should not be open.
Can reporters attach photos?
Yes. The File field maps to a Files column. FormFlow accepts up to 100 MB per file and 30 files per submission.
Is the Signature field a legal signature?
No. It saves a drawn image as a PNG to a file column, with no verified identity or audit trail. Check your jurisdiction’s requirements if reports may be used legally.
How do I stop a report from being edited after review?
Use FormFlow’s read-only form mode with rules, for example locking the form once Status equals “Closed”. The report stays as filed on the board.
Next Steps
- Form settings: password and country restrictions →
- Lock a form after approval →
- Operations form templates →
- Install FormFlow and build your first incident report form.
Last reviewed: 2026-10-29. monday dev’s Incident Management feature described from monday.com’s support article . Features may change.