Appearance
Field app vs office web review workflow
Live now
GoSafety is not only a field capture app and not only an office dashboard. The product is built around an iPhone and iPad field workflow plus a separate office web review workflow.
Snapshot
| Surface | Main use |
|---|---|
| iPhone and iPad field app | Capture time cards, safety checklists, evidence, signatures, PDF submissions, and mobile workflow answers |
| Office web app | Review, approve, configure, manage templates, manage OSHA records, and run exports |
What it is
This is the core operating model of the product. Crews complete records in the field app. Office staff review, approve, configure, and export those records from the web app.
Who uses each side
Field app
- Workers clocking in and out.
- Foremen completing safety forms or PDF-based forms.
- Field users capturing evidence, signature, and location context.
Office web app
- Safety managers reviewing forms and OSHA records.
- Admins configuring time tracking and form behavior.
- Office staff approving time entries and reviewing submissions.
Step-by-step workflow
- A form, template, or policy is configured in the web app.
- The field app loads the current form or policy.
- The field user captures the record on iPhone or iPad.
- The record syncs to the server.
- The office web app displays the submitted record for review or follow-up action.
What happens in the field app
- Time clock actions.
- Shift acknowledgement questions.
- Injury attestation and signature when required.
- Safety checklist completion.
- PDF form selection, dictation, review, and save.
- GPS capture, media capture, and markable diagram interaction.
What happens in the office web app
- Form builder and PDF template setup.
- Checklist review and approval.
- Daily report review.
- Submission review and PDF download.
- Time entry approval and export.
- OSHA 300 and 300A management.
Outputs and downstream effects
- Cleaner separation between field capture and office review.
- Less need to recreate field records by hand from paper or memory.
- Review status and audit trail tied to the canonical server record.
Practical construction examples
- A foreman completes a safety form in the field and a safety manager reviews it in the office.
- A worker signs an injury attestation on the phone and payroll later reviews the linked time entry in the web app.
- A field user dictates into a PDF workflow and office staff download the filled PDF.
Limitations and notes
- The current codebase is iOS on the field side, not Android.
- The office web app remains the system of record for review and administrative control.
- Some web pages still expose raw JSON or basic review surfaces instead of heavily formatted reporting views.