The idea
What this system is
Your tickets live in your inbox, your texts, and hallway conversations. Somebody's printer has been broken for two weeks and nobody wrote it down. The certificate expired because the reminder sat in a spreadsheet only you open. Solo IT Desk puts all of it in one place, in plain words.
It was built by a man who runs a 3-person government IT department for a living — not enterprise software shrunk down, and not a blank database you are supposed to design yourself. Three lists do the work:
Tickets — every problem, tracked from "it broke" to "here's what fixed it," with pre-built views: board by status, by person, oldest first, closed this week, and the Fix Library. Recurring Work — patches, backup checks, renewals: if it comes back around, it lives here with a due date. Assets — your gear, where it lives, and when its warranty runs out. The Dashboard is the morning screen over all three: the ticket board, the oldest open tickets, what's due this week, and an on-call / handoff whiteboard.
Setup
Setup in ten minutes
The quick start above is the whole runway. This section is the same setup with the details filled in.
-
Name your team
In Tickets, open the Assigned to property and rename You, Tech 1, and Tech 2 to your real names. Do the same for Owner in Recurring Work — the two lists use the same names. Renaming an option renames it on every row that already uses it, samples included. One-person shop? Delete the extra options and keep just yours.
-
Skim the samples, then keep or delete them
The sample tickets show what a good ticket looks like: what broke, who reported it, how bad it is, and — on the closed ones — the one-line fix. Every sample starts with the word SAMPLE. Keep them while you learn the views, or select and delete them all now. Underneath them, the system is yours.
-
Add your real gear and your repeating jobs
In Assets, start with what breaks most: the printers, the oldest PCs, the Wi-Fi gear — and each one's warranty end date. In Recurring Work, adjust the seeded jobs (patch cycle, backup check, certificate renewal, license check, warranty sweep) to your real dates, and add your own. If it comes back around, it goes here with its next due date.
-
Star the two pages
Star Start Here and the Dashboard so they are one tap away, on your computer and your phone. The Dashboard is the page you will open every morning.
Every day
The 30-second ticket habit
Somebody stops you in the hallway: "My email is doing that thing again." That is a ticket. Thirty seconds, before you walk away:
Open Tickets and tap New.
Title — what broke, in the words the person used: "Printer on 2nd floor jams."
Category and Priority — pick the closest one; do not agonize. Down means people cannot work.
Reported by and Location — who told you, and where it is. Assigned to — whoever is taking it; if nobody is, it is you.
Save. You are done — everything else can be filled in later.
The habit is the whole system. A request that becomes a ticket has an owner and can't be forgotten in an inbox thread. A request that stays a hallway conversation will be re-explained to you in two weeks, as a complaint.
Closing tickets
Closing a ticket builds your Fix Library
When the work is done, close the ticket properly — it takes one extra line, and that line pays you back for years:
Set Status to Closed and add today's Date closed.
Write one line in Fix notes: what actually fixed it. "Replaced the fuser." "Mailbox was over its limit — archived the old mail."
Every closed ticket with a fix note lands in the Fix Library — its own page, and a view inside Tickets. The next time the same thing breaks, whoever is on it searches the Library and finds the answer in seconds instead of calling you. Your closed tickets also collect in Closed This Week, which is your workload, in writing, when anyone asks what your department does all day.
Every week
The Monday-morning routine
Two minutes, coffee in hand, on the Dashboard:
Oldest First — whatever has been open longest gets touched first. A ticket that sits at the top of this list for days needs a decision, not more waiting. The two-week-old printer problem can't hide anymore.
Due This Week — the recurring jobs coming due: patches, checks, renewals. Clear them before they become surprises.
The board — drag anything that moved. If a card's status is a lie, the whole board is.
Warranty Ending (in Assets) — glance at what's about to run out of cover while there's still time to act on it.
On the move
Phone tips
This whole desk works from the Notion phone app — that is the hallway test: a ticket can be logged standing in a server room and closed from the parking lot.
Keep the Dashboard as your home screen and let the board do the rest. Log the ticket the moment someone tells you about the problem, while you're still standing in front of them — the 30-second habit is built for exactly that. Use the On call / handoff whiteboard on the Dashboard like a note to the next person: who is carrying the phone, what broke overnight, what to check first. Erase and rewrite it freely; it is a whiteboard, not a record.
The honest mechanics
Your data lives in your Notion
The template lives in your own Notion workspace. Your tickets never touch our servers — there is no account with us, nothing to log into, and nothing we can see. We cannot browse your tickets, look your department up, or recover a copy for you, because we never hold one.
What that means in practice: whoever you share your Notion workspace or pages with can see what's in them — your Notion sharing settings are the lock on the door, so share the desk the way you'd share any work document. And keep your own backup habit: Notion keeps deleted pages in Trash for a while, but your copy is your responsibility, the same as any file you own.
Quick fixes
Troubleshooting
A closed ticket isn't in the Fix Library
The Library shows closed tickets with a fix note. Check the ticket's Status is Closed and that Fix notes isn't empty — that one line is what the Library collects.
Due This Week looks empty
It shows Recurring Work with a Next due date from today through the next seven days. If a job is missing, its Next due is probably blank or further out — set the date and it surfaces.
A ticket isn't in Oldest First
Oldest First shows tickets that aren't Closed, oldest Date opened first. If a ticket was closed, it belongs in Closed This Week instead.
The sample rows are still everywhere
Every sample starts with the word SAMPLE. Select them in each database and delete — the views stay exactly as they are, just empty and yours.
A name change didn't stick everywhere
Tickets uses Assigned to; Recurring Work uses Owner. They are separate lists — rename your people in both, the way Start Here describes.
The board columns look wrong
The board groups by Status: Open, In Progress, Waiting, Closed. If a card sits in an odd column, its Status is set to that column's value — fix the ticket, not the board.
Buy once, it's yours
Updates and your copy
Solo IT Desk will be improved over time, and updates are free for buyers. Here is exactly what an update means for the desk you are running — no surprises.
Your copy is yours, forever
The copy you duplicated into your Notion is yours alone. It never changes under you, it never expires, and it keeps working exactly as it is. Updating is always your choice, never a requirement — if you are happy with your version, you can run it for years.
Some updates need no move at all
When an update is just a new view or a wording fix, the update notes will include simple instructions to add it to your existing copy in a couple of minutes, so you get it without duplicating anything. Each update announcement will say plainly which kind it is: add-it-yourself, or duplicate-the-new-version.
Bigger updates
For a bigger change, you can duplicate the new version free. Your old copy stays in your workspace as the complete archive of every ticket you ever closed — most people keep it for exactly that reason and run the new version going forward.
Questions
Solo IT Desk FAQ
What Notion plan do I need?
The free plan is enough. Solo IT Desk uses standard Notion databases and views — no paid features, no formulas, nothing to maintain.
We have more than 5 people. Will it still work?
Yes — nothing in the template counts heads. It is designed and written for departments of 1 to 5, where one person wears most of the hats; a bigger team can use it, but a bigger team usually also needs intake forms and permissions, which are deliberately not in this version.
Do I need a Spud account?
No. There is no Spud account and nothing to log into. You buy the template, duplicate it into your own Notion, and it is yours.
Can my team see the tickets?
Anyone you share the pages with in Notion can. Share the desk with your team the way you would share any work document — your Notion sharing settings decide who sees what.
What if it is not for me?
If it doesn't work in your Notion or it's not for you, email hello@robotpotato.net within 14 days and I'll refund you. Gumroad handles the mechanics.
What if the template is updated later?
Your copy is yours and never changes under you. Updates are free for buyers, and the "Updates and your copy" section above explains exactly what an update involves.
How do I get help?
Email hello@robotpotato.net — that's the Spud Widgets support address, and it reaches a real person: the one who built this system and uses it to run his own department.