Digital Permit to Work in Singapore: A Practical Guide

A digital permit to work (ePTW) replaces paper permit pads with a mobile and web workflow that requests, assesses, approves, monitors and closes hazardous work, with a time-stamped record of who did what and where. In Singapore, the specification the Ministry of Manpower (MOM) publishes sets a clear bar: paperless permits, on-site location capture, workflows that cannot be skipped, and an audit trail. This guide covers what that means in practice, what to ask before you buy, and where site security fits in.

TL;DR

• A permit to work is a formal system for hazardous work. In Singapore it is expected for work at height where a fall of more than 3 metres is possible, and for confined space entry.
• A digital system only helps if the underlying process is sound. Digitizing a weak paper process gives you a faster weak process.
• MOM's ePTW specification calls for paperless permits, location capture, fixed approval stages, offline operation with later sync, and an audit trail.
• The Productivity Solutions Grant lists pre-approved ePTW solutions for the built environment sector. Check the current directory for support levels and eligibility.
• Training on the permit process, not just the app, decides whether the rollout works. Security and facility teams should be part of the design from day one.

Table of Contents

• What a digital permit to work actually is
• What Singapore requires
• The five-step workflow, digitized
• Where digitizing goes wrong
• What to ask before you choose a system
• Funding: the Productivity Solutions Grant
• Where site security meets permit control
• Our perspective
• How BeyondSensor supports permit-controlled sites
• A rollout plan that avoids workarounds
• FAQ
• Sources

What a digital permit to work actually is

A permit to work is a formal, documented system that states exactly what work is to be done, where, when, by whom, and under which precautions. The UK Health and Safety Executive describes it as a more formal control than ordinary instructions or procedures, used for work that needs extra care.

Historically these were paper forms, carbon copies and clipboards. An electronic version moves the same controls into software. The permit is created on a phone or tablet, routed to the assessor and approver, tracked while the work is live, and closed out when the area is handed back.

Two points separate a good ePTW from a scanned form:

1. The workflow is enforced, not suggested. A permit cannot jump from applicant to approver. Each stage must be completed by someone authorised to do it.
2. The record is evidence. Every change carries a user identity and a time stamp, so an investigator or auditor can reconstruct the sequence.

The people searching for "e-permit to work" or "electronic PTW system" are asking the same question in different words: can software do this reliably on a real site? It can, provided the process underneath is sound.

What Singapore requires

When a permit system is mandatory

The Workplace Safety and Health Council states that a documented permit-to-work system is necessary for hazardous work at height where employees could fall more than 3 metres, either from an elevated site or into a depth. The same guidance describes a standardised approach with defined responsibilities for the people who authorise, assess and supervise the work.

Confined spaces follow the same logic. The WSHC describes a confined space entry permit as a formal check that every element of a safe system of work is in place before anyone enters.

The WSH Code of Practice frames the aim of the system as a systematic, tiered authorisation for hazardous work. That tiering is what you are digitizing.

If you manage a site with several contractors, you may also run permits for hot work, electrical isolation or excavation. The same workflow logic applies to all of them.

What MOM's ePTW specification asks for

MOM's electronic permit-to-work specifications template is the most useful checklist a Singapore buyer can hold. In plain terms, it asks that the system can:

• Generate, submit and process paperless permits, with date, time, requester, assessor, approver, work location, description and photos.
• Capture the location of the mobile device, to show that creation, submission and approval happened on site.
• Run pre-set workflows that cannot be skipped, including observations, closure reports, verification and revocation.
• Restrict assessment and approval to authorised people, with safeguards against falsification.
• Keep an audit trail with time stamps and user identity for investigation.
• Send alerts to supervisors as a permit nears its expiry deadline.
• Let an authorised person revoke an issued permit if the work becomes unsafe.
• Operate without a live connection and synchronise once connectivity returns.

That last point deserves attention. Basements, tunnels, plant rooms and tanks are exactly where permits are needed and where signal is weakest. A system that stalls offline invites people to delay closing permits or to write them up afterward. Ask any vendor to demonstrate offline use on a device in airplane mode, not in a slide.

The WSHC also notes that for extended-duration work, permits are typically capped at a maximum of seven days with daily review. Your software should enforce that cap rather than rely on a reminder.

The five-step workflow, digitized

TÜV Rheinland describes an effective permit workflow in five stages: request, hazard assessment, approval with digital signature, active monitoring, and close-out or hand-back. Here is what each looks like when it is done well.

