the job sheet

So there’s this installation company whose systems I look after. The engineer wraps up his job sheet right there on his phone, standing at the customer’s, signature and all. I built that flow myself, and I still keep it running, so I know exactly what sits behind it: a chain that runs lead, quote, sign-off, project, and the job sheet is the hinge the whole thing swings on. But honestly, that’s not even the part that grabs me. Here’s what does. The Dutch technical sector needs 121,000 new skilled people over the next five years. At the same time 118,000 are walking out the door. And the shortfall today already sits around 30,000 technicians. You can’t just go buy yourself an engineer. So every hour of paperwork is, near enough, one engineer hour gone. The sector says that out loud now. What it doesn’t do is measure it. And that gap? That teaches me more than any sales pitch about digital job sheets ever could.

The customer’s side of this same problem, the logistics you never see, that’s over in the portal. This one’s about the inside. The road from done to invoiced.

what does the paper job sheet cost an installation business?

Nobody knows exactly. And that’s the honest place to start. I can’t even hand it to you as a sector comparison, not even for the company I’m in the systems of every single day, because there’s no sector figure to hold it against. Healthcare’s got one. They’ve been measuring this for close to ten years: 31 percent of working time gone to admin per Statistics Netherlands, 34 percent per the rolling Berenschot survey (CBS, 2025; Berenschot, 2025). Care workers themselves reckon 23 percent would be fair. So they’ve been sitting well over their own line for years, and anyone can go read it. The installation sector? Oh, it’s got the words all right. Techniek Nederland talks happily about easing the administrative load. A measurement of what the job sheet actually costs an engineer, though? That the sector just doesn’t publish.

So I’ll tell you how it looked at our place instead. The engineers used to work in a CRM stuffed with custom work and boards. Every morning they’d go dig through their own mobile app for the day’s deal. Then hunt through something like twenty columns to find the job sheet. The calendar made no sense, so they’d go searching in a calendar too. Then search for the address. Then the checklist. It was searching, searching, searching. A platform like that is open custom-build, sure, you can set all of it up yourself, but it isn’t set up for you and it wasn’t built for it in the first place. And here’s one thing I can give you firsthand: the last 24 finished jobs, all 24 of them, have the signed job sheet hanging off the project as a PDF. That’s all it tells you. And already more than any brochure number.

Let me be straight about where I stand, though. I sell these systems. Those figures that jump right into that measurement gap? They’d make my quotes a whole lot easier. Hours a day lost to paperwork. Whole FTEs won back per ten engineers. Sounds great. I don’t use them. I checked them one by one and not one holds up. Not a single one traces back to independent research you can actually go and check. The most-quoted piece on field-service efficiency is from 2013 (Aberdeen Group, 2013). Twelve years old, and it still gets passed hand to hand like it’s fresh off the press. I even ran into one with a tidy little source credit underneath it. Went to look that source up. It didn’t exist. So what do I actually tell a company that’s on the fence? Tally your own hours for a week. Sheets, retyping, follow-up calls. Dull, yeah. But it’s the only number that’s true for you. Because what you don’t measure, you don’t see. At that same company the link between the incoming requests and the planning went dead once. No error message. Nobody spotted it. Now there’s a check running every morning. That lesson came free, after the fact.

why is this more urgent than any ai promise?

Because it’s the arithmetic of the labor market that makes this urgent. The technology’s a tool, at most. At the end of last quarter more than 400,000 vacancies stood open across the Netherlands, and the employment agency UWV has had technical jobs pegged as tight to very tight for years now (UWV, 2025). The sector puts its own staffing gap north of 30,000 people, two thirds of them engineers working for themselves (Techniek Nederland, 2024). And seventy percent of the inflow it needs has to come from people switching careers. People who, right now, just aren’t there yet.

Here’s the thing, though. The chairman of Techniek Nederland is remarkably level-headed about it. Get systems to handle the repetitive, administrative stuff, he says, and technicians keep more time for the actual craft (Techniek Nederland, 2025). Now that sounds like a vendor preaching the AI gospel. Except it isn’t. It’s the sector writing its own labor-market policy. Which makes sense, when you think about it: past hiring more people, productivity is the only dial anyone’s got left to turn. And the dullest productivity win of the whole bunch? The job sheet nobody has to retype anymore. No language model gets anywhere near that one. Structure does.

what does the job sheet have to do with your cash flow?

