Frequently asked questions

Safety managers, EHS (environmental health and safety) staff, compliance officers, site supervisors, inspectors, contractors, and leadership teams who need organized inspection and violation records. We welcome single-site businesses, multi-location organizations, public and private sector teams, union and non-union workplaces, and growing companies that are just formalizing their safety program.

No. The app is designed so both seasoned safety professionals and people newer to compliance can log inspections, attach photos, and run reports. Your organization defines who does the work; we provide the structure and history.

The product uses concepts common in U.S. OSHA and EPA-style recordkeeping (for example CFR references and common violation categories). Teams outside the U.S. can still use locations, inspections, photos, and exports for their own programs — but you should map fields and reports to your local rules with qualified professionals.

We use plain language and avoid assumptions about gender, family structure, or background. In product copy we prefer neutral terms (for example “team member,” “assignee,” “partner organization” where relevant). If we ever get wording wrong, tell us — we want everyone to feel respected.

Create an account from the sign-up page, complete organization setup, and invite colleagues if you like. You can add locations, schedule inspections, and record violations with photos. The public violation report demo shows how findings and categories can look without logging in.

We offer a trial period so you can use the app before committing. Exact terms appear at signup and in your account. If you need a longer evaluation for accessibility or procurement reasons, contact support and we will do our best to help.

Marketing copy on the home page states whether a card is required for the trial; check the current signup flow for the exact policy. We aim to keep evaluation straightforward.

Yes. The experience is mobile-friendly, and you can install the progressive web app (PWA) from supported browsers for quicker access. Connectivity varies by site — plan ahead if you work offline frequently.

Your company is an organization. Members are invited with roles (such as administrator, management, inspector, and staff) that control what each person can see and change — for example who can manage billing, invite users, or clear violations. This helps enforce least-privilege access and safer delegation.

Yes. Contractors, consultants, and temporary coverage can be invited if your policy allows it. Use roles appropriate to their duties, and remove access when the engagement ends.

We recommend individual accounts so audit trails show who acted. Shared credentials weaken accountability and can conflict with internal or regulatory expectations.

Use the settings and account flows in the app. If your organization uses a legal name different from a trade name, you can usually reflect that in organization settings; ask your admin if you cannot edit a field you need.

You create locations, schedule inspections, and log violations tied to an inspection and site. Each violation can include regulatory references, severity, status (such as open, in remediation, or cleared), corrective actions, due dates, and photos for evidence or clearance.

Categories include OSHA, EPA, fire, environmental, electrical, chemical, ergonomic, and general — so you can filter and report in a way that matches how your program is organized.

No software replaces professional judgment or a regulatory inspection. SafetyInspect helps you document conditions and history consistently. Always confirm requirements with current regulations and qualified advisors for your jurisdiction and industry.

Yes. Statuses support work in progress, and you can attach clearance photos when a fix is verified. You can also reopen items if conditions regress.

Evidence and clearance images are uploaded through the app and stored using the project’s configured image pipeline (for example Cloudflare Images). URLs can appear in CSV exports for your records.

Show the hazard or condition clearly, include surrounding context when safe to do so, and avoid identifiable faces of coworkers unless your policy permits and you have consent. When in doubt, follow your employer’s photography and privacy rules.

Upload paths typically compress or constrain images for performance. If an upload fails, try a smaller resolution or check connectivity. Details may vary by deployment.

You can open a filtered printable HTML report (use your browser’s Print dialog to save as PDF) and download CSV exports that include violation rows and image URLs. A location summary helps compare sites.

Internal leadership, clients who require documentation, insurers, and regulators when you choose to share. You control what you export and send; treat exports as sensitive business records.

Organization settings support custom field labels that flow into records and exports — useful when different teams use different terminology but share one system.

See the home page and billing area for current plans. Subscription status (including trial) affects which screens are available; administrators can manage payment methods where permitted.

Follow in-app notices and email from your payment provider. We recommend keeping billing contacts up to date so invoices and retries reach the right people.

If you represent a nonprofit, school, or public agency, contact support with details. We cannot promise a discount in every case, but we welcome the conversation.

See the Privacy link in the site footer. It describes how we handle information at a high level; your organization may also have internal policies that apply to data you enter.

Follow your legal and HR guidance for serious injuries, harassment, or discrimination. The app is focused on safety inspection and violation tracking — not a substitute for HR case management or legal counsel.

Traffic to the service should use HTTPS in production. For encryption at rest, retention, and subprocessors, rely on your deployment documentation and agreements. Ask support if you need specifics for procurement.

We aim for semantic HTML, keyboard-friendly controls, and readable contrast where we control styling. If you use assistive technology and hit a barrier, email support with the page and behavior — we want to prioritize fixes that unblock real users.

Core flows should be operable without a mouse, but gaps can exist. Specific issues are best reported with browser and assistive technology version so we can reproduce them.

The interface is primarily English today. If multilingual support matters for your workforce, tell us which languages you need — it helps us plan inclusively.

We welcome respectful feedback on language, imagery, or flows that feel exclusionary. Safety and compliance work is done by diverse teams; our product language should reflect that respectfully.

No. Nothing on this site or in the app is legal, regulatory, or professional engineering advice. You are responsible for compliance with laws that apply to your operations.

No. Good records support your program, but regulators evaluate real conditions on site. Use the tool to be organized — not as a guarantee of outcomes.

See the Terms link in the footer for the agreement governing use of the service.

Email support at the address on the About page. Include your organization name, a short description, and screenshots if they help. We aim to respond fairly to everyone, including small businesses and first-time safety leads.

Ask support what is available for your plan. For larger rollouts, we may be able to suggest materials or sessions depending on capacity.

Email support with “Security” in the subject line. Do not include passwords or secrets in email.