Order records in Excel work as a list: each order has its own row and the individual attributes are in columns. The spreadsheet can filter, sort and highlight data. It is harder to capture repeat visits, attachments and the sequence of changes in a way that lets the course of one order be reliably reconstructed later.
- Every order needs a permanent number and consistently filled-in columns.
- The status should have a limited list of values, otherwise different names arise for the same phase of work.
- Attachments can stay outside the workbook, but the records must contain an unambiguous link to their folder.
- The file's version history is not the same as the history of a specific order.
- Order records do not deal with technician capacity; planning people over time is a separate purpose.
The basic structure of the records
A practical list starts with these columns:
| Column | What it is for |
|---|---|
| Order number | A permanent identifier for the spreadsheet, e-mail and the attachments folder |
| Customer and site | Distinguishing the company, the premises and the specific site address |
| Description of the request | A brief statement of the job without searching the original e-mail |
| Responsible person | Who is in charge of the next step |
| Status | One value from a predefined list |
| Key dates | Received, agreed appointment, completion or handover |
| Result of the work | What was done and what remains open |
| Attachments | A link to the folder with photos, reports and the purchase order |
| Last change | Date and author of the last substantive edit |
A new column can be added in Excel in a moment. First, though, decide who fills it in, what value belongs in it and whether anyone will filter by it. A column without a shared rule usually ends up holding several different kinds of data and is no help when searching.
One order per row has its limits
An order can consist of several events: receiving the request, the first visit, waiting for a part, the second visit and the handover. One row shows the current status well. It only captures the course of events, though, if old data is not overwritten or is written to a separate sheet.
You have two basic options. Either you keep only the current status in the main sheet and write the history to a second sheet, where each event has its own row and order number. Or you use one row with a running text note. The second option is simpler, but it is harder to filter and the author and date of a change are more easily lost in it.
Statuses must be unambiguous
A free-text status quickly produces variants such as "done", "completed" and "to invoice". A filter then treats them as three different groups, even though the company may mean the same thing. That is why it is advisable to use data validation with a short list of agreed values.
The names should match the company's actual workflow. One company needs to distinguish a complaint from a warranty job, another tracks handover or readiness for invoicing. What matters is not a universal set of statuses but that every name has one meaning and a known next step.
Customisation without a programmer covers the same need in a system: statuses, tags and other code lists can be named to match the company's operations.
Attachments belong to the order number
Photos, the service report, the purchase order and the delivery note do not have to be stored directly in the workbook. Create a folder with the same number for each order and put a link in the spreadsheet. File names should say what they contain; a camera label such as IMG_1234 will be no help on its own later.
The rule has to work for the technician in the field too. If someone else saves the attachment only after returning to the office, the records are complete only after that transcription. Orders and history keeps attachments, internal notes and changes directly with the order. Mobile for technicians lets the result of the work be added where the job took place.
What version history can and cannot do
A shared online workbook supports concurrent work and version history. So it is more accurate to say that changes can be traced than to claim that Excel has no history at all. The history, however, applies to the whole file and serves mainly to compare or restore an earlier state of it.
An order history answers a different question: what happened at one customer, in what sequence, who decided on the status change and which document belonged to it. In Excel you have to build such an overview yourself with a separate event sheet or by consistently writing notes.
An appointment in the records is not a capacity plan
The visit date is an important detail of the order. A column with the appointment alone, though, does not show the whole team over time, absences or the technicians' qualifications. If you are looking for a procedure to check conflicts and capacity, read the separate audit of Excel for planning technicians.
This separation helps keep the file's purpose clear. The records answer the question "what status is the order in and what has happened on it". The plan answers the question "who can do the work and when".
How to transfer records from Excel
- Remove test rows and obvious duplicates from the working view; keep the original file unchanged as an archive.
- Standardise the order numbers and check that none are repeated.
- Convert the various ways statuses were written to the agreed list of values.
- Separate the customer, site, description and responsible person into separate fields.
- Attach to every open order the attachments needed for further work.
- Set the date from which new changes are recorded only in the new place.
The scope of the transfer is not universal. Closed orders can stay in the original file as an archive, provided they can be found and the company does not need them in everyday work. Open orders, on the other hand, need to be checked one by one, because further steps follow on from them.
When Excel is enough for the records
Excel is enough when the number of orders is manageable, the entries have a uniform structure and the team follows the rule for attachments and changes. It is also suitable as an archive over which filters and summaries are used.
The limit appears when one order involves several visits and documents, changes are made by several roles and an answer has to be pieced together from the spreadsheet, e-mail and a phone call to the technician. This is not about capacity planning, but about being able to trace the course of an order.
Frequently asked questions
Can order records be kept in Excel in the long term?
Yes, provided every order has a unique identifier, the team uses the same statuses and there is a clear place for attachments and history. The more people add to the entries and the more visits and documents are tied to one order, the harder the rules are to maintain.
What details should an order record contain?
The order number, the customer and site, a description of the request, the responsible person, the status, key dates, the result of the work, a link to the attachments and an internal note. It is also useful to record who last changed the entry and when.
Does Excel's version history replace the order history?
The version history of an online file helps restore an earlier state of the spreadsheet. On its own, though, it does not create an overview of events for one order, nor does it link a change to a photo, a report and the reason for a decision.
What happens to the data from Excel when switching to a system?
The spreadsheet can be kept as an archive of closed orders. What is worth transferring to the new system is mainly open orders, customers, sites and the attachments needed for ongoing work; the exact scope depends on the structure of the original file.
Are order records the same thing as the technician plan?
No. The records describe the order, its status, documentation and result. The technician plan deals with people's capacity over time, conflicts and qualifications. An appointment can be one field in the records, but it does not replace a capacity plan.
When Excel is enough for planning technicians, where it stops being enough and what changes when you switch.
Orders and historyAttachments, internal notes and a record of every change in one place on the order.
Customisation without a developerName statuses, appointment types, labels and qualifications the way your company does.
Mobile for techniciansThe technician opens a browser, sees their day, starts work and logs the tasks performed.
The cost of software for a service company over three years of use: how pricing models behave over time, how to calculate it and what decides by team size.
Installation planning for beginners: where to start and what to avoidInstallation planning differs from service in job length and crew size. Six steps to start with and the mistakes that most often sink it.
A service log in Excel: what belongs in it and when it stops being enoughA service log in Excel is enough as long as one person fills it in. What belongs in it, what Excel can handle with the right design and what stays expensive in it.
Plan more simply
ServisBook free for 30 days, no credit card.
Free trial →