Skip to main content
Skip to main content

Daily Safety Check-In Procedure

Document Type: Procedure
Version: 1.1
Last Updated: April 2026
Distribute To: Foremen, Superintendents, Safety Directors, HR

Purpose​

This procedure matches how BLDR Safety Meetings labels the per-worker flow: Daily Safety Check-In—each employee’s daily attestation (readiness, PPE, hazards, emergency awareness, signature). It also covers crew-level documentation: toolbox talk sign-in sheets and pre-task planning records, which often sit alongside the check-in in a complete program.

Clear documentation supports OSHA-style training records, GC and audit requests, and dispute defense when someone claims they were never told about a hazard.

Related procedures:

What “check-in” and “sign-off” mean here​

Daily Safety Check-In (app / Model B): A dated record per person per day (or shift) showing they completed the attestation your program requires.

Meeting sign-off (Model A): A group record for a toolbox talk, safety meeting, or pre-task brief—presenter, topic, roster, signatures (or digital equivalent).

Both are dated, attributable records of who received or acknowledged safety information. They are not the same as work order approvals or financial sign-offs.

Strong records usually include:

  • What was covered (topic, JHA reference, or checklist)
  • When (date and, when it matters, time)
  • Where (project or work area, when relevant)
  • Who presented or led (foreman, competent person, safety rep)—for crew meetings
  • Who received or attested (named individuals with signatures or equivalent)
  • How it was captured (paper, app, kiosk—consistent with your policy)

Two complementary models (use both when needed)​

Many contractors need both. They answer different questions for auditors and lawyers.

Model A — Crew-led meeting record​

What it is: One document for a group event: toolbox talk, safety meeting, or pre-task planning brief led by a foreman or lead.

Typical contents: Topic or agenda, project, presenter, list of attendees, attendee signatures (or digital equivalent), sometimes key discussion points.

Best for: “Who was at the morning brief?” “What did we cover today for the crew?”

Procedure reference: Follow Toolbox talk procedure for meeting flow and sign-in fields.

Model B — Daily Safety Check-In (per-worker attestation)​

What it is: In BLDR Safety Meetings, this is the Daily Safety Check-In: a separate record per person per day—each worker confirms readiness (e.g. fit for duty, PPE, understanding of tasks and hazards, emergency awareness, and reporting concerns per your wording).

Best for: “Did every employee prove they completed today’s safety step?” staggered crews, subs who missed the group huddle, or programs that require individual liability trails.

Important: The Daily Safety Check-In is not a full replacement for a crew-level pre-task form with one roster and one foreman-led hazard table unless your policy and fields are designed that way. If you use both a crew brief and Daily Safety Check-In, state that in your safety plan so expectations stay clear.

When to use which model​

SituationRecommended approach
Weekly toolbox talkModel A — documented meeting + signatures
Daily foreman-led crew brief with shared task/hazard planModel A — Pre-task planning form
Policy requires every employee to complete a daily step on their own deviceModel B — Daily Safety Check-In
Worker arrives after the group briefModel B or a make-up brief documented on Model A
JHA review for a high-risk taskOften Model A at the crew level, plus Model B or named acknowledgment on the JHA as your program requires
Orientation / new hire trainingModel A roster or training log + individual sign-off on training completion as required

Roles, timing, and frequency​

RoleTypical responsibilities
Company / safety leadershipDefines whether Daily Safety Check-In, crew meetings, or both are mandatory; sets retention; approves digital vs paper policy
Foreman / field supervisorLeads Model A briefs when required; verifies crew sign-in sheets; encourages or enforces Daily Safety Check-In before work where policy requires it
WorkerCompletes their own check-in; signs their own name on crew records; reports barriers (no phone access, language needs) to supervision
Safety coordinator / adminMonitors completion rates, exports records for audits, files paper originals or verified scans

When to complete: Set a clear rule in your program—for example, Daily Safety Check-In before starting hazardous work or before the end of the start-of-shift window; toolbox / pre-task at the crew brief, not after the fact. Write the rule down so enforcement is consistent.

Language and access: If workers are not fluent in the language of the form, provide translation, an interpreter at the brief, or a documented equivalent. “Signed without understanding” weakens the record.

Subcontractors and multi-employer sites​

  • Your subs should follow your documented rules for Daily Safety Check-In and crew meetings when your contract or site orientation requires it; retain proof the same way as for employees.
  • Multi-employer jobs: Clarify in the site-specific plan who produces the crew-level toolbox/pre-task record and who requires per-worker check-ins (prime GC vs each sub). Avoid duplicate or contradictory requirements when one record can satisfy the rule.

Process (standard workflow)​

Step 1 — Plan before anyone signs​

  1. Identify which model (A, B, or both) applies to the activity.
  2. Assign who may lead the meeting or who may authorize the check-in workflow (foreman, safety rep, etc.).
  3. Gather materials: topic sheet, JHA, pre-task form, or Daily Safety Check-In in your app.
  4. Confirm project name and location if the record is job-specific.

Step 2 — Conduct and capture in real time​

  1. Run the meeting or present the content before work starts when the topic is about that day’s hazards.
  2. For Model A: Complete attendance at the meeting; do not backdate signatures.
  3. For Model B: Each worker completes their own Daily Safety Check-In; avoid “one person signs for everyone” unless your policy explicitly allows a legally valid proxy (unusual—get legal advice if unsure).
  4. If using digital signatures, use a system that stores who, when, and what they acknowledged (audit trail).

Step 3 — After sign-off​

  1. File the record where your safety meeting program or document control says it lives.
  2. Retain for the period your counsel and contracts require (training-related records are often kept multiple years—confirm with your attorney; many contractors use three to five years as a starting point for training attendance).
  3. Do not alter completed records; if a correction is needed, add a dated addendum or new entry per your policy.
  4. Pull records promptly for OSHA, insurance, GC, or legal requests.

Digital vs paper​

Digital check-ins and sign-offs are widely accepted when they provide reliable identity and time and tamper-evident storage. Your program should state:

  • How workers are identified (login, badge ID, etc.)
  • How timestamps are generated
  • How exports or PDFs are produced for third parties

Paper remains valid if legible, complete, and stored like any other controlled document.

Quality checks (supervisor / safety)​

  • Every required field on the sign-in or check-in is filled before filing
  • Signatures (or digital equivalents) match printed names
  • Subcontractor company name appears when subs sign (toolbox requirement)
  • No blank “topic” or “date” lines on crew records
  • Per-worker Daily Safety Check-In records are one person per record unless the tool is explicitly designed for joint attestation

If someone does not complete the check-in​

Your disciplinary and site-access policies should say what happens next (reminder, one-on-one, removal from task, etc.). This procedure does not replace HR or union rules—document the escalation path in your safety program so foremen are not improvising under pressure.

Common mistakes to avoid​

  • Backdating or signing sheets before the meeting happened
  • One signature for the whole crew without a named roster
  • Losing the only copy (no scan, no cloud backup)
  • Mixing models without explaining it in the safety plan (auditors ask why two systems exist—answer: crew brief + individual Daily Safety Check-In)
  • Promising clients a “full pre-task plan” in software when the product only collects a lightweight daily check-in—align sales language with what the record actually contains

Template provided by support.construction. Customize retention periods and roles with your attorney and corporate safety program.

Was this page helpful?