Inspection report in 30 minutes instead of 3 hours.

Run the inspection, capture defects with an action, a responsible person and a deadline, then seal it. Whatever stays open shows up again in the follow-up inspection, with the date it was first recorded.

Four things that slow down your safety routine today

Inspection takes one hour, the report takes three. Retyping notes, sorting photos, comparing against the last inspection, drafting corrective actions. Post-processing costs three times as much time as the inspection itself.

On the follow-up inspection you retype the same findings. Which item has been open since when, which action is in place? Without a running history, you lose the overview.

Action tracking lives in Excel. The list travels by email, everyone edits, no one merges. Version chaos is the rule, not the exception.

As an external safety officer you handle multiple clients. Each wants the report in their own layout, separated from the rest. Enterprise suites are built for internal teams, smartphone apps deliver only defect lists. You patch it together with Word templates.

What an inspection with Begehung.pro looks like

Prepare · capture on-site · seal it and follow up on the next inspection.

1

Prepare the inspection

You create the inspection under the client's inspection series and add your own checklists, each as a fixed version, with the source address on the check item. Open defects from the previous inspection are already loaded, together with the date they were first recorded. Before the first step you know what needs following up.

2

Capture on-site

You structure the inspection into areas and record defects with a title, a note and a photo. Check items go to passed or not passed, with a note per item, and you link the defect to the check item. The action sits on the defect: what, who, by when. Structural and text data work offline, photos need a connection.

3

Close and follow up

Sealing freezes the state, with the sealing timestamp and the inspector. Rework creates a new, numbered version; the old one stays readable. If the series has an interval, the next appointment is set from there: inspection date plus interval. Open defects and their actions show up there again, with the previous state read-only beside them. You set each item to open or resolved.

What your occupational safety inspection records

Areas, capture, and result, tailored to the duties of an occupational safety specialist.

AreasProduction halls, offices, outdoor storage, workshops, hazardous material storage, construction sites, escape routes, fire safety installations.
CaptureDefect with title, note and photo as evidence. Check item passed or not passed, with a note. Action with responsible person and deadline. Structural and text data also offline.
ResultSealed inspection: an immutable state with sealing timestamp and inspector, previous versions stay readable. Open defects with action and deadline carry over to the next inspection. Report export is planned.

The key capabilities for your inspections

Open defects carry over · sealed versions stay readable · your own checklists · data in Germany.

Open defects come back on their own

Open defects and their actions reappear in the follow-up inspection automatically, with the date they were first recorded. In the web app the defect history shows across the sealed inspections of the series how the defects developed: cumulative per inspection and as a timeline per defect. The previous state sits read-only beside them. You decide again per item: open or resolved.

  1. 08:14Inspection started, area hall 2
  2. 08:31Note on the defect: welding station shielding
  3. 08:47Photo for the defect
  4. 09:12Action with responsible person and deadline
  5. 09:28Sealed, next appointment set

Sealed means sealed

Sealing makes the version immutable, with the sealing timestamp and the inspector. Rework creates a new, numbered version. The chain of previous versions stays readable.

Your check catalogues, not ours

You maintain your checklists yourself, continuously versioned, with the source address on the check item. Adding one to an inspection copies that version, so the wording freezes. You read existing catalogues in as PDF, Word or Excel in the web app: the AI proposes a name, a description, the inspection items and the source addresses named in the document, and you review the proposal before adopting it. Legacy reports go through the report import in the web app as well.

Data in Germany, DPA per Art. 28 GDPR

Databases in Frankfurt am Main, application servers in the EU, DPA at onboarding, GDPR without workaround. TOMs per Art. 32 GDPR are oriented towards ISO 27001 and BSI C5. We do not hold a formal certification against those standards.

  • Data in Germany
  • DPA per Art. 28 GDPR

Frequently asked questions from safety officers

The sealed version records the inspection date, the inspector, the areas covered, the defects found with note and photo, and the actions with responsible person, deadline and status. Once sealed, none of it changes; rework creates a new version. There is no hazard rating or scoring scale on the defect.

Inspections, photos and reports are stored in databases in Frankfurt am Main. All processing takes place in the EU; the application servers run in Belgium. We provide the DPA per Art. 28 GDPR as a ready-to-sign PDF. The summary of technical and organisational measures per Art. 32 GDPR and the list of subprocessors are available at /avv and /subprozessoren. Those measures are oriented towards ISO 27001 and BSI C5. We do not hold a formal certification against those standards.

You control retention in line with your obligations: general risk assessments typically 10 years, equipment risk assessments for the full life of the equipment (TRBS 1201), hazardous-substance risk assessments 30 years after end of exposure (§14 GefStoffV), exposure registers for CMR substances 40 years. Sealed inspections stay readable in your account, including every previous version. Export into your own archive is planned. After the contract ends we keep your data available for export for 90 days, longer on request.

Through the status of the defect. A defect is either open or resolved. Open defects carry over with their action to the follow-up inspection, where you decide again. There is no graded rating such as effective or partially effective, and no rationale field. The action itself carries text, responsible person, deadline and a status of open or done, with no assignment to a tier scheme.

Yes. You maintain your checklists yourself, across your whole organisation and continuously versioned. Every check item can carry source addresses, for instance to the rule or work instruction behind it. Every checklist carries versions with the states draft, in use and superseded; the history shows the validity period and the usage count per version. Adding one to an inspection copies that version, so later edits leave running and sealed inspections untouched. That way you can run the revised DGUV V2 edition and the previous one side by side for a while. You read existing catalogues in as PDF, Word or Excel in the web app: the AI proposes a name, a description, the inspection items and the source addresses named in the document, and you review the proposal before adopting it. Legacy reports go through the report import in the web app as well.

Your clients are separate records within one account. Every inspection hangs off a client, a project and an inspection series, which keeps areas, defects and actions together per site. There is no multi-tenant setup with a dedicated environment per client.

Structural and text data are captured offline, and sync runs as soon as coverage is back. Photos need a connection. There is no paper workflow.

You'll find transparent pricing on the main page under the pricing section. The license is priced per user and month, and the feature set is the same for everyone; only the term differs. In the demo we work through your case with concrete numbers. Binding offer, no sales pressure.

Get your inspections out of spreadsheets.

30 minutes demo, no sales pitch, no pressure. We'll show you Begehung.pro using your own inspection setup. You decide whether it fits the way you work.

  • Data in Germany
  • DPA per Art. 28 GDPR
  • No sales pressure