Skip to main content
Skip to main content

Run your first digital safety meeting

Replace the paper sign-in sheet with a repeatable process that a supervisor can run from the field and the office can verify later.

At a glance​

Best forContractors running toolbox talks, JHAs, daily check-ins, permits, inspections, or hazard reporting
Initial setupApproximately 30–60 minutes after company, worker, and project information is ready
Pilot sizeOne supervisor, one crew, one active project
RolesSafety administrator, field supervisor, 3–10 workers
Success looks likeMeeting completed, attendance/signatures captured, record searchable, and one follow-up action assigned if needed

Use this solution when​

  • paper meeting sheets are late, incomplete, or lost;
  • supervisors use different topics or formats;
  • the office cannot quickly prove who attended;
  • JHAs and permits are disconnected from the crew performing the work;
  • hazards are reported but follow-up ownership is unclear;
  • certifications or training expirations are difficult to see;
  • field teams need access when connectivity is unreliable.

Decide the first outcome​

Do not attempt to configure the entire safety program on day one. The first target is:

One supervisor selects an appropriate topic, conducts the meeting, records attendance and acknowledgment, submits the record, and confirms that the office can retrieve it.

If a hazard or follow-up item is identified, assign an owner and due date before closing the test.

Before you begin​

Prepare:

  • company name and basic safety contact information;
  • one active project and its location;
  • one supervisor;
  • 3–10 pilot workers;
  • the crew's preferred language;
  • the first meeting topic;
  • the organization's attendance and acknowledgment policy;
  • the escalation contact for unresolved hazards;
  • one phone or tablet that will be used in the field.

Decide whether workers will use individual accounts, crew sign-in on the supervisor's device, QR access, or another supported attendance method. Confirm the method in the actual product before publishing company policy around it.

Step 1: Configure the pilot project​

  1. Create or select one real active project.
  2. Confirm its name, address, responsible supervisor, and emergency information.
  3. Add only the workers participating in the pilot.
  4. Verify that the supervisor can access the project and create the intended safety record.
  5. Verify that a worker cannot see projects or records outside the access intended for that role.

Acceptance test: the supervisor opens Safety Meetings from the field device and sees the correct pilot project and crew.

Step 2: Choose a relevant meeting topic​

Select a topic based on work being performed, observed hazards, recent events, equipment, weather, or required training—not merely what is convenient in the library.

Before the meeting, review:

  • topic title and learning objective;
  • task-specific hazards;
  • project-specific controls;
  • required PPE;
  • emergency and stop-work expectations;
  • questions the supervisor should ask;
  • the language used by the crew.

OSHA publishes material that employers can use during toolbox talks, including fall-prevention resources, but the employer remains responsible for determining the training required for the work. See OSHA fall-prevention training resources.

Step 3: Rehearse before the crew arrives​

The safety administrator and supervisor should run a private test:

  1. Open the meeting.
  2. Confirm project, date, supervisor, and topic.
  3. Read or present the material.
  4. Add a project-specific note.
  5. Add a test attendee.
  6. Capture a test acknowledgment or signature.
  7. Add a test photo only if photos are part of company policy.
  8. Submit the meeting.
  9. Find the record from the office view.
  10. Generate or view the intended report.

Delete or clearly label test data according to company policy. Do not leave a fake training record that could be mistaken for real attendance.

Step 4: Run the live pilot meeting​

The supervisor should:

  1. Confirm that the selected topic matches today's work.
  2. Gather the crew before work begins or at the designated time.
  3. Explain the task, hazards, controls, PPE, and stop-work process.
  4. Ask workers to describe the critical control in their own words.
  5. Record questions, site-specific conditions, and required follow-up.
  6. Capture attendance using the approved method.
  7. Obtain acknowledgment or signatures according to company policy.
  8. Submit the record while the crew is still present.
  9. Confirm that the screen shows a successful save or synchronization state.

Keep the meeting interactive. A captured signature does not prove that the worker understood the subject.

