Every inspection stays traceable as a sealed state. Open defects do not disappear.

Begehung.pro guides you through the fire safety inspection: record defects with a note and a photo, set an action with a responsible person and a deadline, then seal it. One state per appointment that does not change afterwards.

Four things that slow down your fire safety routine today

Your inspection records live in Word, Excel or a paper folder with scanned PDFs. Word is editable after the fact, and in Excel nobody can tell which state applied when. Falling back to paper is the honest but costly answer.

On the third visit you're at the same blocked escape route. Which finding has been open since when, which escalation went out, with what result? Without a running history you can't show management, building authority or insurer that you raised the issue long ago.

Fire alarm, fire doors, smoke and heat exhaust, emergency lighting, wall hydrants, extinguishers. Every installation has its own maintenance interval. You keep dates in Outlook and Excel, and when staff changes the thread breaks. When the inspector asks for the latest fire alarm maintenance report, the hunt across five folders begins.

The fire prevention inspection is due. Building authority or fire safety service want the fire safety concept, fire alarm maintenance records, evacuation drill protocol, defect list with closure status and training records of the fire safety helpers. Not bundled and ready, it looks bad and earns you orders.

What a fire safety inspection with Begehung.pro looks like

Prepare · capture on-site · seal it and carry it forward.

1

Prepare the inspection

The property sits in the system as a client and a project, and the inspection series carries your interval. You add your own checklists for structural, operational, installation-based and organisational fire protection. Open defects from the previous inspection are already loaded, with the date they were first recorded.

2

Capture on-site

You structure the property 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

Seal and carry forward

Each appointment produces a sealed, numbered version with the sealing timestamp and the inspector. Rework creates the next version; previous versions stay readable. The next appointment follows from the interval of the series: inspection date plus interval. Open defects and their actions show up there again.

v1v2v3

What your fire safety inspection records

Areas, capture, and result, tailored to the duties of a fire safety officer.

AreasStructural, operational, installation-based and organisational fire protection, from compartments and escape routes through fire alarm systems and sprinklers to fire safety regulations.
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.
ResultOne sealed, numbered version per appointment, with sealing timestamp and inspector. The chain of previous versions stays readable. Open defects with action and deadline carry over to the next inspection. Report export is planned.

The key capabilities for your fire safety inspections

An unbroken chain per property · open defects across inspections · your own checklists · data in Germany.

An unbroken chain per property

The inspection series carries the interval, and each appointment produces a sealed, numbered version with sealing timestamp and inspector. Rework creates the next version, and every previous version stays readable. What applied at which appointment is on record.

  1. 07:42Inspection started, area hospital corridor 3rd floor
  2. 07:58Note on the defect: closing function of fire door T30
  3. 08:15Photo for the defect
  4. 08:33Action with responsible person and deadline
  5. 09:05Sealed, version 1

Open defects across inspections

An open defect carries over with its action to the next inspection, with the date it was 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 it. You decide again: open or resolved.

Your own checklists, versioned

You maintain your checklists yourself, continuously versioned, with the source address on the check item. Special-construction requirements such as KhBauR, MVStättVO, MIndBauRL and MHHR go in as their own checklist. 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. Sealed inspections and all their previous versions stay readable.

  • Data in Germany
  • DPA per Art. 28 GDPR

Frequently asked questions from fire 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, numbered version. There is no classification of findings and no scoring scale.

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. Inspection records typically 10 years, evacuation drill protocols at least 10 years, the fire safety concept and the fire prevention inspection report for the lifetime of the building. 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.

Yes. You maintain your checklists yourself, continuously versioned, including for special-construction requirements such as KhBauR, MVStättVO, MIndBauRL and MHHR. Every check item can carry source addresses. Adding one to an inspection copies that version, so later edits leave running and sealed inspections untouched. 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 property. 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.

Which version applies to you depends on the federal state. The revision is being adopted inconsistently. In Begehung.pro you maintain the checklists yourself. Every checklist carries versions with the states draft, in use and superseded; the history shows the validity period and the usage count per version. A new version applies to new inspections only, while ongoing and sealed ones keep their copy. That way you keep the transitional version and the new version in parallel and decide per site when to switch.

Data in Germany, all processing in the EU, technical measures oriented towards BSI C5. For sites that fall under NIS 2 or the KRITIS umbrella act, you work together with your IT security officer. Begehung.pro keeps the fire safety inspections available as sealed versions.

Currently SaaS, with inspection data stored in databases in Frankfurt am Main; all processing takes place in the EU. The subprocessor list shows which service providers are involved. For sites under KRITIS or in hospitals we discuss your requirements in the demo.

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 fire safety inspections out of Word.

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

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