A credible lightning safety policy reads like a playbook, not a poster. It blends statutory duties with site realities, turns risk appetite into rules, and sets out who does what when clouds build. The goal is simple. Fewer shocks to people, assets, and continuity. The path needs rigour, repetition, and clear language grounded in recognised standards.
Anchor to recognised standards
UK organisations should base governance on BS EN 62305, which frames protection across principles, risk assessment, physical safeguards, and surge control for internal systems. This suite superseded BS 6651 and remains the reference point for method, documentation, and periodic review. Treat it as the skeleton for your policy and the yardstick for audit.
Define scope and duty of care
Set policy scope for people, buildings, temporary structures, and connected services. Reference the Health and Safety at Work Act duties for outdoor workers and event operators, with attention to risk assessment and control measures where exposure is predictable. Embed accountability across operations, estates, procurement, and incident command.
Build a risk model that fits your estate
Structure a Lightning risk assessment process aligned to BS EN 62305 Part 2 with inputs on occupancy, structure class, service lines, and tolerance for downtime. Record tolerable risk, then specify measures to reduce actual risk below that threshold. Document reasoning for each protective measure across structural air termination, bonding, earthing, and surge protection devices.
Standardise practical protection rules
Translate assessment outputs into rules people can follow. For outdoor works and events, list safe shelters, publish suspension and resumption criteria such as the 30/30 rule, and define alerting and crowd movement methods. For indoor safety, specify surge protection practice, isolation of vulnerable equipment, and restrictions on water use and corded phones during storms. Clarity beats slogans.
Integrate Lightning software into workflow
Lightning software can streamline repeatable calculations, document versioning, and reporting. It should support BS EN 62305 methodologies, provide traceable inputs, and output audit-ready records that align with procurement and maintenance schedules. Treat the tool as part of the control system, not a substitute for engineering judgement or statutory testing.
Plan for temporary structures and events
Temporary stages, towers, and marquees need focused guidance. Use pre-event risk reviews, named decision makers, and a communications plan that reaches contractors and crowd managers. Reference sector guidance for outdoor events and align suspension triggers with public address messages and steward actions. Practice the script before the season starts.
Make maintenance non negotiable
Set inspection and testing intervals that meet BS EN 62305 expectations. Require annual tests for structural systems and surge protection checks after alterations or severe weather. Log earth resistance measurements, connection integrity, and visible condition of terminations. Repairs should follow the standard and be recorded with photographic evidence.
Train for action under pressure
People remember drilled actions. Teach teams to recognise storm proximity, move to safe structures, and avoid conductive pathways such as metal rails, plumbing, and exposed water points. Rehearse shutdown steps for sensitive equipment and set criteria for work stoppage on rooftops and open ground. Short, scenario based sessions create muscle memory.
Address heritage and specialised sites
Historic fabric, archives, labs, and hazardous stores need tailored treatments. Combine protection of external fabric with internal surge management that respects the building’s character. Consult guidance for historic sites and ensure designs come from specialist practitioners with documented competence.
Write lean procedures and checklists
Keep procedures tight. One page quick guides for supervisors. Checklists for pre storm checks, during storm controls, and post event inspections. Link every step to a named role and a traceable record in the safety management system. Concision speeds compliance.
Procurement and assurance
Procurement should reference BS EN 62305 deliverables, competency criteria, and testing handover documentation. Independent inspection adds confidence for high consequence sites. Store certificates with the asset register and tie re inspection dates to automated reminders.
Communicate with plain language
People in the field do not speak in clauses. Use direct verbs. Shelter. Power down. Move the crowd. Publish a simple map of safe locations. Make the policy readable by those who carry it.
Where modern tools fit
Many organisations now pair in house engineering with Lightning software to cut clerical effort and keep records consistent. Some adopt specialist platforms such as the assessment tool LRA Plus from Skytree Scientific active vendor that focuses on standards aligned reporting and practical guidance for engineers. Treated quietly as a component in the process, such tools help teams keep assessments aligned with the policy rather than drive the policy itself.
Continuous improvement
Log incidents, near misses, and storm related faults. After each season, compare downtime, repair costs, and inspection findings against last year’s baseline. Feed lessons back into siting decisions, surge coordination, and training content. Policy lives when numbers change behaviour.
Practical checklist for policy owners
- Map assets, occupancies, and service lines with BS EN 62305 categories and target tolerable risk per site class.
- Define shelters, suspension criteria, and communication channels for outdoor work and events.
- Specify annual testing, SPDs maintenance, and post storm inspections with record keeping.
- Train supervisors and crews on concise storm actions and equipment shutdown.
- Use Lightning software to standardise documentation and align outputs with procurement and audits.
A policy that reads well is not the finish line. It is the start of a habit. Build the habit on the standard, teach it to the team, prove it in the logbook, and revisit it when the season turns.
