Configured to your project
Permit & Isolation Suite
Permit lifecycles, multi-energy isolations, switching where included, and the site controls that support each handoff.
Permit offices, supervisors, isolation teams and work crews
PermitSync software
Start with the work your team needs to control.
Choose the scope around your permits, energy controls and safety records. Agree the modules, roles and site procedures together, with Quality & Completions in development for the next stage of the project lifecycle.
Explore the suites
Three areas of work. One clear place to start.
Explore the current software scope and the forthcoming suite. Inclusions and operating arrangements are confirmed for your project before rollout.
Explore the suite
Configured to your project
Safety & Assurance Suite
Work-method records, personal field checks, hazards, incidents, inspections and the actions that follow.
Field teams, safety professionals, reviewers and action owners
Coming soon
Quality & Completions Suite
Planned inspection and test plans, equipment-specific test records, completion evidence and project handover.
Planned for inspectors, engineers, construction and commissioning teams
Standalone or connected
Match the configuration to the work.
A safety-focused scope can be configured without the full permit-to-work lifecycle. Connected configurations bring enabled work controls into a shared project context. These are configuration paths; your proposal confirms the actual inclusions.
| Your starting point | Scope to discuss | What to confirm |
|---|---|---|
| Safety-focused workspace | Safety records, team and site context, with isolation controls where included. | Workflows, client procedure mapping and acceptance without the full permit lifecycle. |
| Permit & Isolation | Permit lifecycle, isolation dependencies, site coordination and supporting evidence. | Permit types, responsibilities, interfaces and enabled safety records. |
| HV switching scope | Switching programs and their isolation, authority and execution records. | Package inclusion, appointed roles and relationship to your permit process. |
| Quality & Completions Coming soon | Planned inspection, testing, completion and handover records. | Future requirements only. Not included as an available operational suite. |
Software access, implementation and training, specialist personnel, hardware and custom integration work are separately scoped. You can use your own competent people and existing hardware.
Shared foundations
Manage the team and project around the work.
Shared context depends on the modules enabled for your organisation. Confirm responsibilities and access before bringing people into the workspace.
People and responsibilities
Scope team invitations, roles and access for your employees and contractor teams. Administrative access remains separate from client-appointed authority to authorise work.
Sites and configuration
Agree site setup, terminology, templates, workflow configuration and who maintains each part. PermitSync implementation support is scoped around that agreement.
Records and oversight
Agree the assets, documents, registers, history and outputs your enabled modules need to share. Include acceptance checks, training and support responsibilities in the rollout.
Working with other systems
Scope the connection before promising the integration.
Connections between PermitSync modules are different from connecting to another provider's software. Asset-management, mapping, identity and other external systems need a separate discussion of interfaces, licensing, access, data ownership and testing.
Tell us which systems you use and the information that needs to move. We will assess the integration scope before confirming a solution.
Start with the work
Bring one real workflow to the conversation.
Tell us the work, people, sites and evidence you need to manage. We will help define a suitable software and implementation scope.