Skip to content
Profile & journal2026
Back to the blog

Safety permits: what I focus on when managing the procedure

From supervising safety permits to managing the Safety Department: clear requirements, accurate follow-up, and linking field information to the application.

A safety helmet above a trail of permit papers and the boundary of a construction site, in a 1960s print style
AI-generated editorial illustration in a 1960s style; it does not document a real site or event.

I worked as Safety Permits Controller, Farwaniya Governorate, from 2021 to 2024, and since 2024 I have led the Safety Department in Mubarak Al-Kabeer Governorate. In this professional reflection I start from that career sequence to discuss three aspects I consider essential in managing the procedure: clear requirements, connected information, and the ability to follow up.

Clarity starts before the application is submitted

When applicants understand what is required of them, communication becomes more focused. That is why the list of documents should be tied to the type and status of the application, and comments should be written in language that describes what is missing and explains how to complete it. A general phrase such as "please review" leaves a lot of room for interpretation, whereas pointing to a particular document and a specific field makes the next step clear.

Inside the organisation, staff also need a clear reference. Requirements can differ depending on the subject or stage of the application, so the context of the case should appear next to the data. Updates to guidance text should happen at the same time as updates to the procedure, so that the screen and what actually happens at work stay in step.

Field information in the right place

My preference is to organise comments, photos and attachments around a specific site, application and date. A standalone photo may be visually clear, but it lacks context unless we know what it documents, when it was taken and how it relates to the comment. The technical review should stay with the specialist, while the information that helps them do their job is made available.

In any digital development in this area, I put the work states first, for example: application received, under review, completion of missing items, and the next action according to the approved path. The benefit is that at every transition we ask: what is the condition, who is responsible, and what information must be kept?

Follow-up that helps the work

A monitoring dashboard needs to show where things are held up and why, not just the total number of applications. I want to distinguish between internal waiting and waiting for a document from the applicant, and between a routine case and one that needs special review. That way the numbers become a means of distributing and understanding the work, rather than merely a comparison between different volumes of applications.

As for AI, I see it as a potential aid in sorting attachments, summarising comments and finding related information. When proposing its use, the results should be tested on suitable examples, with the original text and attachment kept available for review. Service quality here is made up of an accurate procedure, ease of understanding and continuity of follow-up, all together.