Validation rules engine

Validation rules
for gas inspections

Every report is checked against your inspection body’s and each distributor’s rules when the inspector closes it in the app. If something doesn’t add up, the inspector sees what to fix while still on site, not days later.

The engine flags and the person decides.

See examples Configure them by chatting

What a rule looks like

Start time before end time

Checks: Start time and End time
Blocks when: The start is equal to or later than the end
Message to the inspector: “The start time must be earlier than the end time.”
Applies to: Periodic inspection forms

Start 9:00 · end 9:45 Passes
Start 9:45 · end 9:00 Blocks

What a validation rule is

A condition on the report data that your inspection body defines. It’s fixed: the same inspection always gives the same result. It runs when the rule is active and linked to the form.

What it checks

The form fields, its tables, the photos and visit data such as the distributor or the fee.
When it blocks

The condition that must not hold for the report to be sent. It can apply only to certain distributors.
What the inspector sees

A clear message, with the values they entered, so they know what to fix right away.

What it can check

Fields

Required fields, value ranges, option lists and data formats.
Across fields

“If this was marked, then that,” such as a result consistent with the checklist.
Tables

Complete columns, totals, number of rows, the appliance census and calculations cross-checked between tables.
Times

Start before end and a minimum or maximum visit duration.
Photos

Capture date and time against the visit’s date and times.
Visit data

The distributor and the inspection fee, for rules that apply only to some.

Configuration examples

Rules inspection bodies use today, with the distributors’ names changed. Each with its configuration and its test cases.

Times The start time comes before the end time The start time is equal to or later than the end time. See the rule → Times The visit lasts at least the minimum time The visit lasts 20 minutes or less. Your inspection body sets the minimum; in this example, 20. See the rule → Photos The photos were taken on the day of the visit Any photo has a date different from the visit date. See the rule → Result consistency A compliant report can’t have failed items The result is Compliant and some item is marked Fails, NC, Critical or Non-critical. See the rule → Distributors The meter serial on the bill matches the actual meter The visit is for Distributor A or B, the bill was recorded and the two serials don’t match. See the rule → Tables Exposed piping has length, diameter and type Only exposed piping is marked and some section lacks length, diameter or type. See the rule → Calculations The appliances’ power adds up The appliances’ total power doesn’t match the rooms’. It doesn’t apply when the installation is a main line. See the rule → Distributors The inspection fee is the one agreed with each distributor The visit is for Distributor A, B or C and the fee is not 90,000 or is empty. See the rule → Appliance census The census code follows each distributor’s format A code doesn’t have the distributor’s format: 4 characters for A, 3 for B, with a valid type in its position. Special codes for planned points are accepted. It doesn’t apply on a main line. See the rule → Appliance census The census type matches the flue (D.E.P.C.) column The code’s type is B, C or D and the D.E.P.C. column isn’t Yes, or the type is another one and the column isn’t No. It doesn’t apply on a main line. See the rule → Appliance census Planned points in the census are marked as planned A special code (99, 98, 9090 or 9080) isn’t marked Planned, or a regular code isn’t marked Installed. Rows without an appliance aren’t checked. See the rule → Appliance census Every appliance is in a registered room A room in the appliances table doesn’t exist in the ventilation table, or a ventilation room has no appliance. It doesn’t apply on a main line. See the rule →

Configure them by chatting

With the RETGAS connector, your assistant (Claude) creates, tests, adjusts and activates rules from what you write. You don’t have to write the technical condition.

Configure · Create Create a validation rule by chatting «For Distributor A, B and C I want the inspection fee to always be 90,000. Prepare the rule and test it before saving it.» From a sentence to a rule, no ticket needed See the case → Configure · Understand Why is the inspector getting this message? «The inspector gets the message “The start time must match the capture time of the first photo” on the periodic inspection form. Why, and what do they need to fix?» Which rule blocks and what to fix, in words See the case → Configure · Measure Which rules block the most reports? «Which rules blocked the most reports in the last 30 days, and which inspectors?» Where to train, with data from the engine See the case → Configure · Adjust Adjust a rule and go back to the previous version «Change the inspection fee rule: for Distributor B it’s now 95,000. Test it before saving.» Changes with history and rollback See the case →

Available in Claude for anyone with the rules permissions in RETGAS who ticks the rules box when connecting. ChatGPT coming soon. More about the connector

Safe changes, from the assistant too

No rule reaches the field without you having seen it work.

Tested before saving

Every new or adjusted rule is simulated with at least one case that passes and one that blocks. If something fails, it isn’t saved.
It starts switched off

It’s created inactive and unlinked. Linking and activating are separate steps.
It asks for your confirmation

The assistant sums up the change in words and waits for your go-ahead before any write.
Not deleted from the assistant

From Claude you create, adjust, activate or pause. Deleting is still done on the web.
Every version is kept

The history shows the changes and you can go back to a previous version.
Your permissions, your organization

Each person only does what their role allows in RETGAS, and only in their inspection body.