From paper service forms to digital work orders

In many service companies and maintenance teams work still runs the same way: a fault comes in by phone or WhatsApp, someone writes it in a notebook or a spreadsheet, the technician fills in a carbon-copy service form and gets it signed, and at the end of the month the form goes into a binder. It works, right up to the moment someone asks “when did anyone last look at this unit, and which part did they replace?”

This post is for maintenance managers and service owners who want to move from paper to digital work orders. The goal is not to pick software. It is to make the switch without wearing anyone out.

What paper really costs

The problem with a paper form is not the paper. It is that the information is scattered:

• The request is in one place, the work in another. The fault is in a chat, the assignment was a phone call, the work done is on the form. The only thing holding them together is the memory of whoever follows up.
• No equipment history. Forms are filed by customer or by date, not by asset. Spotting that the same compressor failed for the fourth time in three months means digging through binders.
• Readings get lost. The form says “checked”. The pressure, current or temperature is not written down, or it is scribbled in the margin.
• No evidence. Was it cleaned, was the part replaced? The photos are on the technician’s phone.
• Retention duties. In Turkey, Annex III of the regulation on health and safety in the use of work equipment requires all maintenance and repair records to be kept for the equipment’s whole service life (mevzuat.gov.tr), and the Turkish Commercial Code keeps commercial documents for 10 years. A binder in a storeroom is a poor archive for those periods.

Before you switch: what are you digitising?

A digital work order is not a photo of the paper form. Before starting, draw today’s flow on one page:

1. Where do faults and maintenance needs come from? (Phone, chat, email, a branch manager, the technician)
2. Who decides, and who gets sent?
3. What does the technician record on site?
4. When does a job count as “done”, and who confirms it?
5. How are parts requested, and who hands them out?

The answers are the skeleton of your system: request → work order → assignment → site record → completion → approval.

Step 1: List your assets

A work order is worth most when it is tied to a piece of equipment. List your locations (branches, buildings, floors, kitchens) first, then the equipment at each. For each item, this is enough to start:

• Name and type (cold room, combi oven, generator…)
• Make, model, serial number
• Where it is
• Warranty end and a nameplate photo, if you have them

Do not wait for a perfect inventory. Start with the equipment that fails most and the equipment with legal record duties, and add the rest as jobs come in.

Step 2: Keep the work order lean

Do not move every box on the paper form into software. A work order really needs:

Field	Why
Number	“SRV-1024” on the phone beats “that job in the north branch last Tuesday”
Asset and location	History builds up around them
Work type	Breakdown, preventive maintenance, installation, site survey…
Priority and planned date	For ordering the day
Assignee or team	For ownership
Status	So everyone sees the same thing
Checklist	The standard for what to do
Notes, photos, parts	Evidence of what was done
Resolution and labour time	The closing summary

Step 3: Keep statuses few

Paper has no statuses; software easily has too many. Start with a chain everyone understands: new → assigned → en route → in progress → on hold → done → approved, plus cancelled. Add sub-statuses like “waiting for parts” only if you genuinely track them separately.

Step 4: Turn the paper form into a checklist

Go through your current form line by line. Turn “checked” boxes into measurable items, drop what nobody uses, and mark where a photo is needed. We explained how in the post on checklists with measurements.

Step 5: Start small, and do not run paper alongside

The most common mistake is running the digital system next to paper “for a while”. With two systems, technicians fill in both halfway. Instead:

• Start with one location or one team.
• Retire the paper form for that team completely from a set date.
• For the first two weeks, spend five minutes a day reviewing work orders together: what is missing, what is noise?
• Then roll out to the next team.

Step 6: Win over the technicians

If the system feels like extra work to the people on site, it will not be filled in. What wins them over:

• Less writing. Choice items, ready fault types, measurement fields.
• No hunting for phone numbers. Address, equipment details and history are on the work order.
• It works in the basement. An app that fails in the cold room, the boiler room or the underground car park gets abandoned on day one. We wrote about why that matters.
• It protects them. A job closed with photos and readings is the technician’s evidence when someone says “you came last week and it broke again”.

How Saha makes the switch easier

When a company signs up for Saha it picks its sector. Templates for refrigeration, HVAC, electrical, generator/UPS, commercial kitchen and general service bring ready asset types, fault types, work types and checklists, so day one starts from something you can edit rather than an empty system.

Requests come from staff or from the QR label on the equipment; the QR page needs no app and no sign-in. A request turns into a work order in one step, gets a number starting with SRV-, and is assigned to an employee or a team. Statuses run in fixed categories, and your company can add its own statuses inside them. Technicians fill in the checklist, take photos, request parts and close the job in the iOS or Android app, even without a connection on the work assigned to them. A job cannot be completed while required items are unanswered, requested photos are missing or a part request is still open.

Every work order has a timeline: assignments, status changes, notes, photos, part requests. Those events are never edited or deleted, and every job adds up in the asset’s service history. You can export work orders, assets and part usage as CSV. If you run accounting software or an ERP, Saha does not replace it; it works next to it.

A short list for the switch

• Draw today’s flow on one page.
• List the critical equipment first.
• Keep work order fields and statuses lean.
• Turn the paper form into a checklist with measurements.
• Start with one team and drop paper there completely.
• Review together every day for the first two weeks.

What you gain at the end is not a form on a screen. It is being able to look at a piece of equipment and see its whole story in one place.