Working at Heights Permit
A Working at Heights Permit template for authorizing elevated work, checking fall protection, and confirming rescue arrangements before the job starts.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Construction · Facilities Management · Manufacturing · Utilities · Telecommunications
Overview
This Working at Heights Permit template is used to authorize elevated work before anyone starts climbing, lifting, or accessing a fall-risk area. It captures the job details, the planned date and time, the height involved, the access method, the condition of the work area, the fall protection system in use, anchor point verification, hazards, weather, rescue readiness, and the final approval record.
Use this template for planned tasks where a fall hazard must be reviewed before work begins, such as roof access, ladder work, scaffold tasks, platform maintenance, or exterior repairs. It is especially useful when multiple people need to confirm the same controls before the job starts and when you want a clear audit trail of who approved the work and under what conditions.
Do not use it as a generic job ticket or for ground-level work with no fall exposure. It is also not a substitute for training, equipment inspection logs, or a site rescue procedure. If the task changes after approval, if weather becomes unsafe, or if the access method changes, the permit should be updated or reissued before work continues.
Standards & compliance context
- The template supports fall-hazard review and documented authorization practices commonly used to align with OSHA working-at-heights controls.
- The form structure supports WCAG 2.1 AA-friendly design when fields, labels, validation, and error messages are clear and keyboard accessible.
- Collect only the minimum necessary PII for the permit and emergency response to support GDPR Article 5 data minimization.
- If the permit is used in an HR or contractor intake context, include any needed ADA reasonable-accommodation prompts without requiring unnecessary medical detail.
- For any health-related rescue or exposure notes, keep information to the minimum necessary principle and avoid collecting sensitive details that are not needed for the permit.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Permit Overview
This section identifies the job, location, and work window so the permit is tied to one specific elevated task.
- Permit title
-
Work order or job number
Optional reference for internal tracking and audit trail.
- Site / area where work will be performed
- Description of work at height
- Planned work date
- Planned start time
- Planned end time
Work at Height Details
This section confirms whether the work truly involves a fall hazard and how the worker will reach the area.
- Estimated work height above ground or lower level (feet)
- Does this work exceed the applicable OSHA fall protection threshold?
- Primary access method
- If other, specify access method
- Work area condition
Fall Protection and Equipment
This section records the protection system, inspection status, and anchor verification that make the job controllable.
- Fall protection system to be used
- Has all fall protection equipment been inspected before use?
- Describe any damaged, missing, or out-of-service equipment
- Have anchor points been verified for strength, compatibility, and location?
-
Anchor point details
Include anchor location, attachment method, and any engineered or approved anchorage information.
Hazards and Controls
This section captures site conditions and the controls that reduce exposure before anyone starts work.
- Known hazards at the work location
- Other hazards
- Control measures to prevent falls or dropped objects
- Are weather and surface conditions acceptable for the planned work?
- Weather or surface condition notes
Rescue and Emergency Plan
This section proves there is a practical retrieval plan if a worker is suspended, injured, or unable to self-rescue.
- Is a rescue plan in place for a fall event?
- Primary rescue method
- If other, specify rescue method
- Are trained rescuers and required equipment available on site?
-
Emergency contact number
Use the site emergency number or control room contact.
Authorization and Acknowledgment
This section creates the approval record and confirms the requestor understands the permit conditions before work begins.
-
Permit requestor name
Enter the name of the person requesting the permit.
- Requestor role
- Approving supervisor name
- Permit approval status
- Approval conditions or restrictions
- I confirm the information provided is accurate and work will not begin until all controls are in place.
How to use this template
- Enter the permit title, work order number, site location, work description, and planned work window so the job can be identified without ambiguity.
- Record the work height, confirm whether the height threshold is met, and select the access method that matches the actual task, using the other field only when needed.
- Document the fall protection system, confirm equipment inspection status, note any defects, and verify the anchor point with enough detail for a reviewer to assess it.
- List the hazards present, add site-specific control measures, and record whether weather conditions are acceptable for the planned work.
- Complete the rescue and emergency plan, then have the supervisor review the permit, set any approval conditions, and capture the requestor acknowledgment before work begins.
Best practices
- Use conditional logic so ladder, scaffold, roof, and lift jobs only show the fields that apply to that access method.
- Mark required versus optional fields clearly, and keep nonessential PII out of the permit unless it is needed for the job or emergency response.
- Record the actual anchor point location or identifier, not just "verified," so the approval has a usable reference.
- Photograph equipment defects and unsafe work area conditions at the time of review when your site process allows attachments.
- Stop the permit and re-review it if weather, access method, or work scope changes after approval.
- Keep the rescue method specific to the site, including who will respond and how the worker will be retrieved.
- Use plain language for hazards and controls so the permit is understandable to the crew, supervisor, and rescue team.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
When should I use a Working at Heights Permit?
Use this permit any time a task will be performed above the applicable height threshold or where a fall hazard exists, even if the job is short. It is meant for planned elevated work such as roof access, ladder work, scaffold tasks, or platform maintenance. If the work can be done from the ground, this permit usually is not needed.
Who should complete and approve this permit?
The requestor should complete the work details, hazards, and equipment fields, then a supervisor or other authorized approver should review and sign off. The person approving should understand the site, the access method, and the rescue plan before work starts. In higher-risk settings, a competent person or safety lead may also need to review it.
How often do I need a new permit?
Create a new permit for each job, shift, or work location change unless your site procedure explicitly allows a longer permit window. If the weather changes, the access method changes, or the hazard profile changes, the permit should be rechecked and updated. A permit should not be reused as a standing approval for unrelated work.
What should be included in the rescue plan section?
The rescue plan should state how a worker will be retrieved if they are suspended, injured, or unable to self-rescue. Include the rescue method, whether a rescue team is ready, and the emergency contact number. Avoid vague entries like "call for help" because the permit should show a practical, site-specific response.
What are the most common mistakes when using this permit?
Common mistakes include leaving the anchor point field blank, marking equipment as inspected without noting defects, and approving work without checking weather or access conditions. Another frequent issue is treating the rescue plan as optional. The permit works best when each field is completed with specific, job-level information.
Can this template be customized for ladders, scaffolds, or roof work?
Yes. The access method, hazards, and control measures fields are designed for conditional logic or branching so you can tailor the permit to ladders, lifts, scaffolds, roofs, or other elevated work. You can also add site-specific controls such as tie-off requirements, exclusion zones, or spotter checks.
How does this fit with other safety systems or integrations?
This permit can be linked to work orders, maintenance requests, incident reporting, and training records so the approval trail stays connected. Many teams also route it to supervisors, safety managers, or contractors for review before work begins. Keeping the permit tied to the job record helps preserve the audit trail.
Is this better than using an ad-hoc checklist or email approval?
Yes, because it standardizes the fields that matter most: height, access method, fall protection, anchor verification, hazards, weather, and rescue readiness. Ad-hoc approvals often miss one of those items or leave no clear record of who approved the work. A permit creates a consistent review path and a clearer audit trail.
Related templates
Go deeper on the topic
-
A standard operating procedure (SOP) is a documented, step-by-step procedure for a repeatable task — the written version of "how we do this here." Good SOPs...
-
Workforce management (WFM) is the operational discipline of getting the right employees, with the right skills, in the right place, at the right time — and...
-
A daily huddle is a brief (10–15 minute) standing meeting held at the start of a shift or workday to align the team on priorities, surface issues, and...
-
A deskless worker is any employee whose job happens without a desk, a company laptop, or a fixed workstation. They're roughly 80% of the global workforce —...
-
MangoApps NoCode Workflow Apps let teams build, customize, and deploy employee apps without IT—automating workflows and boosting operational efficiency fast.
-
Compare 9 top shift scheduling platforms for 2026—features, pricing, and workforce fit for frontline, retail, healthcare, and enterprise teams.
-
MangoApps refreshes its brand and logo to power AI-first frontline work with a unified workforce platform that keeps teams aligned daily
-
Gallup 2026 workplace report reveals falling engagement, manager burnout, and $10T losses—actionable HR insights for leaders.
Ready to use this template?
Get started with MangoApps and use Working at Heights Permit with your team — pricing built for small business.