Everything. And you need no vendor figure for this one, just the mechanics. An invoice can’t go out until it’s nailed down what got done and what got delivered. That’s the job sheet. So every day that sheet sits there unprocessed, your invoice slides back along with it. When I built the job sheet flow, that was the whole design brief: finished means billable, nothing in the middle. I went and checked for this piece, actually. Of the last 24 final invoices there, 23 went out inside a day, most of them the same day. One sat for five. And you know what, that one’s the whole point. In the old days something like that would just vanish into the pile. Now you catch it straight away. Those days pile up on top of a payment term you can barely move anyway. The law says 30 days. In practice, big companies paid their small and midsize suppliers after 40 to 43 days on average (Rijksoverheid, 2023). European b2b sits north of 60 (European Commission, 2025). So that law mostly lives on paper.

I’m not going to dramatize it, mind you. The Netherlands is actually one of the EU countries where the fewest businesses land in real trouble over late payment, and that’s worth saying out loud too. The pinch sits narrower than that. Hang at the bottom of a chain, main contractor up top, subcontractor under them, and you wait on whoever’s above you. From the van you change none of that, however good your software is, and any vendor who promises you otherwise I’d treat with suspicion. What you do control is that one stretch: the time between done and invoiced. Sheet wrapped up on site, signature and all, billable that same day. I’ve never needed more of a business case than that to build the thing.

so is going digital always a win?

No. Anybody who says it is has never watched a form get built badly. And I’ve seen both sides of this from up close. That first digital setup was the custom platform I just described: all of it digital, and still a mountain of explaining, training, searching. So after that I built a proper field-service tool. The engineer opens his phone and the very first thing sitting there in front of him is the mobile view of his own schedule. He can swipe through it: right, I’ve got these three jobs today. They only see today’s work; the full calendar’s in there too, two taps away. Open a job and it walks you through a step plan. You see the location straight off, today’s route, the checklist, and the materials list for the entire day, so all the job sheets rolled together: three job sheets, and you see every bit of material you have to load in that morning. Heading off from the shop, they flag it right there. It’s just something they carry alongside the workday, and every single time they open the app they drop back into that same view. When it went live, honest, the engineers were genuinely pleased with it. The old system had to be taught, it took a lot of explaining. This one, far less. It felt like a natural thing: open the app and have every button right there in front of you, one screen, clear and tidy.

Now flip it round. If the app starts forcing more required fields than an engineer ever filled in willingly on paper, the burden doesn’t vanish. It just shifts. From the kitchen table at night to the customer’s doorstep, where it stretches the visit out longer. The sector warns about exactly this. In Techniek Nederland’s own digitalization program it comes out as “we do not make a form for the sake of making forms” (Techniek Nederland, 2024). That’s the bar I hang over my own forms: whatever the law or the invoice doesn’t ask for, it doesn’t get in.

And there’s a second thing going on here, one the brochures almost never touch. The Wet kwaliteitsborging voor het bouwen, the Dutch building quality assurance act, has been demanding a good deal more file-keeping and evidence per project since 2024. So part of all this digitalizing in the sector is just keeping pace. You’re logging new obligations. You’re not shedding the old clutter with it. And those extra fields eat right back into your gain. Reason to skip it? No. Reason to build soberly, and to keep the fields the law demands strictly apart from the ones you happen to find handy.

One bright spot is buried in those same numbers, mind you. If seventy percent of the inflow has to come from outside the sector, then the crews of tomorrow are going to be mostly people without decades of paper habit stacked up behind them. To them, the phone just is the tool. So the harder the shortage bites, the smoother this whole shift gets, not the other way round. Thin consolation, I know. But a real one, and it’s got a practical edge to it.

where do you start?

In the order I go about it myself. First, the baseline, and it’s the dullest bit right off the bat: a week spent tallying how much time your engineers and your back office lose to sheets, to retyping, to chasing calls, plus how many days on average sit between done and invoiced. Nobody thinks that’s fun work. But it hands you the one number you’ll actually have any use for later, so I never skip it.

Then, and only then, completion on site. Tick off the tasks, snap photos instead of writing paragraphs, take the customer’s signature right there on the screen. Done is done.

The step after that is the one I care about most, and it’s exactly why I kept banging on about the payment chain up top: hang the job sheet on the invoice, so finished lands as billable. The days you claw back there are the only days in the whole chain that are actually yours.

And stay ruthless about fields. Whatever the law and the invoice don’t ask for, out it goes. Any bit of digitalizing that leaves the form fatter than the paper ever was is a step backward with an app icon slapped on it.

And yes, I’ve got a stake in this, so weigh it accordingly: building this stuff is my job. For that same company, right alongside the job sheet flow, I also built a customer portal where customers book in their own breakdowns and maintenance, which again saves on phone calls and admin. But the arithmetic up above stands entirely apart from what I sell. Tally your week, wrap up on site, hang the sheet on the invoice, keep the form sober. The sum keeps adding up whichever system you land on. Whoever you end up buying it from.