When your app has to replace a lie.

Design · 5 min read

I was working on a safety compliance app for industrial workplaces. The kind of environment where someone does a welding job in a room full of chemicals and then has to go back and check the site 15 minutes later, then 30 minutes later, then an hour later, just to make sure nothing is smouldering. That's the process. It's required by the insurer. It's required by the safety standards. And under the old paper system, people just ticked a box and said they did it.

They didn't go back. They ticked the box, handed in the form, and left site. Nobody checked. Nobody could check. The form said it happened, and that was the end of it.

That's the lie the app had to replace.

Paper lets people cheat

Look, I'm not saying workers are dishonest. Most of them aren't. But paper systems rely entirely on trust. There's no verification. There's no timestamp that proves someone was physically present. There's no photo that shows the site was actually inspected. It's a checkbox on a form and a signature at the bottom. That's it.

In industries where safety is the whole point, that's a problem. Not because people want to cut corners. Because the system makes it easy to cut corners. And when people are tired, running late, or just trying to finish and go home, easy wins. Every time.

The client I was working with had seen it happen over and over. Workers would sign off on safety checks without doing them. Not out of malice. Just because the paper system had zero accountability built in. The process existed on paper but not in practice.

Enforcement by design

So we designed the app to make the lie impossible. Not difficult. Impossible. The worker has to take a timestamped photo at each check interval. The app won't let them progress to the next step without it. If they miss a check, the system flags it immediately and the site manager gets a notification. There's no box to tick. There's evidence or there isn't.

That's what I call enforcement by design. The app doesn't ask the user to be honest. It makes honesty the only way through the flow. You can't skip a step. You can't backdate a check. You can't say you were there when the system knows you weren't.

This is a fundamentally different design problem from most apps. Most apps are designed to be flexible. To give users options. To get out of the way. This app had to do the opposite. It had to be rigid on purpose. The constraint was the feature.

When trust isn't enough

If your app is replacing a manual process in a regulated industry, ask yourself this. Is the current system working because people follow the rules? Or is it working because nobody has checked whether they do? Those are very different situations. And the answer changes everything about how you design the app.

In our case, the answer was clear. The insurer wanted proof. The site managers wanted visibility. And the workers needed a system that protected them too, because a timestamped record of every check they completed is also evidence that they did their job properly. That's the thing people don't always see. Enforcement by design protects honest workers just as much as it catches the ones who aren't.

If you're building an app that replaces a paper process, don't just digitise the form. Ask what the form was hiding.

Sources
Permits to Work (Safe Work Australia) - Guidelines on managing workplace safety through permit systems.
Forcing Functions in UX Design (Nielsen Norman Group) - How design constraints prevent user errors and enforce correct behaviour.

Related blog posts:

Compliance isn't a feature →

The accountability gap →

One app, three users: permission layers →