Before any approval, any hazard check, or any sign-off, every Permit to Work starts with a single moment: someone raises the application. In most PTW systems, this first stage has a name — PTW Day 0 — and how well it’s filled in decides how smoothly everything that follows will go.
This guide explains what PTW Day 0 actually covers, why it’s treated as its own stage rather than folded into the general request process, and what a well-structured Day 0 form should include.
What Is PTW Day 0?
PTW Day 0 is the applicant stage of a Permit to Work: the point where a worker, supervisor, or contractor first submits a request to carry out a task, before any hazard assessment or approval has taken place. The “Day 0” label comes from how permit lifecycles are usually tracked day by day, from the day the application is raised (Day 0) through active work and eventual closeout.
Because it’s the entry point, PTW Day 0 sets the baseline for everything downstream. A hazard checklist, an approver’s review, and an isolation authority’s sign-off all depend on the details captured at this stage being accurate and complete.
Why the Day 0 Stage Matters
Treating PTW Day 0 as a distinct step — rather than a single field buried inside a longer form — matters for a few reasons:
- It creates a clean starting record. A Day 0 form is timestamped and numbered the moment it’s submitted, which becomes the anchor for every later approval, revision, and closeout entry tied to that permit.
- It filters incomplete requests early. A Day 0 stage that requires work activity details and supporting attachments upfront stops an under-specified request from reaching an approver, who would otherwise have to send it back and restart the clock.
- It separates “requesting” from “approving.” Keeping Day 0 as the applicant’s stage — distinct from the safety officer’s review that follows — makes the approval chain easier to audit, since each stage has a clear owner.
What Goes Into a Day 0 PTW Application
A well-structured PTW Day 0 form usually captures the same core information, regardless of the permit type (hot work, confined space, working at height, demolition, and so on):
Company and Applicant Details
The applicant’s company name and contact details, so the permit is tied to a specific organization from the outset — important on multi-contractor sites where several companies may be working under the same project.
Work Activity Details
A description of the actual task — for example, welding activities for a hot work permit, or breaking and clearing work for a demolition permit. This is the field an approver reads first, so vague descriptions (“general works”) are a common cause of a Day 0 application being sent back.
Supporting Attachments
Photos, drawings, risk assessments, or method statements attached at Day 0 give the approver the context they need without a separate back-and-forth. Some PTW systems make at least one attachment mandatory before the form can be submitted.
Auto-Generated Form Status and Form Number
In most digital PTW systems, the form status (“autofill”) and form number are generated automatically the moment a Day 0 application is created. This removes a manual numbering step that’s easy to get wrong on paper, and it’s what every later stage references.
Real-World PTW Day 0 Use Cases
What goes into a PTW Day 0 form shifts slightly depending on the type of work being requested. Here’s how the Day 0 stage plays out across common permit types:
Hot Work (Welding, Cutting, Grinding)
A hot work Day 0 application typically names the specific activity — “welding activities” rather than “hot work” alone — plus the exact location and any nearby flammable materials. Because hot work carries a fire risk, most systems won’t let the Day 0 form move forward without at least one supporting attachment, such as a fire watch arrangement or a site sketch.
Masuk Ruang Terbatas
Here, the Day 0 stage needs to capture the space being entered, the entry and exit points, and whether atmospheric testing has already been arranged. Since a gas tester or isolation authority signs off later in the lifecycle, an incomplete Day 0 description of the space itself is one of the most common reasons this permit type gets sent back.
Bekerja di Ketinggian
A working-at-height Day 0 application usually needs the height involved, the access method (scaffold, MEWP, rope access), and the fall protection equipment that will be used. Attaching an inspection record for that equipment at Day 0 — rather than producing it only when asked — is what keeps this permit type moving quickly through approval.
Pembongkaran
Demolition permits carry some of the highest risk in a PTW system, so the Day 0 form tends to ask for more upfront: the structure or section being demolished, the method (manual, mechanical, or controlled), and a clear boundary for the work area. A Day 0 submission tagged simply “Demolition” with a one-line activity description is a common source of delay here, since approvers need the method and boundary to assess the request properly.
Excavation Work
For excavation, the Day 0 stage should flag whether underground services (cables, pipelines) are present in the area, since this determines whether a separate utility clearance is needed before approval. Capturing this at Day 0 — instead of discovering it during the site visit — avoids a permit being paused mid-review.
Multi-Contractor Sites
On sites where several contractors work under one project, the company and applicant details captured at PTW Day 0 matter as much as the work activity itself. A Day 0 form that clearly identifies which company is requesting the work — not just which crew — keeps responsibility traceable when multiple permits are active in the same area at once.
Common Day 0 Mistakes That Delay Approval
Most delays in a PTW lifecycle can be traced back to the Day 0 stage. The recurring issues are:
- Work activity descriptions too vague for an approver to assess risk from
- Missing or incomplete attachments (no risk assessment, no site sketch)
- Company or applicant details that don’t match the site’s contractor records
- A permit type selected that doesn’t match the actual work, which routes the request to the wrong approval chain
Each of these sends the application back to the applicant, resetting the approval clock — which is exactly what a clear, well-designed Day 0 form is meant to prevent.
How Digital Tools Streamline the Day 0 Stage
A digital PTW system handles Day 0 differently from a paper form: work activities and attachments are structured fields rather than free text scrawled in the margins, the form number and status are generated automatically, and the submission routes straight into the approval workflow without anyone needing to carry a paper copy to the site office.
PEER’s HSE Permit to Work module builds the Day 0 application around exactly this structure, so a submission is complete and routable the moment it’s raised. For a broader look at how Day 0 fits into the rest of the permit lifecycle — hazard assessment, multi-level approval, active monitoring, and closeout — see Electronic Permit to Work System: How It Works and How to Implement It.
FAQ
Is PTW Day 0 the same as the permit request stage?
Yes — “Day 0” and “permit request” refer to the same applicant-side stage of a Permit to Work, before any hazard review or approval has taken place.
Who fills in a PTW Day 0 application?
Usually the worker, supervisor, or contractor who needs to carry out the task. On larger sites, a project admin may submit it on the crew’s behalf.
Can a PTW Day 0 application be edited after submission?
This depends on the system’s configuration. Many digital PTW tools allow an applicant to revise a Day 0 submission if an approver sends it back, without having to start an entirely new form. Regulatory bodies such as the UK’s Health and Safety Executive treat this kind of clear, documented request-and-revision trail as part of what makes a permit to work system auditable.
Kesimpulan
PTW Day 0 isn’t just paperwork — it’s the stage that decides whether everything downstream moves quickly or gets stuck in back-and-forth. A Day 0 form that captures clear work activity details, the right attachments, and accurate company information gives approvers what they need the first time, which is ultimately what keeps a permit to work lifecycle moving.