Stage	What happens	What good software adds
1. Request	Contractor describes the work, location and timing	Templates per work type, mandatory fields, photos, location capture
2. Hazard assessment	Competent person inspects and sets controls	Checklists tied to the work type, links to risk assessment
3. Approval	Authorised approver signs	Role-restricted sign-off, no skipping stages
4. Active monitoring	Work proceeds under the permit	Live status, expiry alerts, conflict warnings
5. Close-out	Work completed, area made safe and handed back	Closure report, verification, immutable record

Advanced systems go further. They connect to job safety analysis, lockout/tagout, and simultaneous operations (SIMOPS) conflict detection, so that incompatible tasks are not authorised at the same time. On a site with maintenance crews, contractors and security patrols moving through the same areas, that conflict check is often where the real safety gain sits.

Where digitizing goes wrong

The most common misconception is that going digital improves safety by itself. It does not. HSE's human factors guidance makes the point that a permit system works through the people who use it, and that designing it with end users matters. Overly complex systems push people toward workarounds.

Four failure patterns come up repeatedly.

1. Digitizing a bad process. If your paper permit has vague fields, unclear authority or inconsistent hand-back, software will reproduce those faults at speed. Fix the process first, then configure it.

2. Losing physical verification. When operators trust the screen, they can stop looking at the site. A green status is not a substitute for a competent person walking the job. Design the workflow so the assessor must confirm conditions on site.

3. Ignoring offline use. Covered above. It is the cheapest problem to test for and the most expensive to discover after go-live.

4. Training on the app, not the process. TÜV Rheinland notes that staff need training in the permit process itself, including hazard identification and risk assessment levels. Without that, you get 'garbage in, garbage out' data that fails the first time someone audits it.

Permits are one of several documented controls a construction site must keep audit-ready. Other site-level obligations, such as this construction mosquito control checklist, follow the same principle: if it is not recorded, it did not happen.

What to ask before you choose a system

Use this as a procurement checklist. It is built from the MOM specification and the failure patterns above.

• Offline mode. Can a user create, approve and close a permit with no signal, then sync cleanly?
• Location evidence. Does the system capture device location at creation, submission and approval?
• Workflow lock. Can any stage be skipped by an administrator or by the applicant?
• Competency control. Can you tie approval rights to training records, so only qualified people sign?
• Expiry and revocation. Are expiry alerts automatic, and can an authorised person revoke a live permit?
• Audit trail. Is the history immutable, exportable and retained long enough for your needs?
• Conflict detection. Does it flag overlapping or incompatible permits across areas and contractors?
• Integration. Can it exchange data with your access control, visitor management and monitoring systems?
• User testing. Did frontline supervisors and contractors test it before you signed?

Write down your own pass mark for each item before the demos. It keeps the decision on your requirements rather than on the best presentation.

Funding: the Productivity Solutions Grant

For built environment companies, the Productivity Solutions Grant has a pre-approved e-Permit-to-Work category. The listed solutions must meet specifications that include paperless permits, location capture, multi-stage approval workflows and an audit trail retained for at least five years.

Based on the directory's listings at the time of our research, support for SMEs can reach up to 50% of qualifying costs, and package prices range from roughly S$8,800 to S$24,000 depending on the number of projects covered. Those figures change, so confirm eligibility, support level and the current list of solutions on the directory page before you budget. A pre-approved listing also means the vendor has already been checked against the grant's specification, which shortens your own due diligence.

Where site security meets permit control

Most ePTW discussions stay inside the safety team. In practice, a permit is only as good as what happens at the gate, in the corridor and at the work location. That is where security and facility managers come in.

Industry practitioners describe the goal of ePTW as a single source of truth that removes silos between maintenance, security and operations. Here is what that looks like on a real site:

• Visitors and contractors. A permit names the people doing the work. The gate should know whether those people are expected, cleared and inside the permitted window. Screening at arrival, as covered in our note on visitor watchlist screening, keeps unplanned arrivals from becoming unplanned workers.
• Access rights. Permit approval should map to roles. Our guide to role-based access control covers how to keep authority aligned to training and responsibility.
• Zone awareness. A permit defines a work area. Geofencing alerts can tell the control room when people or vehicles enter or leave defined zones, which supports the on-site verification MOM's specification asks for.
• Environmental risk. Hot-weather work is a permit consideration on many sites. Our piece on heat stress monitoring looks at the 32°C rule for Singapore safety managers.
• Compliance evidence. Permits, patrol records and visitor logs together make the story an auditor wants. See our step-by-step compliance guide for how to structure that evidence.

None of this replaces an ePTW. It makes the permit more trustworthy by confirming, with sensors and records, that what the permit says matches what the site is doing.

