Internal Help Desk Spreadsheet: Free IT Ticket Tracker

There are two of you in IT and eighty of everyone else. Requests arrive through every channel the company has: a Slack DM at 8:47, a shoulder-tap on the way to the kitchen, and the hallway ambush that starts with "quick question" and ends with a laptop swap. None of it is written down anywhere except, occasionally, your own memory — which is also where it gets lost.

The failure mode isn't laziness; it's physics. A password reset takes ninety seconds, so you do it on the spot and it evaporates. An access request takes an approval, a change, and a record you'll need when the auditor asks who granted the finance-drive permission and when — and right now that record is a Slack thread someone will eventually delete. Meanwhile half your interruptions are the same person asking, "hey, did you get my ticket?" There is no ticket. That's the problem.

Enterprise service desks solve this with per-agent seats, workflow designers, and a training course — a mortgage for a doorbell when there are two of you. An internal help desk is fundamentally a shared list with rules — and a Google Sheet plus an AI-built portal on top gets you the list, the rules, and the audit trail without a procurement cycle.

Step 1: Set Up the IT Ticket Sheet

One tab, one row per request. Eight columns cover nearly everything:

Add two supporting tabs. A directory tab that says which of you owns what — Marcus takes hardware and onboarding, you take access and software. And an FAQ tab seeded with the self-serve answers you repeat weekly: password self-resets, printer setup, VPN configs.

The Asset column is the sleeper: point it at an inventory tab of every laptop, monitor, and license key, and each ticket carries hardware history with it.

Step 2: Register a Free Account

Head to lovespreadsheets.com and create an account — the free tier both builds and runs the desk. Paid features are the login wall on your admin view and hosting at something like help.yourcompany.com.

Step 3: Describe the Desk in Plain English

Choose the Website template and write out both halves. The requester half — remembering your users are your coworkers:

"Employees open an internal request page and pick a type: access, hardware, software, or password. Each request becomes a row with an auto-generated ticket ID, and the employee gets an instant confirmation email with that ID. For password-type requests, check my FAQ tab first and include the self-serve steps in the confirmation, worded as 'this may fix it now — we'll follow up either way.' Route the alert to whichever of us the directory tab says owns that request type."

The IT half:

"Behind a login, show us every open ticket, filterable by type, priority, and department, editable inline. Access requests need a visible approval trail — who approved, when, and what changed."

Three requests worth typing:

• Type-based routing with an approval step — access requests pause at "waiting on approval" and log the approver, so the audit trail writes itself
• Asset linking — the asset field pulls from your inventory tab, so a flaky laptop's third ticket is visible on its fourth
• A self-serve FAQ page — published alongside the form, aimed squarely at deflecting password resets before they're filed

Hit AI Optimize if the description sprawls, answer whatever clarifying questions come back, and the build takes roughly 15–20 minutes.

Step 4: The Interruptions Become Rows

You get a URL to pin in the #it-help Slack channel and the onboarding doc. From then on, every request has an ID the moment it's submitted, the requester has a confirmation in their inbox, and the right half of your team gets the alert. "Did you get my ticket?" finally has a boring answer: yes, it's IT-0187, status is visible.

The sheet stays the source of truth: portal edits update the row, and row edits show up in the portal.

Why IT Teams Keep the Sheet

Audits stop being archaeology. When access grants live as rows with approvers and timestamps, the annual review is a filter, not a week of Slack spelunking.

Asset history compounds. Tickets joined to an inventory tab turn "this laptop feels cursed" into data — the full service record is there before you decide to replace it.

Two people can't afford per-seat pricing. Service-desk suites bill by agent; this desk costs nothing to run whether it's two admins or five.

Common Questions from IT Teams

Will people actually use the form instead of DMing us? They will once the form is faster than you are — instant ID, instant confirmation, visible status. Politely answer DMs with the link for two weeks and the habit flips.

Can non-IT employees see each other's tickets? No — requesters see the form and their own confirmations. The full queue sits behind the login-gated admin view.

Can we get response-time tracking? Ask for SLA timers and priority auto-assignment in your description. Timestamps are columns, and columns are what sheets do best.

Build Yours

Open a fresh Google Sheet, add the eight columns and an inventory tab, and describe your two-person desk at lovespreadsheets.com. Twenty minutes from now, the next hallway ambush ends with "file it at the link — you'll have a ticket ID before you're back at your desk."