Article

Before contacting IT: what to collect

A good IT ticket gets fixed faster than a vague one - every time. Five details cover most situations: exact app and version, exact error, what changed, what you tried, and a screenshot. Spend two minutes collecting them and you save an hour of back-and-forth.

The Five

What to include in every IT ticket

1. Exact app, vendor, and version

Not "the CAD program," not "Adobe." "AutoCAD 2026.1," "Microsoft 365 Apps for enterprise (Office 16.0.18xxxx)," "Bluebeam Revu 21," "ArcGIS Pro 3.x." Versions live under Help > About, File > Account, or the Help / About menu.

2. Exact error or behavior

"It does not work" is unactionable. "After clicking Plot, AutoCAD shows 'Plot device requested is not supported. Plot to default Windows printer?'" tells IT exactly where to start. Quote the message word for word, or screenshot it.

3. What changed and when

"Worked yesterday afternoon, broken this morning. Windows updated overnight." "Started after I got the new laptop on Monday." "Started after the password change last week." Timing is half the diagnosis.

4. What you already tried

"Restarted, signed out and back in, tested with another drawing - same result." This stops IT from asking you to re-do steps you already did and shows you took the issue seriously.

5. A screenshot

One picture beats five sentences. See the article on taking screenshots for IT for the fastest way on Windows, Mac, and phone.

Bonus Details

Extras that make a ticket great

The work account email shown in the app

Open the app's account screen and copy the email. This rules out the most common cause (wrong account) in seconds.

Whether the same task works in another place

"Outlook on the web works fine, only desktop Outlook fails." "AutoCAD plots to PDF fine, only the office plotter fails." "Civil 3D works on my coworker's laptop with the same drawing." That is gold for narrowing the cause.

Project / file / printer / folder name

"Project Riverside School" or "C-101.dwg" or "HP DesignJet T1700 in 4th-floor copy room" or "Construction Cloud project Northbridge." If the ticket is about something specific, name it specifically.

Whether other people are affected

"The whole BIM team can't open the central model" is very different from "Only my computer can't open the central model." That single sentence often decides whether the issue is your computer, the project file, or the cloud service.

How urgent it actually is

"Blocking my deliverable due tomorrow" vs "noticed but I have a workaround." Honest urgency helps IT prioritize correctly. Inflating the urgency for everything backfires.

Template

A ticket template you can copy

Subject line

"[App] - [short symptom]" works well. Examples: "AutoCAD 2026 - Plot fails to office plotter, works to PDF." "Outlook desktop - Repeated sign-in prompts, web works." "Revit - Central model freezes on 3D view."

Body

App and version: ___
Account signed in: ___
Exact error or behavior: ___
What I have tried: ___
What changed and when: ___
Other people affected: ___
Urgency: ___
Attachments: screenshot, sample file if allowed.

One sentence at the top: what you actually need

"I need to plot Project ABC sheet C-101 to the 4th-floor plotter today." That tells IT what success looks like, not just what is broken. It is easier to help when the goal is explicit.

Slow Down

Do not do this

Do not paste a wall of text from a chat conversation

Summarize. Three short paragraphs beats a copy-paste of two days of frustrated chat. IT can ask follow-up questions if needed.

Do not include the answer to a problem you decided yourself

"My Outlook needs reinstalling" is a guess at the answer. Describe what is actually happening and let IT decide whether reinstall is the right fix. Often it is not.

Do not send screenshots that crop out the error

Capture the whole window, including the title bar and any error code. Partial screenshots make IT ask for more.

CAD / AEC Notes

Extra details for design-team tickets

Project and file context

Include the project name, file path, model or drawing name, sheet number, data source, cloud project, or library involved. "Revit is slow" is broad; "Revit 2025 is slow opening this ACC cloud model" is actionable.

App version and environment

Send the app year and build, whether you are on VPN, Citrix, Windows 365 Cloud PC, or local desktop, and whether coworkers can do the same task from the same project.

Shared standards and add-ins

Mention plot styles, templates, fonts, tool palettes, add-ins, plug-ins, project workspaces, and license helper apps when they are part of the problem. Those details often decide whether IT or a CAD/BIM manager owns the fix.

Taking screenshots for IT

The fastest ways to capture what IT needs on Windows, Mac, and phone.

Open article

Reading license & activation errors

What "trial," "unlicensed," and sign-in errors usually mean before you send a ticket.