Describe your incident process. Makeform turns it into an IT incident report form that captures severity, affected systems, impact, timing, evidence, and contact details for triage.
Send incident reports to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adapt it, or send it to the Makeform builder. The structure is an example, not a live AI result.
Audience
Employees reporting technology failures
Format
Guided severity and system intake
Prompt size
219 chars
Example form structure
Guided severity and system intake
Reporter, department, and contact
When did the incident begin?
Severity and users affected
Systems, devices, or services affected
Screenshots, logs, or supporting files
Suggested routing tags
Critical impact
Application issue
Device or network
Define severity beside the selector so each level names its expected impact.
Step 1
Observe
employee records what failed and when
Step 2
Classify
severity, system, and user impact are structured
Step 3
Route
the right IT queue receives the report
Step 4
Investigate
evidence and contact details support follow-up
Better incident intake
Structured intake captures scope, impact, timing, and evidence while details are fresh.
Label severity by impact, from one user with a workaround to a critical service unavailable across teams.
Use consistent choices for applications, networks, devices, accounts, and locations.
Collect exact errors, screenshots, logs, and troubleshooting in separate fields.
Built around the incident
Replace example systems, owners, severity language, and escalation instructions with your own.
Capture environment, outage pattern, business process blocked, affected users, start time, and recent changes.
Collect version, browser, reproducible steps, expected versus actual behavior, error text, and screen recordings.
Show device, asset, network, and location questions only when the reporter selects that incident family.
Use a focused path with safe contact details and no password collection.
Build the intake workflow
Describe systems and escalation rules, refine the questions, then publish one reporting route.
Name the incident types, systems, locations, and impact levels.
Require core details, then reveal questions relevant to the selected incident.
Send submissions to the IT inbox or connected channel for routing.
Test low- and high-impact examples and remove questions that do not aid triage.
Form vs email vs chat
Email and chat are convenient, but the reporter decides which facts to include. An IT incident report form asks the same triage questions every time.
Field guide
Use fields that establish urgency, ownership, reproducibility, and a working contact route.
Reporter
Collect identity, location, and a contact method that still works during the incident.
Severity & impact
Define severity by service availability, affected users, blocked work, and workaround availability.
System context
Offer structured system choices, then ask only relevant environment, device, network, or asset questions.
Description & timeline
Ask when it began, what came before it, and what happened instead of the expected result.
Evidence & actions
Accept relevant evidence and attempted steps, while telling employees to omit passwords and secrets.
Routing & follow-up
Use category, system, location, and severity for routing, with separate urgent instructions when needed.
Related tools
Separate incidents from routine support, change requests, access needs, software defects, and closure documentation while keeping each intake focused.
Collect everyday technical questions and assistance requests that are not operational incidents.
Open toolCapture reproducible steps, environment, expected behavior, and evidence for software defects.
Open toolRoute planned IT services and standard requests separately from unexpected failures.
Open toolDocument resolution details, follow-up actions, and ownership after a security investigation.
Open toolGather business need, users, integrations, and approval context for planned software requests.
Open toolCollect application access needs, role, manager context, and requested start or end dates.
Open toolFAQ
Practical answers for IT teams replacing incomplete incident emails and chat messages.
It gives employees a structured way to report an unexpected technology failure or suspected event. It captures the observer, timing, severity, affected systems, impact, description, troubleshooting, and evidence for triage.
Include reporter contact, timing, severity, category, affected system, users affected, blocked work, workaround, description, exact errors, recent changes, attempted steps, and evidence. Add environment or asset questions only when relevant.
Put an impact definition beside every choice. Distinguish one user with a workaround from reduced service across teams or a critical unavailable service. Match labels and escalation instructions to your process.
An incident report covers an unexpected interruption, degradation, or suspicious event, emphasizing scope, severity, timeline, and systems. A support ticket can cover routine help, access, questions, or planned service.
Yes. A device path can ask for asset and operating system, a network path for connection and location, and an application path for environment and reproducible steps. Each can share severity, impact, description, and contact fields.
Yes. Add uploads for screenshots, recordings, log excerpts, or suspicious message details. Explain useful evidence and tell reporters to remove passwords, tokens, and secrets. Keep a text field for exact errors.
Yes. Makeform provides unlimited free forms and responses, including generating, editing, publishing, and using the form. The paid tier removes the Makeform badge.
Submissions reach the Makeform inbox and connected workflows such as email, Slack, Google Sheets, or Zapier. Test each destination and make urgent internal contact instructions visible before submission.
Replace incomplete incident messages.
