Good morning David. Shift brief: medium-voltage substation maintenance, Bergamo North, 07:30. Light rain until 11:00, 9°C. Yellow hydrogeological alert until 18:00. PPE: class E insulating helmet, dielectric gloves, S3 footwear, harness. Roadworks 1.2 km away, alternative SP41.
The field technician starts the shift with a safety brief specific to the zone.
Field Worker Safety Brief produces every morning the pre-shift safety brief for each utility or telco field technician. Weather conditions for the intervention zone, active civil protection alerts, personal protective equipment required for the scheduled intervention type. Daily traceability for occupational health and safety audit.
Field Worker Safety Brief at work.
Received. Taking SP41. PPE confirmed on board.
Confirmation recorded in the OHS audit registry. Safe shift.
Why it exists.
Field work for utility technicians (electricity, gas, water networks) and telco technicians (fibre, telephone network) carries specific risks: work on live equipment, work at height, work in zones with active roadworks, work in adverse weather. EU and national occupational health and safety frameworks require pre-intervention risk assessment and the use of PPE consistent with working conditions. Systematic coverage of conditions specific to each technician's intervention zone is often limited for technicians spread across large areas.
How it works pre-shift.
Field Worker Safety Brief activates pre-shift, typically thirty or sixty minutes before each technician's shift starts. For each technician it reads the scheduled intervention plan, retrieves the weather forecast for the specific zone (not a regional average), checks active civil protection alerts, identifies the PPE required for the intervention type based on company procedures. The brief reaches the technician on their work channel before they leave.
The decision stays with the field manager.
The agent provides the structured information. The decision to proceed, modify the intervention type, or postpone the shift stays with the field manager, following company procedures. The agent supports an informed decision; it does not replace it.
The teams that improve systematic safety coverage in the field.
Field technician
Receives the brief specific to their intervention zone directly on their work channel, without manually consulting multiple sources (civil protection website, weather app, PPE manual). The brief arrives before departure, personalised for the day's intervention.
Field manager and Health and Safety Officer
Have daily traceability of safety briefs sent and receipt confirmations. When an OHS authority audits, the registry is queryable by technician, by date, by intervention type.
Head of operations utility or telco
With tens or hundreds of technicians distributed across large regional areas sees systematic pre-shift safety coverage without delegating each zone manager to verify conditions for each technician's area.
A safety brief ready for every technician, every morning.
The agent starts at six. The shift starts at seven.
For a utility with eighty field technicians spread across five provinces, the agent activates every morning at six. The standard shift starts at seven.
Zone weather, alerts, PPE in under two minutes.
For a technician scheduled for a medium-voltage substation intervention in a hill zone, the agent retrieves in under two minutes the zone-specific weather conditions (not a regional forecast, but the forecast for the intervention coordinates), checks active civil protection alerts, identifies the PPE required by OHS procedures for medium-voltage work, and flags any available local notices (roadworks, access routes).
The technician confirms PPE on board. The event enters the registry.
The brief arrives on the technician's work channel — WhatsApp, Telegram, Slack, or HTTP depending on the utility's configuration — as a structured message readable in under thirty seconds. The technician replies with a receipt confirmation and PPE on board. The confirmation enters the audit registry with a timestamp. If a technician does not respond within a configurable time window, the field manager receives an alert.
Declarative rules from the Health and Safety Officer and field manager.
The rules of Field Worker Safety Brief are declarative. The Health and Safety Officer and field manager of the utility or telco define in a readable format the PPE required for each intervention type (medium- or high-voltage work, work at height, excavation work, fibre maintenance on poles), the rules for reading civil protection alerts, and the brief templates per intervention type. The rules live in the customer's repository, versioned. Weather data and civil protection alerts are retrieved from official public sources via an adapter configured during delivery.
- Language
- TypeScript (Node.js)
- LLM model
- customer's choice: Anthropic, OpenAI, Mistral, open source models hosted internally, AWS Bedrock for a private model
- Built-in controls used
- pii-detector, message-length-limit
- Native delivery channels
- WhatsApp, Telegram, Slack, OpenAI-compatible HTTP
- Scheduling
- configurable per instance (typical 30-60 minutes before shift start)
- Field service system integration
- dedicated adapter built during delivery by the Exelab team
- Weather data + civil protection alerts
- official public sources via adapter configured during delivery
- Memory
- persistent per instance
- Registry
- immutable, queryable with a standard SQL client (OHS audit inspectable)
How Field Worker Safety Brief works in detail.
No. The agent provides the structured information: weather conditions, active civil protection alerts, required PPE. The decision to proceed, modify the intervention type, or postpone the shift stays with the field manager, following company procedures. The agent supports an informed decision; it does not replace it.
The brief is delivered before departure, when the technician is still at base or in an area with connectivity. Receipt confirmation happens at the same time. If the intervention zone has poor coverage, the brief has already been received and confirmed before the shift starts. For specific situations, the system can also send via SMS through an adapter configured during delivery.
Yes, as long as the technicians are included in the shift plan of the customer's field service system. Brief configuration is based on the shift plan, regardless of the technician's contract type. Inclusion criteria are defined during configuration with the customer's Health and Safety Officer.
The typical pattern is 8-12 weeks. Discovery and intervention-type mapping two weeks, PPE rule and brief template configuration two to three weeks, field service system integration two weeks, pilot testing with a group of technicians and hand-off to the Health and Safety Officer two weeks. Actual duration depends on the complexity of the field service system and the variety of intervention types.
From a 30-minute conversation to the squad in production.
A 30-45 minute conversation to understand how Field Worker Safety Brief would configure to the customer's case. Number of technicians, field service system, intervention types that cover the priority PPE rules.