The card machine at the south branch has stopped reading contactless again. The branch manager emails IT: "it's broken again, can someone look?" IT replies asking which machine. Two days later a repair quote arrives, and nobody's sure whether the branch can just say yes or whether head office has to approve it.
Meanwhile the same model was replaced at the north branch last month, and the one at the south branch is still under warranty. Nobody knew, because that's in a spreadsheet only one person opens.
An equipment fault report form fixes most of this. It just needs to ask the right questions and send each answer to the right place.
What a fault report form needs
Whatever you build it with, a fault report needs very few fields. Each one exists because someone later in the process needs it:
- Which asset. Picked from a list, not typed. "The laptop" and "Sam's laptop" and "LT-0042" are the same thing to you and three different things to a spreadsheet.
- What's wrong. One plain sentence. "Screen flickers on the left, worse when it warms up" tells the repairer more than "screen issue".
- When it was noticed. So you can tell a fault from a pattern.
- What kind of job it is. A repair, or just an inspection.
- The quoted cost. This is the field that decides what happens next.
- A photo, if you want one. It helps whoever fixes it, and it settles "it was like that when it arrived" conversations.
Just as important is what the person approving sees next to the report: the asset's warranty date, what's already been spent on it and its repair history. Without those, people approve a £300 repair on a machine that's still under warranty, or on a laptop that's had three repairs this year and is worth less than the quote.
Why approval should depend on the cost
Most fault reports don't need anyone's sign-off. A £40 replacement charger shouldn't wait three days for the area manager. A £600 repair on a four-year-old laptop should, because the real question is whether to repair it at all.
So set one limit. Under it, the repair goes ahead and gets logged. At or above it, someone with budget decides: repair it, or replace it instead. One rule, one decision, and only for the repairs where the decision matters.
Whatever limit you choose, write it down and put it in the form itself, so branches stop asking "do I need approval for this?"
The template, step by step
The Asset Register template includes all of this: an Assets Table, a maintenance log, and a Report a Fault Form with its Workflow. Add it to your workspace and here's what you get:
- The Report a Fault Form. It asks Which asset? (a choice from your Assets Table), What is wrong with it?, Kind (Repair or Inspection), Noticed On and Quoted Cost. The quoted cost has a note telling the person filling it in that it decides whether anyone has to approve it.
- The asset beside the form. Once someone picks an asset, the Form shows its tag, state, custodian, warranty date and Repair Spend (everything spent on it so far), plus its maintenance history. The person reporting sees it, and so does the person approving.
- One Rule on the cost. The Workflow checks the quoted cost. Anything under the limit goes straight to Repair approved, with nobody to wait for. Anything at or above the limit becomes a Task for your IT Ops team.
- One approval Step with two Actions. The Step's instructions tell the approver to check the quote against what the asset is worth and what's already been spent. They choose Repair It or Replace Instead. The requester sees Repair approved or Replacing instead.
- Every report lands in the maintenance log. Approved or not, the report becomes a row in the log with its cost, against the right asset. Repair Spend adds itself up from that log, so the next approver has the real figure.
- A daily warranty check. An Automation called Warranty Watch runs every morning and logs an inspection on any asset whose warranty ends within 30 days, so you can get faults fixed while they're still covered.
Changing it for your branches
The template works as it is, but a few changes make it fit a team spread across branches:
- Set your own limit. The template's Rule is set at 400 (labelled "$400 and above"). Change the number and the label to your currency and your actual limit. If branches have different limits, add a path to the Rule for each one.
- Use your own branch names for Location. Location is a text column in the Assets Table. Change it to a choice of your branch names, so you can filter the board by branch and see every faulty asset at the south branch in one view.
- Map IT Ops to a real team. The approval Step is assigned to an IT Ops placeholder. Map it to whoever actually holds the budget: IT, facilities, or the area manager's team. Anyone in that team can pick up the Task, so one person on leave doesn't hold up every repair.
- Add a photo field. Add a file upload to the Form for a picture of the fault. It goes with the report to whoever does the repair.
- Add your own asset types. The Category column comes with Laptop, Monitor, Phone, Furniture, Vehicle and Other. Add tills, card machines, fridges, or whatever breaks at your branches.
The template needs a shared Employees Table so an asset's custodian is a real person. If your workspace already has one, the app uses it; if not, one is created for you.
Start with the things that break most
You don't need every asset in the register on day one. Add the equipment that causes the most fault emails, often card machines, laptops and anything in the kitchen. Put the Form's link or QR code where people will see it. Once the branches see repairs under the limit go straight through, you'll stop getting "who do I ask?" emails.
Add the Asset Register template, or describe your own repair process at stepbase and build it from your own wording.