Template-driven permit requests
Create repeatable permit workflows from dynamic safety templates, filtered by module and locked to the right version for each submission.
Safety module
Permit-to-work control for live site risk
SiteGrip digitises permits from request to closure so main contractors and subcontractors can manage high-risk work with defined approvals, live status control, and complete evidence across the shift.
What teams get with permits
Controlled status lifecycle
Move permits through draft, requested, approved, active, suspended, closed, expired, or rejected states with clear business rules.
Location-aware coordination
Tie permits to project locations, zones, and work windows so supervisors can see exactly where high-risk activities are happening.
Linked safety evidence
Attach hazards, controls, PPE, emergency procedures, and optional RAMS references so approvals are grounded in site context.
Permit feature stats
Snapshot from the safety module and workflow documentation to show how permits are structured in the product model.
Permit types
8
Hot works, confined space, excavation, electrical, lifting, roof work, and more.
Lifecycle states
8
Draft, requested, approved, active, suspended, closed, expired, rejected.
Core workflow stages
5
Request, review, activation, handover, and closure control in one flow.
Notification templates
4
Requested, approved, rejected, and closed communication events in the catalog.
Lifecycle built for site reality
- Draft for preparing the request before formal submission.
- Requested when the permit is locked and waiting for reviewer action.
- Approved once the work is authorised and ready to be activated.
- Active while the high-risk activity is live on site.
- Suspended if conditions change and work must pause safely.
- Closed after handover, inspection outcome, and closure signatures.
- Expired or rejected when the work window lapses or approval is denied.
Role-based accountability
- Project teams can view approved permits, while only authorised main contractor and safety roles can approve or reject requests.
- Subcontractor supervisors can request permits and close out their own work once the area is handed back safe.
- Every stage records who requested, approved, activated, rejected, or closed the permit.
Approval notifications
- Approvers receive permit-requested notifications with project, location, work type, and direct review links.
- Requesters are notified when permits are approved or rejected, with validity windows or rejection reasons included.
- The workflow keeps communication tied to the permit record instead of email-only side channels.
Live site controls
- Permit clash rules can be configured per project to reduce conflicting high-risk activities in the same location.
- Emergency cards can be generated for approved permits and are revoked automatically when permits are closed.
- Suspension and reactivation support temporary site changes without losing the audit trail.
Documented lifecycle map
Visual workflow summary based on the Safety Module specification lifecycle and transition branches.
Primary flow
Draft → Requested → Approved → Active → Closed
Approval branch
Requested → Rejected (resubmit required)
Active control branch
Active → Suspended → Active
Validity branch
Approved/Active → Expired when work window lapses
Governance and assurance
Audit-ready history
Permit numbers, timestamps, approval notes, rejection reasons, closure results, and signature events remain attached to one record throughout the lifecycle.
Permission-led workflow
The documented access matrix keeps approval and closure actions aligned with project role and safety responsibility, not informal site practice.
Green-light compliance
Permits sit alongside inductions and RAMS as part of the SiteGrip gatekeeping model for high-risk work before anyone proceeds on site.
Run permits with clear approvals and closure evidence
Give site managers, safety teams, and subcontractor supervisors one structured system for permit requests, authorisation, live status, and safe handback across every high-risk activity.