A ready-to-use work order log for Excel or Google Sheets — track every job with priority, labor hours, parts, and failure cause. Free, no signup.

One row per job, with these columns: WO #, Date Opened, Due Date, Asset, Location, Priority, Description of Work, Assigned To, Status, Labor Hours, Parts Used, Failure Cause, Date Completed, Age Days, and Closeout Notes. Age Days fills in on its own, counting from the day the job was opened until it is completed.
A work order form is one page per job, filled in by hand and filed. A log puts every job on one sheet, so you can sort by status, see what is overdue, and add up hours and parts by machine. This template is a log. If you need a page per job that a tech fills in on their phone, with photos, that is what work order software does.
A work order log like this works fine while one person runs it. The cracks show as soon as work has to move between people: a spreadsheet can't assign a job to a tech or notify them it exists, there's nowhere to attach a photo of the leak or the nameplate, and pulling the full repair history for one asset means filtering and hoping every row was typed consistently. That's usually when teams move to software built around the work order itself. We cover the habits that matter either way in our guide to maintenance work order best practices.
Yes. The Excel workbook is free with no signup, and it opens in Excel or Google Sheets. It has one row per job with dropdowns for priority (Low, Medium, High, Urgent) and status (Open, In Progress, Waiting, Completed, Cancelled), and it counts open, completed, and high-priority jobs for you.
Give every job a status from a fixed list instead of free text, then filter or count by it. This template's Status column is a dropdown, the summary at the top counts open and completed jobs, and the Age Days column shows how long each job has been open, so old jobs stand out.
At minimum: a unique work order number, the date opened, the equipment and its location, a priority, a clear description of the work, who it's assigned to, and the current status. To get real value from the log, also record labor hours, parts used, the failure cause, and the completion date — that history is what tells you which machines are costing you the most.
A simple three-level scale works for most small teams: High for safety issues and breakdowns that stop production, Medium for problems that degrade performance or will get worse if ignored, and Low for cosmetic or convenience items. Work the highs first, batch the lows into slow periods, and re-check priorities weekly so nothing quietly ages into an emergency.
Keep them for the life of the asset at minimum — repair history is what makes repair-vs-replace decisions possible, and it's often requested during audits, insurance claims, and warranty disputes. Many teams keep 3–7 years of records as a baseline; digital storage is cheap, so when in doubt, don't delete.
RunTight turns this log into mobile work orders your techs complete in 2 minutes — Free plan available, no per-user fees.
Start live work orders