Check a project before you send it AIAI feature

AI planning validation reads a finished plan the way an experienced colleague would review it before it goes out: against the rules your company actually works to. It checks every variant on the project, explains what it found in words rather than error codes, and suggests what to change.

It is a review step for your own team: it reports what it finds, leaves the plan exactly as you built it, and stays internal.

Before you start

• Your workspace needs validation rules. Reonic ships none deliberately — the checks are your company's rules, not generic ones, so someone has to write them first. If validation opens and says no rules are configured, that's the reason. Your Reonic account manager sets them up with you.
• Finish the plan first. Validation reads the plan as it stands, including the roof layout and the components on each variant. Running it on a half-finished variant produces findings about the unfinished parts.
• You need an Editor role or higher. Validation runs in the Portal; there is no mobile version.
• Residential and commercial are configured separately. Rules written for one don't apply to the other, so a commercial project can come back with nothing to check even though your residential rules are in place.

Run the check

1. Open the project and finish planning the variants you want checked.
2. Click AI planning validation.
3. Wait for the run. Every variant is checked in the same pass — typically a few seconds, occasionally longer when the service is busy.
4. The results open on their own when the run finishes.

The button is unavailable while a check is already running on the project, and while no rules are configured.

Read the results

The top of the results panel counts everything found across all variants, in four groups:

• Error — a rule was violated in a way your company treats as a real problem.
• Warning — a soft signal worth a look, not a blocker.
• Pass — the rule was checked and satisfied.
• Not relevant — the rule didn't apply to this plan, for example a wallbox rule on a project with no wallbox.

Below the counts, each variant is its own collapsible section with its own tallies. The variant you had selected sits first and opens automatically.

Work errors first, then warnings. Each finding gives you the rule's name, an explanation of what was found, and a suggested change.

Fix and re-run

1. Go back to the planning view and change the variant.
2. Click AI planning validation again.

The new run replaces the previous one. Only the latest result is kept, so note anything you want to remember before re-running.

Things to know

• Validation is a review, and you make the call. It gives your team the findings before the offer goes out; what to change, and what to accept, stays a human decision.
• Nothing is changed for you. Validation reads the plan and reports. It never edits a variant, adjusts a component or fixes anything automatically.
• The customer never sees it. There's no validated badge on the offer PDF and nothing surfaces in the customer portal.
• Only the most recent run is kept. There's no history of past validations, so a re-run overwrites what came before.
• If the run fails, no variant gets results. A failed run is all-or-nothing rather than partial. Wait a moment and run it again; a repeated failure is worth reporting to your account manager.
• Don't run two checks on one project at once. Starting a second run while the first is in flight will overwrite it. If a run seems stuck for more than a couple of minutes, refresh the page and start again.
• Each variant is judged on its own. Validation doesn't compare variants against each other or tell you which to recommend.
• Rules are read as written. Vague rule text produces vague findings, which is why rules that state numbers and units work better than ones that say a system should be appropriately sized.

Last updated on September 9, 2026