- Home
- Smart meter field operations
- Pre-job brief app
Solution
Pre-job brief app for utility field crews, offline
PIEBENCH runs pre-job briefs, also called tailboards or job briefings, as a no-code workflow. The crew lead fills in the brief on Scout, an offline Android app: hazards, work procedures, energy source controls, PPE and special precautions, with each crew member's acknowledgement, a site photo, GPS and time. Supervisors review every brief, and the record stays with the job.
Who it's for: utility line and metering crews, the crew leads who run the brief, and the safety and operations managers who need a record that it happened. The workflow builder that creates the brief form is part of the Pro plan.
What OSHA requires in a job briefing
In the United States, OSHA's standard for electric power generation, transmission and distribution work, 29 CFR 1910.269, sets out the job briefing in paragraph (c):
- Before each job. The employer must ensure that the employee in charge conducts a job briefing with the employees involved before they start each job.
- What it covers. At least the hazards associated with the job, work procedures involved, special precautions, energy-source controls and personal protective equipment requirements.
- How often. For repetitive work, at least one briefing before the first job of each day or shift, and additional briefings if significant changes that might affect safety occur during the work.
- How deep. A brief discussion is enough for routine work the crew can recognize and handle by training and experience. A more extensive discussion is required if the work is complicated or particularly hazardous.
This page describes how to record a briefing. It is not legal advice; check the standard and your own safety program for what applies to your work.
Why paper tailboards fall short
Paper tailboard forms get filled in at the truck, signed, and put in a folder that nobody reads until something goes wrong. Then the questions are hard to answer. Was the brief held before the job started, or written up afterwards? Which hazards were discussed? Was there a second brief when the crew moved to a different structure? A paper form with no time or location can't say.
How a pre-job brief runs in PIEBENCH
- Build the brief form. In the no-code workflow builder, add the sections your safety program uses. A typical form is outlined below.
- Assign it with the work. The brief is a work order of its own, assigned to the crew lead for the job or the shift, so it sits next to the work it covers.
- Hold the brief at the site. The crew lead works through the form on Scout, with the crew, before work starts. It saves offline, with GPS and a timestamp.
- Record acknowledgement. Each crew member is ticked off in a checklist field as having attended and understood the brief.
- Brief again when things change. If conditions change, the lead submits a new brief, so there is a timestamped record of each one.
- Review. A supervisor or safety lead sees each brief in the approval queue, and can send it back with a note if a section is missing.
A typical pre-job brief form
| Section | Field type in the builder | Example |
|---|---|---|
| Job and location | Text, with GPS | Work order, structure number, GPS recorded automatically |
| Type of work | Dropdown | Routine, complicated, particularly hazardous |
| Hazards | Checklist | Energized lines, traffic, confined space, weather, dogs |
| Work procedures | Text | Steps agreed for this job |
| Energy source controls | Checklist | Lockout/tagout, grounding, isolation points confirmed |
| PPE requirements | Checklist | Arc-rated clothing, gloves, hard hat, fall protection |
| Special precautions | Text | Anything specific to this site |
| Crew acknowledgement | Checklist | One item per crew member |
| Site photo | Photo | The work area before starting |
| Crew size | Counter | Number of people on site |
Make any section required, and the brief can't be saved without it. Change the form when your program changes, and phones pick up the new version on their next sync.
Built for the job site
Offline-first. Many job sites have no signal. Scout saves the brief on the phone first and syncs it later, with the time and GPS of when and where it was actually filled in. See the offline field app.
Fast to fill in. Checklists and dropdowns mean a routine brief takes a few taps, which makes it more likely to be done properly every time. Scout is designed for gloved hands and bright sun, and runs on Android 7.0 and later.
Tied to the crew. Crew members check in for duty with a selfie and GPS, so the brief, the attendance record and the job sit together. See field attendance.
What PIEBENCH does not do yet
Be clear about two limits:
- No signature field. The builder doesn't have a signature field today, so crew acknowledgement is a checklist tick by the crew lead, not each worker's own signature. If your program requires individual signatures, PIEBENCH does not meet that yet.
- No ready-made template. You build the brief in the no-code workflow builder, usually from your existing paper form.
Dedicated job briefing and safety apps exist too, some with hazard libraries and individual sign-off. PIEBENCH fits best when you want the brief in the same app as the job itself: the pole inspection, the meter exchange or the repair.
Pro is $499/month, with users included. Plans start at $199/month, and the free trial needs no card. See pricing.
Built to integrate with your systems
HES, MDM, SAP IS-U, Oracle CC&B and billing systems, over REST, OAuth or a direct SQL connection. How integrations work
Questions buyers ask
What is a pre-job brief?
A pre-job brief, also called a tailboard or job briefing, is a short meeting the person in charge holds with the crew before work starts. It covers the hazards, work procedures, special precautions, energy-source controls and PPE for the job. In the US, OSHA 1910.269 requires one for electric power work.
Is there an offline pre-job brief app for utility crews?
Yes. PIEBENCH lets you build a pre-job brief form in its no-code workflow builder and fill it in on Scout, an offline Android app. The brief saves on the phone with GPS and time and syncs later, so it works at job sites without signal.
How often does OSHA require a job briefing?
Under 1910.269(c), before each job. For repetitive work, at least one briefing before the first job of each day or shift, and more if significant changes that might affect safety occur. Check the standard and your safety program for your situation.
Can each crew member sign the brief?
Not yet. PIEBENCH has no signature field today. Crew acknowledgement is recorded as a checklist, one item per crew member, ticked by the crew lead, with the brief's time and GPS location. If your program needs individual signatures, plan for that separately.
Can supervisors review pre-job briefs?
Yes. Each submitted brief lands in the approval queue. A supervisor or safety lead can approve it, or reject it with a note if a section is incomplete, and the crew lead sees the note on the phone.
Which plan includes the pre-job brief workflow?
Building your own brief form needs the workflow builder, which is part of the Pro plan at $499 a month, with users included. The free trial lets you try the app first.
Free trial · no card
See it with your own crew
Start a free trial, or ask us for a walkthrough of your rollout.