FAQ
Frequently asked questions
What the product does, what it does not do, and where the line sits. Where something is on the roadmap rather than shipped, the answer says so.
Straight answers
Questions worth asking first
- Is this legal advice?
- No. What you get is informational safety documentation, not legal advice, and it does not create an attorney-client or consultant relationship. Have a qualified safety professional review every SOP against your actual operation before it goes into service. You know your building; we know the paperwork.
- Does a generated SOP make us OSHA compliant?
- Written procedures are one part of compliance. Training, implementation, and records are the rest. What we give you is the documented program an inspector asks for first, mapped to the specific 29 CFR 1910 paragraph it addresses, plus the sign-off sheets that prove your crew was trained on it. Inside the app, Help maps each common inspector request to the screen that answers it.
- How long does one SOP take?
- Minutes. You answer the facility questionnaire once, pick a template, and generation itself takes well under a minute. The real work is the review: reading the facility-specific sections against how your floor actually runs, fixing what the questionnaire could not know, and getting a qualified person to sign off. Budget an afternoon for a first batch of procedures, not a weekend per SOP. Facilities can be described in metric; generated text follows.
- How do we know which SOPs we need?
- The facility questionnaire tells you. Answer it once and every template that applies to your building is listed, with the answer that triggered it and the section it cites, so the list is not a guess. Each item shows as written, draft, or missing, on one panel per facility, on every plan, and answering an unanswered question can open more of the library at once.
- Do you cover OSHA state-plan states?
- Today the library is mapped to the federal standard, 29 CFR 1910 (with 49 CFR for the hazmat procedures). If you are in a state-plan state such as California, Washington, or Michigan, the federal text is the floor your state plan builds on, but the state deltas are not in the product yet. Mapping those differences is a roadmap item, and we would rather say so than sell it before it ships.
- Can we use these at more than one building?
- Yes, on the Multi-Site plan. Each site keeps its own facility profile, so a procedure fitted to one building is not silently reused at another. Network standards let you publish an SOP once, copy it to every site, and push updates out so each site can adopt the new revision, with a dashboard that shows which sites are behind. Facility counts and seat counts are on the pricing cards. See Multi-Site on the pricing cards
- What about Spanish?
- Bilingual output is included on Pro and above. Every section of the SOP carries its Spanish rendering under the English, and every step on the floor card does too, generated from the same source procedure so the two languages cannot drift apart. The free trial includes bilingual output, so you can check the Spanish before you pay.
- What do you do with our facility data?
- We use it to generate your documents and for nothing else. Generating an SOP sends the template text and the relevant parts of your facility profile to the Claude API, which returns the customized document. The privacy policy states it plainly: that content is not used to train models, by Anthropic or by us, and we do not add your content to a shared template library. We do not sell personal information and there are no advertising trackers on this site. Read the privacy policy
- Is our data secure?
- Yes, in ways that do not rely on a promise. Two-factor sign-in is available on every account. When support opens a session to help with a ticket, it can look but never write, and that session ends itself after thirty minutes. Signatures and training records are inserted once and cannot be edited after the fact, only added to, so the history nobody can quietly rewrite is the same history an inspector sees.
- What happens when a standard changes?
- Every SOP records the clauses it is built against. On Pro and Multi-Site, when a cited standard is revised you get an alert naming the affected SOPs, so you are not re-reading the CFR to find out what moved.
- How does training tracking work?
- Every plan gets printed training sign-off sheets and a weekly one-page toolbox talk generated from each active SOP, in English and Spanish when the SOP is bilingual. Pro and Multi-Site add a signing kiosk (hand a tablet around instead of a page), digital signatures with an audit trail, bulk roster import from a CSV or XLSX file (up to 2,000 people, matched first by badge number so re-importing the same file never creates duplicates, and export it back out as CSV), and training records tied to the exact SOP revision each person was trained on. The one-click audit binder bundles a facility's active SOPs, approvals, revision history, training records, and floor cards into a single indexed PDF for an inspector. Where a standard sets an expiry, such as the three-year forklift re-evaluation, the record carries a due date and a weekly email names who is expiring and who has expired.
- What happens when someone scans the QR code on a floor card?
- They land on a public page, no account needed, that says in one line whether that exact printed card is current, has been superseded by a later revision, was never approved, or is out of service, along with the org name, the SOP title, its control number, the live revision, and the effective date. It never shows the procedure text or which facility the card belongs to. Every floor card carries this QR, on every plan.
- Where do the templates come from and how are citations verified?
- From a fixed library, not from a model asked to invent a procedure. The library is curated and version-controlled: each template carries the date it was last reviewed, and it marks which sections are regulatory boilerplate that passes through generation unchanged and which are meant to be fitted to your facility. Generation fits one of those templates to your building rather than composing a safety program from nothing. A template may only cite sections on a maintained whitelist, enforced by an automated test, and every cited paragraph is quoted in the standard's own words, taken from the eCFR rather than paraphrased. A weekly sweep re-checks every cited section against eCFR's amendment record, which is what drives the standard-change alerts.
- Can we export to Word?
- Not yet. Exports are PDF today: the branded SOP, the floor card, and the training sign-off sheet. DOCX export is on the roadmap. The PDFs are yours to keep and put your own letterhead on.
- Do you charge per worker?
- Never. Pricing is per facility, and every plan covers everyone in the building. Charging by headcount would mean charging you more for training more people, which is the opposite of the point.
- Can we edit what comes out?
- Yes, and you should. Each template marks which sections are fixed regulatory boilerplate and which are meant to be fitted to your facility. Exports are yours to keep, edit, and put your own letterhead on. Nothing is overwritten: every revision is kept, and the history page lists them newest first with the summary of what changed and who saved it.
- What happens when the trial ends?
- Your account goes read-only. Nothing is deleted and every SOP you generated stays readable in the app, but new SOPs, edits, and exports wait for a paid plan. No card is required to start, and we never convert a trial to a paid plan on our own. During the trial, exports are watermarked, so the clean documents are part of what a plan buys.
Not answered here?
Write to us. You do not need an account, and a person reads every message.