Our perspective

We build sensing and security systems for sites across Singapore, Malaysia and the Philippines, and we see one pattern in permit-controlled environments: the paper or the app is rarely where control breaks. It breaks in the gaps between teams. The safety officer issues a permit, the security desk does not know, the patrol walks through a live work zone, and the contractor's crew brings an extra person nobody listed.

That is why we treat a digital permit to work as one layer in a connected picture, not a standalone tool. We do not present ourselves as a permit-to-work software vendor. Our role is the layer around it: knowing who is on site, where they are, whether patrols covered the areas that matter, and whether an exception needs a human decision. Exception-based monitoring suits this well. Software watches continuously, and people are pulled in when something does not match the permit. AI never blinks, but it also does not hold authority. Approval and accountability stay with named, competent people.

Our advice to security directors and facility managers is simple. Fix the process before buying software. Test offline behavior on your hardest site. Involve supervisors and contractors in the trial. Then connect the permit system to the systems that watch the perimeter, the gate and the patrol route, so the permit becomes a live control rather than a filed document.

— Eumir

How BeyondSensor supports permit-controlled sites

If you are a facility owner, system integrator or security team planning around an ePTW rollout, the surrounding security layer is where we can help.

• BeyondVisitor handles automated visitor management, so contractors and visitors are registered and cleared before they reach a work area.
• BeyondPatrol supports virtual guard tours, so patrol coverage of permitted zones is recorded.
• BeyondWatch provides AI-powered video analytics for monitoring sites.
• Our Solution Integration service helps connect multi-vendor systems into one operating picture.

Tell us about your site through the BeyondSensor homepage and we will map where your permit workflow meets your security controls.

A rollout plan that avoids workarounds

A realistic sequence for a single site or project looks like this.

1. Map the current process. Walk through a real permit from request to hand-back. Note where people wait, re-key data or phone each other.
2. Define roles and competency. List who can request, assess, approve and verify each permit type, and what training each role needs.
3. Write requirements from the MOM specification. Add your site-specific needs, such as integration and language support for crews.
4. Trial on one work type. Work at height or confined space entry are common starting points because the rules are clear.
5. Train on the process first, the tool second. Cover hazard identification and risk levels, then show the interface.
6. Run paper and digital in parallel briefly. Only for the pilot, with a fixed end date, to avoid permanent double work.
7. Review the audit trail. After a few weeks, sample permits and check that data is complete and times make sense.
8. Expand by work type and site. Add SIMOPS checks and integrations once the basics are stable.

Review results with the people who use the system daily. If crews are working around the software, the software or the process needs to change.

FAQ

Is a digital permit to work mandatory in Singapore?

A documented permit-to-work system is expected for hazardous work such as work at height with a fall of more than 3 metres and confined space entry. The WSHC guidance sets that expectation for the system, not for the format. Whether you use paper or digital depends on your project and any contract or grant conditions, so check the requirements that apply to your site.

What is the difference between ePTW and e-permit to work?

Nothing meaningful. Electronic permit to work, e-PTW, ePTW, e-permit to work and digital permit to work all describe the same idea: a paperless permit workflow with digital approvals and records. When comparing products, look at features such as offline operation, location capture and audit trail rather than the name.

Can an ePTW work without internet access?

It should. MOM's specification requires the system to function without a live connection and synchronise once connectivity is restored. Test this on your own devices in your own basement or tank area before committing.

Does the PSG cover electronic permit to work systems?

The Productivity Solutions Grant lists pre-approved ePTW solutions for the built environment sector, with support that can reach up to 50% for SMEs. Eligibility and amounts change, so confirm them on the PSG directory page before you apply.

How does a digital permit system connect to security?

The permit says who may work where and when. Security systems can confirm who is actually on site and in which zone. Linking visitor records, access roles and zone alerts to the permit gives the control room a way to spot work happening outside its permit.

Sources

• ANNEX B: Electronic Permit-to-Work Specifications Template, MOM
• Preventing Falls from Heights, WSHC
• Working Safely in Confined Spaces, WSHC
• Code of Practice, WSHC
• E-Permit-To-Work, PSG Grants
• An introduction to electronic permit to work systems, TÜV Rheinland Solutions
• Permit to work systems, HSE

Recommended

• Role-Based Access Control: A Practical Guide for Singapore Security Teams
• Heat Stress Monitoring for Singapore Safety Managers: The 32°C Rule
• Geofencing Alerts for Site Security: Setup Guide for Singapore
• Physical Security Tools Comparison for Singapore Facilities