IT Support Ticket Form
An IT support ticket — requester and contact, device/asset, issue category and priority, a clear description with steps to reproduce, impact, and an IT-use section for triage and resolution.
Live preview
IT SUPPORT TICKET Ticket #: INC-2026-0312 Date: May 23, 2026 REQUESTER Name: Sample User Contact: user@example.com · ext. 204 Department: Accounting — 3rd floor Device/asset:Laptop LT-0457 (Windows 11) ISSUE Category: Software Priority: Medium DESCRIPTION Excel crashes when opening the monthly report file. Happens every time since this morning; other files open fine. Error: "Excel has stopped working." STEPS TO REPRODUCE / WHEN IT STARTED 1) Open Excel 2) File > Open monthly-report.xlsx 3) Crashes after ~3 seconds. Started today after the morning update. IMPACT Cannot complete month-end reporting; blocking. Attachments (screenshots / error messages): [ ] attached [ ] none ------------------------------------------------------------------- FOR IT USE ONLY Received: ______ Assigned to: ______________ Status: ____________ [ ] Open [ ] In progress [ ] Waiting on user [ ] Resolved [ ] Closed Root cause / resolution: ___________________________________________ Resolved date: __________ Time spent: __________
About this template
An IT support ticket exists to get a problem fixed fast, and the quality of the ticket largely determines how fast that happens. The single biggest time-saver is a **specific, reproducible description**: what is broken, the exact error message, when it started, and the steps to reproduce it — "Excel crashes opening monthly-report.xlsx, error 'Excel has stopped working,' started after this morning's update" is something a technician can act on immediately, while "Excel is broken" guarantees a round-trip of questions. The other essentials are the **requester and contact** (so IT can follow up), the **device/asset** and **department** (which narrow the cause and let IT check the right machine), a **category** to route the ticket to the right queue, and a **priority** so genuinely urgent issues (system down, many users affected, security) jump ahead of cosmetic ones. Encourage **screenshots or the literal error text** — a picture of the error removes ambiguity. The **impact** line ("blocking month-end reporting") helps IT triage business urgency, not just technical severity. Keep an **IT-use section** for the work side — who it is assigned to, status, root cause/resolution, and time spent — which turns tickets into a record you can mine for recurring problems and response-time metrics. Good practice: one issue per ticket (so each can be tracked and closed independently), set realistic priorities (not everything is "critical"), and update status so the requester knows where things stand. Store tickets in your help-desk system; this printable form is handy for walk-ups, environments without a portal, or as an offline backup.
When to use it
- Logging an IT/help-desk request (hardware, software, network, account).
- Walk-up support or environments without a ticketing portal.
- Capturing a reproducible description, priority, and impact.
- Tracking triage, assignment, and resolution.
What to include
- Requester, contact, department, and device/asset.
- Category and priority for routing and triage.
- A specific description with steps to reproduce and error text.
- Business impact and whether screenshots are attached.
- An IT-use section: assignment, status, root cause, time spent.