Step 5: Turn findings into accountable work​

If the meeting, JHA, inspection, or check-in identifies a problem, the process should create a corrective action with:

  • clear description;
  • project/location;
  • severity or priority;
  • responsible person;
  • due date;
  • immediate control;
  • supporting photo or document when appropriate;
  • verification requirement;
  • closure evidence.

Do not treat “meeting completed” as success when an identified hazard remains unowned.

Step 6: Verify the record from the office​

The safety administrator should confirm:

  • the correct project and date;
  • the correct topic and supervisor;
  • every expected attendee is present once;
  • signatures or acknowledgments display correctly;
  • project-specific notes are readable;
  • photos or attachments open;
  • assigned actions contain owner and due date;
  • the record is searchable;
  • export/PDF output is accurate;
  • the audit history shows the expected activity;
  • offline-created records synchronize without duplication.

If any part is wrong, correct the workflow before expanding to another crew.

First-week rollout​

Day 1 — controlled pilot​

  • One supervisor
  • One meeting
  • One device
  • Administrator observes the process

Days 2–3 — repeat without administrator assistance​

  • Supervisor selects and runs the next meeting independently
  • Office verifies submission
  • Record every question or delay

Days 4–5 — add one adjacent workflow​

Choose only one:

  • recurring schedule;
  • daily safety check-in;
  • JHA/JSA;
  • hazard report;
  • equipment inspection;
  • certification reminder.

Do not enable every safety feature simultaneously.

Operating rhythm​

Supervisor — every meeting​

  • Select a task-relevant topic
  • Add site-specific hazards and controls
  • Verify attendance before submission
  • Assign follow-up work
  • Confirm saved/synced status

Safety administrator — daily during rollout​

  • Review missing meetings
  • Review open high-priority actions
  • Resolve worker/project access problems
  • Coach supervisors on content quality

Safety leadership — weekly​

  • Review completion by project
  • Review overdue corrective actions
  • Review recurring hazards
  • Review upcoming certifications
  • Decide where coaching or intervention is needed

Definition of done​

  • A real project and pilot crew are configured.
  • Supervisor access works on the intended field device.
  • The topic matches work being performed.
  • All pilot workers are captured once.
  • Acknowledgments/signatures are readable and associated correctly.
  • The office can retrieve and export the submitted record.
  • Any identified hazard has an owner and due date.
  • Offline/sync behavior has been tested if field connectivity is unreliable.
  • The supervisor can repeat the process without administrator assistance.
  • The company knows who reviews missing meetings and overdue actions.

Common mistakes​

Uploading the entire workforce first​

Start with the pilot crew. Large imports create identity and permission problems before the process is proven.

Choosing generic topics without site context​

Require a short project-specific discussion on every meeting.

Treating signatures as the outcome​

The outcome is worker understanding, documented attendance, and corrected hazards.

Closing records while actions remain unclear​

Every corrective action needs an owner, date, and verification method.

Assuming offline support works without testing​

Run an airplane-mode or low-connectivity pilot on the devices crews actually use.

Measure success​

Track:

  • scheduled meetings completed on time;
  • expected workers with valid attendance records;
  • average time to conduct and submit;
  • hazards with an assigned owner;
  • corrective actions closed by due date;
  • certification expirations resolved before lapse;
  • supervisors completing the workflow without support.

Avoid publishing a safety score until the denominator and meaning are valid. Use “Not measured” when there is insufficient data.

What to add next​

If meeting attendance is working but the office still chases labor hours, add BLDR Time using the same workers and projects. If the safety team needs a company-specific inspection or approval, create it in BLDR Pro rather than duplicating the entire safety program.

For the paper process behind this guide, see the toolbox talk procedure and toolbox talk library.

Important: This guide supports operational implementation and recordkeeping. It does not determine the safety training, meeting frequency, content, retention period, or other legal requirements that apply to a particular employer, jurisdiction, project, or hazard. Consult qualified safety professionals and applicable authorities.

Was this page helpful?