Audience and access
The employer controls client access. A pending application or relationship does not grant access. An approved scope, an eligible named consultant seat and explicit entry into the correct client workspace precede protected work.
Plan the visit, prepare the supported work product and keep the client response separate. Report delivery is not acknowledgment; acknowledgment is not acceptance or completion of a corrective action. Filing and employer certification remain with the responsible employer.
Availability is separate from described behavior
This guide explains behavior found in the software; it does not show that the live service has passed a test. Production AI remains held: it is not available for use until authorized. A description, demo or subscription does not activate it.
Availability depends on which features are enabled, which data they may process and your workspace. Use the public fictional examples to explore the steps without sending workplace records to an AI service.
What waits for a person
Site Scan suggests possible hazards with related standards. A supervisor accepts or rejects each suggestion; accepted findings become corrective actions. A reviewed finding does not establish that remediation is complete.
A person must review drafts and outputs used to make decisions. The assistant proposes record changes; a person with the required authority approves them. Starting an automated run does not approve its proposed changes. An assistant can suggest verification but cannot record the human verification itself.
AI does not submit filings. A responsible person reviews the facts, the applicable requirements and the final material before sending it.
Two bounded actions before review
Defect Snap: a qualifying equipment detection at or above the lock threshold can create the provisional do-not-operate hold and its linked action before human review. The detection stays PENDING. This is not a human-confirmed defect or completed corrective action; a competent person confirms or overrides it later.
Automated summary notifications: only the designated summary and notification tools may prepare and queue notifications without a new human approval. Each run has a limit, and retrying the same notification does not create a duplicate. This narrow exception does not allow other record changes, verification of work or report filing.
These exceptions do not remove Site Scan supervisor review or authorize AI activation while the service is held.
Jurisdiction depends on the feature
Site-tied features (Site Scan, photo analysis, voice capture, inspection intake and incident forms) resolve physical-work context from the incident case, then the establishment, then workspace headquarters, then the federal fallback. Resolver errors use the federal fallback; they do not prove state-specific coverage.
Chat and document/SDS analysis use workspace headquarters jurisdiction by design. They are not universally worksite-first. Confirm the relevant worksite and authority before relying on an answer.
Authored state depth varies. Where state vocabulary is not authored, answers use federal citations; Site Scan discloses that fallback. A checked citation is not verification that a workplace is safe.
First-report preparation is not filing
Prepare the employer first-report materials for the physical work jurisdiction. A published regulator form, an external portal and notice to a carrier are different routes. A form is not available merely because a jurisdiction appears in a directory.
Where a supported published form exists, preparation may produce a PDF; otherwise follow the applicable portal or carrier-notice instructions. The employer, carrier or other legally responsible filer transmits the report. EDI transmission is not included.
OSHA recordkeeping, a workers compensation notice and an agency filing are separate obligations. An internal render check is not regulatory approval, acceptance of a filing or nationwide certified-form coverage.
Choosing a jurisdiction during setup does not mean every feature is ready there. If no readiness decision is recorded for a feature, its status is Not indicated, never Ready. A published review does not prove the live service is ready.
Preparation and follow-through, not promised outcomes
There is no universal same-day filing or complete-documentation-from-intake promise. Timing and completeness depend on facts, attachments, jurisdiction, access, human review and the recipient route. Check the actual deadline separately.
Synthetic examples illustrate a workflow. They are not customer results, a regulator acceptance receipt or evidence of an injury reduction.
Published-form example: DWC001
The official DWC001 (Rev. 10/24) gives these recipient instructions: “Send this form to your workers’ compensation insurance carrier and to the injured employee or the injured employee’s representative. Do not send this form to the Texas Department of Insurance, Division of Workers’ Compensation (DWC), unless DWC specifically requests it.”
We checked the official blank’s three pages, revision and recipient instructions. SafeGora’s template is a separate file, not an unchanged copy of the official blank.
Certified-PDF preparation is marked Not ready for this example. A public listing does not make form preparation ready. We have not verified a completed form from the live service, submission or recipient acceptance. The employer’s notice to the carrier is separate from the carrier’s reporting to the agency.
Certified-PDF preparation: Not ready. Verification in the live service: Not indicated.
Alternative-route example: employer online report
The agency describes an online report to the commission, with copies to the carrier or administrator. Follow that separate reporting process. SafeGora does not submit it for you or provide a certified regulator-form PDF for this route.
We could read a summary of the agency’s page in search results, but could not open the page itself. We have not verified the current portal version or completed a submission. Read the current official instructions and confirm the route before use; this example does not establish readiness.
Certified-PDF preparation: Not ready. Verification in the live service: Not indicated.
Audience-specific commercial boundaries
Consulting practice access: $79 per named consultant per month, plus applicable tax, with no practice base fee. After manual approval and workspace readiness, the trial is 30 days for up to 10 consultants, no card required and no charge unless the practice chooses to subscribe. Employer subscriptions are separate.
Employer plans: Starter $79/month or $790/year; Pro $249/month or $2,490/year, plus applicable tax. Employer trials are 30 days with no card required.
These prices and trial terms match the pricing page. Before subscribing, review the current price, your order and the agreement you will accept. This guide does not replace those documents or change an existing customer’s accepted terms. Keep your acceptance receipt.
A first-use reading exercise without a client
You need a browser and a reviewer, not a client account, employer permission, payment card or signed agreement. This is a reading exercise, not a private sandbox or live filing test.
Use only the fictional inspection and consulting records already shown in the public example. Do not upload names, injury details or client files.
Produce a short review note: the selected workflow; its input; the person who decides; the resulting record and its state; the next responsible person; and one unanswered question.
Reading the public example does not create a workspace or start a trial. A consultant application receipt is not approval, workspace readiness, a named seat or client permission. After approval, the consultant trial starts when the workspace is ready; waiting for client approval uses trial time. No pause, extension or review-turnaround promise is added here.
- Name the client or worksite context shown in the fictional example.
- Separate an AI suggestion from a human-reviewed finding.
- Separate a delivered report, client acknowledgment, action acceptance and action completion.
- Name the owner of the next action and what evidence is still needed.
- Mark missing readiness or filing evidence as unknown, not complete.
Edition, sources and limits
Edition: October 2026. Content version: 2026-10-18.2. Reviewed on 2026-10-18.
Replaces the August/September summaries and corrects the first October revision. Preserves the DWC001 request exception and clarifies review, reporting and pricing explanations. No price, accepted agreement, trial clock or AI activation changes.
Checking the software does not verify the live service or establish regulatory certification. Missing decisions remain unknown. Confirm the supported reporting route and workspace before relying on any output.
SafeGora is independent software, not affiliated with, approved by or endorsed by OSHA or any government agency. This guide is not legal advice. Filing and compliance responsibilities remain with the employer or other legally responsible party.
AI governance and review boundaries
First-report preparation limits
Technical appendix — review record
Reviewed source snapshot: e0f0aaaab42a17f6fe980018c31b1f4986afed13. Evidence level: source-observed.
The review records and PDF artifact manifest retain file hashes and capability decision identifiers. Owner approval and independent deployed verification are not recorded for this edition.
PDF SHA-256: 952f8f200f9e6406ce8504612e524234b0484d9f9dcf3be1266450443a4d5d00