Injury forms

Live now

GoSafety injury forms currently center on daily injury attestation at clock-out, plus template-based injury submission workflows that can feed OSHA intake. The current codebase does not treat every injury workflow as one single dedicated incident module, so it is important to separate what is already live from what is still split across related workflows.

Snapshot

Item	Details
Who uses it	Workers, foremen, safety managers
Current status	Live now
Main live record	Daily injury attestation
Related workflows	Time cards and shift survey questions, OSHA 300 management, OSHA 301 management

What it is

The live injury workflow starts when a worker clocks out. If the organization requires daily injury attestation, the worker must confirm whether there was an injury or illness, provide a description when needed, and sign if the policy requires signature. Separate template-based submission workflows can also capture injury-related PDF forms.

Who uses it

• Workers completing the end-of-shift attestation.
• Safety managers reviewing attestations and linked time entries.
• Office staff using the result as input for OSHA and incident reporting.

Step-by-step workflow

1. The worker starts clock-out in the field app.
2. The app checks org policy for injury attestation wording, signature requirement, and GPS requirement.
3. The worker answers the injury question.
4. If an injury is reported, the worker must provide a description.
5. If signature is required, the worker signs in the field app.
6. The server creates or updates the daily injury attestation record and links it to the time entry.

Data captured

• Employee and organization ID.
• Attestation date.
• no_injuries boolean.
• Injury description when needed.
• Injury signature SVG when required.
• Linked time entry.
• GPS coordinates when provided.

Outputs and downstream effects

• A stored injury attestation record.
• A linked time entry record for office review.
• A record that can feed broader OSHA workflows.
• Webhook notification that an injury attestation was created.

Device and platform context

• Injury attestation capture happens in the iOS clock-out flow.
• Injury attestation list and review happen in the web app.
• Template-based injury PDFs use the separate PDF submission workflow.

Practical construction examples

• A worker finishes a shift, reports no injuries, and signs the attestation.
• A worker reports an injury at clock-out, adds a description, and the office follows up in OSHA workflows.
• A company uses a template-based injury PDF in addition to the daily attestation record.

Limitations and notes

• The live injury module is strongest at daily attestation and linkage to time tracking.
• The current codebase does not include one dedicated all-in-one injury case manager beyond attestations, template submissions, and OSHA case workflows.
• Dedicated OSHA 301 management is not yet implemented as a separate product surface.

Related pages

• Time cards and shift survey questions
• OSHA 300 management
• OSHA 301 management