When the spreadsheet runs out of room

Every service team reaches the moment when the spreadsheet cannot cope any more. Not because it is a bad tool — but because the work has outgrown the shape you squeezed it into. Ten people in the field, three in the office, each with their own copy of the truth. In the studio we built a demo of the TAKT system to show what it looks like when every job gets a single home.

Signs you have outgrown the spreadsheet

It is not about the number of rows. It is about the point where the format starts getting in your way:

• Two people edit the same file and one of them loses their changes.
• The schedule is a whiteboard that you photograph with your phone every morning.
• Parts get counted at the moment they run out — halfway through a job.
• Hours are reconstructed on Friday afternoon, from memory.
• The invoice waits for whoever can remember what exactly was done.

Each of these is small. Together they are a week of work a month that nobody charges for.

What we built

TAKT is a system for work orders — for service, maintenance and installation teams. The demo runs in the browser on invented data, but it behaves the way a real system would: filters, search, opening a job, moving a job forward. Open it and try it — it is not a screenshot.

The system stands on four views, because those are the four questions a dispatcher asks every day.

1. Work orders — what is open

One record per job: the reported fault, the machine, the customer, the location, the assigned technician, the due date, the reserved parts, the hours logged and the value. Filters by status (in progress, waiting for parts, done, urgent) and search by customer, machine or technician. Clicking a row opens the detail, and a button moves the job forward — from waiting for parts to in progress, from in progress to done, and finally into a draft invoice.

The detail that matters: when you move a job, the figures at the top recount immediately. Nobody reports the status — the status is a consequence of the work.

2. Planner — who is where

Technicians in rows, hours in columns, jobs as blocks. A red line follows the actual time, so at a glance you see what ought to be in progress and what has got stuck. Below it is the day’s utilisation as a percentage — how many of the available hours are actually sold.

That is the most underrated number in field service. Companies often do not know whether they have too few people or merely badly scheduled ones.

3. Parts — stock that matches the shelf

A part is reserved the moment you add it to a job, and written off once it is fitted. The minimum stock level is configurable, and the system flags what has dropped below it on its own. The difference between “we have three” and “we have three, two of them reserved for tomorrow” is the difference between a job done and a job postponed.

4. Reports — what actually happened

Invoiced work by day, the average time from reported fault to sign-off, the share of jobs closed on the first visit, and the hours logged in the field. None of it is entered separately — all of it comes out of the same records.

The spreadsheet did not fail. It simply ran out of room.

Why a custom system and not an off-the-shelf one

Honestly: if your process is standard, take the off-the-shelf tool. We wrote about that in the article custom or off-the-shelf booking system, and the same logic holds for work orders.

A custom system pays off when at least one of these is true:

• your workflow has peculiarities that off-the-shelf tools do not cover (several locations, contract clients on different rates, legally required reports);
• jobs have to be connected to stock, accounting or an ERP;
• your data is scattered across files today and first has to be brought into one database;
• the team is growing and the monthly per-user subscriptions start to hurt.

How a rollout runs

It is not a big bang. First we move the work orders across, because that is where the pain is greatest and the effect quickest. Once the team has taken to it, we add scheduling, then stock, and invoicing last. Each step has to save time on its own, otherwise it is not worth introducing.

The old system runs alongside until it is clear that the new one holds. Nobody loses data and nobody does the work twice for longer than a few weeks.

If you run a service team

Write and tell us how many technicians you have and where it gets stuck today — in scheduling, in parts or in invoicing. From that we can quickly see whether you need the whole system or just one module, and whether it is worth it for you at all.