Permit to Work at Your Site, Part 2: The Self-Service Model

Not every job needs a second set of eyes before work can start. On many sites, waiting on a central reviewer for each permit can slow things down without adding real safety value. That's where the self-service model comes in.

The Self-Service Model – what is it?

For lower-risk, high-frequency work, the self-service model runs like this:

1. Notification – A worker or contractor notifies the system what work they're doing and where, rather than waiting for a permit to be written for them.
2. Guardrails – The system checks competency, location, and risk level automatically, and flags anything that needs closer attention.
3. Risk-based inspection – Instead of reviewing every notification, the safety team focuses their time on the highest-risk locations and spot checks.
4. Execution – Work proceeds under the self-issued permit, visible and traceable on site, exactly as in the request model.
5. Close-out – The permit is closed by the worker, with the full record logged.

The strength of this model is speed and efficient use of everyone's time without losing control.

In Gate Apps, self-service isn't a separate product, it's the same permit engine with different rules applied. You set the competency requirements, the risk thresholds, and the escalation triggers, and the system enforces them consistently, every time.

At Meyer Turku shipyard, this shift changed the entire operating model. Where firefighters once wrote hundreds of permits every morning before work could begin, they now review only a few dozen a day, even with 500–600 active permits at any given time, because most work is simply notified into the system, with the fire department's attention focusing on the riskiest locations.

As Deputy Fire Chief Ville Rahkala put it, "the whole worker network has been happy with the change, no more waiting for permits, and we save a great deal of time."