Inspection protocol: defects only when defective
A result of “defective” reveals defect description, photo, deadline and owner. With “OK” the protocol stays short — evaluated per circuit, room or device.
Logic in the protocol
Neu
Control your protocols intelligently with logic and conditions
A result of “defective” reveals defect description, photo and deadline. A device type brings its own checkpoints. A category decides which pages exist at all. This is not a yes/no gimmick but logic across blocks, levels, page breaks and individual tokens — while filling internally and as an embedded form on your website alike. And you do not have to click it together yourself: the Hero AI Assistant builds template and rules from your description, and via MCP you hand a Hero Agent a complex inspection protocol from ChatGPT, Claude or Cursor — and it gets built.
Only what matters
Shorter forms, fewer mistakes while filling.
1 template
instead of one variant per device, system or job type.
PDF fits
No “n/a”, no empty tables in the record.
Describing is enough
Hero AI Assistant and Hero Agent build template and logic — via MCP from ChatGPT, too.
In the editor
A rule that reads like a sentence.
“Show this block when result equals defective.” Field, comparison, value — built by clicking, with search in the field picker, a “Conditional” chip on the block and auto-repair when a source field is missing.
- Several rules with “all” / “at least one”
- Preview with and without conditions
- Plain-language description in DE and EN
While filling
The technician only sees what belongs to their answer.
Fields appear and disappear live — on the phone, offline, per instance in recurring levels. A hidden required field never blocks, hidden answers are discarded on submit.
As a form on your website
Requests that qualify themselves.
Quote request, fault report, application: the embedded form asks step by step only what fits the previous answer. The submission lands as a card on the board — complete, without follow-up questions.
- Same evaluation as internally, no second form tool
- Guests cannot overwrite hidden or prefilled fields
Built by AI
You describe the protocol. The AI builds it — with logic.
From your description the Hero AI Assistant creates blocks, recurring levels and conditions. Via MCP you hand the same requirement from ChatGPT, Claude or Cursor to a Hero Agent — including a complex standards-based inspection protocol that used to take an afternoon of clicking. The agent knows layout and rules, you review the result.
- Hero AI Assistant: template and conditions from sentences
- Hero Agent via MCP: complex protocols from ChatGPT, Claude or Cursor
- Fill-in assistant explains why a field is currently hidden
In the PDF
A document that fits the case.
Hidden blocks and tokens are absent from the PDF and the confirmation email. No “n/a”, no empty tables — the record reads as if written for exactly this inspection.
Where it fits
Use cases you will recognise
Same idea, different trades: one level, as many instances as the job needs.
Maintenance: checkpoints per device type
Heat pump, air conditioner or ventilation — the selection brings its own checkpoints and measurement fields. One maintenance template instead of one per device.
Quote request on the website
“Wallbox” asks for charging power and parking space, “PV system” for roof area and orientation, “other” for free text. The customer answers five questions instead of twenty — the request is still complete.
Fault report via QR code
Category “water” shows “where does it leak?” and photo, “electricity” shows “which area is affected?”, “emergency” shows the callback number first. Tenants and users report without login — every report becomes a card.
Application form on the careers page
Driving licence “yes” asks for the classes, “apprenticeship completed” for trade and year, “career changer” for previous roles. The application lands complete as a card in the applicant inbox.
Acceptance and handover
“Acceptance with reservations” reveals the open-items table and the follow-up date; “without reservations” leads straight to the signature. A page break appears only when the table does.
How it works
In just a few steps
- 1
Describe the protocol including its logic to the Hero AI Assistant (“defect fields only when defective, checkpoints per device type”) — or hand the requirement to a Hero Agent via MCP from ChatGPT, Claude or Cursor. Blocks, levels and conditions get created.
- 2
Fine-tune by hand: open the block settings in the protocol editor and adjust or add rules under “Condition”.
- 3
Triggers are checkbox, choice, dropdown, text, number, signature or media; you combine several rules with “all” / “at least one”.
- 4
The block now carries the “Conditional” chip. With “Show conditions” you can view the whole document at any time.
- 5
While filling, in the preview and in shared links, fields appear and disappear live. Hidden required fields never block, hidden answers are discarded on submit.
- 6
PDF and confirmation email contain only the visible blocks.
Your digital team member takes over
Have complex protocols built — by the Hero AI Assistant or via MCP
You describe what the protocol has to do — the Hero AI Assistant creates blocks, levels and conditions in the editor. Through the MCP connection you hand the same requirement from ChatGPT, Claude, Cursor or your own AI to a Hero Agent: it knows layout and rules, builds the template and later fills it in line with the rules — skipping hidden fields.
Discover Hero AgentHero & Enterprise plans · one seat per agent
- “Standards-based inspection protocol, one level per circuit, defect fields only when defective” → built
- Handed to the Hero Agent via MCP from ChatGPT, Claude or Cursor
- Agents fill protocols in line with the rules — from photo, CSV or report
At a glance
Features at a glance
Everything this feature brings — summed up.
- Triggers: checkbox, choice, dropdown, image choice, text, number, signature, media
- Targets: blocks, media, page breaks, whole levels — and individual tokens in text and table blocks
- Several rules per block, combined with “all” or “at least one”
- Evaluated per instance in recurring levels
- Applies while filling, in preview, in shared links and embedded forms
- PDF and confirmation email with visible blocks only
- A deleted source field pauses the rule and is flagged in the editor — nothing disappears silently
- Hero AI Assistant builds template and conditions from your description
- Hero Agent accepts complex protocols via MCP — from ChatGPT, Claude or Cursor — and builds them
Trusted by trades
Trades across the field rely on ProtocolHero every day.
Als ich das erste Mal von ProtocolHero gehört habe, war ich von der ersten Minute an von der Vision begeistert – und bin heute stolz, dass ich mir das Produkt sofort geholt habe, als allererster Kunde von ProtocolHero. Ich bin überzeugt: Ein Produkt kann nur wachsen, wenn wir Betriebe uns gegenseitig unterstützen – nur so lässt sich der Zeitaufwand beim Kunden wirklich optimieren. Anfangs war für mich vieles neu, aber Geschäftsführer Steven hat mich stets freundlich beraten und ist sofort auf meine eigenen Wünsche eingegangen. Deshalb setzen wir ProtocolHero künftig auch für unsere Photovoltaikanlagen, Wärmepumpen und weitere Bereiche ein. Besten Dank an das ganze Team – und auf eine gute Weiterentwicklung!
Robin Twietmeyer
Twietmeyer Energietechnik
FAQ
Frequently asked questions
- Does conditional logic work in forms embedded on my website?
- Yes. The same evaluation runs while filling, in preview, in shared fill-in links and in forms you embed on your website. A quote request, for example, only asks for wallbox power when “wallbox” was selected.
- What happens to required fields in a hidden block?
- They do not block submission. A field is only required while it is visible. Answers in hidden blocks are discarded on submit so nothing contradictory ends up in the record.
- Do hidden fields appear in the PDF?
- No. PDF and confirmation email contain only the visible blocks and tokens — including long documents rendered in sections.
- Can I combine several conditions?
- Yes. You add several rules and combine them with “all must match” or “at least one must match”. The plain-language description above shows what the combination means.
- What about recurring levels such as circuits or rooms?
- Each instance evaluates only its own answers. A defect in circuit 3 reveals the defect fields in circuit 3 only.
- What happens if I delete the trigger field?
- The condition is not removed silently; it is paused and flagged in the editor as “check condition”. You decide whether to pick a new source field or remove the rule.
- Do I have to click the rules together myself?
- No. From a description such as “show the defect field only when defective, one level per circuit, checkpoints per device type” the Hero AI Assistant builds the blocks, levels and conditions in the editor. While filling, the assistant explains on request why a field is currently hidden.
- Can I have a complete protocol built from ChatGPT or Claude?
- Yes. Through the MCP connection you hand a Hero Agent the requirement from ChatGPT, Claude, Cursor or your own AI — including a complex inspection protocol with levels and conditions. The agent knows the layout and the rules, builds the template, and you review the result in the editor.
Goes well with
Discover more features
Vorlagen
Bewährte Vorlagen für viele Gewerke – inklusive Belege wie Reisekosten und Bewirtung. Nutze sie direkt oder passe sie mit eigenen Feldern an. Kein Aufbau von Null, kein Word-Chaos.
Learn moreRecurring blocks
Statt zwanzigmal dasselbe Formular: Du legst eine Ebene an und fügst beim Ausfüllen Instanzen hinzu – Stromkreis, Raum, Gerät, Mangel.
Learn moreTry Conditional logic
Start for free or book an intro call with a live walkthrough.