IT Change and Release Record
Change a live system deliberately, with a written way back and a record of what was done. Agreed beforehand, verified afterwards, by name.
IY-03 1 page
IT and office systems · IY-07
IT Support Ticket Log Sheet
A free printable IT ticket log — who raised it, what was wrong, who took it, the fix that worked and the date it was closed, one line per request.
Download Free · no sign-up
One page. Choose your paper size — both versions are laid out identically, so neither one gets shrunk to fit.
Print it and write on it
Fill it in type and save
The fillable versions have real form fields — open them in any PDF reader, type into them and save. Printing help.
What this sheet is for
Stop the same fault being solved from scratch each time, and see which device or person is generating most of the calls.
Who it is for
One-person IT departments, office managers who field the calls, and small businesses without a ticketing system.
How to use it
- Number each ticket and write it on any note or email that goes with it.
- Record the device or system, not just the person, so patterns show.
- Write the fix that worked, in enough words to repeat it.
- Close with a date and rule the line off.
What is on the sheet
One page, top to bottom:
Printed under the title: Every call for help in one place — who asked, what was wrong, who picked it up and what fixed it — so the same fault is recognised the second time it appears.
The fix column earns its keep. Write the fix, not just 'resolved'. Six months on, 'printer offline — reset the network cable at the wall' is worth more than the ticket number. Leave the priority column to whatever scale your own team uses.
Write-on lines: Team / site · Log started · Sheet no. · Kept by
Tickets — one line per request · rule it off when closed
Table, 12 rows: Ticket · Date · Raised by · Device · Problem · Priority · Assigned to · Fix applied · Closed
Questions
What goes in the priority column?
Whatever scale your own team uses — a number, a word, a colour. The sheet does not set one, because what counts as urgent depends on what your business does.
Why keep this on paper?
Because a ticketing system is often the first thing that stops working when the network does. A sheet by the phone still takes the call.
Related sheets
Backup Run and Restore Test Log
Know that the backup ran, and prove a file can come back from it. Assumed backups are the ones that fail on the day they are needed.
IY-02 1 page
Issue Log
Track the things that have already happened separately from the things that might, so today's problems do not crowd out next month's risks.
OC-06 1 page
Device Issue and Return Record
Know who has which laptop, tablet or handset right now, and have a signature for the moment they took it and the moment they gave it back.
IY-05 1 page
