Permit-to-Work Navigation
Permit-to-Work Navigation helps authorized employees and contractors identify whom to ask about a proposed job and which approved process to verify. It is a routing aid, not a permit or work authorization.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Utilities · Oil and gas · Manufacturing · Infrastructure and facilities operations
Overview
Permit-to-Work Navigation is a service page template for employees and contractors who need to identify the right authority to ask about proposed field work. Its fictional Northbank Utilities example contrasts a routine request within one managed asset boundary with work that interfaces with a specialist-controlled system. A comparison table makes the routing distinction visible: the authority to ask, the process to verify, and the scope that changes the route.
Use the page as an early navigation aid when a requester needs to describe work and find the operational owner who can confirm the governing approved process. The boundary-check examples address work within one asset, work that crosses an asset boundary, specialist interfaces, and scopes that do not fit the examples. A handoff section lists the information to provide: location and asset, proposed scope, known boundary crossings or dependencies, and any process reference found in an authorized source. The FAQ reinforces what to do when routes overlap or scope changes.
This template does not decide whether a permit is required, identify actual local authorities, define permit controls, or authorize work. Do not use it as a substitute for an approved procedure, a permit system, or advice from the responsible operational owner. Before publishing, replace the fictional routing examples with verified local roles and process names, confirm a correction route, and remove any statement that is not supported by local sources. Keep authoritative procedures at their approved home and link to them only when a valid destination is available.
Standards & compliance context
- Treat the page as a routing aid only; it does not establish permit requirements, approvals, or authorization to work.
- Have operational and compliance owners validate local process names and applicability against the organization's approved sources before publication.
- Preserve the scope qualifications in local procedures; do not infer jurisdiction or applicability from the fictional examples.
- Use accessible heading structure and readable comparison content so employees and contractors can distinguish the routes and their limitations.
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
Find the right permit authority
This introduction establishes who the page serves and makes clear that routing guidance does not authorize work.
-
For authorized employees and contractors coordinating field work Fictional example: Northbank Utilities uses this sample routing map to show how work category and specialist interfaces can affect who should be asked about a permit. Use the examples to identify the authority to contact and the governing process to verify. This page is a routing aid only: it does not authorize work, confirm that a permit is required, or replace an approved procedure.
Compare the work scope
The comparison shows how an in-boundary request and a specialist interface can lead to different authorities and processes to verify.
-
Illustrative Northbank examples only; local approved sources determine the actual authority and process. Illustrative scope Routine maintenance request within one Northbank-managed asset boundary Proposed work that interfaces with a specialist-controlled system Authority to ask Local asset permit issuer Designated specialist authority, coordinated with local operations Process to verify Northbank Asset Work Control process Northbank Specialist Interface Control process Routing distinction The example stays within one asset's stated boundary A specialist interface changes who must confirm the governing process
Check the boundary before routing
These examples help readers identify when to ask about asset boundaries, cross-area work, specialist involvement, or an unmatched scope.
-
Describe the proposed scope; do not infer authorization from a category match. Work stays within one asset If the request is clearly within one asset boundary and has no identified specialist interface, ask the local asset permit issuer which approved process applies. Work crosses an asset boundary If the scope touches more than one asset or operating area, ask local operations to identify the coordinating authority and confirm the governing process. A specialist interface is involved Name the known specialist system or team when contacting the designated specialist authority; ask how the interface affects the applicable process. Scope does not match an example Treat the example as insufficient for routing. Ask local operations or the relevant specialist authority to identify the right owner and approved process.
Questions about routing
These answers address ambiguous routes, scope changes, and the difference between routing and approval.
-
When uncertain, resolve the authority and process with the appropriate operational owner. The work does not fit either example. Which route should I use? Do not force the request into a category. Give local operations the location, asset, and proposed scope, including any known specialist involvement, and ask them to identify the responsible authority and governing approved process. Both a local issuer and a specialist authority seem relevant. Who decides? Ask local operations to coordinate with the relevant specialist authority and confirm which authority owns the routing decision. Do not assume one route replaces the other. The actual scope has changed since the request was described. Can I keep using the original route? No. A change in scope may change the applicable authority or process. Recheck the routing with local operations or the relevant specialist authority before relying on the earlier classification. Does this page or a matching example mean the work is approved? No. This page only helps identify whom to ask and which process to verify. Authorized local sources determine the governing procedure and any approvals required.
Make the handoff useful
This checklist helps requesters give the receiving authority the scope details needed to confirm the route and governing process.
-
When contacting the local asset permit issuer, local operations, or a specialist authority, provide: The work location and asset or interface involved. A concise description of the requested scope and any known boundary crossings. Known specialist systems, teams, or dependencies. The process reference you believe may apply, if one is available in an authorized local source. Ask the receiving authority to confirm the responsible issuer and governing approved process. Follow the authorized local sources for the actual requirements; this routing page does not establish them.
How to use this template
- Replace the fictional Northbank examples with confirmed local asset boundaries, authority roles, and approved process names.
- Ask the responsible operational owner to verify each route and provide a practical help or correction path for uncertain cases.
- Publish the page where authorized employees and contractors can find it before they need to route proposed field work.
- Have requesters describe the location, asset, scope, boundary crossings, and known specialist systems when contacting the relevant authority.
- Ask the receiving authority to confirm the responsible issuer and governing approved process using authorized local sources.
- Recheck the route whenever the work scope or known interfaces change, and update the page when local ownership or approved process references change.
Best practices
- Label fictional examples clearly and replace them before presenting the page as local guidance.
- Name authorities by confirmed role rather than hard-coding an individual's name.
- Keep the distinction between authority to ask and process to verify explicit in every route example.
- Tell requesters to include location, asset, scope, boundary crossings, and known specialist dependencies in the handoff.
- Direct readers with unmatched or overlapping scopes to local operations or the relevant specialist authority instead of implying a default route.
- Reassess routing when the actual scope changes, even if an earlier request was classified.
- Keep the approved procedure at one authoritative location and add only confirmed links to it.
- Assign an operational owner to review the page when authority roles, asset boundaries, or process references change.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
Who should use this permit-to-work navigation page?
It is for authorized employees and contractors coordinating proposed field work. Use it to prepare a routing question for local operations, a local asset permit issuer, or a relevant specialist authority. It does not determine who is authorized to perform work.
How do I route work that does not match either example?
Do not force the request into a sample category. Give local operations the location, asset, proposed scope, and any known specialist involvement. Ask them to identify the responsible authority and governing approved process.
What if both a local issuer and a specialist authority may be involved?
Ask local operations to coordinate with the relevant specialist authority and confirm who owns the routing decision. Do not assume one route replaces the other. Verify the applicable process with the authorized operational owner.
How often should the routing be checked?
Recheck it whenever the proposed scope, location, asset boundary, or known specialist interface changes. The page does not set a permit review cadence or replace local requirements. Confirm the current route and process with authorized local sources before relying on it.
Does a matching example mean the work is approved or that a permit is required?
No. The examples illustrate routing distinctions only; they do not determine whether a permit is required or authorize work. The responsible authority and approved local sources determine the governing process and any approvals.
Does this template meet a specific regulatory requirement?
The page is a navigation aid, not a statement of regulatory compliance or a substitute for an approved procedure. Applicable requirements depend on the work, location, and organization. Have the responsible operational and compliance owners verify local wording and process references before publishing.
What should I customize before publishing this page?
Replace the fictional Northbank examples with confirmed local authority roles, asset boundaries, and approved process names. Have the operational owner verify every route and identify a help or correction path. Remove any example that does not accurately reflect local arrangements.
Can this page integrate with permit software or approve work?
The supplied page structure contains static example content and no configured live permit-system connection. It cannot issue a permit, submit a request, or approve work. If linking to an authorized system or process reference, add only a confirmed destination supported by your site setup.
What is the rollout pitfall to avoid?
Do not publish fictional routes as if they were company rules or leave old process names in place after local arrangements change. Validate the page with operational owners, label examples clearly, and give readers a route for resolving uncertain or changed scopes.
Related templates
Go deeper on the topic
-
A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Permit-to-Work Navigation ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
